search for: get_answer

...4 send_to_all: SETINFO device.type "ups" 0.014868 send_to_all: SETINFO driver.version "2.6.1" 0.014911 send_to_all: SETINFO driver.version.internal "0.24" 0.014972 send_to_all: SETINFO driver.name "bcmxcp_usb" 1.026913 entering get_answer(31) 6.026797 get_answer: exiting (len=0) 7.046961 entering get_answer(31) 7.047086 get_answer: (156 bytes) => ab 01 73 01 02 20 01 02 01 00 0f 00 01 00 09 50 7.047225 57 35 31 31 35 20 52 4d 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7.047332 00 00...

...at happens when I try to get the driver to talk to the UPS: $ sudo /lib/nut/bcmxcp_usb -DD -a pw5110 Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) USB communication subdriver 0.18 0.000000 debug level is '2' 0.008810 device 004 opened successfully 0.011517 entering get_answer(31) 0.013401 get_answer: (8 bytes) => ab 01 79 01 02 50 00 50 0.014623 get_answer: block_number = 1 0.015972 get_answer: need to read 118 more data 0.017549 get_answer: (16 bytes) => ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.018769 get_answer: block...

...troubleshoot this problem (assuming it should work to begin with)? Thanks, Charlie Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3-2392) USB communication subdriver 0.18 0.000000 debug level is '2' 0.329754 device 002-06da-0002-00-00 opened successfully 0.332582 entering get_answer(31) 1.083837 get_answer: (166 bytes) => ab 01 74 01 02 00 01 05 10 00 14 00 01 00 13 35 1.083919 31 31 35 31 30 30 30 41 20 20 20 20 20 20 20 20 20 20 51 00 00 00 00 00 00 1.084676 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 00 f0 00 00 00 52 52 00 00 1.084704 00 00 52...

...troubleshoot this problem (assuming it should work to begin with)? Thanks, Charlie Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3-2392) USB communication subdriver 0.18 0.000000 debug level is '2' 0.329754 device 002-06da-0002-00-00 opened successfully 0.332582 entering get_answer(31) 1.083837 get_answer: (166 bytes) => ab 01 74 01 02 00 01 05 10 00 14 00 01 00 13 35 1.083919 31 31 35 31 30 30 30 41 20 20 20 20 20 20 20 20 20 20 51 00 00 00 00 00 00 1.084676 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 00 f0 00 00 00 52 52 00 00 1.084704 00 00 52...

...2 send_to_all: SETINFO device.type "ups" 0.290403 send_to_all: SETINFO driver.version "2.4.3" 0.290410 send_to_all: SETINFO driver.version.internal "0.23" 0.290417 send_to_all: SETINFO driver.name "bcmxcp_usb" 0.292362 entering get_answer(31) 3.991792 get_answer: (8 bytes) => a8 81 a4 c5 d8 c9 b0 b2 3.991811 get_answer: wrong header 3.993783 entering get_answer(31) 4.055796 get_answer: (8 bytes) => b9 b4 dc dc dc dc d0 ef 4.055807 get_answer: wrong header 4.057786 entering get_answer(3...

...nd /dev/ugen0 on /dev/usb2 usb_control_msg: 128 6 512 0 0xcfbcadc8 8 1000 usb_control_msg: 128 6 512 0 0x82cbc240 34 1000 skipped 1 class/vendor specific interface descriptors 0.019716 device /dev/ugen0 opened successfully usb_control_msg: 0 7 772 0 0xcfbcacd0 4 1000 0.024370 entering get_answer(31) USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource temporarily unavailable usb_control_msg: 0 7 772 0 0xcfbcacd0 4 1000 0.029368 entering get_answer(31) USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource temporarily unavailable usb_control_msg:...

...h 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 0...

...card, even when only using one port (and I don't give a shit about the other ports, if anybody has a one-port laying around...) so stop whining already. $OpenBSD$ --- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006 +++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006 @@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi /* now we have the whole answer from the ups, we can checksum it */ if (!checksum_test(my_buf)) { - ser_comm_fail("checksum error! "); - return -1; + upsdebugx(2, "checksum error!"); + return -1; } memcpy(data+end_length, my_buf+4...

...er] Powerware (Eaton) Prestige 9 UPS To: Charles Lepple <clepple at gmail.com> Charles - As a quick followup, the Prestige (both FW 2.13 and 3.09 - 2.x is pre-Eaton, 3.x post) reply to the topology block query thus: 3.064046 send_command: (4 bytes) => ab 01 43 11 3.136246 get_answer: (2 bytes) => 34 43 Unfortunately, this does not correspond to any of the defined topology values in the spec, and the block size that was returned from block 0x01 was 2.410028 Length of topology block: 36864 for 2.13 firmware and 2.518815 Length of topology block: 127 for 3.09,...

I noted some correspondence from several years back about supporting this device with bcmxcp, and the problems therein. Since I have one of these UPS units, still going strong, and the Eaton LanSafe stuff has finally caused me enough grief to abandon it, I figured I'd take a look at this. The issue is not that bad - the bcmxcp driver query of the topology block (2 bytes!) is returning

...in signedness gcc -I../include -O -Wall -Wsign-compare -c libusb.c libusb.c: In function libusb_get_interrupt: libusb.c:321: warning: pointer targets in passing argument 3 of usb_interrupt_read differ in signedness gcc -I../include -O -Wall -Wsign-compare -c bcmxcp_usb.c bcmxcp_usb.c: In function get_answer: bcmxcp_usb.c:47: warning: pointer targets in passing argument 3 of usb_interrupt_read differ in signedness gcc -I../include -O -Wall -Wsign-compare -c tripplite_usb.c tripplite_usb.c: In function hex2d: tripplite_usb.c:350: warning: pointer targets in passing argument 1 of __builtin_strncpy diffe...