search for: _writing_a_subdriver

...route to go. When I can no longer live with the limited nature of the openups-hid driver, I'll revisit writing our own. I'll take this as a TODO item to make it clearer, but for later the basic information is here: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver "You must also add the subdriver to USBHID_UPS_SUBDRIVERS in drivers/Makefile.am and call "autoreconf" and/or "./configure" from the top level NUT directory." To run autoreconf, you need automake, autoconf and libtool. automake turns Makefile.am into Makefile.in, and...

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,

On 5/21/2017 10:39 AM, Charles Lepple wrote: > Mike, > > Thanks for the info. I have enough to add an entry to the DDL, but I have a few more questions inline. > > On May 14, 2017, at 1:21 PM, Mike wrote: >> >> [updated] >> >> OpenBSD 6.1/amd64 >> NUT 2.7.4p0 (from OpenBSD package) >> >> >> Results of upsc: >> >>

...gt; wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > > http://new.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver When I ran: drivers/usbhid-ups -DD -u root -x explore -x vendorid=0764 auto it balked at "auto": Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 Error: too many non-option arguments. Try -h for help. so I added a -a parameter to poi...

...live with the limited nature of the > openups-hid driver, I'll revisit writing our own. > > I'll take this as a TODO item to make it clearer, but for later the basic > information is here: > > http://www.networkupstools.org/docs/developer- > guide.chunked/ar01s04.html#_writing_a_subdriver > > "You must also add the subdriver to USBHID_UPS_SUBDRIVERS in > drivers/Makefile.am and call "autoreconf" and/or "./configure" from the top > level NUT directory." > > To run autoreconf, you need automake, autoconf and libtool. automake > turn...

...Plus, there's the obvious advice not to do this when the weather forecast is looking grim. Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: http://new.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver The usual recommendations apply (let it run for 30 seconds, and gzip the logs), but the serial numbers might be labeled differently - so perhaps grep for the first few characters, rather than relying on a "serial" label. > >> >>> device.mfr: CPS >>> device.m...

...t;> On 5/21/2017 10:39 AM, Charles Lepple wrote: > [snip] > >> Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: >> >> http://new.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_writing_a_subdriver > > > When I ran: > > drivers/usbhid-ups -DD -u root -x explore -x vendorid=0764 auto > > it balked at "auto": > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > 0.000000 Error: too many non-option argument...

...ature of the openups-hid driver, I'll revisit writing our own. > > > > I'll take this as a TODO item to make it clearer, but for later the > > basic information is here: > > > > http://www.networkupstools.org/docs/developer- > > guide.chunked/ar01s04.html#_writing_a_subdriver > > > > "You must also add the subdriver to USBHID_UPS_SUBDRIVERS in > > drivers/Makefile.am and call "autoreconf" and/or "./configure" from > > the top level NUT directory." > > > > To run autoreconf, you need automake, autoconf and...