similar to: NUT and UPS TS Shara

Hi Rodolfo, [please reply to <nut-upsdev at lists.alioth.debian.org>, not nut-upsdev-owner, and if you have large attachments, upload them to a web server and post the URL. Thanks!] On Jan 29, 2014, at 7:59 AM, rodolfo at tsshara.com.br wrote: > <blazer_usb.c.txt> > Sorry, we forgot to send another file. We developed this code (blazer_usb.c.txt) so that your software is able

I added the sgs subdriver to nutdrv_qx: https://github.com/zykh/nut/tree/ts-shara (I assumed Rodolfo - surname? - is the author of the code, do you want me to change it?) I changed a couple of things: - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478 -

2014-01-31 hyouko at gmail.com <hyouko at gmail.com>: > I changed a couple of things: > - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478 > - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R482 Better links:

Hello, I think that on this file nutdrv_qx_megatec.c the definition for shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m while on the megatec protocol description ( http://networkupstools.org/protocols/megatec.html) the command is just "S%s\r". When I changed it my system was abe to at least stay off, and stopped making an instant power recycling.

Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some

2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hi, > > I had an issue where after returning the power from a shutdown.return the > ups would do another shutdown.return during the boot, and kept this forever. > After some investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my

Hi all I need to control an UPS TSSahara usign NUT in pfsense and it is not working. Can somenone help ? ups.conf user=root [tsshara] driver = megatec_usb port = auto vendorid = 0483 productid = 0035 desc = "No Break TS-Shara" [myups] driver=usbhid-ups port=auto /usr/local/libexec/nut/megatec_usb -u root -a tsshara -DD Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14

On 06/18/2017 05:42 PM, Charles Lepple wrote: > On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: >> >> running autogen.sh was triggered automatically. but even if I do it >> explicitly, I still get: >> + autoreconf -i >> configure.ac:887: warning: AC_LANG_CONFTEST: no

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

On 06/19/2017 11:02 AM, Manuel Wolfshant wrote: > Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function

On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also

Hi, I am trying to get NUT 2.7.2 working on my Solaris 11.2 system with a PowerWalker 2000 VI PSW UPS. I have carefully configured the software such that it 'works' using custom values in the ups.conf file: driver = nutdrv_qx port = auto desc = "my UPS" protocol = voltronic-qs subdriver = cypress vendorid = 0665 productid = 5161 The problem I'm experiencing is that after a

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I would like to propose an interface change/extension, in order to be able to clearly differ from a PRE_SEND and a POST_RECEIVE item_t->preprocess-ing calls. IMHO there is no option to differ from item->preprocess(..), called from [1] and called from [2], at the moment. My idea is to extend the item_t->preprocess(..) with an additional

On Jun 9, 2014, at 6:40 AM, Hill wrote: > Hi, > This is my first post ever on a technical forum, so please forgive any poor etiquette etc. > Also I'm totally new to Linux all of my experience has been trying to get this UPS to work. So please bear this in mind. No worries. On the NUT lists, we don't set or alter the reply-to header, so please use "reply all" to make

Dear Daniele, nice to meet you, I'm a collegue of Gabriele. The problem with "blazer_usb" driver ("blazer_ser" works correctly) is related to the following commands: - "F" and "I": when the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not

Hi, This is my first post ever on a technical forum, so please forgive any poor etiquette etc. Also I'm totally new to Linux all of my experience has been trying to get this UPS to work. So please bear this in mind. I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and

mmh.. it looks like someone forgot to hit 'reply all'. - relaying the originally attached files (gzipped, minus the two screenshots, to keep size down). 2015-03-09 23:20 GMT+01:00 Jakub Scepka (private) <jakub.scepka at gmail.com>: > Hi everyone! > > Here is summary for our fellows wit the same/similar UPS to save them 3 > weeks of life :) > > First of all I'm