search for: qx_process_answ

....033077 Device matches 1.033218 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 1.033353 send_to_all: SETINFO ups.vendorid "0665" 1.033473 send_to_all: SETINFO ups.productid "5161" 1.058070 send: QGS 2.060333 read: No error (-110) 2.060857 qx_process_answer: short reply (input.voltage) 2.080004 send: QGS 3.083062 read: No error (-110) 3.083557 qx_process_answer: short reply (input.voltage) 3.103189 send: QGS 4.105282 read: No error (-110) 4.105819 qx_process_answer: short reply (input.voltage) 4.116063 send: M 5.11927...

...ported UPS detected for ./nutdrv_qx -DDDDD -a infosec 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" 0.000472 debug level is '5' 0.004317 upsdrv_initups... 0.106821 send: 'QGS' 1.108364 read: timeout (0) 1.108647 qx_process_answer: short reply (input.voltage) 1.109384 send: 'QGS' 2.110945 read: timeout (0) 2.111125 qx_process_answer: short reply (input.voltage) 2.111446 send: 'QGS' 3.112802 read: timeout (0) 3.113027 qx_process_answer: short reply (input.voltage)...

...; 0.014961 Trying to match device > 0.015172 Device matches > 0.015305 failed to claim USB device: could not claim interface 0: Device > or resource busy > 0.015942 detached kernel driver from USB device... > 0.017534 send: QGS > 0.152570 read: N > 0.153407 qx_process_answer: short reply (input.voltage) > 0.154812 send: QGS > 0.289577 read: N > 0.290254 qx_process_answer: short reply (input.voltage) > 0.291575 send: QGS > 0.426589 read: N > 0.427286 qx_process_answer: short reply (input.voltage) > 0.428596 send: M > 0.5...

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM:

...8 - Bus: 001 0.012589 Trying to match device 0.012631 Device matches 0.014418 send_to_all: SETINFO ups.vendorid "0665" 0.014498 send_to_all: SETINFO ups.productid "5161" 0.016598 send: QGS 0.066738 read: (NAKss 0.067218 qx_process_answer: short reply (input.voltage) 0.069610 send: QGS 0.122744 read: (NAKss 0.123221 qx_process_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...

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:

...1.0 1.852887 - Serial Number: unknown 1.852978 - Bus: 004 1.853042 Trying to match device 1.853107 Device matches 1.856636 First supported language ID: 0x409 (please report to the NUT maintainer!) 1.856760 send: QGS 1.856818 read: QGS 1.856932 qx_process_answer: short reply (input.voltage) 1.857046 send: QGS 1.857112 read: QGS 1.857185 qx_process_answer: short reply (input.voltage) 1.857259 send: QGS 1.857318 read: QGS 1.857379 qx_process_answer: short reply (input.voltage) 1.857468 send: QS 1.857524...

Hello i need your help regarding the following issue : i have a hero touch ups from infosec. it is connected via USB to a raspberry pi 3. i?ve configure ups.conf file as below [HERO] driver = blazer_usb vendorid = 0665 productid = 5161 either with port = auto or port = /dev/hidraw0 or port = /dev/ttySo the connection never works i get the

...0.561461 - Bus: 004 0.561466 Trying to match device 0.561473 Device matches 0.565355 send_to_all: SETINFO ups.vendorid "ffff" 0.565815 send_to_all: SETINFO ups.productid "0000" 0.566137 send: QGS 0.566421 read: QGS 0.566708 qx_process_answer: short reply (input.voltage) 0.567007 send: QGS 0.567377 read: QGS 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...

...all: SETINFO ups.vendorid "0001" 0.398667 send_to_all: SETINFO ups.productid "0000" 0.398711 command: (8 bytes) => 80 06 04 03 51 47 53 00 0.403387 send: QGS 1.406382 read: could not claim interface 0: Device or resource busy (-110) 1.406443 qx_process_answer: short reply (input.voltage) 1.406477 command: (8 bytes) => 80 06 04 03 51 47 53 00 1.411388 send: QGS 2.413380 read: could not claim interface 0: Device or resource busy (-110) 2.413421 qx_process_answer: short reply (input.voltage) 2.413452 command: (8 byte...

On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at gmail.com> wrote: > Come on, it started to be interesting! Do you have one of these UPSes? If so, here was Dan's email about a branch to test: > If you still can't get it to work with nutdrv_atcl_usb, another > approach could be worth considering. > > Since this UPS seems to be supported by UPSmart2000I, it could

Hi Thank you very much for the feedback. I will download and try to get it working on the Raspberry Pi. Regards Tom On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as > the > > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I > am > >

...d with the latter: 0.007855 Trying to match device 0.007893 Device matches 0.007920 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 0.007944 command: (8 bytes) => 80 06 04 03 51 47 53 00 5.009814 send: Connection timed out (-110) 5.009856 qx_process_answer: short reply (input.voltage) 5.009884 command: (8 bytes) => 80 06 04 03 51 47 53 00 10.012265 send: Connection timed out (-110) 10.012298 qx_process_answer: short reply (input.voltage) 10.012313 command: (8 bytes) => 80 06 04 03 51 47 53 00 15.013766 send: Con...

On Feb 14, 2015, at 2:43 PM, J Neethling <jneethling at webmail.co.za> wrote: > 67611 blazer_usb CALL write(0x2,0x7fffffffd2a0,0xc) > 67611 blazer_usb GIO fd 2 wrote 12 bytes > " 0.280697 " > 67611 blazer_usb RET write 12/0xc > 67611 blazer_usb CALL write(0x2,0x7fffffffd2a0,0x35) > 67611 blazer_usb GIO fd 2 wrote 53 bytes >

...Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) > USB communication driver 0.32 > 0.000000 debug level is '5' ... > 0.574759 send: Q1 > 0.807418 received 46 (40) > 0.807475 read: (225.3 140.0 222.6 015 49.9 13.8 30.0 00001001 > 0.807516 qx_process_answer: short reply (input.voltage) hmm, apparently the UPS doesn't close the replies to our queries with the expected CR and we (I) did not consider that case in nutdrv_qx -- noted: https://github.com/networkupstools/nut/issues/441 But blazer_usb, being less strict on the terminating CR of Q1 rep...

> 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"

..._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_process_answer: short reply (pins_shutdown_mode) The set of instcmds looks good: $ upscmd -l ppro2 Instant commands supported on UPS [ppro2]: shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress test....

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

Hi all, I'm a new user trying to get a Proline UPS I1000 UPS to work with freenas 9.3 over USB. When running upsdrvctl I get a permission denied error. Required debug info: OS name and version, # uname -a FreeBSD freenas.local 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #2 r275790+f84e770: Tue Dec 23 23:35:33 PST 2014 root at