[Nut-upsuser] Tripplite SMX1500XLRT2U through serial

[Roman Serbski]

On Tue, Sep 30, 2008 at 5:30 PM, Charles Lepple <clepple at gmail.com> wrote:
> 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?

Thanks a lot Charles! I think I managed to get NUT working.

NUT was built from ports with uucp owner by default. As soon as I
created separate user (nut), replaced uucp with nut in
/usr/ports/sysutils/nut/Makefile, adjusted devfs.conf and devfs.rules
accordingly and rebuilt the port I immediately got NUT working!

There are couple of small issues though:

1. /var/log/ups.log doesn't contain any numbers but only NA, although
I can see that it's being updated regularly and 'upsc
tripplite at localhost' gives a lot of data:

battery.charge: 90
battery.voltage: 40.50
battery.voltage.nominal: 36
driver.name: tripplite_usb
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/usb3
driver.version: 2.2.2
driver.version.internal: 0.11
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 256
input.voltage.maximum: 140
input.voltage.minimum:   0
input.voltage.nominal: 230
outlet.1.desc: Load 1
outlet.1.id: 1
outlet.1.switch: 1
outlet.1.switchable: 1
outlet.2.desc: Load 2
outlet.2.id: 2
outlet.2.switch: 1
outlet.2.switchable: 1
outlet.3.desc: Load 3
outlet.3.id: 3
outlet.3.switch: 1
outlet.3.switchable: 1
outlet.4.desc: Load 4
outlet.4.id: 4
outlet.4.switchable: 0
ups.debug.D: 38 36 38 37 0d 00 00 '8687...'
ups.debug.load_banks: 3
ups.debug.M: 30 30 38 43 0d 00 00 '008C...'
ups.debug.S: 31 34 30 00 5a 31 0d '140.Z1.'
ups.debug.T: 37 32 31 46 34 30 0d '721F40.'
ups.debug.V: 32 30 36 33 58 58 0d '2063XX.'
ups.delay.shutdown: 64
ups.firmware: F1091.A
ups.firmware.aux: protocol 3003
ups.id: 65535
ups.load: 36
ups.mfr: Tripp Lite
ups.model: SMX1500XLRT2U
ups.power.nominal: 1500
ups.status: OL
ups.temperature: 20.5

%tail /var/log/ups.log
20081001 170732 NA NA NA [NA] NA NA
20081001 171232 NA NA NA [NA] NA NA
20081001 171732 NA NA NA [NA] NA NA

2. I also enabled cgi scripts to show the status of UPS and it works
well. The only thing is that it shows "Not supported" for Output
column. Is it somehow related to ups.debug messages I receive from
upsc or my UPS simply doesn't support this?

Thank you once again!