[Nut-upsuser] Tripplite SMX1500XLRT2U through serial

[Charles Lepple]

On Tue, Sep 30, 2008 at 12:41 AM, Roman Serbski <mefystofel at gmail.com> wrote:

> Greetings Charles-
>
> I followed your advise and with stopped windows-based monitoring
> software I don't get any results from hd at all... So I gave up with
> the serial connection and connected through USB. Looks like my UPS was
> recognized (using tripplite_usb driver), but there is something
> strange going on. When I run '/usr/local/libexec/nut/tripplite_usb -a
> tripplite -DDDDD -u root' I got the following information:
>
> %/usr/local/libexec/nut/tripplite_usb -a tripplite -DDDDD -u root
>
> Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.2)
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
> debug level is '5'
> Checking device (09AE/0001) (/dev/usb3//dev/ugen0)
> - VendorID: 09ae
> - ProductID: 0001
> - Manufacturer: TRIPP LITE
> - Product: TRIPP LITE SMX1500XLRT2U
> - Serial Number: unknown
> - Bus: /dev/usb3
> Trying to match device
> Device matches
> Detected a UPS: TRIPP LITE/TRIPP LITE SMX1500XLRT2U
> send_cmd(msg_len=3, type='W')
> send_cmd: sending  3a 57 00 a8 0d 00 00 00 '.W......'
> send_cmd: received 57 00 0d 00 00 00 00 00 'W.......' (OK)
> send_cmd(msg_len=2, type='
> send_cmd: sending  3a 00 ff 0d 00 00 00 00 '........'
> send_cmd: received 00 30 03 58 58 58 58 0d '.0.XXXX.' (OK)
> Using SMARTPRO protocol (3003)

Aha! This is the protocol number that I was trying to find out before.

> As soon as I run it without '-u root' I have an error (same valid when
> I start nut):
>
> %/usr/local/libexec/nut/tripplite_usb -a tripplite -DDDDD
>
> Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.2)
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
> debug level is '5'
> Checking device (09AE/0001) (/dev/usb3//dev/ugen0)
> - VendorID: 09ae
> - ProductID: 0001
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: /dev/usb3
> Trying to match device
> Device matches
> Detected a UPS: unknown/unknown
> send_cmd(msg_len=3, type='W')
> send_cmd: sending  3a 57 00 a8 0d 00 00 00 '.W......'
> libusb_set_report() returned -1 instead of 8
> Could not reset watchdog. Please send model information to nut-upsdev
> mailing list
> send_cmd(msg_len=2, type='
> send_cmd: sending  3a 00 ff 0d 00 00 00 00 '........'
> libusb_set_report() returned -1 instead of 8
> Error reading protocol
>
> I double checked permissions (according to
> http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt), but it
> didn't help. Does it look like a permission problem?

Definitely seems like a permissions problem.

It's been a while since I messed with USB on FreeBSD. What do the
permissions look like on /dev/ugen*? What modifications did you make
to /etc/devfs.rules?

-- 
- Charles Lepple