similar to: infosec e4

On Aug 1, 2013, at 8:15 AM, Charles Lepple wrote: > On Jul 29, 2013, at 7:12 AM, James HORLEY wrote: > >> There?s a software advised by the constructor that work on linux (http://www.power-software-download.com/viewpower.html), unfortunately it?s heavy (tomcat and java) and I don?t find it as flexible as NUT. > > We have a development branch called "voltronic-driver"

On Jul 29, 2013, at 7:12 AM, James HORLEY wrote: > There?s a software advised by the constructor that work on linux (http://www.power-software-download.com/viewpower.html), unfortunately it?s heavy (tomcat and java) and I don?t find it as flexible as NUT. We have a development branch called "voltronic-driver" which might work better than the blazer* for UPS models which are meant to

I compile nut with the voltronic-driver on my computer then I've copy the driver "/lib/nut/voltronic_ser" on the server. I can now shutdown the ups using "upscmd -u admin myups shutdown.return". My first question is, is it really ok to only take the driver whithout taking the whole package? I'm using upssched to shutdown server after 15mn on battery, the

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

On Aug 26, 2013, at 6:22 AM, James HORLEY wrote: > I've download again nut source today from "https://github.com/networkupstools/nut/tree/voltronic-driver" and try compiliing the voltronic-driver. This branch has been merged in, and will be part of 2.7.1 when it is released. > The drivers is working fine (ie computer is shutting down) except for the shutdown of the ups. >

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

I've download again nut source today from "https://github.com/networkupstools/nut/tree/voltronic-driver" and try compiliing the voltronic-driver. The drivers is working fine (ie computer is shutting down) except for the shutdown of the ups. I can shutdown the ups by sending the command "shutdown.return" but standard shutdown doesn't work. upsmon -K return: kill: No

Great, it's working fine. I'm using upssched to shutdown computer after 15mn when on battery. Should I trigger "upsmon -c fsd" with my script? I mean, is it the normal way to shutdown both computer and ups. Best regards, -----Message d'origine----- From: Charles Lepple Sent: Monday, August 26, 2013 3:07 AM To: James HORLEY Cc: nut-upsuser list Subject: Re: [Nut-upsuser]

(Keep the list CCed) 2014/1/4 Eirik Skorstad <eskorsta at hotmail.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> Assuming shutdown.return works when issued via upscmd (does it >> work?), the problem seems to be that your UPS doesn't accept a >> shutdown.stop when there's no shutdown pending (or, maybe, the UPS >> doesn't

2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > Hi all, Hi > I've problem with the management of my AtlantisLand UPS, the UPS don't want > to wake up after the whiteout and I don't have any idea why.. Some (very old) units are known to have problems with small values for ondelay (hence the default 3 minutes value):

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

2013/12/9 Fabio Cecamore <ceca_89 at hotmail.com>: > and the UPS don't wake up after the whiteout.. 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > desc = "AtlantisLand Host Power 851+" Is your UPS an 'Atlantis Land Host Power 851' or an 'Atlantis Land One Power 841+'? The first one should be using a slighty modified version of the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there! I don't know if you are able to help me. Have tried almost everything at this point.. I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD 2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD 1500VA Online UPS. Seems like the driver is accepting both, however, the shutdown command wont work. And this

Hi there, I made a new driver, based on blazer, that should work with most of the UPSes manufactured by Voltronic Power - http://www.voltronicpower.com/oCart2/index.php?route=product/category&path=37- and rebranded as Atlantis Land, Cablematic, EPC, FSP, Mustek, SHT, Tuncmatik and many others (they come with a software called Viewpower - http://www.power-software-download.com/viewpower.html )

Thanks for your reply Hyouko, these are the actual not working parameters: driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 ups.delay.shutdown: 60 ups.delay.start: 300 and the UPS don't wake up after the whiteout.. My UPS is not so old :( Il 09/12/2013 16.04, hyouko at gmail.com ha scritto: > 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: >> Hi all, > Hi

Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Michal's apcsmart updates. On

In my opinion, there might be just one problem: the blzr driver doesn't provide anymore two splitted drivers (serial and usb), so this isn't going to be a 'silent update' for those using these drivers (should we provide symlinks or the like?). If this doesn't sound like a problem to you, I'll take care of the rename. Plus, if you could take a look to the blazer-fix pull

Hi I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as the MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I am trying to monitor the inverter using NUT on a Raspberry Pi (I have tried Ubuntu as well with the same results). I have tried most of the drivers with no success. The inverter came with the ViewPower software so I assumed that my best chance

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

Hi, There seems to be a problem turning of the inverter on a Mecer online 1000VA UPS. OS: Debian Wheezy Nut: Installed via apt - version 2.6.4-2.3 Debug output from driver. root at proxmox1:~# /lib/nut/blazer_usb -DDDDD -a mecer -k Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000 send_to_all: SETINFO driver.parameter.port "auto" 0.000023