search for: nutdrv_qx

...It is unclear as to whether this can be enabled with a sysctl (hw.usb.debug), or if additional #defines are needed. For this, you might want to check with the FreeNAS folks, or try the FreeBSD USB list. This is a bit of wishful thinking, but NUT 2.7.2 also has a newer driver for Megatec equipment: nutdrv_qx. While I don't recall any FreeBSD-specific tweaks to it, trying it would probably be faster than recompiling the kernel, and there is little to lose. -- Charles Lepple clepple at gmail

Hi all, I'm a new user trying to get a Proline UPS I1000 UPS to work with freenas 9.3 over USB. When running upsdrvctl I get a permission denied error. Required debug info: OS name and version, # uname -a FreeBSD freenas.local 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #2 r275790+f84e770: Tue Dec 23 23:35:33 PST 2014 root at

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my rapsberry pi on it they would cycle forever. I tested the shutdown.return using the upscmd and I didn't see this behavior, so I finally find out that is...

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see...

...nut-latest.tar.gz> > Thank a lot ! Now, conclusions after attempting builds ( with no docs included since attempting to enable them triggers the errors related to missing or too old tools mentioned by me in an earlier message ) - building against libsub 1.0 triggers the following 2 errors : nutdrv_qx-nutdrv_qx.o: In function `ippon_command': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692: undefined reference to `libusb_strerror' nutdr...

...> > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some investigation I found the problem is a bug on the ups - > TSSHARA > > model, driver nutdrv_qx: every time I shutdown with return, and reconnect > > the usb after the power is back it would start another shudown.return > cycle. > > When I used my rapsberry pi on it they would cycle forever. > > Jairo, what's the exact model of the UPS? > TS Shara Soho II > V...

...bestpower-mib.o cyberpower-mib.o delta_ups-mib.o xppc-mib.o huawei-mib.o eaton-ats16-mib.o apc-ats-mib.o raritan-px2-mib.o eaton-ats30-mib.o apc-pdu-mib.o main.o dstate.o -Wl,-z -Wl,relro -Wl,-z -Wl,now ../common/.libs/libcommon.a ../common/.libs/libparseconf.a -L/usr/lib64 -lnetsnmp -lpthread nutdrv_qx-nutdrv_qx.o: In function `ippon_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:679: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:692: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `f...

Hello, I think that on this file nutdrv_qx_megatec.c the definition for shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m while on the megatec protocol description ( http://networkupstools.org/protocols/megatec.html) the command is just "S%s\r". When I changed it my system was abe to at least sta...

...; Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function `ippon_command': > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679: > undefined reference to `libusb_strerror' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692: > undefined reference to `libusb...

Hello, Not really sure. Have not heard about such a brand/model on one hand, and the Home Assistant NUT plugin may be (or not be) limiting the selection of data points it shows from NUT on the other. Can you query the readings with NUT `upsc` client? Also, `nutdrv_qx` is an umbrella driver for many different dialects of "Megatec Q<x>" protocol family. Check the https://networkupstools.org/docs/man/nutdrv_qx.html manual page (or ideally the help message from `nutdrv_qx --help` on your deployment) about supported `subdriver` and `protocol` option...

....rotava at gmail.com>: > Hi, > > I had an issue where after returning the power from a shutdown.return the > ups would do another shutdown.return during the boot, and kept this forever. > After some investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and reconnect > the usb after the power is back it would start another shudown.return cycle. > When I used my rapsberry pi on it they would cycle forever. Jairo, what's the exact model of the UPS? Version of NUT/nutdrv_qx? Is the monitoring system (th...

aehm.. the innards of nutdrv_qx are not exactly well documented (and vars have somewhat confusing names) -- my fault, sorry. This is another thing that has been on my todo list for a while... Briefly, at the moment, in nutdrv_qx, there are actually two kinds of subdrivers: - 'protocols', which are communication-type-agno...

Hello! We have FSP DPV 1000 USB and we want to use NUT to get data from this UPS. Unfortunately we have only Windows and current Windows port doesn't have nutdrv_qx, which should support this UPS. Is there any possibility of getting nutdrv_qx for Windows? Please help.

...at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > > Not sure what other logs I can provide to try to troubleshoot this? > > > Two things: > > - the output of 'lsusb -d 0665:' before and after the 'stale data' warning > - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee > /tmp/nutdrv_qx.log' > > (Please gzip nutdrv_qx.log before sending it, thanks.) > > -- > Charles Lepple > clepple at gmail > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lis...

...uot; product = "MEC0003" vendor = "MEC" bus = "004" --------------------------------------------------- But "blazer_usb" driver does not work with this device. My working "ups.conf": [Viper1200] driver = "nutdrv_qx" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor = "MEC" bus = "004" default.battery.voltage.high = 27.50 default.battery.voltage.low = 20....

Hi, I am trying to get NUT 2.7.2 working on my Solaris 11.2 system with a PowerWalker 2000 VI PSW UPS. I have carefully configured the software such that it 'works' using custom values in the ups.conf file: driver = nutdrv_qx port = auto desc = "my UPS" protocol = voltronic-qs subdriver = cypress vendorid = 0665 productid = 5161 The problem I'm experiencing is that after a random amount of time, usually a few mins, the driver stops providing data and the and the application complains the data is "sta...

..., 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as > the > > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I > am > > This device could be supported by nutdrv_qx (subdriver > 'voltronic-sunny') built starting from this branch: > https://github.com/zykh/nut/tree/nutdrv_qx_voltronic-sunny_rebased+command > > Please note that this subdriver is not ready yet for primetime (I'm > working on it with Nick, CC'ed. - Sorry for my delay...

...ps.conf` or similar during the experiments (generated from YAML settings made in HA GUI somewhere). I have not used it directly, so I can't really help more here. Jim On Wed, Sep 25, 2024 at 5:47?PM Daniele Lamaddalena <dlamaddalena at gmail.com> wrote: > Hi, I'm already using `nutdrv_qx`as driver and everything works fine but > still after reading these documentation I'm not able to find what I'm > looking for, I'm using the integration on home assistant and I'm not able > to find the conf file to modify , > > D. > > Il mer 25 set 2024, 17:27 J...

Hi Daniele, I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. It looks like things mostly work: bestups: battery.charge: 100.0 battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: Best Power device.model: Patriot Pro II 400 device.type: ups driver.name: bestups driver.pa...