Skip to content

nutdrv_qx: Voltronic-QS: Add QI command#3521

Merged
jimklimov merged 4 commits into
networkupstools:masterfrom
Steve-Tech:voltronic-qi
Jul 20, 2026
Merged

nutdrv_qx: Voltronic-QS: Add QI command#3521
jimklimov merged 4 commits into
networkupstools:masterfrom
Steve-Tech:voltronic-qi

Conversation

@Steve-Tech

Copy link
Copy Markdown
Contributor

Hi, this PR adds the QI command for battery charge, runtime, input frequency, output current, and input transfer low/high values to the Voltronic-QS driver.

I am unsure of the consequences of using this with an unsupported UPS, hence marking this PR as a draft. A decompilation of Voltronic's ViewPower software shows this is only used for H/I/J protocols only. I am hoping someone can test this on a V protocol UPS, but otherwise let me know if there's a way to disable this for the V protocol, or if it's fine anyway.

I found this command while collecting a USB packet capture of a Powershield PSDR800 while using the manufacturer's NetGuard software, which seems to be based off of Voltronic's ViewPower.

Thanks,
Steve

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

A ZIP file with standard source tarball and another tarball with pre-built docs for commit ccf8252 is temporarily available: NUT-tarballs-PR-3521.zip.

@AppVeyorBot

Copy link
Copy Markdown

@AppVeyorBot

Copy link
Copy Markdown

@AppVeyorBot

Copy link
Copy Markdown

Build nut 2.8.5.4913-master completed (commit a317ffca7b by @Steve-Tech)

@AppVeyorBot

Copy link
Copy Markdown

@jimklimov jimklimov added the Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others label Jul 13, 2026
@jimklimov jimklimov added this to the 2.8.6 milestone Jul 13, 2026
@jimklimov jimklimov added Voltronic Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) labels Jul 13, 2026
@jimklimov

Copy link
Copy Markdown
Member

Thanks! I suppose this should be safe for those devices which do not support the command, they should just ignore it somehow. At least, while probing for protocol support, the subdrivers spew all kinds of strings into the UPSes and I don't think anyone got bricked by that yet :D

jimklimov added a commit to Steve-Tech/networkupstools that referenced this pull request Jul 20, 2026
…N and reword the news entry [networkupstools#3521]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Steve-Tech and others added 4 commits July 20, 2026 12:04
This command adds battery charge, runtime, input frequency, output
current, and input transfer low/high values to the Voltronic-QS driver.

Tested on a PowerShield PSDR800.

Signed-off-by: Stephen Horvath <s.horvath@outlook.com.au>
Signed-off-by: Stephen Horvath <s.horvath@outlook.com.au>
Signed-off-by: Stephen Horvath <s.horvath@outlook.com.au>
…N and reword the news entry [networkupstools#3521]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
@jimklimov
jimklimov marked this pull request as ready for review July 20, 2026 10:06
@jimklimov
jimklimov merged commit cf973cc into networkupstools:master Jul 20, 2026
3 of 4 checks passed
@Steve-Tech

Copy link
Copy Markdown
Contributor Author

Oh cool! Thank you for reviewing & merging this, and thanks heaps for maintaining NUT!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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 Voltronic

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants