Paul Barber
2013-Mar-07  03:23 UTC
[Nut-upsuser] Power ware 5110 "not the right sequence received"
Hi All,
I have a powerware UPS 5110 connected to an openindiana server with the 
bcmxcp_usb driver and running nut 2.65 compiled and installed as root to 
avoid permission issues.
On running the following debug code to test the UPS's communication it 
fails at the same time with the following error.
    ./bcmxcp_usb -u root -DDD -a 5110
    .......
    2.523879     get_answer: (128 bytes) => ab 01 79 01 02 50 00 50 01 
00 1e 00 01 00 10 50
    2.523926      4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 
00 00 00 00 00 00 00
    2.523956      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
51 51 00 00 00 00 51
    2.523986      00 00 00 00 00 00 00 f0 00 f0 00 00 00 f0 00 00 00 00 
00 00 00 00 f0 00 00
    2.524015      00 00 00 00 00 00 51 00 00 51 00 00 00 00 00 00 00 00 
00 f0 00 00 00 00 00
    2.524039      00 00 00 00 00 00 00 f0 18 2b ab 01
    2.524060     get_answer: block_number = 1
    2.524080     get_answer: data length = 121
    2.524102     get_answer: sequence number (1) is ok
    2.524122     get_answer: checksum is ok
    2.524144     get_answer: block_number = 1
    2.524165     get_answer: data length = 0
    2.524187     Communications with UPS lost: get_answer: not the right 
sequence received 19!!!
    2.524208     Communications with UPS lost: Error executing command
    2.524229     Could not communicate with the ups
    2.524260     CLOSING
Does anyone know if there is a fix for the 2.524187 Communications with 
UPS lost: get_answer: not the right sequence received 19!!! error?
My ups is nothing exciting and just lists the following
[5110]
   driver = bcmxcp_usb
   port = auto
Thankyou
Paul
Charles Lepple
2013-Mar-08  03:57 UTC
[Nut-upsuser] Power ware 5110 "not the right sequence received"
On Mar 6, 2013, at 10:23 PM, Paul Barber wrote:> Does anyone know if there is a fix for the 2.524187 Communications with UPS lost: get_answer: not the right sequence received 19!!! error?I am not very familiar with this driver, but it does seem like this has been patched in the development codebase after 2.6.5 was released: http://article.gmane.org/gmane.comp.monitoring.nut.user/7302 (with a bugfix for that patch later) A number of additional BCM/XCP fixes have been rolled into this branch: https://github.com/networkupstools/nut/tree/bcmxcp You can grab a snapshot from that page, or clone via git. Let us know if you need a snapshot which does not require autoconf and automake. -- Charles Lepple clepple at gmail
Reasonably Related Threads
- BCMXCP UPS driver 0.24 (2.6.1) Hangs
- Getting 'Data stale' error with bcmxcp_usb for a PowerWare 5115 on OSX
- Getting 'Data stale' error with bcmxcp_usb for a PowerWare 5115 on OSX
- bcmxcp_usb can not communicate with Eaton Powerware 5110
- Powerware 5125 (USB) under Debian Squeeze.