similar to: contineously receiving the same values

Hi Charles, Upsmart version is 1.5, copyright says 2012-2014 the github issue seems a bit worse, since it reports: received 10 (85) 1.158700 read: UPS No Ack whereas my system reports : 6.239688 Full update... 6.239776 send: Q1 6.261270 received 47 (40) 6.261371 read: (234.0 000.0 234.0 012 49.9 27.4 29.0 00001000 but it keeps repeating the last line,

On 22-3-2017 14:37, Charles Lepple wrote: > On Mar 22, 2017, at 9:29 AM, Marc Kessels <marc at kessels.name> wrote: >> Hi Charles, >> >> >> Upsmart version is 1.5, copyright says 2012-2014 > Do you have a direct link? I found UPSmart-DryContact-V3-4.zip and UPSmart-Networking-V2-4.zip via web search, but the dates for the Linux components are ~ 2002. my version

Hi Arnaud and NUT team You may recall some time ago, I and a few others posted questions about the above referenced (cheap and cheerful) USB-based UPS - specifically regarding FreeBSD USB support in NUT. The original posting was entitled "Zigor Ebro 650 compatibility". I've since tried the latest Windows port of NUT with my WinXP laptop connected to the Zigor Ebro and finally

The software UPSmart 1.5 is the same as I am using in this thread: http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-November/007248.html (starts in 2016-August) for the powercool 1500VA USB UPS. Have not yet been successful with getting it working with NUT but the symptoms are the same and you may find some of the debug useful from https://github.com/mattwire/powercool-ups If it helps, I

On Mar 22, 2017, at 9:29 AM, Marc Kessels <marc at kessels.name> wrote: > > Hi Charles, > > > Upsmart version is 1.5, copyright says 2012-2014 Do you have a direct link? I found UPSmart-DryContact-V3-4.zip and UPSmart-Networking-V2-4.zip via web search, but the dates for the Linux components are ~ 2002. > > the github issue seems a bit worse, since it reports: >

It seems like it works (partially?) with NUT/driver you mentioned. I will test it more when I return home. root at Failure:/lib/nut# ./nutdrv_qx -a test -x subdriver=fuji -u root -x productid=0000 -x vendorid=0001 -DDDDDD Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5) USB communication driver 0.32 0.000000 debug level is '6' 0.001247 upsdrv_initups...

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Hi again, I tested several times using the Megatec driver from nut 2.2.2 to no avail, as it definitely never "sees" the UPS. Always getting : # drivers/megatec -DDD -a Alpha Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec] Carlos Rodrigues (c) 2003-2008 debug level is '3' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED

Hi, i just got a Phoenix Technologies PH1200UPSB 1200va serial-port ups and it is only partially supported by bestups driver (needs manual ID or driver rewriting). It comes with a tool called UPSilon 2.1 on a CD (which worked better with TERM=linux). After [sl]tracing it i came to these results: COMMANDS : - Command: I Response: "#XPHOENIX TECH PH1200UPS VER2.00C " - Command: F

> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > >

Hello! I'm trying to use nut with a Ippon Smart Winner 3000 UPS (http://shop.key.ru/photo/items/45535.jpg) which looks like a custom-labeled OEM model of the megatec branch. I tried both the megatec_usb and the blazer_usb drivers for it, with a obvious config section: [ippon] driver = blazer_usb port = auto vendorid = 06da productid = 0003 desc = "Ippon Smart Winner 3000" If I

Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon

Hello First things first, thanks for great work with NUT. For years I used Informer compact 3kVA UPS http://www.informups.com/informer_compact.html with nut/megatec serial driver, but it stopped working when I switched to blazer_ser with 2.6.0 upgrade. I'm using 2.6.0 on gentoo. Blazer_ser seems to connect with UPS, but upsmon reports driver not connected. uname -a Linux localhost

UPS: PowerWalker VFI 3000RT LCD CentOS 6.5, nut installed from RPM package: nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Driver: blazer_usb Problem description: USB device "loops" when starting blazer_usb. USB device permissions are ok. Receives some information. Error messages: "failed to claim USB device: could not claim interface 0: Device or resource busy"

2013/9/16 Martyn Hill <martyn.joseph.hill at gmail.com>: > Hi Arnaud and NUT team > > You may recall some time ago, I and a few others posted questions about the > above referenced (cheap and cheerful) USB-based UPS - specifically regarding > FreeBSD USB support in NUT. The original posting was entitled "Zigor Ebro > 650 compatibility". > > I've since

Hi, I have been blessed with the "Numeric 2000 Plus" UPS, suspected to be of 2KVA rating. This UPS does not figure in the list of UPS recognised by NUT. However I get lucky with megatec driver. Here is the log... ----------------------------------------------------------------------------------------------------- Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues

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 Mar 22, 2017, at 6:27 AM, Marc Kessels <marc at kessels.name> wrote: > > with NUT, I am able to connect to the UPS using the blazer_usb and nutdrv_qx. However, the reported values are constant, and only change if I run the UPSmart tool (It can run in parallel). What can I do to get NUT to receive updated values? Which version (and how old) is UPSmart? This just came up in a

Hi! This is the weirdest problem I have found for a long time! Using nut-2.0.5 and a Gentoo powered HP Proliant ML350 I setup the config files just the same as I always do and tried to get the megatec driver chatting to the UPS. It worked fine on a Windoze server with Upsilon2000 so I have a bit of confidence in cable etc! When I ran upsc after starting upsd to complained about stale data! Most