similar to: MEC0003 protocol support

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

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:

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 =

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

http://www.zigor.com/uk/index.php/en/products/upssystems/danubioseries Ships with UPSilon 2000 software, and appears to work with blazer_usb to a certain extent with the following config: [danubio] driver = blazer_usb langid_fix = 0x409 port = stupidly, I seem to have to set this even though it's ignored vendorid=0001 productid=0000 Yes, vendor 0001,

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

Hello I am using Freenas 11.3 (freebsd like) with a GREENCELL usb ups. with nut 2.7.4_13 pre installed But, this ups is not detected as "blazer_usb" on port "auto" neither "ugen0.4"! Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4) No supported devices found. detail below. Another info : This

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

On Monday 22 June 2020 15:36:21 Charles Lepple wrote: > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one > user- I think the allowed commands all need to be listed on one >

On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed on one

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

On Monday 22 June 2020 18:50:25 Gene Heskett wrote: > On Monday 22 June 2020 18:03:16 Charles Lepple wrote: > > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > >> So I just edited /etc/nut/upsd.users to add both the commands it > > >> claims to have but get this response to either: > >

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20

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

Regards I am installing NUT for the UPS Skate UPS-2200D, the UPS have conection with USB to PC and i have problems to configure nut the ups is conected and Linux report this config Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7 Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002 Aug 19 23:35:06 dakota kernel:

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

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

Hello, we have a problem using APC Back-UPS CS 500 (connected via USB, usbhid-ups-apc) and UPS-NUT. We've tried different Versions of UPS-NUT (2.2.1 and 2.2.2), including the latest from SVN (28th November 2008). We've also tried apcupsd, which works fine for our requirements, but we don't want use it. What we need is simple: The UPS should turn off after power loss and shutdown

I was dropping off junk at the waste transfer station and scarfed a UPS out of the pile of old TV's and VCR's. It was in good physical condition and as I expected, the battery was toast. A new RBC-2 battery restored it to working condition. Then I tried to get it to talk to some software. And I am having no luck. The unit is branded as a Nexxtech Model 6118507 650VA imported into