search for: pollonly

Hello, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" I've been looking for "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are these interrupts ? What exactly may not work ? Regards. -- Fr...

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in the usbhid-ups man page, but it didn't > help me. > Only add pollonly to your ups.conf ex: [APC] driver = usbhid-ups port = auto pollonly...

Hello, Yes, "pollonly" is a driver option for certain devices (and relevant to just some drivers). Disconnects are probably relevant, at least to loss of connection (and staying that way, with less agressive retries in NUT v2.7.4 and before). There is a logged issue that "pollonly" mode might have troubl...

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto pollonly...

...in frequent lost comms. The USB Interrupt channel is being reserved in 5G UPSs for a proprietary protocol. In order to enable Nut to communicate with the UPS, a poll only configuration is required. The details of my ups.conf file are as follows: [apc] driver = usbhid-ups port = auto pollonly = 1 Thanks, -Chris Collins Chris Collins | APC by Schneider Electric | Senior Software Engineer Phone: +353-91-702000 x2661 | Mobile: +353-87-4189477 Email: chris.collins at apcc.com | Address: City East Business Park, Ballybrit, Galway, IRELAND *** Please consider the environment befor...

...-sles last message repeated 3 times If I run usbhid-ups, upsd and upsmon as the root user, I get... Feb 21 12:55:02 g540-sles usbhid-ups[15701]: libusb_get_interrupt: No error Feb 21 12:55:34 g540-sles last message repeated 8 times Feb 21 12:55:50 g540-sles last message repeated 4 times If I use pollonly=1 in the ups.conf no errors at all, and all works. I haven't tried the pollonly option on the RS232 models. So, I am assuming I do have a permissions error with udev and am slowing working my way through that, but struggling. Are these syslog messages important? Should they be logging if...

...------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left on device SOLUTION: pollonly in ups.conf II) Can not disable beeper (seems to be a general problem with usbhid-ups driver): --- upscmd -uMY_USER -pMY_PASSWORD 3s beeper.disable 'OK' returned, but no effect III)UPS doesn't wait for LB flag: --- a) 1st attempt: (based on LB flag) My ups.conf: [3s] driver = usbhi...

...y 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. usbhid-ups -a ups -DDDDD -x pollfreq=30 -i 30 2>&1 | egrep '(update|ups.status)' 8.580411 upsdrv_updateinfo....

Hello, On one hand, sorry to hear that higher polling frequency in upsmon did not help. On another, question is if the driver gets the info (online state and its changes) from device quickly enough. Initially I meant for you to also try if the "pollonly" flag (in each device section of ups.conf for usbhid-ups instances) would make a difference?.. I'd expect data-transfer interrupts to be less laggy - but that's as long as they work reliably or at all, which may rely on whole chain from vendor firmware implem to chips, hubs, OS drivers...

...ry a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is automatic (no subdriver param), as i read source code this driver uses usb manufacture signature (vendorid/productid) to choose subdriver so there was no chance to more tests, just few params (pollonly, pollfreq, maxreport). But... Help needed ! OS: Debian Jessie (Proxmox 4.3 distro) NUT: 2.7.2 driver: usbhid-ups #cat ups.conf [ups] driver = usbhid-ups port = auto vendorid = 06da productid = 0005 pollonly pollfreq = 15 # lsusb Bus 001 Device 003: ID 06da:0005 Phoenixtec Power Co., L...

...oo many kernel logs: > --- > In /var/log/kernel.log > usbdevfs: usb_submit_urb returned -28 > > In /var/log/daemon.log: > usbhid-ups[744]: libusb_get_interrupt: No error > usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left on device > > SOLUTION: pollonly in ups.conf > > II) Can not disable beeper (seems to be a general problem with usbhid-ups driver): > --- > upscmd -uMY_USER -pMY_PASSWORD 3s beeper.disable > 'OK' returned, but no effect > > III)UPS doesn't wait for LB flag: > --- > > a) 1st attempt: (ba...

On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309001233" > desc = "MIDAPC" > [BOTAPC] > driver = usbhid-ups...

...dex. I would like to change this behavior. For all report descriptors that I could find, the input- and feature reports seem to cover the same variables, so there shouldn't be a problem to do this. In case this would be a problem, there is still a workaround possible by adding the 'pollonly' flag to ups.conf, which will make the driver ignore input reports altogether. Any objections? Best regards, Arjen -- Please keep list traffic on the list

...e "upsc myups" and get a status report?? Its been years since I >> dived thru all these flaming hoops the last time. >> >> Thanks. > Found the help on the web pages, and upsc is working. But I've an odd > msg at startup: > interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message) > > However, any attempt to add it to the [myups] stanza in ups.conf is a > showstopper error. No mention of this "flag" in the rest of the file's comments. So how does that syntax actually look like? >&...

...many kernel logs: > --- > In /var/log/kernel.log > usbdevfs: usb_submit_urb returned -28 > > In /var/log/daemon.log: > usbhid-ups[744]: libusb_get_interrupt: No error > usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left > on device > > SOLUTION: pollonly in ups.conf > > II) Can not disable beeper (seems to be a general problem with usbhid-ups > driver): > --- > upscmd -uMY_USER -pMY_PASSWORD 3s beeper.disable > > 'OK' returned, but no effect > > III)UPS doesn't wait for LB flag: > --- > > a) 1st attem...

Hi, folks! There is FreeBSD 7.1, NUT 2.4.1, UPS APC Smart 2200 XL. NUT is compiled from ports with following options: --------------------------------------- _OPTIONS_READ=nut-2.4.1_5 WITH_SERIAL=true WITH_USB=true WITH_SNMP=true WITHOUT_NEON=true WITHOUT_PDU=true WITHOUT_HAL=true WITHOUT_IPV6=true WITHOUT_CGI=true --------------------------------------- UPS is successfully recognized by OS

...-C is sufficient) and re-run the driver with line power turned off. > 0.355333 upsdrv_updateinfo... > 0.607995 libusb_get_interrupt: Connection timed out > 0.608075 Got 0 HID objects... ... > Keeps going the same all the time... This part is disappointing, but we have a "pollonly" workaround. You can try it now, but I don't think it works with the "explore" sub-driver, since pollonly iterates over a list of known HID Path IDs, and we haven't added that yet. Before we set that up, I think we need to verify that the values actually change based on power...

...ry.charge.low: 10 battery.charge.warning: 50 battery.runtime: 1673 battery.runtime.low: 376 battery.type: PbAc battery.voltage: 54.2 battery.voltage.nominal: 48.0 device.mfr: American Power Conversion device.model: Smart-UPS X 1500 device.serial: AS0946124031 device.type: ups driver.flag.pollonly: enabled driver.name: usbhid-ups driver.parameter.offdelay: 20 driver.parameter.ondelay: 30 driver.parameter.pollfreq: 15 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: APC HID 0.95 driver.version.internal: 0.34 ups.beeper.status: e...

...ry.charge.low: 10 battery.charge.warning: 50 battery.runtime: 1673 battery.runtime.low: 376 battery.type: PbAc battery.voltage: 54.2 battery.voltage.nominal: 48.0 device.mfr: American Power Conversion device.model: Smart-UPS X 1500 device.serial: AS0946124031 device.type: ups driver.flag.pollonly: enabled driver.name: usbhid-ups driver.parameter.offdelay: 20 driver.parameter.ondelay: 30 driver.parameter.pollfreq: 15 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: APC HID 0.95 driver.version.internal: 0.34 ups.beeper.status: e...

...iling List Subject: Re: [Nut-upsuser] debian 8 "jessie" nut 2.7.2 slaves not shutting down On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309001233" > desc = "MIDAPC" > [BOTAPC] > driver = usbhid-ups...