[Nut-upsdev] Ovislink

[Charles Lepple]

On Jul 10, 2015, at 9:02 AM, paul at paulcarmichael.org wrote:

> On 10/07/15 14:30, paul at paulcarmichael.org wrote:
>> 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:
>>> 
>>> http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009527.html
>>> 
>>> What does 'lsusb' 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

# define EILSEQ 84      /* Illegal byte sequence.  */

I forget what this error means in the context of USB, but if it happens a lot, I would be concerned about relying on this UPS. (The kernel basically gave up on the first attempt to configure it.)

> [    4.296036] usb 4-2: new low-speed USB device number 4 using uhci_hcd
> [    4.481018] usb 4-2: New USB device found, idVendor=0001, idProduct=0000
> [    4.481024] usb 4-2: New USB device strings: Mfr=1, Product=1, SerialNumber=1
> [    4.481027] usb 4-2: Product: ATCL FOR UPS
> [    4.481030] usb 4-2: Manufacturer: ATCL FOR UPS
> [    4.481033] usb 4-2: SerialNumber: ATCL FOR UPS

hyouko mentioned the following in a thread in April:

"It could work with drivers 'nutdrv_atcl_usb' (available since NUT
version 2.7.2) or with 'nutdrv_qx' (since 2.7.3)."

Unfortunately, I don't think there is a way to tell which driver is needed, since the idVendor and idProduct numbers are the same for both hardware variants.