Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix battery runtime calculation for Q2 protocol #2802

Merged
merged 1 commit into from
Feb 14, 2025

Conversation

dvdesolve
Copy link
Contributor

@dvdesolve dvdesolve commented Feb 11, 2025

New Q2 and Q6 protocols work like a charm - just tested thoroughly on my Innova RT 3/1 and all looks good! However, I've figured out that my translation/interpretation of original Santak's documentation was wrong at least in one place - Q2 request tells estimated battery runtime in minutes rather than seconds. This PR is for fixing this mistake

@jimklimov jimklimov added feature Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) labels Feb 14, 2025
@jimklimov jimklimov added this to the 2.8.3 milestone Feb 14, 2025
@jimklimov jimklimov merged commit caf8d1e into networkupstools:master Feb 14, 2025
29 of 30 checks passed
@dvdesolve dvdesolve deleted the q2_bruntime branch February 15, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants