search for: blazer_r

...; send_to_all: SETINFO beeper.status "disabled" send_to_all: SETINFO ups.type "offline / line interactive" send_to_all: SETINFO ups.status "OL" Status read in 1 tries Supported UPS detected with megatec protocol send: error sending control message: Connection timed out blazer_rating: short reply Rating read 1 failed Checking device (06DA/0003) (002/011) - VendorID: 06da - ProductID: 0003 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (0000/0000) (002/001) ... here it go...

...read: (229.7 231.6 229.7 023 50.1 27.5 --.- 00001001 2.737456 [D2] blazer_status: non numerical value [--.-] 2.737477 [D2] Status read in 1 tries 2.737486 Supported UPS detected with mustek protocol 7.737351 [D3] send: error sending control message: Connection timed out 7.737382 [D2] blazer_rating: short reply 7.737483 [D1] Rating read 1 failed 12.737303 [D3] send: error sending control message: Connection timed out 12.737347 [D2] blazer_rating: short reply 12.739509 [D1] Rating read 2 failed 13.019570 [D3] send: F 13.025314 [D3] read: (231.7 229.7 231.6 023 50.1 27.5 --.-...

...0.1 27.5 --.- 00001001 > 2.737456 [D2] blazer_status: non numerical value [--.-] > 2.737477 [D2] Status read in 1 tries > 2.737486 Supported UPS detected with mustek protocol > 7.737351 [D3] send: error sending control message: Connection timed out > 7.737382 [D2] blazer_rating: short reply > 7.737483 [D1] Rating read 1 failed > 12.737303 [D3] send: error sending control message: Connection timed out > 12.737347 [D2] blazer_rating: short reply > 12.739509 [D1] Rating read 2 failed > 13.019570 [D3] send: F > 13.025314 [D3] read: (2...

...rally. > > Aside from the occasional "blazer_status: short reply ... Communications > with UPS lost: status read failed!" messages (from which it appears to > recover perfectly well), plus the odd corrupted reply from the device - e.g. > "read: #Ff .0 2.0 12.00 50.0... blazer_rating: non numerical value [Ff .0]", > the output seems quite promising! > > Any ideas where I go from here - firstly to iron-out those buggy responses > from the device and secondly (and where we left it previously), how to get > FreeBSD to 'talk' libusb-0.1 or else allo...

...rent for FreeBSD, naturally. Aside from the occasional "blazer_status: short reply ... Communications with UPS lost: status read failed!" messages (from which it appears to recover perfectly well), plus the odd corrupted reply from the device - e.g. "read: #Ff.0 2.0 12.00 50.0... blazer_rating: non numerical value [Ff.0]", the output seems quite promising! Any ideas where I go from here - firstly to iron-out those buggy responses from the device and secondly (and where we left it previously), how to get FreeBSD to 'talk' libusb-0.1 or else allow FreeBSD (8.2) and N...

...ceived 47 (40) 0.201251 read: (230.0 000.0 231.0 012 50.0 27.2 29.0 00001000 0.201404 Status read in 1 tries 0.201439 Supported UPS detected with megatec protocol 0.201473 send: F 0.216208 received 22 (35) 0.216267 read: # . . . 0.216325 blazer_rating: parsing failed 0.216358 Rating read 1 failed 0.216390 send: F 0.230202 received 22 (35) 0.230274 read: # . . . 0.230324 blazer_rating: parsing failed 0.230356 Rating read 2 failed 0.230387 send: F 0.245193 received 22 (35)...

...tion: USB device "loops" when starting blazer_usb. USB device permissions are ok. Receives some information. Error messages: "failed to claim USB device: could not claim interface 0: Device or resource busy" "send: error sending control message: Broken pipe" "blazer_rating: short reply" /etc/ups/ups.conf --- clip --- [pw1] driver = blazer_usb port = auto --- clip --- /var/log/messages --- clip --- Mar 6 10:09:28 iron kernel: usb 2-1.7: new low speed USB device number 60 using ehci_hcd Mar 6 10:09:28 iron kernel: usb 2-1.7: New USB devi...

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller

...e interactive" 1.028049 send_to_all: SETINFO ups.status "OL" 1.028058 Status read in 1 tries 1.028067 Supported UPS detected with megatec protocol 1.028077 send: F 1.150426 received 21 (35) 1.150482 read: #220.0 000 012.0 50.0 1.150492 blazer_rating: short reply 1.150510 Rating read 1 failed 1.150520 send: F 1.273356 received 21 (35) 1.273397 read: #220.0 000 012.0 50.0 1.273402 blazer_rating: short reply 1.273407 Rating read 2 failed 1.273418 send: F 1.396336 received 21 (35) 1.3...

...are always padded to 64 bytes beyond \r payload terminator. When checking that command was successful (i.e. not echoed back) code relies on the response length reported by blazer_command which will always be 64. To fix this ippon_command should return actual payload length. This change also affects blazer_rating. Currently it assumes that battery voltage should be in %06.2f format, but in reality (and according to documentation) it may also look like %05.2f. > > You can merge this Pull Request by running > > git pull https://github.com/singular0/nut master > Or view, comment on, or...