[Nut-upsdev] Prolink UPS NUT driver

[Alexander]

Hello Jim,

Thank you for your feedback, 



[Jim]: 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)?

[Alexander]: 

Now we don't have UPS samples on hands, we will ask the manufacturer to try testing NUT 2.8.0.

Previously, the manufacturer tested this UPS on version 2.6.5-6 NUT for Windows.
Could you suggest the correct link to download NUT v2.8.0 for Windows?



Best regards

Alexander Kirillov

company Enfall

mobile: +7 904 333 38 86 (WhatsApp, Telegram)

e-mail:  <mailto:ak at enfall.com> ak at enfall.com

ENFALL

energy for all

 

УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: 

Это электронное сообщение и любые документы, приложенные к нему, содержат конфиденциальную информацию. Настоящим уведомляем Вас о том, что если это сообщение не предназначено Вам, использование, копирование, распространение информации, содержащейся в настоящем сообщении, а также осуществление любых действий на основе этой информации, строго запрещено. Если Вы получили это сообщение по ошибке, пожалуйста, сообщите об этом отправителю по электронной почте и удалите это сообщение. 

CONFIDENTIALITY NOTICE: 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. 

 

 

 

From: Jim Klimov [mailto:jimklimov+nut at gmail.com] 
Sent: Sunday, January 8, 2023 4:43 AM
To: Alexander <ak at enfall.com>
Cc: nut-upsdev <nut-upsdev at alioth-lists.debian.net>; Pavel <pp at enfall.com>
Subject: Re: [Nut-upsdev] Prolink UPS NUT driver

 

Hello all,

 

  I really hope somebody picks up this bounty :)

 

  Going forward, however, nutdrv_qx driver should be evolved via new subdrivers (and used) rather than older Qx drivers like blazer.

 

@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)?

 

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

 

  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.

 

On Sun, Jan 8, 2023, 00:39 Alexander < <mailto:ak at enfall.com> ak at enfall.com> wrote:

Hello NUT developers,

Happy New Year!
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.  
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  <mailto:ak at enfall.com> ak at enfall.com.

 

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. 
The customer’s NUT monitoring system works on CentOS 6. 

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

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:
1)     UPS status (ups.status)  --》OK

2)     Battery charge level (battery.charge)--- >> Only support battery voltage.

3)     Expected battery life (battery.runtime)---》not support

4)     Input line parameters (input.voltage)---》OK

5)     UPS model (ups.model)- 》OK

6)     Current UPS load (ups. load)- 》OK

7)     The UPS shall transmit to the NUT driver the resulting Runtime value calculated from UPS controller side (without calculation from the driver side)- 》not support

 

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.

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?

2. In what time frame is it possible to modify the driver?

3. How much does it cost to upgrade the driver?

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.

 

 

Best regards

Alexander Kirillov

company Enfall

mobile: +7 904 333 38 86 (WhatsApp, Telegram)

e-mail:  <mailto:ak at enfall.com> ak at enfall.com

ENFALL

energy for all

 

CONFIDENTIALITY NOTICE: 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. 

 

_______________________________________________
Nut-upsdev mailing list
 <mailto:Nut-upsdev at alioth-lists.debian.net> Nut-upsdev at alioth-lists.debian.net
 <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20230109/cd19dc08/attachment-0001.htm>