similar to: Eaton 5PX broken interrupt on usbhid-ups, also pollfreq vs pollinterval?

On Sep 19, 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:

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

Hi, Context of my question: * OS name and version, Synology's distributed Linux: Linux DS 3.10.102 #15152 SMP Fri Sep 1 11:15:03 CST 2017 x86_64 GNU/Linux * exact NUT version, Tricky... the installed tools display: $ /usr/sbin/upsd -V Network UPS Tools upsd DSM6-1-15114-170518 while the one I've compiled, and its not running, displays: $ /opt/sbin/upsd -V Network UPS Tools upsd

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

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

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

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

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- 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

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

I want to revive an old discussion. Should we use the contents of input reports or not? A while back, we decided not to use the contents of input reports, because there is no guarantee that input report 'n' has the same meaning as feature report 'n'. We have not seen any cases so far where this is not the case, but as far as we could see, there is nothing in the HID PDC

On 6/19/23 20:29, gene heskett wrote: Some speeling korrections > On 6/19/23 18:57, gene heskett wrote: >> Greetings Jim & friends; >> >> Just installed nut 2.7.4 on a debian bullseye system.? ups is: >> Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS >> Device Descriptor: >> ?? bLength??????????????? 18 >> ?? bDescriptorType????????

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

Good evening folks, So I configured NUT on a Raspberry Pi 4 both UPS are connected over USB however the switch from AC Power to Battery seems to be delayed on the NUT communication would anyone have any ideas? The Pi Reports that the UPS is on battery around 30 seconds later I think this delay is long. I have tested it on a physical computer and the detection is around 5 to 6 seconds with

Hi! Charles. This is the output with 'explore' # ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.317057 - ProductID: 0002

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

OS name and version, MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB debian 8 "jessie" Linux pdxvhtst01 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux SLAVE SYSTEMS monitoring MASTER via IP debian 8 "jessie" Linux geaaetst01

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All