search for: delinfo

...to the serial number, model and vendor names. By doing so, we would probably get more accurate information on especially the serial number, since this is located in non-standard locations for several subdrivers. If we get a match, we could be sure that this is the same device and need not DELCMD/DELINFO whatever we got already, but could simply update the pointers to the parsed report descriptor (which is a lot lighter on the load). Another thing is that we could probably reject devices (also, depending on whether a subdriver supports this) if they are not a UPS. We could easily check for this in...

...2442.111280 send_to_one: PONG 2445.566594 smsBR_RecAnswer: Started 2445.681823 smsBR_RecAnswer: Finished 2448.174522 send_to_one: PONG 2450.569001 smsBR_RecAnswer: Started 2450.684810 smsBR_RecAnswer: Finished 2450.684884 send_to_all: SETINFO output.voltage "0.0" 2450.684946 send_to_all: DELINFO ups.alarm 2450.684976 send_to_all: SETINFO ups.status "OL BYPASS" 2455.571353 smsBR_RecAnswer: Started 2455.686801 smsBR_RecAnswer: Finished 2455.686885 send_to_all: SETINFO ups.load "0.0" 2455.686931 send_to_all: SETINFO battery.runtime "0" 2460.576291 smsBR_RecAnswer...

Hello again! Sorry for not being able to test this before. Ulisses, please apply the patch to fix typo in my e-mail address. I've compiled it against nut-2.6.5 about 10 hours ago. It was everything fine until now. I'm seeing CHRG but the ups led wasn't blinking at all. Vendor software was strangely showing charging also. I am assuming this is expected behavior. I've set the

...input.voltage "240.0" 15.779532 command: (8 bytes) => 80 06 04 03 51 50 49 00 15.787384 send: QPI 16.789375 read: could not claim interface 0: Device or resource busy (-110) 16.789416 qx_process_answer: short reply (ups.firmware.aux) 16.789437 send_to_all: DELINFO input.voltage 16.789460 command: (8 bytes) => 80 06 03 03 51 31 00 2f 16.795377 send: Q1 17.011385 read [ 0]: (8 bytes) => 28 32 34 30 2e 30 20 30 17.019380 read [ 8]: (8 bytes) => 30 30 2e 30 20 32 33 39 17.027380 read [ 16]: (8 bytes) => 2e 30 20 30 30...

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