Nut upsuser - Feb 2013 - Data string for 2 instant commands to Powerware 9110

Hi all

I was wondering if one of you kind gentlemen (or ladies) would assist me 
in finding the data string required to tell my ups to turn on and off. 
No more no less :)

  I guess it would be the actual string of an instant command sent down 
the rs232 port to the ups.

I have no programming experience and have done a list search to no 
avail. Sorry to trouble you with this.

I have a lan to rs232 device called a Global Cache gc-100 which can send 
a data string out the rs232 port (commonly used for home automation). I 
know how to address the gc and get to the point of sending an ascii 
command out the port (or raw hex code).

I dont need to handshake/communicate with the ups, all I need to do is 
to turn the load or output on and off so that the thing isnt chewing 
power when I'm away. Its a rather big 6kva in a hard to get to location 
in my recording studio.

Rather than trying to install nut and getting into deep water it would 
be much simpler if someone could extract the string required from the 
upscode2 driver with the correct syntax to instantly control the ups. Or 
point me in the right direction. Is there a list of raw strings and 
their corresponding commands available for the code 2 driver?

My ups:
Powerware 9110 6kva with rs232 port

Best Regards
Ben Chase
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130210/43ae0f55/attachment.html>

On Feb 10, 2013, at 9:11 AM, Ben Chase wrote:
>  I guess it would be the actual string of an instant command sent down the
rs232 port to the ups.
Probably one of these?

   https://github.com/networkupstools/nut/blob/master/drivers/upscode2.c#L406
(middle column, most likely)

Not sure whether your model takes a "\n" or "\r\n" around
the command:

   https://github.com/networkupstools/nut/blob/master/drivers/upscode2.c#L1003

Baud rate seems to default to 1200.

Sorry I don't have more detail - I haven't worked on this particular
driver.

-- 
Charles Lepple
clepple at gmail