search for: hidded

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

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 dependency on 'usb.h' with

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

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,

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 modify that struct dynamically, or

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

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

Sorry for the bad formatting of the previous message...I tried to use plus signs as bullet points, and that caused a problem somehow. Ok...I discovered that if I do the autoreconf after the first failed make (and the autoreconf still gives that error message), and then do make again...it builds. Conclusions: 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c

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"

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

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

I am having an issue running NUT and using an 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

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.

Hello all, I am trying to set up my brother's UPS (remotely over internet) on an OpenIndiana-based storage box. According to him, the UPS is probably an Ippon Back Power Pro 600 dated around 2003 (battery recently replaced), and it has an USB connection. Sorry for a relatively long post with a log of my successes and failures, in the hopes that someone would point out what I did wrong.

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

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

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/i386/compile/SRV i386 *** NUT ver.2.0.3 root.srv# ll /var/db/pkg/

Hi, I am wanting to use NUT to connect to an Eaton Powerware 5110 UPS using USB to connect. - I am using NUT 2.0.2 - I have compiled it with USB support - I can see 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.

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.317057 - ProductID: 0002

On Jan 11, 2020, at 1:58 AM, Gene Heskett wrote: > > On Friday 10 January 2020 20:43:55 Gene Heskett wrote: > >> On Friday 10 January 2020 19:04:11 Charles Lepple wrote: >>> On Jan 10, 2020, at 5:29 PM, Gene Heskett wrote: >>>> input.transfer.high: 0 ???? Shouldn't these two be something real >>>> ???? input.transfer.low: 0 ???? ditto