search for: pollinterv

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and get the same behavior. With the driver usbhid-ups, what is the relationship between pollfreq and pollinterval? It looks like pollinterval overrides pollfreq. u...

...dups directly, and noticed that the poll frequency of the dstate_poll_fds() calls in main.c can be heavily skewed by the timeout provided in the libusb_get_interrupt() call in libhid.c (currently 5 sec!). For a UPS that provides few interrupt messages, this may result in a behavior equivalent to a pollinterval of 5 or more for any pollinterval settings of less than 5. Since pollinterval is generic for all types of UPS's, may I suggest that the timeout in libhid.c be significantly reduced (50 ms would affect even a pollinterval of 1 by at most 5 %). Unfortunately this change does not address a...

Hello, Some more data about my experiences with riello_ups on iDialog 800 In orderr to avoid "stale data" problems, i tried to increase pollinterval in ups.conf: ==== ups.conf ===== pollinterval = 4 maxretry = 3 [idg800] driver = riello_usb port = auto desc = "idg800" =================== It seems that pollinterval is ignored by the driver: # upsc idg800 | grep poll Init SSL without certificate database driver.parameter.pollin...

...ice name and related information Eaton 5PX 1500 * Problem description Not a problem, just an observation. I made a program to monitor my UPS, the final objective is to implement a power use totalizer, and wanted to see which polling frequency is the minimum required. Read about pollfreq, and pollinterval, but didn't see NUT's code. The values of those are: driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 5 I found that power consumption (ups.realpower) only changes every 35 seconds, which is (pollfreq + pollinterval). Does this looks correct? I would expect changes at poll...

On Nov 18, 2014, at 6:28 PM, Shade Alabsa <shade34321 at gmail.com> wrote: > I then noticed that in ups.conf I did not set the pollinterval, we normally set it to 15, so I set it to test on a RHEL 6.6 machine which caused this issue to happen again. On our own custom system we took the poll interval out and prelim testing doesn't showing the repeated disconnects/reconnects. I started playing more with this pollinterval and notice...

...2017, at 1:36 PM, Ren? Berber <rberber at fastmail.fm> wrote: > My guess is that they are the same version (Synology keeps it updated). Is there a way to check which version they are using? (Just curious - probably will not affect the problem you described.) > Read about pollfreq, and pollinterval, but didn't see NUT's code. The usbhid-ups code is here: https://github.com/networkupstools/nut/blob/v2.7.4/drivers/usbhid-ups.c#L851-L871 > The values of those are: > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 5 > > I found that power consumption...

...using the problem but as of right now we are unsure as to why it might be causing the issue. Recently I had to restart testing this to figure it out and for some odd reason I wasn't able to reproduce it with any system but our own custom system. I then noticed that in ups.conf I did not set the pollinterval, we normally set it to 15, so I set it to test on a RHEL 6.6 machine which caused this issue to happen again. On our own custom system we took the poll interval out and prelim testing doesn't showing the repeated disconnects/reconnects. I started playing more with this pollinterval and notice...

...is disconnecting due to inactivity on the bus. Thanks! Shade On Tue, Nov 18, 2014 at 8:40 PM, Charles Lepple <clepple at gmail.com> wrote: > On Nov 18, 2014, at 6:28 PM, Shade Alabsa <shade34321 at gmail.com> wrote: > > > I then noticed that in ups.conf I did not set the pollinterval, we > normally set it to 15, so I set it to test on a RHEL 6.6 machine which > caused this issue to happen again. On our own custom system we took the > poll interval out and prelim testing doesn't showing the repeated > disconnects/reconnects. I started playing more with this pol...

...imes I received a lot of log messages with USB timeouts. It might work 2 hours or 2 days w/o them, and then a lot of such errors. NUT restart helped, so they were not a VM/host hardware problems. As suggested everywhere, I tried to change timeouts. Pollfreq made no changes. But changing the driver pollinterval to 10 (instead of default 2) has helped. No more timeouts were received. But suddenly I found that now NUT does not see OnBattery events at all. If I pull the power cord from UPS, it immediately reports input voltage = 0, but still "is" OnLine. I found that very weird but started to pla...

On Sep 19, 2017, at 9:50 PM, Ren? Berber <rberber at fastmail.fm> wrote: > > On 9/19/2017 6:45 PM, Charles Lepple wrote: > >> On Sep 19, 2017, at 1:36 PM, Ren? Berber wrote: > >>> My guess is that they are the same version (Synology keeps it updated). >> >> Is there a way to check which version they are using? (Just curious - probably will not

...20 battery.mfr.date: CPS battery.runtime: 450 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 139 input.transfer.low: 88 input.voltage: 117.0 input.voltage.nominal: 120 output.voltage: 117.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.de...

Dear NUT users and contributors, The first round on the new NUT website is mostly done: http://new.networkupstools.org The general layout has changed a bit to overcome some navigation issues. The Hardware Compatibility List is also finalized, using actual data and providing a static version for browser without JavaScript. There are still a few things remaining, and most of all the conversion of

It looks like I'm currently on 4.4.0-38 uname -a: Linux kvm 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux On Mon, Oct 10, 2016 at 10:04 PM, Charles Lepple <clepple at gmail.com> wrote: > > On Oct 6, 2016, at 7:26 PM, Lane Russell <lanerussell028 at gmail.com> wrote: > > Ubuntu Server 16.04.1 LTS > NUT 2.7.2-4ubuntu1

On 9/19/2017 6:45 PM, Charles Lepple wrote: > On Sep 19, 2017, at 1:36 PM, Ren? Berber wrote: >> My guess is that they are the same version (Synology keeps it updated). > > Is there a way to check which version they are using? (Just curious - probably will not affect the problem you described.) None I could find, tried strings, might try telnet but my guess is that it will spew

...ttery.charge: 100 battery.current: 0.4 battery.date: 12292015 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 00 battery.voltage: 163.4 device.mfr: NHS Sistemas de Energia device.model: Laser Senoidal 5000VA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 20 driver.parameter.port: /dev/ttyACM2 driver.version: 2.6.3 driver.version.internal: 0.02 input.frequency: 59.9 input.transfer.high: 144 input.transfer.low: 096 input.voltage: 127.6 input.voltage.nominal: 120 output.current: 0.0 output.frequency: 60.0 output.voltage: 119.1 ups.firmw...

...ry.runtime.low: 300 battery.temperature: 36.0 battery.type: PbAc battery.voltage: 25.7 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Smart-UPS 1500 device.serial: ASXXXXXXXXXX device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.2 driver.version.data: APC HID 0.95 driver.version.internal: 0.38 input.sensitivity: high input.transfer.high: 253 input.transfer.low: 208 input.transfer.reason: input voltage out of range input.voltage: 233.2 output.frequency: 50.0 output.voltag...

This unit works fine with the "cyberpower" driver (which reports it as "Unknown model - 15"). It reads this much from it: battery.charge : 100 driver.name : cyberpower driver.parameter.pollinterval : 2 driver.parameter.port : /dev/ttyS0 driver.version : 2.2.0- driver.version.internal : 1.00 input.frequency : 60.2 input.voltage : 121 ups.firmware : 5.100 ups.load : 024 ups.mfr : CyberPower ups.model : Unknown model - 15 ups.status : OL ups.temperature : 36.0 Th...

...e", SUBSYSTEMS=="usb|usb_device", ATTR{idVendor}=="09ae", ATTR{idProduct}=="2012", MODE="664", GROUP="nut", RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl start" LABEL="nut-usbups_rules_end" My ups.conf: # /etc/nut/ups.conf pollinterval = 1 [ups] driver = usbhid-ups port = auto desc = "Tripp Lite SMART1500LCD" vendorid = 09ae productid = 2012 And I also removed MTP as it was trying to take the device. sudo apt-get remove --auto-remove libmtp-common On Mon, Dec 9, 2019 at 10:04 PM Layne Fowler <layne.fowler at gm...

...s. The problem is that it's constantly losing connection with the UPS because it keeps falling off the bus and coming back immediately (under a different device number). On /var/log/syslog I have block after block of this, each precisely separated by the same time interval (which gets longer if pollinterval grows): Feb 17 06:12:52 myhost kernel: [322433.317805] usb 3-7: USB disconnect, device number 40 Feb 17 06:12:52 myhost kernel: [322433.797116] usb 3-7: new low-speed USB device number 41 using xhci_hcd Feb 17 06:12:52 myhost kernel: [322433.825669] usb 3-7: New USB device found, idVendor=06da,...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though