search for: send_to_on

...azer_usb-soyntec open on fd 5? ?4.115515 send_to_all: SETINFO driver.parameter.pollinterval "2"? ?4.116204 send: Q1? ?4.467429 read: (230.7 231.1 231.1 019 50.1 13.5 25.0 00001001? ?4.467466 send_to_all: SETINFO output.voltage "231.1"? ?5.838873 new connection on fd 6? ?5.838909 send_to_one: SETINFO battery.voltage "13.50"? ?5.838923 send_to_one: SETINFO battery.voltage.nominal "12.0"? ?5.838931 send_to_one: SETINFO beeper.status "enabled"? ?5.838939 send_to_one: SETINFO device.type "ups"? ?5.838947 send_to_one: SETINFO driver.name "blazer...

...r.parameter.pollinterval "2" 0.062505 send_to_all: SETINFO device.mfr "PPC" 0.062509 send_to_all: SETINFO device.model "USB UPS " 0.062513 upsdrv_updateinfo... 0.062516 Not using interrupt pipe... 0.062518 Quick update... 0.228313 new connection on fd 6 0.228325 send_to_one: SETINFO device.mfr "PPC" 0.228347 send_to_one: SETINFO device.model "USB UPS " 0.228350 send_to_one: SETINFO device.type "ups" 0.228354 send_to_one: SETINFO driver.flag.explore "enabled" 0.228375 send_to_one: SETINFO driver.flag.pollonly "enabled&q...

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

...ys returns "Error: Data stale" 3096.067419 smsBR_RecAnswer: Started 3098.069531 smsBR_RecAnswer: Exiting by timeout (2 seconds) 3098.069592 Communications with UPS lost: upsdrv_updateinfo: UPS at port /dev/ttyUSB0 is returning by timeout... 3098.069617 send_to_all: DATASTALE 3098.069699 send_to_one: PONG 3101.070466 smsBR_RecAnswer: Started 3103.072605 smsBR_RecAnswer: Exiting by timeout (2 seconds) 3103.072686 Communications with UPS lost: upsdrv_updateinfo: UPS at port /dev/ttyUSB0 is returning by timeout... 3106.073475 smsBR_RecAnswer: Started 3108.075605 smsBR_RecAnswer: Exiting by timeo...

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

...send_cmd: received 54 26 00 02 58 01 58 0d 'T...X.X.' (OK) 3139.498387 send_cmd(msg_len=2, type='P') 3139.500193 send_cmd: sending 3a 50 af 0d 00 00 00 00 '.P......' 3139.602964 send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.' (OK) 3139.604267 send_to_one: PONG 3139.606315 send_to_one: PONG 3139.608288 send_cmd(msg_len=2, type='S') 3139.608448 send_cmd: sending 3a 53 ac 0d 00 00 00 00 '.S......' 3139.711475 send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..' (OK) 3139.713276 send_cmd(msg_len=2, type=...

...upsdrv_updateinfo: NO-OP: input file was already read once to the end May 24 08:23:49 gateway dummy-ups[284580]: [D2] entering setvar(battery.runtime, 100) May 24 08:23:52 gateway dummy-ups[284580]: [D1] upsdrv_updateinfo... later changing charge May 24 08:37:28 gateway dummy-ups[284580]: [D2] send_to_one: sending PONG May 24 08:37:32 gateway dummy-ups[284580]: [D1] upsdrv_updateinfo... May 24 08:37:33 gateway dummy-ups[284580]: [D2] upsdrv_updateinfo: NO-OP: input file was already read once to the end May 24 08:37:33 gateway dummy-ups[284580]: [D2] entering setvar(battery.charge, 5) May 24 08:37...

...nput file was already read once to the end > May 24 08:23:49 gateway dummy-ups[284580]: [D2] entering setvar(battery.runtime, 100) > May 24 08:23:52 gateway dummy-ups[284580]: [D1] upsdrv_updateinfo... > > later changing charge > > May 24 08:37:28 gateway dummy-ups[284580]: [D2] send_to_one: sending PONG > May 24 08:37:32 gateway dummy-ups[284580]: [D1] upsdrv_updateinfo... > May 24 08:37:33 gateway dummy-ups[284580]: [D2] upsdrv_updateinfo: NO-OP: input file was already read once to the end > May 24 08:37:33 gateway dummy-ups[284580]: [D2] entering setvar(battery.charge, 5)...

Hmm. Is there maybe something there already that will do this? Maybe kind of back-handed. In drivers/dstate.c, I see: In status_init(), if ?driver.flag.ignorelb? is set in the driver state, the ?ignorelb? flag is set. In status_set(), if ignorelb is set, and the status being set (presumably from the UPS) is LB, it?s ignored. In other words, LB reported by the UPS is ignored. In status_commit(),