[Nut-upsuser] Contact-closure UPS
Charles Lepple
clepple at gmail.com
Sat Nov 21 02:28:58 UTC 2015
On Nov 20, 2015, at 12:17 PM, Róbert SZAKSZ <robert at szaksz.eu> wrote:
>
> No progress has been made:
>
> cable is UPS - PC
> 6 - 3
> 7 - 5
> 9 - 2
>
Maybe pins 4 and 7 (ground) both need to be connected on the UPS side?
> for ./blazer_ser -DDDDD -a infosec
> 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1"
> 0.000323 debug level is '5'
> 0.103068 send_to_all: SETINFO device.type "ups"
> 0.103104 send_to_all: SETINFO driver.version "2.7.3"
> 0.103118 send_to_all: SETINFO driver.version.internal "1.56"
> 0.103131 send_to_all: SETINFO driver.name "blazer_ser"
> 0.103141 Trying megatec protocol...
> 0.103687 send: 'Q1'
> 1.105456 read: timeout
> 1.105823 blazer_status: short reply
Unfortunately, I don't think there is a safe way (in software) to determine whether the UPS is not receiving the signal, or whether the PC is not receiving the reply.
If you have a multimeter, you could check pin 9 on the UPS relative to pin 4/7 to see if it is being driven negative.
--
Charles Lepple
clepple at gmail
More information about the Nut-upsuser
mailing list