similar to: QX/hunnox device init requires upsmart

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.

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

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

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

Hello, I have an UPS Hunnox HNX-650 (http://www.hunnox.com/), but it's not quite running yet with NUT. Any hints? Thanks... Some info: * lsusb: Bus 005 Device 003: ID 0001:0000 Fry's Electronics * usb-devices: T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0001 ProdID=0000 Rev=01.00 S:

Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides

Hello, 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 trigger a battery

> 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

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

Dear R users: I was trying to fit a HMM with mixture of Gaussian into the dataset, and I tried to implement it by R2Winbugs. But I got the following errer. * Error in FUN(X[[1L]], ...) : .C(..): 'type' must be "real" for this format* Does anybody know what's the problem? Does R2Winbugs accept some matrix as inits? I would really appreciate your help. Thank you very much.

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,

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

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

Hello all, I've gotten the printing subsytem almost working - I think. I am able to install my print drivers to the server IAW the instructions found here: http://us4.samba.org/samba/docs/man/printing.html The drivers are being installed to /etc/samba/drivers/W32X86 IAW /etc/samba/smb.conf by following the instructions above This line specifically seems to do it: [print$] path =

On Wed, Aug 31, 2016 at 4:19 AM, Matthew Wire <mjw at mjwconsult.co.uk> wrote: > 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? It is certainly possible - there is no comprehensive protocol guide for all these variants. I was hoping we would hear from

Hi, it does communicate using the fabula subdriver but I don't get any of the values parsed. If I execute: ./nutdrv_qx -a powercool -DDDDD -x subdriver=fabula -x vendorid=0001 -x productid=0000 I get the following returned: 12.242991 upsdrv_updateinfo... 12.243047 Quick update... 12.243069 send: Q1 12.243087 command index: 0x03 12.249983 read: (47 bytes) => 28 30 30 30 2e 30 20

> On Oct 10, 2016, at 4:29 PM, Matthew Wire <mjw at mjwconsult.co.uk> wrote: > > Here is the complete log for two minutes from startup. thank you compressed to fit on the mailing list. > > On 9 October 2016 at 23:41, hyouko at gmail.com <hyouko at gmail.com> wrote: > > 12.243069 send: Q1 > > 12.243087 command index: 0x03 > > 12.249983 read: (47

Thanks again for the logs. Now... let's assume those interrupts are needed to get valid values... well, we can't do exactly the same thing, but let's start from this one: https://github.com/zykh/nut/tree/nutdrv_qx_fabula-zero Please, test nutdrv_qx (with subdriver 'fabula') from that branch and post the output of it running with debug-level of 5.