similar to: Call for testing: usbhid-ups and working interrupt pipe

> Also, I don't think we have any confirmation of the variables that the AP9620 provides. Here is the list of full 'upsc' output for various APC models: > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/index.html Frantz, Actually, it would be useful if you could send a copy of the output of 'upsc', 'upscmd -l' and

On Dec 17, 2014, at 3:46 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > This seems to me a little bit complicated :-( Instead, can I use the > apcsmart driver with the provided 940-0625a c?ble (RJ45/DB9 connectors) ? Or > do I need to acquire an AP9620 SmartSlot expansion card, as I've seen in the > Hardware compatibility list page ? It sounds like you might

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

Greg, I think I fixed it. Thanks for your patience. https://github.com/networkupstools/nut/pull/213 Diffs: https://github.com/networkupstools/nut/compare/usbhid_ups_input_vs_feature If anyone else can test usbhid-ups against their hardware before I merge this to master, I would appreciate it. I tried my MGE UPS on a Linux box as well, and it does not get interrupt events there, either. -

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

Le Tue, 16 Dec 2014 15:36:29 +0100 Frantz de Germain <frantz at info.univ-angers.fr> ?crivait: > 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

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

[please use reply-all to include the list. thanks!] On Oct 16, 2015, at 12:47 PM, Charles Mccrea <charlesmccrea at gmail.com> wrote: > > Hello, > > We have a small server room for our various Proxmox Host Servers, UTM system and managed switches. I've recently discovered NUT and would like to use it to monitor our UPS boxes using Raspberry Pi's. I have a few

On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru wrote: > This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;) We're working on it: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/docs/man/snmp-ups.html#_shutdown A quick check says that the implementation has been there since v2.6.4, and

thanks - this has been fun. There is one other thing I have been having trouble with - and i've tried it on two archlinuxarm installs and gotten the same thing. i am not even sure if its important for me. but if i try to configure and make with neon support - it cant find the neon libraries. despite neon having been installed several different ways (i tried pacman, as well as compiling

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 trouble detecting a disconnection/staleness, I'm not sure there's merit

(please use reply-all - this list does not alter reply-to headers) On Sep 10, 2015, at 6:23 AM, Thomas Aichinger <taich at qpl.at> wrote: > > Hi, > > I am using a ALLNET 91500 UPS with blazer_usb driver > > /usr/lib/ups/driver/blazer_usb -a ups91500 -L > Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) [...] > I set delay.shutdown to 600 sec but UPS

Le Tue, 16 Dec 2014 20:38:50 -0500 Charles Lepple <clepple at gmail.com> ?crivait: > On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > > > Bye the way I just realize that I can't retrieve the ups.load, among other > > thing :-( > > To the best of my knowledge, Microlink is not supported by any third-party tools

Hi, There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. Please consider adding this to the

On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > Bye the way I just realize that I can't retrieve the ups.load, among other > thing :-( To the best of my knowledge, Microlink is not supported by any third-party tools (including NUT), but some variables are exposed via standard USB HID. Apparently, ups.load is not one of them. Your UPS might

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

On 2014-02-27 14:21, Charles Lepple wrote: > On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru <mailto:jimklimov at cos.ru> > wrote: > >> This apparently implies that, unlike some docs say, the snmp-ups >> driver can send the shutdown signals (is not crippled by design)? ;) > > We're working on it: > >

Hi Charles, Thanks for your response. > For the 1000, do the values match this page? > > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/Smart-UPS_1000.html > > Yes it does (except that mine is a 120 V model, so input/output voltage is about 125) It doesn't look like we have an entry for a C1500 yet. Would you care to > submit the output of

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