search for: mattwir

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

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

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

...cts and monitors this UPS. I am unable to use it with NUT at present. It seems that the driver nutdrv_qx could be made to support it but does not at present. I am testing with the command: ./nutdrv_qx -u root -a powercool -DDDDD -x vendorid=0001 -x productid=0000 On my github https://github.com/mattwire/powercool-ups you can see some debug data. The file powercool_usbmon.txt is captured using wireshark and contains a startup, connection and shutdown of UPSmart software. You can see that it is reading some data correctly from the UPS. Could you advise what is the best way to proceed with this p...

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

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.

...cts and monitors this UPS. I am unable to use it with NUT at present. It seems that the driver nutdrv_qx could be made to support it but does not at present. I am testing with the command: ./nutdrv_qx -u root -a powercool -DDDDD -x vendorid=0001 -x productid=0000 On my github https://github.com/mattwire/powercool-ups you can see some debug data. The file powercool_usbmon.txt is captured using wireshark and contains a startup, connection and shutdown of UPSmart software. You can see that it is reading some data correctly from the UPS. Could you advise what is the best way to proceed with this p...

...ead: 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 can provide additional logging/testing etc. On 22 March 2017 at 14:09, Marc Kessels <marc at kessels.name> wrote: > > > On 22-3-2017 14:37, Charles Lepple wrote: > >> On Mar 22, 2017, at 9:29 AM, Marc Kessels <marc at kessels.name> wro...