UPDATE: As commented in
https://github.com/networkupstools/nut/issues/139#issuecomment-1369527363
I've stashed a one-off copy of their history at
https://github.com/networkupstools/apcupsd using GitHub importer for SVN
sources to grab the current state of https://svn.code.sf.net/p/apcupsd/svn
just in case (so it does not evaporate as abandonware).
Further browsing revealed that:
* Last release was 3.14.14 (2016-05-31)
https://sourceforge.net/projects/apcupsd/files/apcupsd%20-%20Stable/3.14.14/
with a couple more commits tracked at
https://sourceforge.net/p/apcupsd/svn/HEAD/tree/branches/Branch-3_14/ (up
till 2017-05-06)
* Last announced release was 3.14.13 (2015-02-03) per
https://sourceforge.net/p/apcupsd/mailman/apcupsd-announce/
* The mailing list community is quite active however, archive maintained at
https://sourceforge.net/p/apcupsd/mailman/apcupsd-users/
More and more I'm thinking this is less of a poaching and more of a rescue
mission...
Would anyone please get your hacker hats on and mercifully save that
protocol-support code in a maintained project? :)
Jim
On Tue, Dec 27, 2022 at 6:47 PM Jim Klimov <jimklimov at gmail.com> wrote:
> Cheers all,
>
> Every now and then there are questions about how NUT drivers for APC
> devices are behind apcupsd, especially for modbus where most data is served
> in the past decade (compared to USB HID on same media, at least).
>
> Per http://www.apcupsd.org/ and
> https://sourceforge.net/p/apcupsd/svn/HEAD/tree/branches/Branch-3_14/
> latest release was 2016 and latest commits overall in 2017, and it is also
> GPLv2 - maybe it would be right to port their logic as a NUT driver proper?
>
> We have had several modbus drivers added by community members in the
> past year or two, so there is precedent and first lessons learned for the
> general integration...
>
> WDYT?
> Jim Klimov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20230103/ca7680ea/attachment.htm>