search for: ups_infoval_set

...StringIdx=0, buf=0x40204 <buf> > "", buflen=20) at libusb.c:496 > #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, > Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) > at libhid.c:407 > #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, > value=<optimized out>) at usbhid-ups.c:1552 > #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 > #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at > main.c:708 You did everything right on the ba...

...t;>> "", buflen=20) at libusb.c:496 >>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >>> at libhid.c:407 >>> #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, >>> value=<optimized out>) at usbhid-ups.c:1552 >>> #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 >>> #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at >>> main.c:708 &gt...

...y UPS. (The manual describes fixed timeouts in the pinout section, so that makes sense.) 9.562389 Using protocol: BestUPS 0.01 9.562405 upsdrv_initinfo... 9.562480 send: 'Q1' 9.772351 read: '(119.0 118.1 118.1 020 60.0 13.9 XX.X 00101000' 9.772424 ups_infoval_set: non numerical value [ups.temperature: XX.X] 9.772530 send: 'ID' 9.896340 read: 'PR2,400,120,120,10.8,13.6' 9.896482 send: 'RT' 9.927323 read: '053' 9.927433 send: 'SS?' 10.928470 read: timeout (0) 10.928491 qx_p...

...cess_answer: short reply (input.voltage) 0.125613 send: QGS 0.178743 read: (NAKss 0.179162 qx_process_answer: short reply (input.voltage) 0.181615 send: M 0.226746 read: (NAKss 0.227193 voltronic_qs_protocol: invalid protocol [(NAKss] 0.227609 ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAKss] 0.231126 send: M 0.274751 read: (NAKss 0.275170 voltronic_qs_protocol: invalid protocol [(NAKss] 0.275566 ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAKss] 0.277877 send: M 0.3227...

...40204 <buf> >> "", buflen=20) at libusb.c:496 >> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >> at libhid.c:407 >> #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, >> value=<optimized out>) at usbhid-ups.c:1552 >> #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 >> #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at >> main.c:708 > > You did e...

Thank you for your reply Charles, this is the "upsc" result: root at artu:~# upsc ups at localhost Init SSL without certificate database Error: Unknown UPS Trying with nutdrv_qx, protocol megatec the driver does not start... 2017-06-08 14:47 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote:

...20) at libusb.c:496 >>>>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>>>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >>>>> at libhid.c:407 >>>>> #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, >>>>> value=<optimized out>) at usbhid-ups.c:1552 >>>>> #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 >>>>> #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at &gt...

...;", buflen=20) at libusb.c:496 >>>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >>>> at libhid.c:407 >>>> #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, >>>> value=<optimized out>) at usbhid-ups.c:1552 >>>> #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 >>>> #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at >>>&gt...

...or about five seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this: > > 228.304623 send: 'Q1' > 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010' > 228.515494 ups_infoval_set: non numerical value [ups.temperature: XX.X] > 228.515506 blazer_process_status_bits: output voltage too low > 228.515510 Communications with the UPS lost: status read failed! > > Similarly, when I unplugged the unit around t=638, I also got "data stale" messages fro...

....voltage.fault "239.1" 0.807235 send_to_all: SETINFO output.voltage "244.2" 0.807256 send_to_all: SETINFO ups.load "5" 0.807291 send_to_all: SETINFO input.frequency "50.0" 0.807312 send_to_all: SETINFO battery.voltage "27.40" 0.807331 ups_infoval_set: non numerical value [ups.temperature: --.-] 0.807347 update_status: OL 0.807375 update_status: !LB 0.807398 send_to_all: SETINFO ups.type "offline / line interactive" 0.807426 update_status: !CAL 0.807442 update_status: !FSD 0.807459 send_to_all: SETINFO ups.beeper.stat...

> I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. > > It looks like things mostly work: Nice, merging bestups.c into nutdrv_qx has been on my todo list for a while, let's see how far we can get. > 1) The bestups driver uses an "ID"

Thank you for the rapid response. I will try and investigate getting answers to some of your points but I'm a little new to Solaris so I'll need some time. Glancing at the configure output, it looks like it built against v0.1.7 of libusb (yes i think that is derived from the one you mention), checking for libusb version via pkg-config... 0.1.7 found checking for libusb cflags... checking

...00}) = 1 (out [4], left {0, 944}) ioctl(4, USBDEVFS_REAPURBNDELAY, 0x7ffdca143278) = 0 write(2, " 42.693227\t", 12) = 12 write(2, "read: (224.4 224.4 224.4 007 50.0 13.7 --.- 00001001\n", 53) = 53 write(2, " 42.693517\t", 12) = 12 write(2, "ups_infoval_set: non numerical value [ups.temperature: --.-]\n", 61) = 61 %<------------%<------------%<------------%<------------ I downloaded the code and patched and compiled myself. Using some "sleeps" it goes better, but not so fine I would like: %<------------%<------------...

...0.567668 qx_process_answer: short reply (input.voltage) 0.567965 send: QGS 0.568256 read: QGS 0.568609 qx_process_answer: short reply (input.voltage) 0.568952 send: M 0.569310 read: M 0.569498 voltronic_qs_protocol: invalid protocol [M] 0.569678 ups_infoval_set: failed to preprocess value [ups.firmware.aux: M] 0.569866 send: M 0.570071 read: M 0.570262 voltronic_qs_protocol: invalid protocol [M] 0.570460 ups_infoval_set: failed to preprocess value [ups.firmware.aux: M] 0.570653 send: M 0.570834 read: M 0.571024...

Hi Daniele, I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. It looks like things mostly work: bestups: battery.charge: 100.0 battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: Best Power device.model: Patriot Pro II 400 device.type: ups

On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Hi Charles. I patched, reconfigured, remake'd, remake install'd - but > no change. however, some more likely helpful information below for > you. Thank you Odd. Are you sure that the new version of usbhid-ups got installed to the same path you are running? Also, there is no protection against

...imit was broken on Belkin, we decided to go with UPS.BELKINStatus.BELKINBatteryStatus instead, which is a variable that is *not* sent on the interrupt pipeline. In general, not every UPS that uses the interrupt pipeline can be trusted to send all important values on it. -- Peter > - Added a ups_infoval_set() function that is doing the actual setting of values we got from the UPS. This is convenient, so that if we change something in the way we deal with those, it is all in one location.

...seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this: >> >> 228.304623 send: 'Q1' >> 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010' >> 228.515494 ups_infoval_set: non numerical value [ups.temperature: XX.X] >> 228.515506 blazer_process_status_bits: output voltage too low >> 228.515510 Communications with the UPS lost: status read failed! >> >> Similarly, when I unplugged the unit around t=638, I also got "data stale&quo...

...20 20 20 20 20 20 20 20 20.403380 read [ 16]: (8 bytes) => 20 32 30 30 30 56 41 20 20.411383 read [ 24]: (8 bytes) => 20 20 20 20 56 32 2e 30 20.419387 read [ 32]: (8 bytes) => 20 20 20 20 20 20 0d 00 20.419412 read: # 2000VA V2.0 20.419541 ups_infoval_set: non significant value [device.mfr] 20.419572 send_to_all: SETINFO device.model "2000VA" 20.419591 send_to_all: ADDCMD beeper.toggle 20.419607 send_to_all: ADDCMD load.off 20.419633 send_to_all: ADDCMD load.on 20.419649 send_to_all: ADDCMD shutdown.return 2...

...get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> "", buflen=20) at libusb.c:496 #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) at libhid.c:407 #2 0x00012e18 in ups_infoval_set (item=0x3ee48 <tripplite_hid2nut>, value=<optimized out>) at usbhid-ups.c:1552 #3 0x00013da8 in upsdrv_updateinfo () at usbhid-ups.c:835 #4 0x00012410 in main (argc=<optimized out>, argv=<optimized out>) at main.c:708