similar to: Error processing nut-client and nut-server

Hi, I'm trying to generate a skeleton driver with usbhid-ups and gen-usbhid-subdriver but the output seems to be incorrect. Same behavior with stable 2.6.5, so I guess there is something wrong with data coming out of device. I attached the output of usbhid-ups and gen-usbhid-subdriver from the commands: drivers/usbhid-ups -DD -u root -x explore -x vendorid=04d8 -a openups >&

[please keep the list CC'd. thanks!] On Mar 13, 2015, at 10:53 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > I?ve set up UPSMON to simply execute ?shutdown -h now? and my system shuts down when I type ?upsmon -c fsd?. The problem is that the OpenUPS doesn?t shut down as a result; and therefore when the power comes back on, unless the battery has totally run out, the

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

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

Charles, Did you get chance to look at the data I sent you, please? I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to

On Mar 17, 2015, at 11:46 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > Charles, > > Did you get chance to look at the data I sent you, please? > > I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant

Charles, Thanks again for your help, and sorry I didn?t :cc - noted for the future! I?m suspicious that the OpenUPS doesn?t behave properly in a number of ways, of which the USB traffic is the one of immediate concern. It seems to me that NUT can read from it but probably not write to it: and the OpenUPS doesn?t flag ?low battery? conditions correctly either. It does shut itself down at a

Hi, Debug output of driver is attached, started with OpenUPS2 input feed online @ 12V and going offline at 15th second of debug run. Second attached file is debug output of unsuccessful UPS shutdown captured with command: /lib/nut/usbhid-ups -a openups -x productid=d005 -u root -DDD *-k* 2>&1 |tee openups-d005-shut.log I believe input voltage on my earlier upsc run was around 16V,

Charles, to your specific points : > The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to the HID PDC spec, is read/write. I wonder if the firmware responds to this? So are you suggesting if I modify openups-hid.c to include

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

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,

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

I bought a very nice little, self contained, UPS from mini-box: http://www.mini-box.com/OpenUPS2 thinking it would be handled by NUT. I think I misread or misinterpreted the HCL http://www.networkupstools.org/stable-hcl.html The OpenUPS UPS is listed as supported under usbhid-ups, and I had assumed that OpenUPS2 would be as well. Bzzzzt. I get a unknown device ID for d005 Is adding (or

On Sep 8, 2014, at 5:46 PM, John Thurston <john.thurston at alaska.gov> wrote: > I bought a very nice little, self contained, UPS from mini-box: > http://www.mini-box.com/OpenUPS2 > thinking it would be handled by NUT. > I think I misread or misinterpreted the HCL > http://www.networkupstools.org/stable-hcl.html Correct, we only knew about the original openUPS (USB ID

Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the

On Nov 6, 2014, at 1:44 PM, Toomas Suurmets (Priv) <toomas at suurmets.com> wrote: > Hi, > > Debug output of driver is attached, started with OpenUPS2 input feed online @ 12V and going offline at 15th second of debug run. Thanks, the voltages seem to only be off by a factor of 10: Path: UPS.PowerSummary.Output.Voltage, Type: Feature, ReportID: 0x21, Offset: 0, Size: 16, Value:

Charles Lepple a ?crit : > Thanks for the patch. For reference, what does the rest of the "upsc" > output look like for this device? Here it is: $ upsc openups2 Init SSL without certificate database battery.capacity: 100 battery.charge: 100 battery.charge.low: 5 battery.charge.warning: 20 battery.current: 0.000 battery.mfr.date: battery.runtime: 3932100 battery.temperature:

Ok Steve, Now its time to edit the status file of the packages. make a backup of : /var/lib/dpkg/status open it with an editor. search for "Package samba" , you probly see" installed ok not-configured. and change status to : Status: install ok installed after the change run : apt-get -f install that should do the trick. Greetz, Louis >-----Oorspronkelijk

Faster than I expected, I've become somewhat disenchanted by the openups-usb driver. So, if I write my own subdriver for our UPS...how quickly can I expect that it will be incorporated in some downloadable version of nut that a user can then use? The main reason I ask is because I have to include a guide for getting the UPS to work in Linux. If I can simply stipulate that they have to