Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
On 2/16/07, Arjen de Korte <[EMAIL PROTECTED]> wrote: Charles Lepple wrote: > Can you send the output of 'upsc [EMAIL PROTECTED]'? The '@localhost' part is optional for the version in the trunk. So upsc name-of-ups will behave the same as upsc [EMAIL PROTECTED] Might save you some typing... :-) Understood, but with all the people still using 2.0.4 and 2.0.5, that can get a little confusing. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
On 2/16/07, Forest Bond - Logic Supply <[EMAIL PROTECTED]> wrote: > The other errors look like they did not show up in the debug log > requested by Arjen - true? On line 428: Error reading L value: Unknown error 0 And on line 446: Error reading S value: Unknown error 0 oops, missed those. I thought you meant it did that consistently - if so, then the variables are not supported. But those are just every once in a while. (These occurred shortly after I unplugged the UPS to trigger activity.) yup, sounds like the UPS was just busy at the time. > I need to revise the polling timeouts for when the unit is offline, > but otherwise, it is probably working. (Some commands take several > tries to get through.) Hmm, I didn't let the test run for very long; I'm happy to perform some variation on that test, if you need different timing. Otherwise, what you just said doesn't mean much to me, so if you don't need anything else from me, just ignore this paragraph :). Note that most commands complete with "send_try 1" and "recv_try 1" - it just says that the driver didn't have to repeatedly write and read to get a response. Each "try" waits for a certain amount of time - that's the timeout. That's all I meant. We're trying to get quick results in the normal case, but recognize that sometimes, you just won't get an answer back at all (until you re-send the command). > Can you send the output of 'upsc [EMAIL PROTECTED]'? I don't actually have upsd up and running. It may be a few minutes for me to do that, at which point I'm happy to send the info you need. Is there some other command I can run to get what you're looking for without yet completing the full nut setup? Nope, no other way. But it's just an end-to-end sanity check to be sure that the numbers you see are in line with reality. If I had the time, I could work it out from the log, but that's error-prone (as you can see by the fact that I missed those two errors). -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
On Fri, Feb 16, 2007 at 11:03:50AM -0500, Charles Lepple wrote: > Can you send the output of 'upsc [EMAIL PROTECTED]'? Finally [EMAIL PROTECTED]:~# upsc [EMAIL PROTECTED] battery.charge: 100 battery.voltage: 13.69 battery.voltage.nominal: 24 driver.name: tripplite_usb driver.parameter.port: auto driver.version: 2.0.5 driver.version.internal: 0.7 input.voltage: 112.27 input.voltage.nominal: 120 output.voltage: 113.5 ups.debug.load_banks: 0 ups.delay.shutdown: 64 ups.firmware: F2211.A ups.firmware.aux: protocol 2001 ups.mfr: Tripp Lite ups.model: UPS ups.power.nominal: 1500 ups.status: OL Looks like everything is working great! Thanks! -Forest -- Forest Bond Computer Engineer Logic Supply, Inc. Phone: (802) 244-8302 Fax: (802) 244-7938 [EMAIL PROTECTED] www.logicsupply.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
Charles Lepple wrote: > Can you send the output of 'upsc [EMAIL PROTECTED]'? The '@localhost' part is optional for the version in the trunk. So upsc name-of-ups will behave the same as upsc [EMAIL PROTECTED] Might save you some typing... :-) Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
Hi, > The "Error reading Unit ID" is normal on this model, because it does > not appear to support that particular command. OK > The other errors look like they did not show up in the debug log > requested by Arjen - true? On line 428: Error reading L value: Unknown error 0 And on line 446: Error reading S value: Unknown error 0 (These occurred shortly after I unplugged the UPS to trigger activity.) > I need to revise the polling timeouts for when the unit is offline, > but otherwise, it is probably working. (Some commands take several > tries to get through.) Hmm, I didn't let the test run for very long; I'm happy to perform some variation on that test, if you need different timing. Otherwise, what you just said doesn't mean much to me, so if you don't need anything else from me, just ignore this paragraph :). > Can you send the output of 'upsc [EMAIL PROTECTED]'? I don't actually have upsd up and running. It may be a few minutes for me to do that, at which point I'm happy to send the info you need. Is there some other command I can run to get what you're looking for without yet completing the full nut setup? thanks, Forest -- Forest Bond Computer Engineer Logic Supply, Inc. Phone: (802) 244-8302 Fax: (802) 244-7938 [EMAIL PROTECTED] www.logicsupply.com On Fri, Feb 16, 2007 at 11:03:50AM -0500, Charles Lepple wrote: > On 2/16/07, Forest Bond - Logic Supply <[EMAIL PROTECTED]> wrote: > >Hi, > > > >I'm working with svn trunk rev 815, testing tripplite_usb with this model. > >I > >haven't gotten far in my testing, but thought I'd notify the list of this > >error > >message. Is this message of any consequence, and is it worthwhile for me > >to > >continue testing prior to resolving this? I am happy to help debug any > >driver > >issues, so please let me know if I can be of assistance. > > The "Error reading Unit ID" is normal on this model, because it does > not appear to support that particular command. > > The other errors look like they did not show up in the debug log > requested by Arjen - true? > > I need to revise the polling timeouts for when the unit is offline, > but otherwise, it is probably working. (Some commands take several > tries to get through.) > > Can you send the output of 'upsc [EMAIL PROTECTED]'? > > -- > - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
On 2/16/07, Forest Bond - Logic Supply <[EMAIL PROTECTED]> wrote: Hi, I'm working with svn trunk rev 815, testing tripplite_usb with this model. I haven't gotten far in my testing, but thought I'd notify the list of this error message. Is this message of any consequence, and is it worthwhile for me to continue testing prior to resolving this? I am happy to help debug any driver issues, so please let me know if I can be of assistance. The "Error reading Unit ID" is normal on this model, because it does not appear to support that particular command. The other errors look like they did not show up in the debug log requested by Arjen - true? I need to revise the polling timeouts for when the unit is offline, but otherwise, it is probably working. (Some commands take several tries to get through.) Can you send the output of 'upsc [EMAIL PROTECTED]'? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
On Fri, Feb 16, 2007 at 04:36:12PM +0100, Arjen de Korte wrote: > Running the driver in debug mode would be helpful, to see what goes wrong. I used the following command-line: ./tripplite_usb -u root -DD auto Attached is the log file. -Forest -- Forest Bond Computer Engineer Logic Supply, Inc. Phone: (802) 244-8302 Fax: (802) 244-7938 [EMAIL PROTECTED] www.logicsupply.com debug level is '6' Checking device (/) (007/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17-11-generic ehci_hcd - Product: EHCI Host Controller - Serial Number: :00:1d.7 - Bus: 007 Trying to match device Device does not match - skipping Checking device (/) (006/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17-11-generic ehci_hcd - Product: EHCI Host Controller - Serial Number: :00:1a.7 - Bus: 006 Trying to match device Device does not match - skipping Checking device (/) (003/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17-11-generic uhci_hcd - Product: UHCI Host Controller - Serial Number: :00:1d.0 - Bus: 003 Trying to match device Device does not match - skipping Checking device (/) (005/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17-11-generic uhci_hcd - Product: UHCI Host Controller - Serial Number: :00:1d.2 - Bus: 005 Trying to match device Device does not match - skipping Checking device (09AE/0001) (004/003) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: TRIPP LITE UPS - Serial Number: unknown - Bus: 004 Trying to match device Device matches HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 34 00 i=0, extra[i]=09, extra[i+1]=21 HID descriptor, method 2: (9 bytes) => 09 21 00 01 00 01 22 34 00 HID descriptor retrieved (Reportlen = 52) Report descriptor retrieved (Reportlen = 52) Found HID device Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.8 (2.1.0) Warning: This is an experimental driver. Some features may not function correctly. Report Descriptor size = 52 Report Descriptor: (52 bytes) => 06 a0 ff 09 01 a1 01 09 02 a1 00 06 a1 ff 09 03 09 04 15 80 25 7f 35 00 45 ff 75 08 95 08 81 02 09 05 09 06 15 80 25 7f 35 00 45 ff 75 08 95 08 91 02 c0 c0 Detected a UPS: TRIPP LITE/TRIPP LITE UPS send_cmd(msg_len=3, type='W') send_cmd: sending 3a 57 00 a8 0d 00 00 00 '.W..' send_cmd send_try 1 ok send_cmd: received 57 00 0d 00 00 00 00 00 'W...' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type=' send_cmd: sending 3a 00 ff 0d 00 00 00 00 '' send_cmd send_try 1 ok ok ok send_cmd send_try 2 ok send_cmd: received 00 20 01 58 58 58 58 0d '....' (OK) send_cmd: send_try = 2, recv_try = 1 Using OMNIVS 2001 protocol (2001) send_cmd(msg_len=2, type='S') send_cmd: sending 3a 53 ac 0d 00 00 00 00 '.S..' send_cmd send_try 1 ok send_cmd: received 53 31 34 30 30 00 30 0d 'S1400.0.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='P') send_cmd: sending 3a 50 af 0d 00 00 00 00 '.P..' send_cmd send_try 1 ok send_cmd: received 50 30 31 35 30 30 58 0d 'P01500X.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='F') send_cmd: sending 3a 46 b9 0d 00 00 00 00 '.F..' send_cmd send_try 1 ok send_cmd: received 46 32 32 31 31 20 41 0d 'F2211.A.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='V') send_cmd: sending 3a 56 a9 0d 00 00 00 00 '.V..' send_cmd send_try 1 ok send_cmd: received 56 31 30 34 30 58 58 0d 'V1040XX.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='U') send_cmd: sending 3a 55 aa 0d 00 00 00 00 '.U..' send_cmd send_try 1 ok ok ok send_cmd send_try 2 ok ok ok send_cmd send_try 3 ok ok ok send_cmd: received 56 31 30 34 30 58 58 0d 'V1040XX.' (bad) send_cmd: send_try = 3, recv_try = 3 Error reading Unit ID send_cmd(msg_len=2, type='S') send_cmd: sending 3a 53 ac 0d 00 00 00 00 '.S..' send_cmd send_try 1 ok send_cmd: received 53 31 34 30 30 00 30 0d 'S1400.0.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='B') send_cmd: sending 3a 42 bd 0d 00 00 00 00 '.B..' send_cmd send_try 1 ok send_cmd: received 42 30 44 30 31 45 44 0d 'B0D01ED.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='L') send_cmd: sending 3a 4c b3 0d 00 00 00 00 '.L..' send_cmd send_try 1 ok send_cmd: received 4c 30 30 45 45 58 58 0d 'L00EEXX.' (OK) send_cmd: send_try = 1, recv_try = 1 dstate_init: sock /var/state/ups/tripplite_usb-auto open on fd 5 send_cmd(msg_len=2, type='S') send_cmd: sending 3a 53 ac 0d 00 00 00 00 '.S..' send_cmd send_try 1 ok send_cmd: received 53 31 34 30 30 00 30 0d 'S1400.0.' (OK) send_cmd: send_try = 1, recv_try = 1 send_cmd(msg_len=2, type='B') send_cmd: sending 3a 42 bd 0d 00 00 00 00 '.B..' send_cmd send_try 1 ok send_cmd: received 42 30 44 33 31 45 44 0d 'B0D31ED.' (OK) send_cmd: send_try = 1, recv_try =
Re: [Nut-upsuser] Tripp Lite OMNIVS1500XL, tripplite_usb, Error reading {L, S, B} value
> I'm working with svn trunk rev 815, testing tripplite_usb with this model. > I > haven't gotten far in my testing, but thought I'd notify the list of this > error > message. Is this message of any consequence, and is it worthwhile for me > to > continue testing prior to resolving this? I am happy to help debug any > driver > issues, so please let me know if I can be of assistance. > > My platform is Ubuntu Edgy. Running the driver in debug mode would be helpful, to see what goes wrong. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
