search for: subdriver_list

...> As I've found out since I came up with the original idea (see one of my > previous messages) I can't call subdriver->function() from makevartable as > subdriver hasn't been given a sensible value at that point, instead, I'm > having to do: > > for (i=0; subdriver_list[i] != NULL; i++) { > subdriver_list[i]->extendvartable(); > } > > So I assume that I should modify this to be: > > for (i=0; subdriver_list[i] != NULL; i++) { > if (subdriver[i]->init != NULL) { > subdriver_list[i]->init(); > } > } This is a bad...

Ok, so please correct me if I?m wrong?. The quickest way to get my UPS running with nut (as the current release exists) is to either: 1) Add my vendor and device ID to the openups_usb_device_table OR 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list And then recompile/install. Obviously #1 will be easier at this point, but I understand that it will only get me the functionality that currently exists in the openups driver (which is ok, I structured my USB reports around what that driver makes available). If I want full functionality I?ll nee...

...lt;rgroner at RTD.com> wrote: > The quickest way to get my UPS running with nut (as the current release exists) is to either: > > 1) Add my vendor and device ID to the openups_usb_device_table OR > 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list > > And then recompile/install. > Correct. For posterity, here's the discussion thread from last March: http://article.gmane.org/gmane.comp.monitoring.nut.devel/6669 I may not have been clear then, but the changes to the driver/*.c files will definitely require a recompile/install...

Browsing through the newhidups.c code, I stumbled across the following: /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { #ifndef SHUT_MODE &generic_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE &apc_subdriver, &belkin_subdriver, &tripplite_subdriver, NULL #endif }; Shouldn't the 'NULL' terminator be outside the condition? If SHUT_MODE is defined, the list will not be...

...trunk megatec_usb detects its vendorid 0665 productid 5161 but uses the agiler driver for it which apparently does not work (timeout...). I think this device is using that USB-to-serial chip but a different protocol behind. I got the phoenix subdriver working with the device but I had to extend subdriver_list[] by &phoenix_subdriver in order to be able to specify it on the command line. Could you please fix this in the trunk? With that change the following ups.conf settings work fine with the USV: [powermust] driver = megatec_usb port = auto vendorid = 0665 subdriver = phoenix Thanks B...

...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 the various (#include'd) 'protocols' the driver supports. - Once nutdrv_qx has set up the communication with a supported device in `upsdrv_initups()` (see below, for serial or USB devices), it gives all (unless otherwise instructed by the user) 'protocols' in `subdriver_l...

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

...> > > The quickest way to get my UPS running with nut (as the current release > exists) is to either: > > > > 1) Add my vendor and device ID to the openups_usb_device_table OR > > 2) Create my own driver file, and then add that driver to the usbhid-ups > subdriver_list > > > > And then recompile/install. > > > Correct. > > For posterity, here's the discussion thread from last March: > http://article.gmane.org/gmane.comp.monitoring.nut.devel/6669 > > I may not have been clear then, but the changes to the driver/*.c files w...

...ed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added "rtd-hid.c" to USBHID_UPS_SUBDRIVERS in drivers/Makefile.am + I added "rtd-hid.h" to dist_noinst_HEADERS in drivers/Makefile.am + I executed ./configure --with-usb --with-dev --etc --etc I execute make, a...

On Feb 20, 2015, at 3:15 PM, Rob Groner <rgroner at RTD.com> wrote: > Instead, it seems that the usbhid-ups driver will search through its own list of known devices with vid/pid, and won't "match" my device unless that device exists as an entry in its device table. Is that correct? More or less, yes. It turns out that UPS vendors all have somewhat different

...> wrote: > >> The quickest way to get my UPS running with nut (as the current release exists) is to either: >> >> 1) Add my vendor and device ID to the openups_usb_device_table OR >> 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list >> >> And then recompile/install. >> > Correct. > > For posterity, here's the discussion thread from last March: http://article.gmane.org/gmane.comp.monitoring.nut.devel/6669 > > I may not have been clear then, but the changes to the driver/*.c files will def...

...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 the various (#include'd) 'protocols' the driver supports. - Once nutdrv_qx has set up the communication with a supported device in `upsdrv_initups()` (see below, for serial or USB devices), it gives all (unless otherwise instructed by the user) 'protocols' in `subdriver_l...

I think I had a misconception about something.. My goal was that someone could use our UPS with the "default" UPS driver in NUT right out of the box, so they wouldn't have to alter any NUT code to get it working. NUT config files, yes, but not NUT code. I thought that if I put in the ups.conf file that I wanted to use the usbhid-ups driver, and then put our vendor and product ID,

On Mar 2, 2015, at 12:49 PM, Rob Groner <rgroner at RTD.com> wrote: > Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid

...cally: > > + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. > + I put them in the drivers subdir > + I added the include line (#include rtd-hid.h) in usbhid-ups.c > + (specifically in the #ifndef SHUT_MODE section) I added > + &rtd_subdriver, to the subdriver_list in usbhid-ups.c (specifically > + in the #ifndef SHUT_MODE section) I added "rtd-hid.c" to > + USBHID_UPS_SUBDRIVERS in drivers/Makefile.am I added "rtd-hid.h" to > + dist_noinst_HEADERS in drivers/Makefile.am I executed ./configure > + --with-usb --with-dev --etc --...

...rs */ > #include "generic-hid.h" > +#include "tripplite-hid.h" > #include "mge-hid.h" > #include "apc-hid.h" > #include "belkin-hid.h" > @@ -34,6 +35,7 @@ > /* master list of avaiable subdrivers */ > static subdriver_t *subdriver_list[] = { > &generic_subdriver, > + &tripplite_subdriver, > &mge_subdriver, > &apc_subdriver, > &belkin_subdriver, Ah, sorry, I had forgotten these. Good catch. > That made this work with ... > > user=root > [myup...

...ivers */ #include "mge-hid.h" + #ifndef SHUT_MODE #include "explore-hid.h" #include "apc-hid.h" @@ -48,10 +49,14 @@ #include "idowell-hid.h" #endif +#include "openups-hid.h" + /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { + #ifndef SHUT_MODE &explore_subdriver, + &openups_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE Index: drivers/Makefile.am =================================================================== --- drivers/Makefile.am (revision 3782) +++ drivers/Makefile.am (working cop...

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: