search for: openup

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 commands! You are correct; I don't see any HU_TYPE_CMD entries in openups-hid.c. I latched on to the other error you mentioned (about claiming the device). The other HID driv...

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 read a Report b1 of size 248 which results in a broken pipe. Is...

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 a...

...rigger 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 this specific command as an instant command, it may respond? I could give it a try if you confirm that?s what you mean. > Out of curiosity, which notifications? In the openups_drv_start_onbatt log, the PresentStatus values look the same as the online log. Or do you mean you go...

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 battery voltage I can...

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

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

On Mar 13, 2015, at 8:21 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > 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 re...

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

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 (o...

* Ubuntu 12.04 Precise * NUT 2.6 * From Ubuntu terminal ---> sudo apt-get install nut * Openups from mini-box.com (http://www.mini-box.com/OpenUPS) * - Intelligent UPS, USB interface - SMBUS slave and I2C master - Input 6-34V - Programable output 6-24V - Default output is 12V - Input/Output current 6A/10A peak - Charge between 6-30V, 3A - Voltage and current limits - Li-Ion, Li-Po, LIFEPO4...

Monitoring the input and output currents reported through upsc for an OpenUPS device suggests that it is an energy creation device - the power out is greater than the power into the system once the battery is fully charged. Analysis and measurement reveals several issues: 1. "UPS.PowerStatus.Output.Current" is scaled for NUTs "output.current" value,...

[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 system stays dead. Once the battery dies completely, the UPS will reboot itself and turn the server on - but this may never happen. > > Do I have to modify the Centos ?shut...

Hello, Would like to see if I could get some help with this UPS on a debian set-up. Am not the best with linux and have tried what I managed to find elsewhere on the list so am just trying here. 1) Device seems supported: http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html 2) lsusb -v -d 04d8: seems to give the right parameters including product name, max power etc from the unit 3) Followed the steps here as an initial starting point: https://gist.github.com/clungzta/2b5f737f006e1530cc59 4) Have edited the ups.conf and nut.conf files with the necessary ent...

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

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

On Nov 4, 2014, at 4:36 PM, Toomas Suurmets (Priv) <toomas at suurmets.com> wrote: > Hi Charles, > > I tried your suggestion with OpenUPS2 (on Raspberry PI, Debian Jessie), it works. Thanks for the update. We can add the ID to the driver, but I noticed a few inconsistencies (indicated below). > OpenUPS2 Configuartion variables modification would be very welcome.... I'm assuming these are exposed via USB HID? If so, we need...

On Mar 17, 2015, at 10:32 PM, Charles Lepple <clepple at gmail.com> wrote: > A bit of explanation on the debug output: the "Report Descriptor: (739 bytes)" hex dump is the HID representation of the individual reports available. NUT parses that out, and iterates over all of the "Usage IDs" (status variables, and settings). The values for the usages are grouped in

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: 36.79 battery.type: battery.voltage: 10.13 device.mfr: Mini-Box.Com device.model:...

...; wrote: > 4) Have edited the ups.conf and nut.conf files with the necessary entries but trying to start the driver with upsdrvctl start gives: > "Network UPS Tools - UPS driver controller 2.6.4 > > Network UPS Tools - Generic HID driver 0.37 (2.6.4) > Support for the original OpenUPS was added in NUT v2.7.1. Is there any way you can use Debian Backports to get a newer version of NUT?