similar to: UPS Requiring URB_INTERRUPT with Megatec Protocol

> I have a UPS unit with a USB Interface that appears to work with the blazer_usb and nutdrv_qx drivers. I have tried all combinations of subdriver and protocol and the result is always the same. The values returned are all zero's. > > The issue seems to be the same as https://github.com/networkupstools/nut/issues/307 > > Attempts to send a command to silence the beeper or

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

Hi Mario, Mario Cassani wrote: > Hallo Arnaud, > some months ago I bought an SBS GC400 UPS. > I came with a kit RS232 + UPSmart CDROM that works only with RedHat 7.0-7.3. > As I use Debian I tried alien with no success. > > Can you please provide me with any hint to understand if my UPS can be managed by NUT? > Can a driver be written, knowing how the cable

Hello, I'm trying to get an energenie EG-UPS-033 (http://energenie.com/item.aspx?id=8087) to work with nut. It standard comes with linux software (UPSmart), which shows the input/output voltage, load level, input frequency. and battery and case temperature. The values change about every second. The selected monitor mode in this tool is Mega(USB). The bad thing of this tool that it

Hello folks, I have a question regarding a sweex product. Its bundled with UPSmart v 2.12. I installed nut accordingly to the user manual included in the software. A quick check of data/drivers.list revealed to me i should use the: "Sweex" "500/1000" "contact closure - shipped with UPSmart" "genericups upstype=7" driver this driver

Wow just seen this screenshot. I did not know it did that. Is this the port is ask for? Can I go to it's webpage and some port to see this type screen? -Raymond Day On 11/3/2016 6:39 PM, Matthew Wire wrote: > https://github.com/mattwire/powercool-ups/blob/master/UPSmart_connected.png > - is a screenshot of the UPSmart software when connected (shows some > values from UPS).

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Thanks for the log - apparently we always get valid (apart from 0.191312) but empty replies, not only for index 0x03, but also for the other queried index (0x0c). I've re-looked at the logs you posted on GitHub, but I don't see anything exotic going on there. Maybe we're missing some sort of handshaking or the like: can you post the whole captures/logs, right from when you plug the

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

Further analysis it looks like the status string matches the q1 subdriver but a lowercase "f" is sent to request it instead of "Q1\r". What do you think? ---------- Forwarded message ---------- From: "Matthew Wire" <devel at mrwire.co.uk> Date: 30 Aug 2016 22:51 Subject: powercool 1500VA USB UPS To: <nut-upsuser at lists.alioth.debian.org> Cc: I have

Hello, I am new to UPS stuff, please be patient with me ;-) Archlinux i686, kernel 3.0-ARCH #1 SMP PREEMPT. nut 2.6.1 installed from source via Arch's AUR repository. Mother board GA D525TUD with two serial ports, both enabled in BIOS. I got some old Orvaldi 520 PL UPS [1], which is supposed to be supported by the vendor [2] with sw called UPSmart. The statically compiled i386 binary ran

Hi Charles, I've added 3 more files to github. https://github.com/mattwire/powercool-ups/blob/master/wireshark-UPSmart-startup.pcapng - captures startup of UPSmart software and continues for about 5 minutes. https://github.com/mattwire/powercool-ups/blob/master/wireshark-UPSmart-ups_off-on.pcapng - UPSmart software is running, UPS is OFF. UPS is switched on and connects to software.

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

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, I've sent the following message 3 weeks ago, yet have recieved no reply at all. I don't want to nag, but could anyone please help me? Thanks, Dror ------------------ Hi, I have a UPS of the Israeli company Sustainer, model S-1000C (http://www.sustainer.co.il/data/files/specifications%20smart%20en.pdf - don't worry, it's in english...). I've been trying to connect to

Cheers all, Got an interesting report at https://github.com/networkupstools/nut/issues/2208 about Qx devices that do not respond to NUT unless `upsmart` somehow inits them first (until a re-plug). This behavior is something I've heard of a couple of times, and now there are pcap captures to help smart folks make heads or tails of it and teach `nutdrv_qx` the optionto initialize the UPS

Hi All, I've finally found solutions for my previous problems. But since this includes changes in the shared files, I'd like to discuss them here. 1. Driver restart problem. When I start the driver for the first time, everything is ok. But when I want to restart it, problems begin. The driver fails to read Report descriptor for the second time (libusb_open is used to open the device).

I have recently purchased a powercool 1500VA UPS (this one: https://www.cclonline.com/product/106782/PC-1500VA/UPS-Battery-Backup/Powercool-Smart-UPS-1500VA-3-x-UK-Plug-3-x-IEC-RJ45-x-2-USB-LCD-Display/UPS0171/?gclid=Cj0KEQjw3ZS-BRD1xu3qw8uS2s4BEiQA2bcfMwMPzsshzLqNK3E8NoAKQ6PPWRW589_zkYZ5YZDInb4aAuqK8P8HAQ ). It comes with software for windows/linux called UPSmart1.5 which connects and monitors

Hi, I have a UPS of the Israeli company Sustainer, model S-1000C (http://www.sustainer.co.il/data/files/specifications%20smart%20en.pdf - don't worry, it's in english...). I've been trying to connect to it from Debian to no avail for a long time now. The company has attached to it a program called Commander Pro (for windows) and RPMs of UPSmart for old versions of Redhat and