similar to: Merging blzr as blazer (and un-merging voltronic?)

On Nov 1, 2013, at 9:03 AM, Charles Lepple wrote: > But if blzr supersedes both voltronic and blazer, I propose we rename blazer_{ser,usb} to blazer_{ser,usb}_old, then rename blzr* to blazer*, and revert the voltronic merge. Dan, The pull request against master looks good - thanks! What do you think about the renaming of blazer to blazer_old, and making blzr the new blazer driver? I still

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

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

Hello, I?m looking for the protocol for Voltronic power inverter (Axpert MKS 24V). Now I?m finding your e-mail communication: http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-April/006431.html where is a link to Voltronic_Power_UPS_Protocol.pdf Is there any *.pdf document for the Voltronic power photovoltaic inverters ?

Hi, it has been a while now since the last changes to the Voltronic Sunny code, because it's working just fine. I saw that there are a lot of changes in the master tree and my question is what I should do with the Voltronic Sunny part? Does it still make sense to try to make a pull-request out of it? Best, Nick

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

Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides

Dear All, Does anybody know the author of Voltronic USB driver , The protocol of some UPS was changed , If the author received this mail ,please contact me . Thank you very much . Best regards, Bluefish

Hi Thank you very much for the feedback. I will download and try to get it working on the Raspberry Pi. Regards Tom On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > 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 > >

(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

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

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"

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

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

Not of a big help here, but I think it's a voltronic power vesta 650: http://www.voltronicpower.com/oCart2/index.php?route=product/product&path=37&product_id=52 If that is the case, it should work both with the blazer drivers (i.e. all but the shutdown sequence) and with the now defunct voltronic ones. With arno's words: "We are currently merging a new driver to replace

On Nov 8, 2013, at 3:23 AM, Josu Lazkano wrote: > Hello, I have a Salicru SPS One 700VA device, I want to manage it with > Debian Whezzy. > > I read some information in the net about how to configure but I can > not get it working. I'm assuming you mean this blog post? http://blog.ciberterminal.net/2013/04/28/ups-salicru-en-nut/ > Could you help with this? > >