Hi!
I don't know how I missed it before, but "bestups" seems to
implement
mostly the same protocol as megatec. Is anybody out there using this
driver willing to try "megatec" to see if it works?
AFAIK, the only difference seems to be the command that gets the UPS
identification data ("I" on "megatec", "ID" on
"bestups"), but that's
not mandatory in "megatec" (and I'm willing to implement the other
command, provided there's someone out there to test it).
And there's "energizerups"... How feasible is it to have
"megatec_usb"
obsolete this driver?
--
Carlos Rodrigues
On 7/6/07, Carlos Rodrigues <carlos.efr at mail.telepac.pt> wrote:> Hi! > > I don't know how I missed it before, but "bestups" seems to implement > mostly the same protocol as megatec. Is anybody out there using this > driver willing to try "megatec" to see if it works?I have an old Patriot Pro II UPS that uses the bestups driver. I might be able to try that later this weekend.> And there's "energizerups"... How feasible is it to have "megatec_usb" > obsolete this driver?Check the list archives - there was actually just some discussion about this with the energizerups driver author. If I recall correctly, testing is the issue. -- - Charles Lepple
On Fri, 6 Jul 2007 19:33:07 +0100 "Carlos Rodrigues" <carlos.efr at mail.telepac.pt> wrote:> And there's "energizerups"... How feasible is it to have "megatec_usb" > obsolete this driver?Hi Carlos, could you help me with a megatec_usb problem? If I use one of thesse options (krauler or agiler) it returns the following: sudo ../bin/megatec_usb -u root -a tsshara -DD Checking device (0483/0035) (001/003) - VendorID: 0483 - ProductID: 0035 - Manufacturer: STMicroelectronics - Product: ST7 RS232 USB BRIDGE - Serial Number: unknown - Bus: 001 Trying to match device Device matches Starting UPS detection process... Attempting to detect the UPS... Sending "Q1" command... Wrong answer to "Q1" command. Attempting to detect the UPS... Sending "Q1" command... Wrong answer to "Q1" command. Attempting to detect the UPS... Sending "Q1" command... Wrong answer to "Q1" command. Attempting to detect the UPS... Sending "Q1" command... Wrong answer to "Q1" command. Attempting to detect the UPS... Sending "Q1" command... Wrong answer to "Q1" command. 5 out of 5 detection attempts failed (minimum failures: 2). Megatec protocol UPS not detected. And then lsusb -v: HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 29 Report Descriptor: (length is 29) Item(Global): Usage Page, data= [ 0x80 0xff ] 65408 (null) Item(Local ): Usage, data= [ 0x00 ] 0 (null) Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Report Count, data= [ 0x08 ] 8 Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255 Item(Local ): Usage, data= [ 0x01 ] 1 (null) Item(Main ): Feature, data= [ 0x82 ] 130 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Volatile Bitfield Item(Local ): Usage, data= [ 0x01 ] 1 (null) Item(Main ): Input, data= [ 0x82 ] 130 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Volatile Bitfield Item(Local ): Usage, data= [ 0x02 ] 2 (null) Item(Main ): Output, data= [ 0x82 ] 130 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Volatile Bitfield Item(Main ): End Collection, data=none Endpoint Descriptor: *** Is possible to discover where's the problem? Thank you! --
On 7/6/07, Carlos Rodrigues <carlos.efr at mail.telepac.pt> wrote:> Hi! > > I don't know how I missed it before, but "bestups" seems to implement > mostly the same protocol as megatec. Is anybody out there using this > driver willing to try "megatec" to see if it works?I finally found the serial cable for my Patriot Pro II (it's not straight through), and I tried both bestups and megatec from 2.2.0 (essentially; it's branches/Testing from SVN). Output from bestups: battery.charge: 100.0 battery.voltage: 13.7 battery.voltage.nominal: 13.6 driver.name: bestups driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.0-1023:1024 driver.version.internal: 1.03 input.frequency: 60.0 input.voltage: 120.9 output.voltage: 120.9 ups.load: 000 ups.mfr: Best Power ups.model: Patriot Pro II 400 ups.status: OL ups.temperature: XX.X Output from megatec: battery.voltage: 13.70 driver.name: megatec driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.0-1023:1024 driver.version.internal: 1.5.4 input.frequency: 60.0 input.voltage: 119.9 input.voltage.fault: 119.9 input.voltage.maximum: 120.9 input.voltage.minimum: 119.9 output.voltage: 119.9 ups.beeper.status: disabled ups.delay.shutdown: 0 ups.delay.start: 2 ups.load: 0.0 ups.mfr: unknown ups.model: unknown ups.serial: unknown ups.status: OL BYPASS ups.temperature: 0.0 Besides the info from the ID command, the BYPASS bit is inverted on some Best Power products: http://boxster.ghz.cc/projects/nut/browser/trunk/drivers/bestups.c#L51 (Apparently this unit does not have a temperature sensor, as the verbatim string returned is "XX.X". The load is usually non-zero, but nothing is plugged in at the moment.) -- - Charles Lepple