similar to: Lupus 500 MEC0003 Problems

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

Sorry for the huge delay and thanks Charles for taking care of this topic. >> 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 running NUT 2.6.5. >> But unfortunately none of the Instcmds such as load.off etc. worked. > > Can you post

Sorry for my delay, I've only just read this mail. At first glance the driver looks like it should work, I will test it tomorrow (if possible) and let you know. I'll also give a reply to your questions. Many thanks for the work you've already put into this. -------------------------------------------------- From: <hyouko at gmail.com> Sent: Monday, June 30, 2014 12:42 AM To:

Finally I got time to test this. >>> Can you post the output of upsc, and note if any of those values look >>> wrong? serwer2:/tmp/nut-fabula # upsc myups battery.charge: 100 battery.voltage: 13.10 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.model: 500VA UPS device.type: ups driver.name: nutdrv_qx driver.parameter.pollfreq: 30

> Everything looks fine apart from ups.beeper.status always shows enabled > even if the status bit fom the ups has changed state. Probably because the driver updates the beeper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff /

-------------------------------------------------- From: <hyouko at gmail.com> Sent: Tuesday, July 08, 2014 12:16 AM To: "Hill" <hill at fermot.com.pl> Cc: "Charles Lepple" <clepple at gmail.com>; <nut-upsuser at lists.alioth.debian.org> Subject: Re: [Nut-upsuser] Lupus 500 MEC0003 Problems >> Everything looks fine apart from ups.beeper.status

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

Hi Folks, This is my first post on nut-upsdev. I would like to share a small patch to enable support for the Powercool PCRACK 1200VA ups. I found that the UPS uses megatec/krauler protocol but is sensitive to the USB buffer length passed to it in requests via usb_get_string(), and usb_get_string_simple(). If the buflen is greater than 102 then the ups will reply to requests but does not

Hi, I am using a ALLNET 91500 UPS with blazer_usb driver /usr/lib/ups/driver/blazer_usb -a ups91500 -L Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) I have this settings: upsc ups91500 at localhost battery.charge: 100 battery.runtime: 12000 battery.voltage: 27.50 battery.voltage.high: 27.3 battery.voltage.low: 18.0 device.type: ups driver.flag.novendor: enabled driver.name:

Dear Daniele, i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver: some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2: - first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short

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

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see drivers that uses the VID

On Wed, 14 Oct 2015, Davide Baldini wrote: >> Is there any command in the list provided by "upscmd -l myups" which is >> accepted by this UPS? > > None of the command sin the list successfully completes, not even > beeper.toggle. It looks as if the problem is more general than turning off the UPS. The command mechanism is broken. > I added -q and -D to

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

Sorry about the noise guys. Below a significantly improved patch. The main difference is that all calls to usb_get_string_.. have been wrapped in a new function nut_usb_get_string()  that is implemented in libusb.c This was necessary in order to make the bufflen_fix available in libusb.c where usb_get_string() is called in libusb_open() This wrapper function mops up and hides all the work

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 have an UPS by Legrand, model Daker DK 1 kVA, i have tried to use "nutdrv_qx" driver with usb but have no success. I will send you all the information you need to try to solve or write the correct driver. Hope to be useful. regards Andrea

Would you be so kind and provide some examples (commands), please? I would run them today in the evening and report back with the logs. Thank you. Jakub S. On Tue, Mar 10, 2015 at 11:44 PM, hyouko at gmail.com <hyouko at gmail.com> wrote: > mmh.. it looks like someone forgot to hit 'reply all'. > > - relaying the originally attached files (gzipped, minus the two >

On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at gmail.com> wrote: > Come on, it started to be interesting! Do you have one of these UPSes? If so, here was Dan's email about a branch to test: > If you still can't get it to work with nutdrv_atcl_usb, another > approach could be worth considering. > > Since this UPS seems to be supported by UPSmart2000I, it could