Skip to content

New driver: microsol-apc - #994

Merged
jimklimov merged 15 commits into
networkupstools:masterfrom
ygorre:new-driver-microsol-apc
May 24, 2021
Merged

jimklimov merged 15 commits into
networkupstools:masterfrom
ygorre:new-driver-microsol-apc

Conversation

@ygorre

@ygorre ygorre commented Mar 20, 2021

Copy link
Copy Markdown
Contributor

Derived from solis driver supporting newer APC Back-UPS BR hardware.
Support added for APC Back-UPS BZ1500, BZ2200BI and BZ2200I.
Tested on BZ2200BI.
Created common file that may be used on solis as well.

Derived from solis driver, for newer APC Back-UPS BR hardware.
Support added for APC Back-UPS BZ1500, BZ2200BI and BZ2200I.
Tested on BZ2200BI.
Created common file that may be used on solis as well.
@lgtm-com

lgtm-com Bot commented Mar 20, 2021

Copy link
Copy Markdown

This pull request introduces 1 alert when merging 69a3c00 into fbe7806 - view on LGTM.com

new alerts:

  • 1 for Use of potentially dangerous function

@rpvelloso

Copy link
Copy Markdown
Contributor

I'll be testing this! 👍👍

Comment thread drivers/microsol-apc.c
#include "microsol-apc.h"

#define DRIVER_NAME "APC Back-UPS BZ series UPS driver"
#define DRIVER_VERSION "0.68"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check if the DRIVER_NAME is right? It seems to mismatch the description in the file heading a bit. Also, for a new driver makes sense to start with new numbering, unless it is very closely related to this version (minus one?) of another driver used as a starting point?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just pushed a new commit fixing the DRIVER_NAME. As for the version, does the project have any guidelines for the numbering? If not, I would use version 1.0.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, I don't remember any such guidance. Looking at existing sources, most drivers have 0.XY numbers with a few claiming non-zero major number and a few having one digit after decimal. I don't think there were particular reasons for any number, other than increasing the value as features/logic were changed or added. Probably the zero reflects a "young" driver that should graduate into higher numbers as many devices are proven to be supported and bugless, but I think this was never automated or pursued manually.

@clepple @aquette : any insights on DRIVER_VERSION assignments?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed X.YZ. probably around the new-driver doc, or simply inherited from what Russel did setup. Would need official formalization and possible enforcement mister new Leader ;)

@jimklimov

Copy link
Copy Markdown
Member

@rpvelloso : how did the testing go? :)

@ygorre: thanks for the contribution! Is this a vendor-backed update (to reflect in docs/acknowledgements.txt)?
Also, can I ask you to please add the manpage for the new driver, probably also starting as a copy of solis with respective modifications?

In upsdrv_info, split contributors one per line for better source readability
@rpvelloso

Copy link
Copy Markdown
Contributor

Had not time to test it yet.

@jimklimov
jimklimov merged commit 294b833 into networkupstools:master May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants