search for: hid

Ok, I tried 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 &q...

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a depe...

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 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/de...

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, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] &gt...

I think I'm going to have the slightly rejigger the tripplite-hid.c driver to 'properly' support all of the data I know about it's outlets. A given UPS may have 'n' output loads. I could have 5, I could have 10, I won't know until I actually ask the UPS. But in order to use the hid to nut struct, I'm actually going to have to modi...

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining information, and the...

In a separate discussion, on 6/26/17 4:04 AM, Arnaud Quette wrote: > Hi > > If you're sure it's a HID device, add an entry in drivers/powercom-hid.c > { USB_DEVICE(POWERCOM_VENDORID, 0x0002), NULL }, > > Then autogen.sh + configure... > Please also report back so that I can update the code > > Cheers > Arno Thanks! I don't *know* whether or not it's an HID device, b...

...o: 'nut-upsuser List' > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > Ok, I tried 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 SH...

On Mar 6, 2014, at 3:55 PM, Rob Groner wrote: > To make this UPS as easy to use as possible for the end-user who chooses Linux, I figured I would just completely implement the official USB HID UPS spec. That way no subdriver would be needed, or at least very little. At the moment, we use USB VID and PID to select which HID-to-NUT tables to consult (since some vendors have "custom" (incorrect) interpretations of standard HID PDC Usages. So at the very least, you would need a s...

...USB Controller 2x APC Smart-UPS 1500, connected via USB Debian GNU/Linux (sid, up-to-date), kernel 2.6.16.18 * the nut package can't be started anymore: backer:~# /etc/init.d/nut stop Stopping Network UPS Tools: (upsdrvctl failed) upsd upsmon. * In the old configuration I was using the hidups driver, now I tried newhidups, as well - none of them is actually able to find the UPSes connected: backer:~# /lib/nut/newhidups -a power2 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) No matching USB/HID UPS found backer:~# /lib/nut/newhidups -a power2 Network UPS Tools: New USB/...

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the process). I...

...n TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable (ups.test.result) does not exist If I run ./newhidups -u root -DD auto, I get this scrolling gibberish until I ctrl-c the process, it will continue forever if I let it. [player@V0002-S002 bin]$ sudo ./newhidups -u root -DD auto Network UPS Tools:...

Charles, Thank you so much for the information. I'm trying to digest it along with the other docs I have, the example code from Microchip, and a USB HID tutorial I found online. So, if I understand correctly.... When the device first connects, it sends a huge dump of data (which the usbhid driver shows when you use the debug option) which fully describes the data it is capable of sending. The usage id's, pages, etc use values from the USBHID...

...nt in OI, libusb and other packages that the build wanted 2) Compiled nut-2.6.5 (with the patch mentioned a week ago) 3) Installed NUT in the global zone, and defined the ups.conf entry: [ippon] driver = blazer_usb port = auto desc = "Ippon Pro 600 USB" [hid] driver = usbhid-ups port = auto 4) The interesting part is about getting USB to be found at all :) Do credit where credit is due - some helpful posts were: http://barbz.com.au/blog/?p=407 http://www.mail-archive.com/nut-upsuser at lists.alioth.debian.org/msg06556.html # /usr...

My company is developing a new UPS, with smarts provided by a PIC32 Microchip micro-controller. The controller comes with a demo for a USBHID-UPS, and after some tweaking, I was able to get NUT to recognize it and start showing some reasonable values. To make this UPS as easy to use as possible for the end-user who chooses Linux, I figured I would just completely implement the official USB HID UPS spec. That way no subdriver would be n...

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 start /lib/nut/(null)...

Hello, Help me please with *newhidups* setup. Does it work for someone on *BSD ? Here is the data. --------------------------------------------------------------- *** FreeBSD root.srv# uname -a FreeBSD xxxxxx.dyndns.info 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Tue Feb 8 07:38:22 UTC 2005 admin@temp.botka.homeunix.org:/usr/src/sys/i38...

...that the UPS is registered as connecting in /var/log/messages eg usb 3-1: USB disconnect, address 3 usb 3-2: new low speed USB device using uhci_hcd and address 4 But I don't know how to progress from here. I have used the following commands: mkdir /dev/usb mkdir /dev/usb/hid mknod /dev/usb/hid/hiddev0 c 180 96 mknod /dev/usb/hid/hiddev1 c 180 97 mknod /dev/usb/hid/hiddev2 c 180 98 mknod /dev/usb/hid/hiddev3 c 180 99 However, I'm not sure how to check that there is a link between hiddev0 and the USB device that's registering above. - In a fit of woeful optimis...

Hi! Charles. This is the output with 'explore' # ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.31...

...t any load caused by the internal UPS electronics, which is also pretty far down in the noise compared to a 625 VA design rating, and then it probably gets clamped to zero if it's close enough.) If you stop all of the NUT components, and run the driver manually in debug mode ("/lib/nut/usbhid-ups -a myups -DDD" as root), the raw values before and after scaling are printed. For instance, on issue #482 (attached file "sx650g.txt"), this is what gets mapped to "ups.load": 0.070141 Report[get]: (3 bytes) => 13 14 00 0.070177 Path: UPS.Output.PercentLoad, T...