search for: atcl

On 31/12/13 21:00, Charles Lepple wrote: > > There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. > > We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. > > There should also be a tarball here fairly soon: > > http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 > That...

.... If nothing else, it would be >> good to improve the diagnostics for that script. > > Here's the output (attached). I interrupted the process, but it > continues looping forever. > > Kind regards. > <debug.log> There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. There should also be a tarball here fairly soon: http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 -- Charles Lepple clepple at gmail

...USB disconnect, device number 112 [15144.484861] usb 4-2: new low-speed USB device number 113 using xhci_hcd [15144.506553] usb 4-2: New USB device found, idVendor=0001, idProduct=0000 [15144.506565] usb 4-2: New USB device strings: Mfr=1, Product=1, SerialNumber=1 [15144.506572] usb 4-2: Product: ATCL FOR UPS [15144.506578] usb 4-2: Manufacturer: ATCL FOR UPS [15144.506583] usb 4-2: SerialNumber: ATCL FOR UPS [15144.506859] usb 4-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [15144.506870] usb 4-2: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 micr...

...ting with shorter timeouts so that the battery doesn't get depleted? You would need to record the exact time when it shuts down, I think. Also, I quickly put together a man page: http://buildbot.networkupstools.org/~buildbot/cayman/docs/r17df4ff7b73aa76d01e168c6d4bc4f017193443a-116/man/nutdrv_atcl_usb.html Let me know if I should add anything. -- Charles Lepple clepple at gmail

...nas-27lfc kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2 Jan 25 12:46:37 nas-27lfc kernel: usb 1-1: configuration #1 chosen from 1 choice Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver hiddev Jan 25 12:46:39 nas-27lfc kernel: hiddev96: USB HID v1.11 Device [ATCL FOR UPS ATCL FOR UPS] on usb-0000:00: 17.0-1 Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver usbhid Jan 25 12:46:39 nas-27lfc kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Installed 2.4.1 using apt and installed in place of initial version Found various web docum...

...bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0001 Fry's Electronics idProduct 0x0000 bcdDevice 0.00 iManufacturer 1 ATCL FOR UPS iProduct 1 ATCL FOR UPS iSerial 1 ATCL FOR UPS bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0029 bNumInterfaces 1 bConfigurationValue 1...

...t 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 kerne...

On 10/07/15 04:26, Charles Lepple wrote: > On Jul 9, 2015, at 9:43 AM, paul at paulcarmichael.org wrote: > >> Is there currently a way of implementing NUT with an Ovislink Chrome 1500 UPS? > > Not sure. There was a thread in February talking about an Ovislink Chrome 1000, but I don't think we ever resolved what was causing the "Device busy" error: > >

...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

...1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0001 Fry's Electronics idProduct 0x0000 bcdDevice 0.00 iManufacturer 1 ATCL FOR UPS iProduct 1 ATCL FOR UPS iSerial 1 ATCL FOR UPS bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfigur...

Hi folks, Can?t seem to get this working with Frys Electronic / ATCL FOR UPS device connect direct via USB. This post suggests it should work: http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-April/009692.html OS Debian Jessie NUT 2.7.4-20 Driver: nutdrv_qx I?ve built nut from source and but get ?device not supported? Any ideas? Thanks. J

...o the UPS. There's no serial control port. "dmesg | grep usb" gives me: usb 1-3.1: new low speed USB device number 4 using ehci_hcd usb 1-3.1: New USB device found, idVendor=0001, idProduct=0000 usb 1-3.1: New USB device strings: Mfr=1, Product=1, SerialNumber=1 usb 1-3.1: Product: ATCL FOR UPS usb 1-3.1: Manufacturer: ATCL FOR UPS usb 1-3.1: SerialNumber: ATCL FOR UPS usb 1-3.1: configuration #1 chosen from 1 choice usb 1-3.1: can't set config #1, error -71 and lsusb gives: Bus 001 Device 016: ID 0001:0000 Fry's Electronics The idVendor and idProduct are horrid, alas. I...

Dear Steve, Thanks. Until today I could not install the nut in my raspberry. All installation good, but with my ups " Ovislink Chrome 1000VA" and "nutdrv_atcl_usb" driver, it inform me the following error details. I can startup nut but nutmon don't receive anything only (lost conection). My setup: root at pi1:/nut# lsusb Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hu...

[please use Reply-All to include the list - the list server does not modify the headers] > On Jan 11, 2017, at 1:49 PM, london jak wrote: > > Hi folks, > > Can?t seem to get this working with Frys Electronic / ATCL FOR UPS device connect direct via USB. > > > This post suggests it should work: > > http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-April/009692.html > > > OS Debian Jessie > > NUT 2.7.4-20 > > Driver: nutdrv_qx > > I?ve built nut from sou...

...' say? If the UPS has been unplugged since the logs were generated, replace "005/002" with the path suffix from this set of messages: 5.499162 Checking USB device [0001:0000] (005/002) 5.510156 - VendorID : 0001 5.510202 - ProductID : 0000 5.510209 - Manufacturer : ATCL FOR UPS 5.510219 - Product : ATCL FOR UPS 5.510225 - Serial Number: ATCL FOR UPS 5.510231 - Bus : 005 5.510237 Matched expected vendor='ATCL FOR UPS'. 5.512216 USB device [0001:0000] opened Depending on your distribution and how you installed NUT, some extra st...

...; list about this UPS? > > Bus 004 Device 003: ID 0001:0000 Fry's Electronics > > > And: [ 3.613024] usb 4-2: New USB device found, idVendor=0001, idProduct=0000 [ 3.613029] usb 4-2: New USB device strings: Mfr=1, Product=1, SerialNumber=1 [ 3.613033] usb 4-2: Product: ATCL FOR UPS [ 3.613036] usb 4-2: Manufacturer: ATCL FOR UPS [ 3.613039] usb 4-2: SerialNumber: ATCL FOR UPS [ 3.618015] usb 4-2: can't set config #1, error -84 [ 4.056102] usb 4-2: USB disconnect, device number 3 [ 4.296036] usb 4-2: new low-speed USB device number 4 using uhci_hcd [...

...l dependencies. > > Best regards, > Pere Rius > > > > -----Mensaje original----- > De: Charles Lepple [mailto:clepple at gmail.com] Enviado el: jueves, 17 de > julio de 2014 14:41 > Para: pere at riusnebot.com > CC: NUT List > Asunto: Re: About your driver NUTDRV_ATCL_USB(8) for install > > On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote: > >> Dear Charles Lepple, >> Sorry for my email intrusion. > > for next time: > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > >> I have an UPS called...

...I Host Controller 0.171502 - Serial Number: 0000:00:10.1 0.171507 - Bus: 003 0.171511 Trying to match device 0.171517 Device does not match - skipping 0.171524 Checking device (0001/0000) (002/005) 0.209728 - VendorID: 0001 0.209738 - ProductID: 0000 0.209743 - Manufacturer: ATCL FOR UPS 0.209747 - Product: ATCL FOR UPS 0.209752 - Serial Number: ATCL FOR UPS 0.209756 - Bus: 002 0.209761 Trying to match device 0.209802 Device matches 0.218750 Trying megatec protocol... 2.011770 flush: No error 2.015287 send: Q1 3.059778 read: No error 3.059984 b...

On Nov 1, 2014, at 1:30 AM, jani wrote: > Hi Charles, > > I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of 0001. It seems to be a re-badged unit manufactured by Guangdong East Power company, and besides the little brand stamp it looks identical to: > http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447 > > It came with a windows cd contai...

...cond time with debug level 4, just in case there were any extra hints in there. cheers, Jani On 1 November 2014 22:12, Charles Lepple <clepple at gmail.com> wrote: > On Nov 1, 2014, at 1:30 AM, jani wrote: > > Hi Charles, > > I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId > of 0001. It seems to be a re-badged unit manufactured by Guangdong East > Power company, and besides the little brand stamp it looks identical to: > http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447 > > It came with a windows cd...