search for: shut_mod

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 NULL terminated. Rega...

I Seem to have made some progress in getting nut-2.0.5 installed, but hidups still has a version number of 0.13. First is hidups 0.13 the correct version? if not how do I find the correct version. Second if my Geek Squad GS1285U UPS is not supported how do I proceed. I have been a programmer for 35 years(mostly high level computer aided design), written code in 20 some languages, am retired

...d this from scratch on a fresh 2.7.2 directory. I followed 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 ....

...place to submit bugs) I run a FreeBSD box with stack-protector enabled, which raises a problem in the upsdrv_initups() function of the newhidups.c module; the regex_array variable is sized one item too small. Regards, Herve Masson <<<< void upsdrv_initups(void) { int i; #ifndef SHUT_MODE /*! * SHUT is only supported by MGE UPS SYSTEMS units * So we don't need the regex mechanism */ int r; char *regex_array[5]; ^^^^^^^^^^^^^^^ => should be 6 /* enforce use of the "vendorid" option if "generic" is given */...

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

....7.2 directory. I followed 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/Make...

...dif /* OPENUPS_HID_H */ Index: drivers/usbhid-ups.c =================================================================== --- drivers/usbhid-ups.c (revision 3782) +++ drivers/usbhid-ups.c (working copy) @@ -37,6 +37,7 @@ /* include all known subdrivers */ #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_sub...

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 driver, I'll revisit writing our own. Thanks for the helps. Sincerely,

...1000); /* FIXME: to be written */ return 0; } However, it automatically returns a zero, i.e. success. But the msg "none" says otherwise, e.g. -110. The usb version doesn't even seem to have an interrupt_read. But that version is definitely not invoked since the SHUT_MODE compile time variable is set. So I'm curious as to what is happening. I'm also still digging, i.e. following the upsdrv_updateinfo bit. Please feel free to reroute this msg to the developer list if it is deemed more appropriate there. thanks, -jeff

...2 @@ static void process_boolean_info(const char *nutvalue) static int callback(hid_dev_handle_t udev, HIDDevice_t *hd, unsigned char *rdbuf, int rdlen) { int i; - const char *mfr = NULL, *model = NULL, *serial = NULL; + const char *mfr = NULL, *model = NULL, *serial = NULL, *descfile; #ifndef SHUT_MODE int ret; #endif upsdebugx(2, "Report Descriptor size = %d", rdlen); upsdebug_hex(3, "Report Descriptor", rdbuf, rdlen); + /* Check whether we have an override descriptor */ + descfile = getval("hid_descriptor"); + if (descfile) { + unsigned char *buf; + siz...

...matcher, int mode) > +HIDDevice_t *HIDOpenDevice(hid_dev_handle_t **udevp, HIDDevice_t *hd, HIDDeviceMatcher_t *matcher, int *mode) > { > int ReportSize; > unsigned char ReportDesc[4096]; > > - if (mode == MODE_REOPEN) { > + if (*mode == MODE_REOPEN) { > #if defined(SHUT_MODE) || defined(SUN_LIBUSB) > /* Cause a double free corruption in USB mode on linux! */ > if (*udevp != NULL) { > @@ -623,7 +674,7 @@ > if (ReportSize < 0) > return NULL; > > - if (mode == MODE_REOPEN) { > + if (*mode == MODE_REOPEN) { > upsdebugx(4, &quo...

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that