[Nut-upsuser] Powerware 5115 USB Issue

[Arnaud Quette]

Hi Greg,

> Thanks for the quick reply.
>
> His is the output of r2095

thanks

> =============================
> Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.1)
> USB communication subdriver 0.18
>  0.000000     debug level is '4'
>  0.007087     device 013 opened successfully
>  0.009059     entering get_answer(31)
>  0.758797     get_answer: (38 bytes) => ab 01 74 01 02 00 01 04 00 40 00 00
> 00 00 00 05
>  0.759991      00 80 06 08 00 50 00 00 00 00 00 00 03 00 1b 18 00 00 00 11
> 00 2f
>  0.761151     get_answer: block_number = 1
>  0.762279     get_answer: data length = 116
>  0.763425     get_answer: need to read 83 more data
>  1.859184     get_answer: (167 bytes) => ab 01 74 01 02 00 01 04 00 40 00 00
> 00 00 00 05
>  1.860371      00 80 06 08 00 50 00 00 00 00 00 00 03 00 1b 18 00 00 00 11
> 00 2f 00 00 00
>  1.861599      40 00 00 00 00 00 05 00 80 06 08 00 50 00 00 00 00 00 00 03
> 00 1b 18 00 00
>  1.862798      00 11 00 2f 00 00 00 40 00 00 00 00 00 05 00 80 06 08 00 50
> 00 00 00 00 00
>  1.864065      00 03 00 1b 18 00 00 00 11 00 2f 00 00 00 40 00 00 00 00 00
> 05 00 80 06 08
>  1.865326      00 50 00 00 00 00 00 00 03 00 1b 18 00 00 00 11 00 2f 00 00
> 00 40 00 00 00
>  1.866651      00 00 05 00 80 06 08 00 50 00 00 00 00 00 00 03 00 1b 18 00
> 00 00 11 00 2f
>  1.867780      00
>  1.869626     get_answer: block_number = 1
>  1.870760     get_answer: data length = 116
>  1.871908     get_answer: sequence number (1) is ok
>  1.873055     Communications with UPS lost: get_answer: checksum error!
>  1.875154     entering get_answer(31)
>  2.768796     get_answer: (38 bytes) => ab 01 74 01 02 00 01 04 10 00 0a 00
> 01 00 13 35
>  2.769992      31 31 35 30 35 30 30 41 00 00 00 00 03 00 1b 18 00 00 00 11
> 00 2f
>  2.771031     get_answer: block_number = 1
>  2.772136     get_answer: data length = 116
>  2.773156     get_answer: need to read 83 more data
>  3.878796     get_answer: (167 bytes) => ab 01 74 01 02 00 01 04 10 00 0a 00
> 01 00 13 35
>  3.880001      31 31 35 30 35 30 30 41 00 00 00 00 03 00 1b 18 00 00 00 11
> 00 2f 00 00 00
>  3.881265      40 00 00 00 00 00 05 00 80 06 08 00 50 00 00 00 00 00 00 03
> 00 1b 18 00 00
>  3.882518      00 11 00 2f 00 00 00 40 00 00 00 00 00 05 00 80 06 08 00 50
> 00 00 00 00 00
>  3.883799      00 03 00 1b 18 00 00 00 11 00 2f 00 00 00 40 00 00 00 00 00
> 05 00 80 06 08
>  3.885058      00 50 00 00 00 00 00 00 03 00 1b 18 00 00 00 11 00 2f 00 00
> 00 40 00 00 00
>  3.886318      00 00 05 00 80 06 08 00 50 00 00 00 00 00 00 03 00 1b 18 00
> 00 00 11 00 2f
>  3.887489      00
>  3.888686     get_answer: block_number = 1
>  3.889745     get_answer: data length = 116
>  3.890809     get_answer: sequence number (1) is ok
>  3.891947     Communications with UPS lost: get_answer: checksum error!
> (...)

damn, we're finally reading everything to end up with a checksum error!
what's worrying me here is that the first data read seems to be
padded, while subsequent reads contains more data... the XCP frame
seems corrupted!

questions:
- was this test done on the QNAP?
- can you send me a "uname -a" output from the QNAP?
- is it running fine on your Ubuntu box with the trunk?

I'll have some more questions soon...

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