Re: [Nut-upsuser] PowerCOM BNT-800AP (0d9f:0004)

2011-10-07 Thread Frédéric Bohé
On Thu, 2011-10-06 at 16:56 +0200, Arnaud Quette wrote:
 Hi Pavel,
 
 first, please keep the traffic on the list, since other users may be
 interested in these info...
 
 2011/10/6 Павел Гуменюк pavel.gumen...@gmail.com:
  Hi Arnaud,
  Great news. So, it could be working.
  It means that I need to get trunk version of compiled driver for windows,
  isn't it?
  Should I compile it with gcc or other C compiler?
  Thank U
 
 I'll defer to Fred to answer on this one.
 the base is Mingw, but the Windows port is still on a separate branch
 (ie, not the trunk).
 whereas your fix is actually in the trunk...

I am using Mingw and MSYS to produce the actual NUT Windows binaries.
You will have to install both on your system and add the libusb-win32
developpement file.
Then you can get branches/windows_port on NUT's SVN and add Arnaud's
patch.
This might not be straight forward and you might prefer to wait for the
next release of my Windows binaries but be aware that they are currently
post-poned for several (5 or 6 currently) weeks due to other projects
from my side.

Fred


 
 cheers,
 Arnaud

-- 
Team Open Source Eaton - http://powerquality.eaton.com

--

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] PowerCOM BNT-800AP (0d9f:0004)

2011-10-06 Thread Arnaud Quette
Hi Pavel,

first, please keep the traffic on the list, since other users may be
interested in these info...

2011/10/6 Павел Гуменюк pavel.gumen...@gmail.com:
 Hi Arnaud,
 Great news. So, it could be working.
 It means that I need to get trunk version of compiled driver for windows,
 isn't it?
 Should I compile it with gcc or other C compiler?
 Thank U

I'll defer to Fred to answer on this one.
the base is Mingw, but the Windows port is still on a separate branch
(ie, not the trunk).
whereas your fix is actually in the trunk...

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



 2011/10/5 Arnaud Quette aquette@gmail.com

 Hi Pavel,

 2011/10/4 Павел Гуменюк pavel.gumen...@gmail.com:
  Hello.
  I've been trying to got it work but haven't luck.
  I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed
  (USB\VID_0D9FPID_0004REV_0001).
  I had tryed all options with  such config:
 
  PWCOM]
      driver = usbhid-ups
      port = auto
          vendorid = 0d9f
      desc = Powercom BNT-800AP
    type=BNT

 as per a previous report on Ubuntu, we know that this UPS is supported:
 https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661

 that being said, it seems I've not completed my actions and committed
 a patch for this new device ID.
 Fixed in the development version (trunk), r3265.

 Also note that the type option is supported by the powercom
 driver, not the usbhid-ups one.

 cheers,
 Arnaud
 --
 Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
 Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
 Debian Developer - http://www.debian.org
 Free Software Developer - http://arnaud.quette.free.fr/



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] PowerCOM BNT-800AP (0d9f:0004)

2011-10-05 Thread Arnaud Quette
Hi Pavel,

2011/10/4 Павел Гуменюк pavel.gumen...@gmail.com:
 Hello.
 I've been trying to got it work but haven't luck.
 I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed
 (USB\VID_0D9FPID_0004REV_0001).
 I had tryed all options with  such config:

 PWCOM]
     driver = usbhid-ups
     port = auto
         vendorid = 0d9f
     desc = Powercom BNT-800AP
   type=BNT

as per a previous report on Ubuntu, we know that this UPS is supported:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661

that being said, it seems I've not completed my actions and committed
a patch for this new device ID.
Fixed in the development version (trunk), r3265.

Also note that the type option is supported by the powercom
driver, not the usbhid-ups one.

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] Powercom BNT-800AP

2010-02-04 Thread cooleyr
While fundamentally working, I'm having a few issues with the driver...

The default voltage quads (for every model) are way off...  Showing
~95v when it should be ~117V.  I've changed the 4th/final coefficient
to +5.0, but haven't tested extensively (with fluctuating voltages).

The input/output voltage appears to be swapped _most of the time_.
When doing a battery test, or when unplugged, the input stays steady,
and the _output_ voltage reports a drop to ~15V.  OTOH, when the UPS
is shutdown, the ordering appears correct, as the input stays steady,
and the output shows ~5V.

For the above, the Powercom upsmon software appears to special-case
those ~5/15V results, and on the next update, report it as 0V.  I have
no idea how to even special-case the screwy input/output-swapping
behavior...


./powercom -a ups0 -DDD
Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1-2308)
   0.00 debug level is '3'
   0.001406 Flow control disable
   0.150003 Detected: BNT-other-500AP , 120V
   0.153986 Values of arguments:
   0.154001  manufacturer: 'PowerCom'
   0.154009  model name  : 'BNT-other-500AP'
   0.154015  serial number   : 'Unknown'
   0.154022  line voltage: '120'
   0.154029  type: 'BNT-other'
   0.154036  number of bytes from UPS: '16'
   0.154042  method of flow control  : 'no_flow_control'
   0.154051  validation sequence: '{{8,0},{8,0},{8,0}}'
   0.154059  shutdown arguments: '{{1,30},y}'
   0.154073  frequency calculation coefficients: '{0.000208,0.00}'
   0.154084  load percentage calculation coefficients:
'{1.447400,0.00,0.859400,0.00}'
   0.154101  battery percentage calculation coefficients:
'{5.00,0.326800,-825.00,0.465110,0.00}'
   0.154110  voltage calculation coefficients: '{0.954500,5.00}'
   0.305927 input.frequency   (raw data): [raw: 80]
   0.305966 input.frequency: 60.09
   0.305974 output.frequency   (raw data): [raw: 80]
   0.305987 output.frequency: 60.09
   0.305994 ups.load  (raw data): [raw: 0]
   0.306008 ups.load: 0.0
   0.306015 battery.charge (raw data): [raw: 197]
   0.306027 battery.charge: 100.0
   0.306035 input.voltage (raw data): [raw: 119]
   0.306048 input.voltage: 118.6
   0.306055 output.voltage (raw data): [raw: 26]
   0.306067 output.voltage: 29.8
   0.306079 STATUS: OB TEST
   0.306338 dstate_init: sock /var/state/ups/powercom-ups0 open on fd 5
   0.453868 input.frequency   (raw data): [raw: 80]
   0.453907 input.frequency: 60.09
   0.453914 output.frequency   (raw data): [raw: 80]
   0.453925 output.frequency: 60.09
   0.453931 ups.load  (raw data): [raw: 0]
   0.453944 ups.load: 0.0
   0.453950 battery.charge (raw data): [raw: 195]
   0.453961 battery.charge: 100.0
   0.453968 input.voltage (raw data): [raw: 119]
   0.453979 input.voltage: 118.6
   0.453986 output.voltage (raw data): [raw: 26]
   0.453997 output.voltage: 29.8
   0.454008 STATUS: OB TEST
   1.853474 new connection on fd 6
   2.457023 input.frequency   (raw data): [raw: 80]
   2.457070 input.frequency: 60.09
   2.457077 output.frequency   (raw data): [raw: 80]
   2.457088 output.frequency: 60.09
   2.457095 ups.load  (raw data): [raw: 0]
   2.457108 ups.load: 0.0
   2.457115 battery.charge (raw data): [raw: 191]
   2.457140 battery.charge: 95.0
   2.457147 input.voltage (raw data): [raw: 119]
   2.457159 input.voltage: 118.6
   2.457167 output.voltage (raw data): [raw: 25]
   2.457185 output.voltage: 28.9
   2.457197 STATUS: OB TEST
   4.456188 input.frequency   (raw data): [raw: 80]
   4.456240 input.frequency: 60.09
   4.456248 output.frequency   (raw data): [raw: 80]
   4.456259 output.frequency: 60.09
   4.456266 ups.load  (raw data): [raw: 0]
   4.456279 ups.load: 0.0
   4.456286 battery.charge (raw data): [raw: 193]
   4.456656 battery.charge: 100.0
   4.456673 input.voltage (raw data): [raw: 119]
   4.456686 input.voltage: 118.6
   4.456693 output.voltage (raw data): [raw: 119]
   4.456849 output.voltage: 118.6
   4.456978 STATUS: OL
   6.455365 input.frequency   (raw data): [raw: 80]
   6.455420 input.frequency: 60.09
   6.455428 output.frequency   (raw data): [raw: 80]
   6.455439 output.frequency: 60.09
   6.455445 ups.load  (raw data): [raw: 0]
   6.455458 ups.load: 0.0
   6.455465 battery.charge (raw data): [raw: 193]
   6.455476 battery.charge: 100.0
   6.455483 input.voltage (raw data): [raw: 119]
   6.455494 input.voltage: 118.6
   6.455500 output.voltage (raw data): [raw: 119]
   6.455511 output.voltage: 118.6
   6.455522 STATUS: OL

For anyone wondering, I wouldn't recommend these units to anyone else.
 A 400W dumb/personal UPS from