search for: openups_usb_device_table

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 structur...

On Feb 25, 2015, at 11:35 AM, Rob Groner <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 hav...

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

...ude "openups-hid.h" +#include "main.h" /* for getval() */ +#include "usb-common.h" + +#define OPENUPS_HID_VERSION "openUPS HID 0.1" +#define OPENUPS_VENDORID 0x04d8 + +static char openups_scratch_buf[20]; + +/* USB IDs device table */ +static usb_device_id_t openups_usb_device_table[] = { + /* openUPS minimum required firmware 1.4 */ + {USB_DEVICE(OPENUPS_VENDORID, 0xd004), NULL}, + + /* Terminating entry */ + {-1, -1, NULL} +}; + +static const char *openups_charging_fun(double value); +static const char *openups_discharging_fun(double value); +static const char *openups_onli...

On 02/26/2015 03:09 AM, Charles Lepple wrote: > On Feb 25, 2015, at 11:35 AM, Rob Groner <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...

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,

...up permissions) with nut > 2.7.2 > > On Feb 25, 2015, at 11:35 AM, Rob Groner <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.com...