Nut upsuser - Jul 2016 - Powercom EBK 500 ms behind a Keyspan serial to USB

Hello

Does anybody know if it's possible to monitor a Powercom EBk 500 (RS232)?
the trick is that I am using a raspberry pi, it does not have RS232 so I
connected a keyspan RS232 to USB adapter, but so far I can?t make this work.

Thanks for your time to read this.

-Edgar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160720/c412d3dc/attachment.html>

On Jul 20, 2016, at 6:12 PM, Edgar Estrada <edgar.estrada at gmail.com>
wrote:
> Does anybody know if it's possible to monitor a Powercom EBk 500
(RS232)? the trick is that I am using a raspberry pi, it does not have RS232 so
I connected a keyspan RS232 to USB adapter, but so far I can?t make this work.
That model isn't listed in our compatibility table:
http://networkupstools.org/stable-hcl.html?manufacturer=Powercom

However, there are at least two drivers which are compatible with other serial
models: powercom and blazer_ser (nutdrv_qx might be, as well).

Which driver did you use?

If you are using Raspbian, you can stop the NUT service (sudo service nut-server
stop) and run the driver manually in debug mode:

/lib/nut/powercom -a <name-from-ups.conf> -DDDD

The commands and paths will likely be different for other distributions, but you
can find out the path by passing a few "-D" flags to "upsdrvctl
start".

[please use Reply-All to include the list - thanks!]


-- 
Charles Lepple
clepple at gmail

Hi Charles

I?ve tried with the blazer_usb, blazer_ser, genericups and powercom drivers
and its different types -- the only type that kind of works is* BNT-other,*
when I run the command: *sudo /lib/nut/powercom -a int -DDDD, *I will get
this output:

  *12.470014 input.frequency   (raw data): [raw: 80]*

*  12.470093 input.frequency: 45.00*

*  12.470124 output.frequency   (raw data): [raw: 80]*

*  12.470166 output.frequency: 45.00*

*  12.470192 ups.load  (raw data): [raw: 0]*

*  12.470227 ups.load: 0.0*

*  12.470252 battery.charge (raw data): [raw: 242]*

*  12.470288 battery.charge: 242.0*

*  12.470313 input.voltage (raw data): [raw: 150]*

*  12.470349 input.voltage: 300.0*

*  12.470374 output.voltage (raw data): [raw: 150]*

*  12.470411 output.voltage: 300.0*

*  12.470449 STATUS: OL*
However, when I start upsdrvctrl and then run *sudo upsc int at localhost
ups.status 2>&1 | grep  -v '^Init SSL'*, I get the following:

*pi at elektra:/etc/nut $ sudo upsc int at localhost ups.status 2>&1 |
grep  -v
'^Init SSL'*

*Error: Driver not connected*

Apparently the powercom command can "see" the UPS, but the upsdrvctrl
is
not working right.

Any ideas?

Thanks!!

On Thu, Jul 21, 2016 at 8:34 AM, Charles Lepple <clepple at gmail.com>
wrote:
> On Jul 20, 2016, at 6:12 PM, Edgar Estrada <edgar.estrada at
gmail.com>
> wrote:
> > Does anybody know if it's possible to monitor a Powercom EBk 500
> (RS232)? the trick is that I am using a raspberry pi, it does not have
> RS232 so I connected a keyspan RS232 to USB adapter, but so far I can?t
> make this work.
>
> That model isn't listed in our compatibility table:
> http://networkupstools.org/stable-hcl.html?manufacturer=Powercom
>
> However, there are at least two drivers which are compatible with other
> serial models: powercom and blazer_ser (nutdrv_qx might be, as well).
>
> Which driver did you use?
>
> If you are using Raspbian, you can stop the NUT service (sudo service
> nut-server stop) and run the driver manually in debug mode:
>
> /lib/nut/powercom -a <name-from-ups.conf> -DDDD
>
> The commands and paths will likely be different for other distributions,
> but you can find out the path by passing a few "-D" flags to
"upsdrvctl
> start".
>
> [please use Reply-All to include the list - thanks!]
>
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160721/aeefd106/attachment.html>