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 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 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 please? Cheers, Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160831/461103bd/attachment.html>
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? 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 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 please? Cheers, Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160831/e27a9a97/attachment.html>
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 the author of nutdrv_qx, but in the mean time, he also wrote this portion of the developer documentation: http://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#nutdrv_qx-subdrivers In your case, it sounds like you can start from the q1 driver - maybe modify it in-place first to verify assumptions, then move it to a new file. Let us know if you need help getting a development environment set up. It is often possible to configure NUT to match the paths of existing packages, such that you can temporarily run the new driver from the source tree and have it connect to the packaged upsd. One potential hitch is that there are already several devices out there with the 0001/0000 ID. -- - Charles Lepple
Matthew, I've looked briefly at the files you uploaded to GitHub and it seems to me that the device is like something that should work with the 'fabula' USB subdriver (and 'megatec' protocol): what are the issues you are experiencing and that prevent the driver to work?