Nut upsuser - Nov 2007 - trouble with Cyber Power System CPS RS232 USB BRIDGE for UPS

Hi

Recently i bought a MicroDoWell BP50, and with it followed a USB 2  
serial
converter. When i plug it into my 2.6.19 kernel, dmesg shows

hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB  
BRIDGE for UPS] on usb-0000:00:04.2-2
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver


So, i figured i should use usbhid-ups, /etc/nut/ups.conf
[switch]
   driver = usbhid-ups
   port = auto

and then i ran the command
	 /lib/nut/usbhid-ups -DDDDDDDDDDDDDDDD -a switch


root at dksrv003:/etc/nut# /lib/nut/usbhid-ups -DDDDDDDDDDDDDDDD -a switch
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30  
(2.2.0-)

debug level is '16'
Checking device (0764/0005) (001/002)
- VendorID: 0764
- ProductID: 0005
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device matches
Unable to get HID descriptor (error sending control message:  
Connection timed out)
i=0, extra[i]=09, extra[i+1]=21
HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 5a 00
HID descriptor retrieved (Reportlen = 90)
Unable to get Report descriptor (-110): Connection timed out
Checking device (0000/0000) (001/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not match - skipping
No appropriate HID device found
No matching HID UPS found
root at dksrv003:/etc/nut#


The MicroDoWell BP50 only has a serial out, but i am using the serial  
cable that came
with the UPS. Unfortunately it is not very long, so having a USB  
extender cable i connected
the serial cable to the UPS and the USB2serial converter and then the  
extender cable and
into my server.

> Recently i bought a MicroDoWell BP50, and with it followed a USB 2
> serial converter. When i plug it into my 2.6.19 kernel, dmesg shows
>
> hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB
> BRIDGE for UPS] on usb-0000:00:04.2-2
> usbcore: registered new interface driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
That's a little confusing. Apparently, Cyber Power System designed this
device to be used particularly for UPS use. However, all it should do is
provide a serial port, so that you can connect the 'powerpanel' or
'cpsups' driver to it.
> So, i figured i should use usbhid-ups, /etc/nut/ups.conf
> [switch]
>    driver = usbhid-ups
>    port = auto
I understand what made you think this is the correct driver, but
unfortunately it isn't. Worse still, CPS also uses this same VID:PID for
their USB HID UPS'es, so we have really no means to exclude this in the
'apc-hid' subdriver.
> The MicroDoWell BP50 only has a serial out, but i am using the serial
> cable that came with the UPS. Unfortunately it is not very long, so
> having a USB extender cable i connected the serial cable to the UPS and
> the USB2serial converter and then the extender cable and into my server.
Your serial-to-USB converter should provide a virtual COM port, something
like /dev/ttyUSB0 ot something like that. This port should be configured
in 'ups.conf' with either the 'powerpanel' or 'cpsups'
driver. If no
virtual COM port is created upon plugging in the serial-to-USB converter,
it is most likely not recognized by your kernel. In that case, the only
thing we can do for the moment is to suggest to try a different one that
is supported by your kernel.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

On 22/11/2007, at 14.55, Arjen de Korte wrote:
>
>> Recently i bought a MicroDoWell BP50, and with it followed a USB 2
>> serial converter. When i plug it into my 2.6.19 kernel, dmesg shows
>>
>> hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB
>> BRIDGE for UPS] on usb-0000:00:04.2-2
>> usbcore: registered new interface driver usbhid
>> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
>
> That's a little confusing. Apparently, Cyber Power System designed  
> this
> device to be used particularly for UPS use. However, all it should  
> do is
> provide a serial port, so that you can connect the 'powerpanel' or
> 'cpsups' driver to it.
i was thinking it new how to convert a serial port to a USB hid UPS  
protocol?

>> So, i figured i should use usbhid-ups, /etc/nut/ups.conf
>> [switch]
>>   driver = usbhid-ups
>>   port = auto
>
> I understand what made you think this is the correct driver, but
> unfortunately it isn't. Worse still, CPS also uses this same VID:PID  
> for
> their USB HID UPS'es, so we have really no means to exclude this in  
> the
> 'apc-hid' subdriver.
>
>> The MicroDoWell BP50 only has a serial out, but i am using the serial
>> cable that came with the UPS. Unfortunately it is not very long, so
>> having a USB extender cable i connected the serial cable to the UPS  
>> and
>> the USB2serial converter and then the extender cable and into my  
>> server.
>
> Your serial-to-USB converter should provide a virtual COM port,  
> something
> like /dev/ttyUSB0 ot something like that. This port should be  
> configured
> in 'ups.conf' with either the 'powerpanel' or
'cpsups' driver. If no
> virtual COM port is created upon plugging in the serial-to-USB  
> converter,
> it is most likely not recognized by your kernel. In that case, the  
> only
> thing we can do for the moment is to suggest to try a different one  
> that
> is supported by your kernel.
I tried that part, but i can not get it to work. I tried ttyUSB0, 1, 2  
and 3. neither worked.

i will try to find another usb2serial converter


JonB

On 22/11/2007, at 15.15, Jon Bendtsen wrote:
> On 22/11/2007, at 14.55, Arjen de Korte wrote:
>
>>
>>> Recently i bought a MicroDoWell BP50, and with it followed a USB 2
>>> serial converter. When i plug it into my 2.6.19 kernel, dmesg shows
I gave up on using the USB converter and used a regular serial
cable, it works fine using both the powerpanel and the cpsups
driver. I prefer the powerpanel because the name is slightly nicer
in the cgi.



JonB

On 26/11/2007, at 12.06, Arjen de Korte wrote:
> Jon Bendtsen wrote:
>
>> I gave up on using the USB converter and used a regular serial
>> cable, it works fine using both the powerpanel and the cpsups
>> driver. I prefer the powerpanel because the name is slightly nicer
>> in the cgi.
>
> Could you post the output of 'upsc <upsname>' here? We're
working on
> extending the support for the powerpanel driver, but in order to do
> that, we need some information on what is reported by devices that are
> supported already. Thanks in advance.


powerpanel driver:
---------------------------------------------
root at dksrv003:~# upsc bp500
battery.capacity: 7
battery.charge: 100.0
battery.charge.low: 20
battery.packs: 1
battery.voltage.nominal: 12
driver.name: powerpanel
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.2.0-
driver.version.internal: 0.22
input.frequency: 49.9
input.frequency.high: 63
input.frequency.low: 47
input.transfer.high: 272
input.transfer.low: 180
input.voltage: 234
input.voltage.nominal: 230
output.voltage: 234
ups.firmware: 1.704
ups.load: 80
ups.mfr: CYBER POWER
ups.model: 500VA
ups.power.nominal: 500
ups.realpower.nominal: 330
ups.serial: 000000000000
ups.status: OL
ups.temperature: 32


cpsups driver:
--------------------------------------------
root at dksrv003:/etc/nut# upsc bp500
battery.charge: 100.0
battery.runtime:  3:58
driver.name: cpsups
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.2.0-
driver.version.internal: .05
input.frequency: 50
input.voltage: 234
output.voltage: 234
ups.load: 82
ups.mfr: CyberPower
ups.model: OP500TE 1.704
ups.power.nominal: 500
ups.runtime: 16.5
ups.status: OL
ups.temperature: 32