<div dir="ltr"><div>Also, regarding current NUT on CentOS 6: I was curious, so confirmed this is possible (can build and pass programmatic self-tests, did not try it against hardware devices), although it did need a little chiseling around some rough edges.</div><div><br></div><div>Details posted in PR <a href="https://github.com/networkupstools/nut/pull/1804">https://github.com/networkupstools/nut/pull/1804</a> which will be merged into the "master" branch when no other CI farm systems complain about the proposed change.</div><div><br></div><div>Hope this helps,</div><div>Jim Klimov</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 9, 2023 at 9:53 AM Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com">jimklimov+nut@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>>
<span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Previously, the manufacturer tested this UPS on version 2.6.5-6 NUT for Windows.</span>
</div><div><br></div><div>Thanks for this important detail.</div><div><br></div><div>
<div>For immediate re-testing, I would recommend to use either NUT
v2.8.0 already packaged by some distributions in their
testing/bleeding-edge repositories (unfortunately, during the almost
year since release many distros - especially for LTS versions - did not
change recipes to bump up from 2.7.4), or better yet to build from <a href="https://github.com/networkupstools/nut/" target="_blank">https://github.com/networkupstools/nut/</a>
sources on a POSIX platform (Linux, MacOS, *BSD, Solaris/illumos, etc.)
which they would be more comfortable with - to take advantage from
recent bug fixes and improvements, including some that impacted USB drivers and drivers talking the Megatec Qx (numbered "x") family of protocols (which includes older blazer drivers and newer nutdrv_qx with its many subdrivers). <br></div><div><br></div><div>For your target deployment, ensuring a build on CentOS 6 makes sense and might be or not be an adventure of its own. For preparing a build environment, CentOS chapter in <a href="https://github.com/networkupstools/nut/blob/master/docs/config-prereqs.txt" target="_blank">https://github.com/networkupstools/nut/blob/master/docs/config-prereqs.txt</a> and general container setup notes in <a href="https://github.com/networkupstools/nut/blob/master/docs/ci-farm-lxc-setup.txt" target="_blank">https://github.com/networkupstools/nut/blob/master/docs/ci-farm-lxc-setup.txt</a> might help. Also maybe an older discussion on builds for the platform <a href="https://alioth-lists.debian.net/pipermail/nut-upsdev/2015-March/006922.html" target="_blank">https://alioth-lists.debian.net/pipermail/nut-upsdev/2015-March/006922.html</a> would inspire new work...<br></div><div><br></div><div>In any case, old NUT releases are "set in stone" so
further fixes (if needed) can only be made over the master branch, which is a moving target and snapshots of which eventually become releases - and that
fixing would need confirmation the problems are in fact there today (and a way to check
that a fix solves them).</div><div><br></div><div></div>*** For more context about NUT for Windows builds ***<br></div><div><br></div><div>
<div>NUT for Windows was a side-branch project; the latest release of
which (tagged 2.6.5-6 in codebase) was in 2014, and then it was not
addressed at all. I am not certain at the moment if the published MSI
installers were from this revision or some even older code.</div><div><br></div>
During the last year (after NUT v2.8.0 release) the differences of that branch compared to its contemporary NUT codebase (late 2.6 - early 2.7) were analyzed to bring back Windows build-ability and make it part of NUT "master" branch, to allow further developers to complete and test this code (AFAIK nobody stepped up yet, although there were some promising exploratory discussions), and to pass CI builds for at least non-regression of current achievements.</div><div><br></div>However this effort is not fully finished - in particular, the installer was not addressed (which I suppose allows libusb driver hooks to be added to the OS at high enough privilege level to actually capture USB device data, not only see their identification). Also, libusb0 (used before NUT 2.8.0) effectively died off, and libusb1 changes were I think the networked drivers (SNMP, NetXML) and possibly Serial-port drivers should work however. There are also some functional codebase differences, including a few methods that were not converted from POSIX to WIN32 coding and are just place-holders, but this should only impact a certain small subset of programs.<div><br></div><div>
<div>Recent CI results and binary artifacts can be seen in <a href="https://ci.appveyor.com/project/nut-travis/nut/history" target="_blank">https://ci.appveyor.com/project/nut-travis/nut/history</a>
(look for a top entry that says only "master <> commit-id" for
shared codebase iterations based on merged pull-requests, and the
Artifacts tab there - e.g. <a href="https://ci.appveyor.com/project/nut-travis/nut/builds/45872949/artifacts" target="_blank">https://ci.appveyor.com/project/nut-travis/nut/builds/45872949/artifacts</a> for latest build as of today). I think the persistent latest-build link is <a href="https://ci.appveyor.com/project/nut-travis/nut/build/artifacts" target="_blank">https://ci.appveyor.com/project/nut-travis/nut/build/artifacts</a>
but may show PRs as well. These archives are just tarballs of the
build's `make install` proto area including third-party FOSS DLLs, which help in testing when unpacked but are not
currently
a
"proper" Windows package installer.<br></div><div><br></div><div>Helpful links:<br></div><div><br></div><div>* <a href="https://github.com/networkupstools/nut/labels/Windows" target="_blank">https://github.com/networkupstools/nut/labels/Windows</a> - all issues and PRs tagged for this subject<br></div><div></div>
* <a href="https://github.com/orgs/networkupstools/projects/2" target="_blank">https://github.com/orgs/networkupstools/projects/2</a> - tracking what was done and what remains to do in NUT for Windows effort</div><div>* <a href="https://github.com/networkupstools/nut/issues/5" target="_blank">https://github.com/networkupstools/nut/issues/5</a> details much of that work as it progressed</div><div>* <a href="https://github.com/networkupstools/nut/issues/1690" target="_blank">https://github.com/networkupstools/nut/issues/1690</a> contains some analysis for libusb installation to the OS</div><div><br></div><div>Hope this helps,</div><div>Jim Klimov</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 9, 2023 at 8:04 AM Alexander <<a href="mailto:ak@enfall.com" target="_blank">ak@enfall.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div lang="RU"><div><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Hello Jim,<br><br>Thank you for your feedback, <br><br><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">[Jim]: <i>did you have a chance to test those devices with current NUT master branch from Github (some time last year, preferably after 2.8.0 release in April)?</i><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">[Alexander]: <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Now we don't have UPS samples on hands, we will ask the manufacturer to try testing NUT 2.8.0.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Previously, the manufacturer tested this UPS on version 2.6.5-6 NUT for Windows.<br>Could you suggest the correct link to download NUT v2.8.0 for Windows?<br><br><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Best regards<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Alexander Kirillov<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">company Enfall<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">mobile: +7 904 333 38 86 (WhatsApp, </span><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">Telegram</span><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">)<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">e-mail: </span><a href="mailto:ak@enfall.com" target="_blank"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(5,99,193)" lang="EN-US">ak@enfall.com</span></a><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:16pt;font-family:Broadway;color:rgb(31,73,125)" lang="EN-US">ENFALL</span><span style="font-size:16pt;font-family:Broadway;color:rgb(31,73,125)"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US">energy</span><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US"> </span><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US">for</span><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US"> </span><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US">all</span><span style="font-size:10pt;font-family:"Calibri",sans-serif;color:rgb(146,208,80)"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Calibri",sans-serif;color:rgb(146,208,80)"><u></u> <u></u></span></p><p class="MsoNormal"><b><i><span style="font-size:9pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)">УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ:</span></i></b><i><span style="font-size:9pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)"> <u></u><u></u></span></i></p><p class="MsoNormal"><i><span style="font-size:9pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)">Это электронное сообщение и любые документы, приложенные к нему, содержат конфиденциальную информацию. Настоящим уведомляем Вас о том, что если это сообщение не предназначено Вам, использование, копирование, распространение информации, содержащейся в настоящем сообщении, а также осуществление любых действий на основе этой информации, строго запрещено. Если Вы получили это сообщение по ошибке, пожалуйста, сообщите об этом отправителю по электронной почте и удалите это сообщение. <u></u><u></u></span></i></p><p class="MsoNormal"><b><i><span style="font-size:9pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US">CONFIDENTIALITY NOTICE:</span></i></b><i><span style="font-size:9pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US"> This email and any files attached to it are confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email. <u></u><u></u></span></i></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri",sans-serif;color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><b><span style="font-size:11pt;font-family:"Calibri",sans-serif" lang="EN-US">From:</span></b><span style="font-size:11pt;font-family:"Calibri",sans-serif" lang="EN-US"> Jim Klimov [mailto:<a href="mailto:jimklimov%2Bnut@gmail.com" target="_blank">jimklimov+nut@gmail.com</a>] <br><b>Sent:</b> Sunday, January 8, 2023 4:43 AM<br><b>To:</b> Alexander <<a href="mailto:ak@enfall.com" target="_blank">ak@enfall.com</a>><br><b>Cc:</b> nut-upsdev <<a href="mailto:nut-upsdev@alioth-lists.debian.net" target="_blank">nut-upsdev@alioth-lists.debian.net</a>>; Pavel <<a href="mailto:pp@enfall.com" target="_blank">pp@enfall.com</a>><br><b>Subject:</b> Re: [Nut-upsdev] Prolink UPS NUT driver<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><div><p class="MsoNormal"><span lang="EN-US">Hello all,<u></u><u></u></span></p><div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"> I really hope somebody picks up this bounty :)<u></u><u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"> Going forward, however, nutdrv_qx driver should be evolved via new subdrivers (and used) rather than older Qx drivers like blazer.<u></u><u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US">@Alexander : did you have a chance to test those devices with current NUT master branch from Github (some time last year, preferably after 2.8.0 release in April)?<u></u><u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"> If tests were done earlier with packaged NUT version, I suppose it would be 2.7.4 or older. If they used whatever CentOS 6 packaged, it could be even more antique (2.6.5?). As a community, we can only support and patch current NUT codebase, not directly old releases, but it is mostly evolution so what worked years before should not be worse now :)<u></u><u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span lang="EN-US"> I *guess* current NUT might just build on CentOS 6, but CI farm regularly only tests CentOS 7 as an example old platform (and recently Solaris 8 buildability was revived), so there may be some chizeling needed or not for builds there.<u></u><u></u></span></p></div></div><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><div><div><p class="MsoNormal"><span lang="EN-US">On Sun, Jan 8, 2023, 00:39 Alexander <</span><a href="mailto:ak@enfall.com" target="_blank"><span lang="EN-US">ak@enfall.com</span></a><span lang="EN-US">> wrote:<u></u><u></u></span></p></div><blockquote style="border-color:currentcolor currentcolor currentcolor rgb(204,204,204);border-style:none none none solid;border-width:medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin:5pt 0cm 5pt 4.8pt"><div><div><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">Hello NUT developers,<br><br>Happy New Year!<br>We sent a similar request to the mailing list earlier in 2022, hope somebody can be interested now and help us with the issue described below. <br>Of course, we are ready to reward for such help, if you have the opportunity to solve the problem, please let us know the price of the solution. Feel free to email us directly at </span><a href="mailto:ak@enfall.com" target="_blank"><span lang="EN-US">ak@enfall.com</span></a><span style="color:rgb(31,73,125)" lang="EN-US">.</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US"> </span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">The manufacturer Prolink has an 650VA UPS model. To supply this UPS to the customer, we should first ensure the compatibility of this UPS model with the NUT monitoring system. <br>The customer’s NUT monitoring system works on CentOS 6. </span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">At the moment, information has been received from the manufacturer about NUT monitoring support, but only partially support (not all necessary data can be obtained from this UPS).</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">Below is a list of data that needs to be obtained from 650VA UPS from Prolink using NUT. Commands that according to Prolink are currently not supported are indicated below:<br>1) UPS status (ups.status) --</span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">OK</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">2) Battery charge level (battery.charge)--- >> Only support battery voltage.</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">3) Expected battery life (battery.runtime)---</span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">not support</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">4) Input line parameters (input.voltage)---</span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">OK</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">5) UPS model (ups.model)- </span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">OK</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">6) Current UPS load (ups. load)- </span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">OK</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">7) The UPS shall transmit to the NUT driver the resulting Runtime value calculated from UPS controller side (without calculation from the driver side)- </span><span style="font-family:"Calibri",sans-serif;color:rgb(31,73,125)">》</span><span style="color:rgb(31,73,125)" lang="EN-US">not support</span><span lang="EN-US"><u></u><u></u></span></p><p><span lang="EN-US"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">Prolink claims that to fully support NUT, the NUT driver “blaser_usb” for 650VA UPS needs to be improved, so we are asking you for help.</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">1. Please clarify whether it is technically possible to modify the existing driver for the 650VA Prolink UPS and provide the ability to transfer all data from this UPS to NUT in accordance with the list above?</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">2. In what time frame is it possible to modify the driver?</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">3. How much does it cost to upgrade the driver?</span><span lang="EN-US"><u></u><u></u></span></p><p><span style="color:rgb(31,73,125)" lang="EN-US">4. What information and materials do you need to improve the driver for the Apex800, besides the protocol from Prolink? We are ready to provide and receive everything needed from the manufacturer.</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">Best regards</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">Alexander Kirillov</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">company Enfall</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">mobile: +7 904 333 38 86 (WhatsApp, Telegram)</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)" lang="EN-US">e-mail: </span><a href="mailto:ak@enfall.com" target="_blank"><span style="color:rgb(5,99,193)" lang="EN-US">ak@enfall.com</span></a><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:16pt;font-family:Broadway;color:rgb(31,73,125)" lang="EN-US">ENFALL</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Broadway;color:rgb(146,208,80)" lang="EN-US">energy for all</span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;color:rgb(146,208,80)" lang="EN-US"> </span><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><b><i><span style="font-size:9pt;color:rgb(31,73,125)" lang="EN-US">CONFIDENTIALITY NOTICE:</span></i></b><i><span style="font-size:9pt;color:rgb(31,73,125)" lang="EN-US"> This email and any files attached to it are confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email. </span></i><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p></div></div><p class="MsoNormal"><span lang="EN-US">_______________________________________________<br>Nut-upsdev mailing list<br></span><a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank"><span lang="EN-US">Nut-upsdev@alioth-lists.debian.net</span></a><span lang="EN-US"><br></span><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" target="_blank"><span lang="EN-US">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</span></a><span lang="EN-US"><u></u><u></u></span></p></blockquote></div></div></div></div></blockquote></div>
</blockquote></div>