Nut upsdev - Mar 2017 - modbus driver for phoenix contact industrial UPS

Hello,
this is to let you know I will start working on a modbus driver for the
PhoenixContact QUINT-UPS industrial DC UPS, model 2320461.

https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-itemdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1


I will reuse some parts of the nutdrv-modbus branch, but this will be a
model specific driver, not a generic one. Unfortunately generic drivers and
autodetection don't seem to make sense in the modbus world.

I hope the phoenixcontact-quint-modbus drive name will be ok, I'll start by
branching off the current master.

I hope I'll have it running within the week.

Kind Regards,
-Spiros
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170313/ffb9e455/attachment.html>

Hi driver and pull request created, https://github.com/networkupst
ools/nut/pull/404
tested and works fine.
UPS configuration is needed, and included in the man page of the driver.

Is there any indication on the usual time it takes for a driver to be
checked/included on the master?
(We are planning on setting up hundreds of those UPS boxes and it would be
great to have an estimate)

Kind Regards,
-Spiros


On 13 March 2017 at 13:18, Spiros Ioannou <sivann at gmail.com> wrote:
> Hello,
> this is to let you know I will start working on a modbus driver for the
> PhoenixContact QUINT-UPS industrial DC UPS, model 2320461.
>
> https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-i
> temdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1
>
> I will reuse some parts of the nutdrv-modbus branch, but this will be a
> model specific driver, not a generic one. Unfortunately generic drivers and
> autodetection don't seem to make sense in the modbus world.
>
> I hope the phoenixcontact-quint-modbus drive name will be ok, I'll
start
> by branching off the current master.
>
> I hope I'll have it running within the week.
>
> Kind Regards,
> -Spiros
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170314/8475dce6/attachment.html>

On Mar 14, 2017, at 5:28 AM, Spiros Ioannou <sivann at gmail.com>
wrote:
> 
> Is there any indication on the usual time it takes for a driver to be
checked/included on the master?
> (We are planning on setting up hundreds of those UPS boxes and it would be
great to have an estimate)
> 
As an open-source project without corporate backing (for the most part), we
don't do estimates. The history is all available on Github:
https://github.com/networkupstools/nut/pulse
<https://github.com/networkupstools/nut/pulse> so it is possible for you
to extrapolate, but I'm not sure how useful that will be.

If you have the UPSes, you are in the best position to judge when to deploy your
code - the rest of us most likely can't test due to lack of hardware. If you
have a schedule, I would advise deploying your branch, rather than re-testing
with the master branch (or a point release) post-merge.

Updating the GitHub issue as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170314/e3f46872/attachment.html>