search for: tripplite_3005

On Jul 3, 2014, at 11:29 AM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > input.voltage.maximum: 3341 This number is coincidentally what you would get by reading 0d 0d. I'll have to check the offsets. > input.voltage.minimum: 0 This one might actually be zero, before running the reset minmax command (which also takes a few seconds to be processed). The min/max

> Lots of good progress here! I tried to enable a few more commands for > your model. For instance, the "M" values seem to be min/max voltage, > so there is a "reset.input.minmax" command to use with upscmd. Also, > you can trigger a battery test with "test.battery.start". I assume the > work the same way as on Protocol 3003 :-) Hello Charles, The

...ty slow, so you can pass "--without-doc" to the ./configure script. You may also want to add "--with-drivers=tripplite_usb" so that it doesn't try to compile everything. -- - Charles Lepple -------------- next part -------------- A non-text attachment was scrubbed... Name: tripplite_3005.patch Type: text/x-patch Size: 3847 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140628/a7e23666/attachment.bin>

Hello Charles, Thanks for the feedback. I will try to answer some of these questions: > 09AE/0001 is essentially a USB-to-serial converter, and is not > compatible with usbhid-ups. (Theoretically, we could have a companion > driver that talks the same protocols over a real RS-232 port, but the > hardware I used to develop the tripplite_usb driver only has a USB > port.) Ah, that