On Sunday 12 January 2020 11:14:13 Charles Lepple wrote:> On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > >> Instant return, logging this: > > > > in /tmp/info > > > >> 0.000000 Error: too many non-option arguments. Try -h for > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > >> USB communication driver 0.33 > > > > This I assumed was with nut-server and nut-client, both stopped, > > which they had been. Was that incorrect? > > You are correct, with both nut-server and nut-client stopped. > > I should not have been lazy, and I should have just pasted the command > line I was thinking of: > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > (I was looking at the hid-subdrivers.txt file in the latest NUT tree, > which has the command line amended to not generate that "too many > non-option arguments" error. Also, I wanted it to use the existing > cps-hid.c tables, not the generic "explore" sub-driver.)Attached, about 30 seconds worth Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> -------------- next part -------------- A non-text attachment was scrubbed... Name: CP625HGa.txt.gz Type: application/x-gzip Size: 6191 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200112/86fdcfb9/attachment.bin>
On Sunday 12 January 2020 12:09:04 Gene Heskett wrote:> On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > > >> Instant return, logging this: > > > > > > in /tmp/info > > > > > >> 0.000000 Error: too many non-option arguments. Try -h for > > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > >> USB communication driver 0.33 > > > > > > This I assumed was with nut-server and nut-client, both stopped, > > > which they had been. Was that incorrect? > > > > You are correct, with both nut-server and nut-client stopped. > > > > I should not have been lazy, and I should have just pasted the > > command line I was thinking of: > > > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > > > (I was looking at the hid-subdrivers.txt file in the latest NUT > > tree, which has the command line amended to not generate that "too > > many non-option arguments" error. Also, I wanted it to use the > > existing cps-hid.c tables, not the generic "explore" sub-driver.) > > Attached, about 30 seconds worth > > Cheers, Gene HeskettI should add that its -wall broadcast did exactly what I wanted in the night last night: --------------------------- Broadcast message from nut at rpi4 (somewhere) (Sun Jan 12 01:15:04 2020): UPS myups at localhost on battery Broadcast message from nut at rpi4 (somewhere) (Sun Jan 12 01:15:14 2020): UPS myups at localhost on line power Broadcast message from nut at rpi4 (somewhere) (Sun Jan 12 01:54:00 2020): UPS myups at localhost on battery Broadcast message from nut at rpi4 (somewhere) (Sun Jan 12 01:54:10 2020): UPS myups at localhost on line power -------------------------- Two power failures, weather related I assume as I slept thru them. A heavy rain went by on its way to the right coast. My generator starts a couple seconds faster than the 10 seconds shown here, but thats plenty good enough for the girls I go with. The transfer back to true line power as the generator shuts down is invisible. But this doesn't pass the smell test, 3 other machines that are trained to reboot when power returns and have no ups fitted, were NOT rebooted as evidenced by their reported uptimes, one of which shows a 144 day uptime. So why should this have been logged via a -wall bc to every login it is servicing? There was no power failure IOW. Enquiring minds want to know. Maybe this is why it was so cheap, it has buggy firmware? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
On Sunday 12 January 2020 12:09:04 Gene Heskett wrote:> On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > > >> Instant return, logging this: > > > > > > in /tmp/info > > > > > >> 0.000000 Error: too many non-option arguments. Try -h for > > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > >> USB communication driver 0.33 > > > > > > This I assumed was with nut-server and nut-client, both stopped, > > > which they had been. Was that incorrect? > > > > You are correct, with both nut-server and nut-client stopped. > > > > I should not have been lazy, and I should have just pasted the > > command line I was thinking of: > > > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > > > (I was looking at the hid-subdrivers.txt file in the latest NUT > > tree, which has the command line amended to not generate that "too > > many non-option arguments" error. Also, I wanted it to use the > > existing cps-hid.c tables, not the generic "explore" sub-driver.) > > Attached, about 30 seconds worth >Was that enough to get it all?> Cheers, Gene HeskettCheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
On Jan 12, 2020, at 12:58 PM, Gene Heskett wrote:> > But this doesn't pass the smell test, 3 other machines that are trained > to reboot when power returns and have no ups fitted, were NOT rebooted > as evidenced by their reported uptimes, one of which shows a 144 day > uptime. So why should this have been logged via a -wall bc to every > login it is servicing? > > There was no power failure IOW.The thing is that many UPS models will report "on battery" when the voltage fluctuates out of range, but a switching power supply might still be able to coast through it-- especially if the supply is oversized for the load at the time of the abnormality. Since both "outages" (really, the on-battery states) were exactly 10 seconds long means that the UPS was probably trying to "debounce" the voltage fluctuation by not switching back to line power immediately after the voltage went back to normal. For APCs and MGEs, I think it is typically 5 seconds. Several people have rigged up longer timers with upssched to not send the wall message until it has been on battery for, say, a full minute.
On Jan 13, 2020, at 10:17 PM, Gene Heskett wrote:> >>> (I was looking at the hid-subdrivers.txt file in the latest NUT >>> tree, which has the command line amended to not generate that "too >>> many non-option arguments" error. Also, I wanted it to use the >>> existing cps-hid.c tables, not the generic "explore" sub-driver.) >> >> Attached, about 30 seconds worth >> > Was that enough to get it all?I should probably just ask for 60 seconds in the future :-) There are nearly 30 seconds' worth of "Quick update..." lines, but because the 30-second timer doesn't start until after everything is initialized (takes a few seconds at USB 1.1 speeds...), the "Full update..." line isn't there. But no matter, it is quite similar to the CPS SX650g dump - the HID report is byte-for-byte the same. Notably, the "hidrd-convert" tool fails part of the way through parsing it, which is why I suspect that CPS is not following the HID spec. (That's more applicable for the high/low transfer voltages.) It does seem to be reporting 0% load, though: 0.094786 Report[get]: (3 bytes) => 13 00 00 0.094875 Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 0 0.094908 Report[buf]: (3 bytes) => 13 00 00 0.095318 Path: UPS.Output.Overload, Type: Feature, ReportID: 0x13, Offset: 8, Size: 1, Value: 0