[Nut-upsuser] Contact-closure UPS
Róbert SZAKSZ
robert at szaksz.eu
Fri Nov 20 17:17:01 UTC 2015
No progress has been made:
cable is UPS - PC
6 - 3
7 - 5
9 - 2
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
1.106058 Status read 1 failed
1.106825 send: 'Q1'
2.108171 read: timeout
2.108295 blazer_status: short reply
2.108338 Status read 2 failed
2.108638 send: 'Q1'
3.109987 read: timeout
3.110242 blazer_status: short reply
3.110349 Status read 3 failed
3.110509 Trying mustek protocol...
3.111206 send: 'QS'
4.112808 read: timeout
4.113098 blazer_status: short reply
4.113206 Status read 1 failed
4.113868 send: 'QS'
5.115398 read: timeout
5.115631 blazer_status: short reply
5.115736 Status read 2 failed
5.116453 send: 'QS'
6.117979 read: timeout
6.118322 blazer_status: short reply
6.118510 Status read 3 failed
6.118690 Trying megatec/old protocol...
6.119361 send: 'D'
7.120701 read: timeout
7.120934 blazer_status: short reply
7.121038 Status read 1 failed
7.121725 send: 'D'
8.123137 read: timeout
8.123400 blazer_status: short reply
8.123503 Status read 2 failed
8.124140 send: 'D'
9.125620 read: timeout
9.125659 blazer_status: short reply
9.125670 Status read 3 failed
9.125680 Trying zinto protocol...
9.126280 send: 'Q1'
10.127596 read: timeout
10.127641 blazer_status: short reply
10.127653 Status read 1 failed
10.128204 send: 'Q1'
11.129560 read: timeout
11.129596 blazer_status: short reply
11.129608 Status read 2 failed
11.130162 send: 'Q1'
12.131519 read: timeout
12.131556 blazer_status: short reply
12.131568 Status read 3 failed
12.131578 No supported UPS detected
for ./nutdrv_qx -DDDDD -a infosec
0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1"
0.000472 debug level is '5'
0.004317 upsdrv_initups...
0.106821 send: 'QGS'
1.108364 read: timeout (0)
1.108647 qx_process_answer: short reply (input.voltage)
1.109384 send: 'QGS'
2.110945 read: timeout (0)
2.111125 qx_process_answer: short reply (input.voltage)
2.111446 send: 'QGS'
3.112802 read: timeout (0)
3.113027 qx_process_answer: short reply (input.voltage)
3.113659 send: 'M'
4.115052 read: timeout (0)
4.115296 qx_process_answer: short reply (ups.firmware.aux)
4.115916 send: 'M'
5.117221 read: timeout (0)
5.117454 qx_process_answer: short reply (ups.firmware.aux)
5.118082 send: 'M'
6.119436 read: timeout (0)
6.119483 qx_process_answer: short reply (ups.firmware.aux)
6.120102 send: 'M'
7.121221 read: timeout (0)
7.121267 qx_process_answer: short reply (ups.firmware.aux)
7.121534 send: 'M'
8.121940 read: timeout (0)
8.122012 qx_process_answer: short reply (ups.firmware.aux)
8.122584 send: 'M'
9.123768 read: timeout (0)
9.123808 qx_process_answer: short reply (ups.firmware.aux)
9.124381 send: 'QS'
10.125458 read: timeout (0)
10.125510 qx_process_answer: short reply (input.voltage)
10.125784 send: 'QS'
11.127225 read: timeout (0)
11.127248 qx_process_answer: short reply (input.voltage)
11.127516 send: 'QS'
12.128803 read: timeout (0)
12.128839 qx_process_answer: short reply (input.voltage)
12.129325 send: 'D'
13.130616 read: timeout (0)
13.130732 qx_process_answer: short reply (input.voltage)
13.131177 send: 'D'
14.132452 read: timeout (0)
14.132491 qx_process_answer: short reply (input.voltage)
14.133038 send: 'D'
15.134371 read: timeout (0)
15.134413 qx_process_answer: short reply (input.voltage)
15.134985 send: 'Q1'
16.136148 read: timeout (0)
16.136233 qx_process_answer: short reply (input.voltage)
16.136781 send: 'Q1'
17.138132 read: timeout (0)
17.138157 qx_process_answer: short reply (input.voltage)
17.138472 send: 'Q1'
18.139762 read: timeout (0)
18.139800 qx_process_answer: short reply (input.voltage)
18.140562 send: 'Q1'
19.141915 read: timeout (0)
19.142021 qx_process_answer: short reply (input.voltage)
19.142575 send: 'Q1'
20.143857 read: timeout (0)
20.143895 qx_process_answer: short reply (input.voltage)
20.144443 send: 'Q1'
21.145828 read: timeout (0)
21.145869 qx_process_answer: short reply (input.voltage)
21.146458 send: 'Q1'
22.147803 read: timeout (0)
22.147886 qx_process_answer: short reply (input.voltage)
22.148437 send: 'Q1'
23.149876 read: timeout (0)
23.149917 qx_process_answer: short reply (input.voltage)
23.150486 send: 'Q1'
24.151597 read: timeout (0)
24.151635 qx_process_answer: short reply (input.voltage)
24.152194 send: 'Q1'
25.153359 read: timeout (0)
25.153420 qx_process_answer: short reply (input.voltage)
25.153810 send: 'Q1'
26.155268 read: timeout (0)
26.155306 qx_process_answer: short reply (input.voltage)
26.155872 send: 'Q1'
27.157368 read: timeout (0)
27.157405 qx_process_answer: short reply (input.voltage)
27.158010 send: 'Q1'
28.159325 read: timeout (0)
28.159404 qx_process_answer: short reply (input.voltage)
28.159950 send: 'Q1'
29.161389 read: timeout (0)
29.161413 qx_process_answer: short reply (input.voltage)
29.161734 send: 'Q1'
30.163172 read: timeout (0)
30.163194 qx_process_answer: short reply (input.voltage)
30.163200 Device not supported!
30.163204 Device not supported!
Best regards,
Robert SZAKSZ
----- Original Message -----
From: "Charles Lepple" <clepple at gmail.com>
To: "Róbert SZAKSZ" <robert at szaksz.eu>
Cc: nut-upsuser at lists.alioth.debian.org
Sent: Friday, November 20, 2015 1:39:17 PM
Subject: Re: [Nut-upsuser] Contact-closure UPS
On Nov 19, 2015, at 12:04 PM, Róbert SZAKSZ <robert at szaksz.eu> wrote:
> output(nutdrv_qx cmd upsdrvctl -DDD start)
>
> Network UPS Tools - UPS driver controller 2.7.3
> 0.000000
> If you're not a NUT core developer, chances are that you're told to enable debugging
> to see why a driver isn't working for you. We're sorry for the confusion, but this is
> the 'upsdrvctl' wrapper, not the driver you're interested in.
>
> Below you'll find one or more lines starting with 'exec:' followed by an absolute
> path to the driver binary and some command line option. This is what the driver
> starts and you need to copy and paste that line and append the debug flags to that
> line (less the 'exec:' prefix).
>
> 0.000665 Starting UPS: infosec
> 0.000891 1 remaining attempts
> 0.001135 exec: /usr/lib/ups/driver/nutdrv_qx -a infosec
The above message is saying that the debug flags need to be added to the driver command line, not to the upsdrvctl command:
/usr/lib/ups/driver/nutdrv_qx -DDD -a infosec
--
Charles Lepple
clepple at gmail
More information about the Nut-upsuser
mailing list