search for: qgs

...known 1.852830 - Product: STD UPS MON V1.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 re...

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:

...umber: unknown > 0.014875 - Bus: 001 > 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...

...duct: 010937 0.561457 - Serial Number: 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 re...

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

...0.012525 - Serial Number: unknown 0.012558 - 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...

...- Bus: 002 1.032963 Trying to match device 1.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_answ...

...e up after the witheout, he has problems that seem to be related to a specific sequence of commands, but I don't think that's the case with you. The 841+: as it comes with ViewPower, I suppose it's manufactured by Voltronic Power; if that is the case *and* your unit is using their 'QGS' ('voltronic' in NUT) protocol, maybe the UPS has the 'Auto Reboot' (in Voltronic Power's ViewPower) option disabled or 'ups.delay.start' (in NUT, using the new nutdrv_qx driver with protocol=voltronic) option set to 'no'. Can you please launch the driver wi...

...12.131568 Status read 3 failed 12.131578 No supported 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: timeou...

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:

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

...river with debug level = 3 and send the logs of when you execute the command shutdown.return via upscmd? I saw your new UPS is shipped with ViewPower (developed by Voltronic Power, mainly for their UPSes), so, if it's manufactured by Voltronic Power maybe it's using their new protocol 'QGS' (mapped as 'voltronic' in the new driver nutdrv_qx - available in 2.7.1) or one of their other ones. Maybe the command itself is accepted by the UPS, but since it may use '(ACK'/'(NAK' replies instead of the 'ACK'/'echoing back' of Q1 units the driver se...

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

...0.398627 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 0.398652 send_to_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 re...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there! I don't know if you are able to help me. Have tried almost everything at this point.. I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD 2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD 1500VA Online UPS. Seems like the driver is accepting both, however, the shutdown command wont work. And this

Thanks for your reply Hyouko, these are the actual not working parameters: driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 ups.delay.shutdown: 60 ups.delay.start: 300 and the UPS don't wake up after the whiteout.. My UPS is not so old :( Il 09/12/2013 16.04, hyouko at gmail.com ha scritto: > 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: >> Hi all, > Hi

2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > Hi all, Hi > I've problem with the management of my AtlantisLand UPS, the UPS don't want > to wake up after the whiteout and I don't have any idea why.. Some (very old) units are known to have problems with small values for ondelay (hence the default 3 minutes value):

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

...3 00000001 *UPS status (input V, fault V, output V, load, output freq, batt voltage, UPS temp, flags -> 8 bit) [QS] (209.7 209.7 219.7 020 50.0 41.8 23.3 00000001 *UPS status (new) (in V, in F, out V, out F, out Current, load, unknown1, unknown2, batt volt, unknown3, UPS temp, flags->12 bit) [QGS] (209.7 50.0 219.7 50.0 000.8 019 374.9 374.3 041.8 ---.- 023.3 100000000001 *Battery status (Batt Volt, Nr of batt packs, Nr of batt packs in parallel, %battery charge, expected runtime in minutes) [QBV] (041.8 03 01 100 058 *Wide battery status ??? less battery less zeroes ??? [QWS] (000000000000...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking