search for: nutdrv_qx_

...ng some per-model defaults. > Afaik blazer_* supports the same feature, but the power walker usvs don't seem to report anything. I'm using NUT 2.6.3 from the Ubuntu 12.04.4 LTS repo and I have to stick to that until 14.04.1 LTS comes out (July 24th) :/ Anyway, looking at the subdrivers nutdrv_qx_*.c, I see neither a "battery.voltage.high" nor the idea to make model-specific assumptions/presets (only brand-specific (protocols)). -- Thanks Andreas

...by them), only map the protocol used by the device to the protocol used by NUT, and are implemented in their own files using (and exposing only) the `subdriver_t` format (for more info on this type, see the chapter of the developer guide I mentioned before, 'nutdrv_qx.h' or the various 'nutdrv_qx_<name-of-the-protocol>.c' files), - 'USB subdrivers', which only deal with USB I/O operations, and, conversely, are implemented entirely in 'nutdrv_qx.c'. With regard to 'protocols', nutdrv_qx works like this: - 'nutdrv_qx.c''s `subdriver_list` lists th...

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 drivers that uses the VID

...t;> > > Afaik blazer_* supports the same feature, but the power walker usvs don't seem to report anything. > > I'm using NUT 2.6.3 from the Ubuntu 12.04.4 LTS repo and I have to stick to that until 14.04.1 LTS comes out (July 24th) :/ > Anyway, looking at the subdrivers nutdrv_qx_*.c, I see neither a "battery.voltage.high" nor the idea to make model-specific assumptions/presets (only brand-specific (protocols)). We should probably look into ways to make it easier to build custom .deb files for Ubuntu. -- Charles Lepple clepple at gmail

...by them), only map the protocol used by the device to the protocol used by NUT, and are implemented in their own files using (and exposing only) the `subdriver_t` format (for more info on this type, see the chapter of the developer guide I mentioned before, 'nutdrv_qx.h' or the various 'nutdrv_qx_<name-of-the-protocol>.c' files), - 'USB subdrivers', which only deal with USB I/O operations, and, conversely, are implemented entirely in 'nutdrv_qx.c'. With regard to 'protocols', nutdrv_qx works like this: - 'nutdrv_qx.c''s `subdriver_list` lists th...