similar to: Documentation out of date?

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

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

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

On Mar 9, 2015, at 12:00 PM, Rob Groner <rgroner at RTD.com> wrote: > 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c and *.h files and making the makefile changes and then executing ./configure for the first time would be enough. Each tool serves a different purpose. autoreconf (and NUT's autogen.sh, by inclusion) generates the ./configure

I found something particularly strange while trying out different things: I started up upsdrvctl, upsd, and upsmon. I then stopped upsdrvctl, and tried starting the usbhid-ups driver a few times. Each time I executed the driver, it indicated an instance was already running, stopped it, and then started it again....which is what it should do. I then added -DDDD to the command....and then it

Hi, I have tried several drivers for make my Elite UPS working. With blazer_usb I can contact it, but I have no informations. This is the best result. OS: Ubuntu Xenial 16.04.2 LTS NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) Device name: Elite UPS 800VA (http://www.elit-ups.com/ita/pro_ups.html, discontinued) I can provider their *not working* linux monitoring tool

I think I may be of some help in this matter. Since I am running a bunch of Raspberry Pi's with NUT and it took a lot of hacking to make it possible. You could probably copy and paste this right into a shell script and just run it ... # Do an rpi-update FIRST to prevent USB strangeness #some depencies from repo sudo apt-get -y install m4 libtool libudev-dev automake #fixing autoconf for

On Jun 21, 2013, at 4:23 PM, Massimo Savazzi wrote: > Sorry to bother, but I tried to solve the issue without success. > > Here is my configuration > UPS ? NAS > > I have configured the UPS to send the power messages to my clients: > <image001.png> Can you describe this a little more? What kind of NAS? What version of NUT is it running? The part that seems odd is

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,

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto

On Feb 20, 2015, at 3:15 PM, Rob Groner <rgroner at RTD.com> wrote: > Instead, it seems that the usbhid-ups driver will search through its own list of known devices with vid/pid, and won't "match" my device unless that device exists as an entry in its device table. Is that correct? More or less, yes. It turns out that UPS vendors all have somewhat different

On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote: > Dear Charles Lepple, > Sorry for my email intrusion. for next time: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > I have an UPS called Ovislink 1000VA and it use a UPSMART2000R (with ?ATCL FOR UPS?). > I?m a beginner Linux user and I ?will install your new driver <nutdrv_atcl_usb > to work

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

On 12/03/2016 08:03 AM, Charles Lepple wrote: > On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: >> This is new install on Ubuntu 16.04, using packages from Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >>

Dear Charles, Thanks for your quick reply, but I can't install nut_2.7.2 in my raspberry. 1) I create a [nut] directory and use wget to download three files: [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 2)I unpack: dpkg-source -x nut_2.7.2-1.dsc 3) I use command root at pi1:/nut/nut-2.7.2# debuild -us -uc . .. And I have the following error code:

I think I had a misconception about something.. My goal was that someone could use our UPS with the "default" UPS driver in NUT right out of the box, so they wouldn't have to alter any NUT code to get it working. NUT config files, yes, but not NUT code. I thought that if I put in the ups.conf file that I wanted to use the usbhid-ups driver, and then put our vendor and product ID,

Hello, we have a Emerson Liebert GXT4, that we like to connect to our servers to shut them down if there is a power failure (which happens quite often in our area). I couldn't get the GXT4 working with usbhid-ups driver. So I need some advise to continue to get this device working. The GXT3 seems to be working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). Here is my

Ok, so please correct me if I?m wrong?. The quickest way to get my UPS running with nut (as the current release exists) is to either: 1) Add my vendor and device ID to the openups_usb_device_table OR 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list And then recompile/install. Obviously #1 will be easier at this point, but I understand that it

So....seems so better... Each time I rebbot, I miss the /var/run/nut folder... root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) root at artu:~# upsd Network UPS Tools upsd 2.7.2 fopen