On Nov 8, 2014, at 7:01 PM, hyouko at gmail.com wrote:> Since this UPS seems to be supported by UPSmart2000I, it could use a > serial-over-usb implementation of the megatec protocol.Dan, that is a good point - I had not considered it. I assume companies will copy bogus product IDs, but the use of the exact same USB string descriptor is odd. Did you have a chance to compare the rest of the lsusb output that Jani sent earlier in this thread? If it matches, then maybe the "ATCL FOR USB" string comes from some generic USB-to-serial adapter chip. -- Charles Lepple clepple at gmail
Come on, it started to be interesting!
On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at gmail.com> wrote:> Come on, it started to be interesting!Do you have one of these UPSes? If so, here was Dan's email about a branch to test:> If you still can't get it to work with nutdrv_atcl_usb, another > approach could be worth considering. > > Since this UPS seems to be supported by UPSmart2000I, it could use a > serial-over-usb implementation of the megatec protocol. > > A very first early version of the nutdrv_qx driver that should support > it can be found here: > https://github.com/zykh/nut/tree/nutdrv_qx-fuji > > (USB subdriver 'fuji'; but it shouldn't be necessary to set it, as the > driver is expected to automatically select it according to the > iManufacturer/iProduct strings) > > Note that the user I first developed it for abruptly stopped replying > to my mails (maybe his UPS went boom.. who knows?), so I don't really > know if it works or not: quite a lot of testing may be needed.-- Charles Lepple clepple at gmail
2014-11-09 16:29 GMT+01:00 Charles Lepple <clepple at gmail.com>:> On Nov 8, 2014, at 7:01 PM, hyouko at gmail.com wrote: > >> Since this UPS seems to be supported by UPSmart2000I, it could use a >> serial-over-usb implementation of the megatec protocol. > > Dan, that is a good point - I had not considered it. I assume companies will copy bogus product IDs, but the use of the exact same USB string descriptor is odd. > > Did you have a chance to compare the rest of the lsusb output that Jani sent earlier in this thread? If it matches, then maybe the "ATCL FOR USB" string comes from some generic USB-to-serial adapter chip.Ops, sorry - I didn't notice your reply before. I only have the following thing kernel: usb 8-2: new low-speed USB device number 2 using xhci_hcd kernel: usb 8-2: New USB device found, idVendor=0001, idProduct=0000 kernel: usb 8-2: New USB device strings: Mfr=1, Product=1, SerialNumber=1 kernel: usb 8-2: Product: ATCL FOR UPS kernel: usb 8-2: Manufacturer: ATCL FOR UPS kernel: usb 8-2: SerialNumber: ATCL FOR UPS kernel: usb 8-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes kernel: usb 8-2: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes kernel: hid-generic 0003:0001:0000.0002: hiddev0,hidraw1: USB HID v1.11 Device [ATCL FOR UPS ATCL FOR UPS] on usb-0000:03:00.0-2/input0 and the attached capture. -------------- next part -------------- A non-text attachment was scrubbed... Name: Gembird-UPS-PS-001.pcap.tar.gz Type: application/x-gzip Size: 16303 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150309/239457e2/attachment-0001.bin>
On Mar 9, 2015, at 11:28 AM, hyouko at gmail.com wrote:> 2014-11-09 16:29 GMT+01:00 Charles Lepple <clepple at gmail.com>: >> On Nov 8, 2014, at 7:01 PM, hyouko at gmail.com wrote: >> >>> Since this UPS seems to be supported by UPSmart2000I, it could use a >>> serial-over-usb implementation of the megatec protocol. >> >> Dan, that is a good point - I had not considered it. I assume companies will copy bogus product IDs, but the use of the exact same USB string descriptor is odd. >> >> Did you have a chance to compare the rest of the lsusb output that Jani sent earlier in this thread? If it matches, then maybe the "ATCL FOR USB" string comes from some generic USB-to-serial adapter chip. > > Ops, sorry - I didn't notice your reply before. > I only have the following thing > > kernel: usb 8-2: new low-speed USB device number 2 using xhci_hcd > kernel: usb 8-2: New USB device found, idVendor=0001, idProduct=0000 > kernel: usb 8-2: New USB device strings: Mfr=1, Product=1, SerialNumber=1 > kernel: usb 8-2: Product: ATCL FOR UPS > kernel: usb 8-2: Manufacturer: ATCL FOR UPS > kernel: usb 8-2: SerialNumber: ATCL FOR UPS > kernel: usb 8-2: ep 0x81 - rounding interval to 64 microframes, ep > desc says 80 microframes > kernel: usb 8-2: ep 0x2 - rounding interval to 64 microframes, ep desc > says 80 microframes > kernel: hid-generic 0003:0001:0000.0002: hiddev0,hidraw1: USB HID > v1.11 Device [ATCL FOR UPS ATCL FOR UPS] on usb-0000:03:00.0-2/input0 > > and the attached capture. > <Gembird-UPS-PS-001.pcap.tar.gz>Hmm, the enumeration seems to be missing. But it definitely seems to be more of a query-response protocol. The nutdrv_atcl_usb driver just reads interrupt packets, and doesn't send anything except to trigger a shutdown. Could be a generic USB-to-serial chip, then. Too bad there isn't more to distinguish the two UPS types. -- Charles Lepple clepple at gmail