similar to: NUT not recognising Mini-box OpenUPS 2

Hi Charles, Thanks for your reply. So the Jessie or stretch versions will work then since those are 2.7.2 and 2.7.4... I will have to update my sources.list and follow this? https://backports.debian.org/Instructions/ Will give it a go later and update either way. Thanks, ST Via mobile On 1 Aug 2017 19:44, "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 1, 2017, at

Hi Charles, Tim, Ah, thanks for bit about the dependencies. Would have thought them to be version specific. Tried with the client and server debs but it seems too many dependency differences between wheezy and jessie. I also tried upgrading from wheezy to jessie wholesale to see if that worked and it did solve nut but in the process broke something else that's more critical so I'll give

On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the

Hi Charles, That package is supposed to install both server and client (according to the description at https://packages.debian.org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. Cheers, ST On 3 Aug 2017 7:26 a.m., "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 2, 2017, at 12:09 PM, Song Teck <songteck at

Hi Charles, thanks for the clarification on the libusb. that indeed does work to get the value in ./configure. I've tried installing a .deb sudo dpkg -i nut_2.7.4-5_all.deb (Reading database ... 103447 files and directories currently installed.) Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... Unpacking replacement nut ... Setting up nut (2.7.4-5) ... which

Hi Charles, Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? 2) If not and I use the 2.7.4 tar found at http://networkupstools.org/download.html, do i just run the classical process? i.e. ./configure make sudo make install

On Aug 1, 2017, at 3:14 AM, Song Teck Ng <st.ng at leading-edge-automation.com> 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

Hi Charles, Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the shutdown sequence to work properly. Have been following this:

Hi Charles, Ok, will try the ignore lb flag later. How do I go about capturing the log? I might as well do it while testing the flag... Cheers, ST On 15 August 2017 at 20:42, Charles Lepple <clepple at gmail.com> wrote: > On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > > > Hi Charles, > > > > Have managed to make some progress

On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so > > 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? The "nut" metapackage just depends on

On Aug 2, 2017, at 12:09 PM, Song Teck <songteck at gmail.com> wrote: > > sudo dpkg -i nut_2.7.4-5_all.deb > (Reading database ... 103447 files and directories currently installed.) > Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... > Unpacking replacement nut ... > Setting up nut (2.7.4-5) ... > > which doesn't return an error but

On Aug 3, 2017, at 5:35 AM, Song Teck <songteck at gmail.com> wrote: > > That package is supposed to install both server and client (according to the description at https://packages.debian.org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. > Right, but only if you install it via apt. If you install the 2.7.4 .deb with dpkg, and

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

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

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

On Mar 13, 2015, at 10:14 AM, Rob Groner <rgroner at RTD.com> wrote: >> >> The documentation isn't explicit about this, but 'upsdrvctl shutdown' is >> meant to be run after all of the other processes on the system have been >> killed, real filesystems have been unmounted, and the kernel shutdown >> syscall is about to be called. Usually the init

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

> > The documentation isn't explicit about this, but 'upsdrvctl shutdown' is > meant to be run after all of the other processes on the system have been > killed, real filesystems have been unmounted, and the kernel shutdown > syscall is about to be called. Usually the init scripts will take care of this, > although I don't know how CentOS handles that

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