[Nut-upsuser] KIN-1500AP RM + Windows 2008 64-bit Standard R2 SP1 (nut 2.6.1)

Frédéric Bohé fredericbohe at eaton.com
Tue Aug 2 14:23:33 UTC 2011


On Tue, 2011-07-26 at 15:30 +0300, Павел Гуменюк wrote:
> After adding COM1 I've got this:
> 
> c:\Program Files (x86)\NUT\bin>powercom.exe -DDD -a KIN1500
> Network UPS Tools - PowerCom protocol UPS driver 0.13
> (2.6.1-3057:3116M)
>    0.000000     debug level is '3'
>    0.000000     w32_serial_open (notUsed)
>    0.000000     could not open notUsed
> 
> Unable to open notUsed: Operation not permitted
> 
> Things to try:
> 
>  - Check 'port=' in ups.conf
> 
>  - Check owner/permissions of all parts of path
> 
>    0.015600     Fatal error: unusable configuration
> 
> c:\Program Files (x86)\NUT\bin>powercom.exe -DDD -a KIN1500
> Network UPS Tools - PowerCom protocol UPS driver 0.13
> (2.6.1-3057:3116M)
>    0.000000     debug level is '3'
>    0.000000     w32_serial_open (COM1)
>    0.015600     setting initial state on COM1
>    0.015600     00000054 = w32_serial_open (COM1)
>    0.015600     Warning: no locking method is available: No error
> [+яхЁрЎш  єёях
> °эю чртхЁ°хэр. ]
>    0.031200     vmin_ 0, vtime_ 0
>    0.140400     action 0
>    0.140400     vtime 0, vmin 1
> 
>    0.140400     ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1,
> ReadTotalTi
> meoutMultiplier -1
>    0.140400     DTR => 0, RTS => 1
>    0.140400     Values of arguments:
>    0.140400      manufacturer            : 'PowerCom'
>    0.140400      model name              : 'Unknown'
>    0.156000      serial number           : 'Unknown'
>    0.156000      line voltage            : '230'
>    0.156000      type                    : 'Trust'
>    0.156000      number of bytes from UPS: '11'
>    0.156000      method of flow control  : 'dtr0rts1'
>    0.156000      validation sequence: '{{5,0},{7,0},{8,0}}'
>    0.171600      shutdown arguments: '{{0,10},n}'
>    0.171600      frequency calculation coefficients:
> '{0.000210,0.000209}'
>    0.171600      load percentage calculation coefficients:
> '{6.134300,-0.380800,
> 4.311000,0.181100}'
>    0.171600      battery percentage calculation coefficients:
> '{5.000000,0.32680
> 0,-825.000000,4.563900,-835.
> 820007}'
>    0.187200      voltage calculation coefficients:
> '{0.954500,0.000000}'
>    0.343200     data receiving error (validation check)
>    0.343200     dstate_init: sock \\.\pipe\powercom-KIN1500 open on fd
> 100
>    3.432006     data receiving error (0 instead of 11 bytes)
>    6.442811     data receiving error (0 instead of 11 bytes)
>    9.453616     data receiving error (0 instead of 11 bytes)
>   12.464422     data receiving error (0 instead of 11 bytes)
>   21.668438     data receiving error (0 instead of 11 bytes)
>   24.679243     data receiving error (0 instead of 11 bytes)

Hello Pavel,

Maybe it's a bug in serial drivers. It's hard to be sure since I don't
have a Powercom UPS for testing. Anyway, I will privately send you an
experimental binary. If it doesn't fix your issue, please send its
output on this list using -DDDDD ( five D) for maximum output.

Fred

> 
> c:\Program Files (x86)\NUT\bin>
> 
> 
> 2011/7/19 Павел Гуменюк <pavel.gumenyuk at gmail.com>
>         I have only RS-232 on the box (meanwhile, it was manufactured
>         on march of 2011)
>         Here is my configs:
>         
>         nut.conf:
>         
>         
>         MODE = netserver
>         
>         
>         ups.conf:
>         
>         
>         [KIN1500]
>                driver = powercom
>                port = notUsed
>                desc = "Powercom KING PRO KIN-1500AP RM"
>         
>         
>         
>         upsd.conf:
>         
>         
>         LISTEN 192.168.1.2 3493
>         
>         
>         
>         upsd.users:
>         
>         
>         [monuser]
>                        password = xxxxxxxx
>                        upsmon master
>         
>         
>         
>         upsmon.conf:
>         
>         
>         MONITOR KIN1500 at 192.168.1.2 1 monuser xxxxxxxx master
>         MINSUPPLIES 1
>         SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0"
>         NOTIFYCMD /sbin/upssched
>         POLLFREQ 5
>         POLLFREQALERT 5
>         HOSTSYNC 15
>         DEADTIME 15
>         POWERDOWNFLAG "C:\\killpower"
>         NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
>         NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
>         NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
>         RBWARNTIME 43200
>         NOCOMMWARNTIME 300
>         FINALDELAY 5
>         
>         
>         
>         upssched.conf:
>         
>         
>         CMDSCRIPT /bin/upssched-cmd
>         AT ONBATT * START-TIMER   onbattwarn 10
>         AT ONLINE * CANCEL-TIMER  onbattwarn
>         AT LOWBATT * EXECUTE      lowbattwarn
>         AT ONBATT * START-TIMER   timeshutdown 100
>         AT ONLINE * CANCEL-TIMER  timeshutdown
>         
>         
>         After start I can see couple neutral events:
>         upsd.exe - listening on 192.168.1.2 port 3493.
>         upsd.exe - User monuser at 192.168.1.2 logged into UPS [KIN1500].
>         
>         Also, there are a lot of errors, such as "upsmon - Poll UPS
>         [KIN1500 at 192.168.1.2] failed - Data stale."
>         Anybody, please advise how to get it works.
>         Thanks
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

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

--------------------------------------------------------------------------



More information about the Nut-upsuser mailing list