search for: voltronic

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

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 ) My UPS - reb...

...are trying to improve the support for it in NUT and his UPS seems to wake up after the witheout, he has problems that seem to be related to a specific sequence of commands, but I don't think that's the case with you. The 841+: as it comes with ViewPower, I suppose it's manufactured by Voltronic Power; if that is the case *and* your unit is using their 'QGS' ('voltronic' in NUT) protocol, maybe the UPS has the 'Auto Reboot' (in Voltronic Power's ViewPower) option disabled or 'ups.delay.start' (in NUT, using the new nutdrv_qx driver with protocol=voltroni...

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 ? http://www.voltro...

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

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

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

...d 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 > > This device could be supported by nutdrv_qx (subdriver > 'voltronic-sunny') built starting from this branch: > https://github.com/zykh/nut/tree/nutdrv_qx_voltronic-sunny_rebased+command > > Please note that this subdriver is not ready yet for pri...

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

...mmand [shutdown.return] failed > Apart from what the logs say, has the command some effects on the UPS? Can you please launch the driver with debug level = 3 and send the logs of when you execute the command shutdown.return via upscmd? I saw your new UPS is shipped with ViewPower (developed by Voltronic Power, mainly for their UPSes), so, if it's manufactured by Voltronic Power maybe it's using their new protocol 'QGS' (mapped as 'voltronic' in the new driver nutdrv_qx - available in 2.7.1) or one of their other ones. Maybe the command itself is accepted by the UPS, but sin...

...t 2kv is wrong. with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 Network UPS Tools - Generic Q* USB/Serial driver 0.33 (Windows-v2.8.0-alpha3-1252-g757813e) USB communication driver (libusb 0.1) 0.44 Using protocol: Voltronic 0.07 battery_number: 20 battery_number, settable range: 1..9 bypass_alarm: enabled battery_alarm: enabled bypass_when_off: disabled alarm_control: enabled converter_mode: disabled eco_mode: disabled battery_open_status_check: enabled bypass_forbidding: disabled setvar(bypass_when_off, disabled) byp...

...t 2kv is wrong. with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 Network UPS Tools - Generic Q* USB/Serial driver 0.33 (Windows-v2.8.0-alpha3-1252-g757813e) USB communication driver (libusb 0.1) 0.44 Using protocol: Voltronic 0.07 battery_number: 20 battery_number, settable range: 1..9 bypass_alarm: enabled battery_alarm: enabled bypass_when_off: disabled alarm_control: enabled converter_mode: disabled eco_mode: disabled battery_open_status_check: enabled bypass_forbidding: disabled setvar(bypass_when_off, disabled) byp...

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

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 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 can shutdown the ups by sending the command "shutdow...

...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 work with ViewPower. > > Have you rebuilt a .deb package before? Oops, just noticed the new thread where /dan replied: http://thread.gmane.org/gmane.comp.monitoring.nut.user/8023 -- Charles Lepple cl...

-----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 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 would be with the nutdrv_qx driver sin...

...upslogx(LOG_ERR, "instcmd: command [%s] failed", cmdname); return STAT_INSTCMD_FAILED; } Opinions? Is this the correct place to submit pathes? > However, your UPS seems to speak an idiom that's more akin to the one > covered by the voltronic drivers (i.e. the (ACK/(NAK replies) - > available in the github repo - so maybe they're worth a try. > I looked at the voltronic.c file. The protocol seems to be quite different. The rest of the driver works perfectly. (Unless voltronic firmware has an older "backwards compatible...

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