[Nut-upsuser] Unsupported UPS using megatec_usb

Jamie Thompson lists.nut-upsuser at jamie-thompson.co.uk
Tue May 6 22:29:11 UTC 2008


Alexander I. Gordeev wrote:
> I think it should be 'battvolts = x:13.0' from what I've seen from your
> previous mails (you'd better check this). This was a reported real voltage,
> when the UPS (I guess) was fully charged. You can get the current voltage
> from the upsc output:
> 
> battery.voltage: xxxx
> ....
> 
> or from driver debug output:
> 
> Asking for UPS status [Q1]...
> get_data_krauler: index [03], prefix [(]
> Q1 => OK [(234.0 165.0 234.0 000 50.0 13.0 00.0 00001010]

It went up to 12.8v just now and seemed to stay there, but 13 is a good number.

> Btw, please try the complete setup (driver + upsd). What does upsc print?
> Also I think you'll have to add the 'ignoreoff' parameter to ups.conf to
> make ups.status correct (if it is not).

Alas, a new problem.

On the server, I could use upscmd fine, but here on my test bench I can't (syslog):
> May  6 22:44:38 tester upsd[3526]: /etc/nut/upsd.conf is world readable
> May  6 22:44:38 tester upsd[3526]: listen_add: added 0.0.0.0:3493
> May  6 22:44:38 tester upsd[3526]: setuptcp: try to bind to 0.0.0.0 port 3493
> May  6 22:44:38 tester upsd[3526]: listening on 0.0.0.0 port 3493
> May  6 22:44:38 tester upsd[3526]: Can't connect to UPS [plexus] (megatec_usb-plexus): No such file or directory
> May  6 22:44:38 tester upsd[3526]: /etc/nut/upsd.users is world readable
> May  6 22:44:40 tester upsd[3526]: sstate_dead: connection to driver socket for UPS [plexus] lost
> May  6 22:44:46 tester last message repeated 4 times
> May  6 22:44:46 tester upsd[3526]: Signal 2: exiting
> May  6 22:45:19 tester kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd megatec_usb rqt 128 rq 6 len 255 ret -110
> May  6 22:45:20 tester kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd megatec_usb rqt 128 rq 6 len 255 ret -110

...attempting to start the driver manually fails too:
> tester:/usr/local/ups# ./bin/upsdrvctl start
> Network UPS Tools - UPS driver controller 2.2.2-pre3
> Network UPS Tools 2.2.2-pre3 - Megatec protocol driver 1.5.13 [megatec_usb]
> Carlos Rodrigues (c) 2003-2008
> 
> Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
> Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007
> 
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> Successfully reconnected
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> Successfully reconnected
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> Successfully reconnected
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> Successfully reconnected
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> Successfully reconnected
> Megatec protocol UPS not detected.
> Driver failed to start (exit status=1)

...and as you'd expect:
> upscmd -l plexus
> Error: Driver not connected

Damn thing is sitting here beeping at me while I wait for it to discharge and I'm just trying to get upscmd working so I can turn the beep off :(
It also seems that the only way I can communicate with it is via megatec_usb -a plexus -u root

...anything else and I get:
> tester:/usr/local/ups# ./bin/megatec_usb -a plexus -DDDD -u nut
> Network UPS Tools 2.2.2-pre3 - Megatec protocol driver 1.5.13 [megatec_usb]
> Carlos Rodrigues (c) 2003-2008
> 
> Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
> Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007
> 
> debug level is '4'
> Checking device (0001/0000) (001/003)
> - VendorID: 0001
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 001
> Trying to match device
> Device matches
> failed to claim USB device, trying 2 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> failed to claim USB device, trying 1 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> failed to claim USB device, trying 0 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> Starting UPS detection process...
> Asking for UPS status [Q1]...
> set_data_krauler: index [03]
> - Unable to fetch string 3
> set_data_krauler: connection failure
> ser_send_pace: Device detached? (error -1: error sending control message: Operation not permitted)
> ==================================================
> = device has been disconnected, try to reconnect =
> ==================================================
> Checking device (0001/0000) (001/003)
...and so on.

I've tried side-stepping the issue by chown'ing and chmod'ing /dev/usb/hiddev0 to nut:nut & 777, to no avail. The above logs are from the binaries I 
built, but I get the same from the distro binaries.

- Jamie

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080506/abe422a4/attachment.pgp 


More information about the Nut-upsuser mailing list