[Nut-upsuser] Tripplite SMX1500XLRT2U through serial

Charles Lepple clepple at gmail.com
Mon Sep 22 12:49:23 UTC 2008


On Mon, Sep 22, 2008 at 3:08 AM, Roman Serbski <mefystofel at gmail.com> wrote:
> On Fri, Sep 19, 2008 at 12:11 AM, Charles Lepple <clepple at gmail.com> wrote:
>>>>> On Wed, Sep 10, 2008 at 9:05 AM, Charles Lepple <clepple at gmail.com> wrote:
>>>>>> If that doesn't work, you can try echoing an identification command to the
>>>>>> serial port, and see what it returns (untested):
>>>>>>
>>>>>> $ stty -f /dev/cuad0 raw
>>>>>> $ echo -ne ':\000\377\015' > /dev/cuad0
>>>>>> $ hd < /dev/cuad0
>> [...]
>>> Ok, here is the ouput of "hd < /dev/cuad0":
>>>
>>> 00000000  52 01 ff 0d 53 31 34 30  00 64 31 0d 54 36 46 31  |R...S140.d1.T6F1|
>>> 00000010  46 33 30 0d 44 37 44 38  38 0d 4c 31 46 30 44 00  |F30.D7D88.L1F0D.|
>>> 00000020  58 0d 4d 36 34 38 43 0d  52 01 ff 0d 53 31 34 30  |X.M648C.R...S140|
>>> 00000030  00 64 31 0d 54 36 46 31  46 34 30 0d 44 37 44 38  |.d1.T6F1F40.D7D8|
>>> 00000040  37 0d 4c 31 46 30 44 00  58 0d 4d 36 34 38 43 0d  |7.L1F0D.X.M648C.|
>>
>> Odd... is something else monitoring this UPS? I figured we might get a
>> couple bytes back from 'hd', but it looks like this was being output
>> continuously?
>>
>> The really interesting part is that I do not see a result of the
>> protocol request command.
>
> Yes, it's being output continuously. The only thing that is changing
> is L1F0D part. We also monitor this UPS through USB cable, but it
> connected to Windows 2003 server and according to SMX1500XLRT2U specs
> it: "Supports simultaneous remote monitoring of UPS and site power
> conditions via built-in USB and DB9 monitoring ports.".

Interesting. I forget the exact symptoms, but previous units would not
even respond to the other port if, for instance, you first used the
serial port, then tried to connect via USB.

I can't promise that we will be able to support the remote monitoring
thing, but one thing that should capture the protocol number is the
following procedure:

1) Temporarily stop the Windows-based monitoring software
2) Re-run the hd command
3) Let hd run while you restart the monitoring software
4) Stop hd after the monitoring software has retrieved the device
status (online, voltages, etc.)

-- 
- Charles Lepple



More information about the Nut-upsuser mailing list