-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
blazer / Megatec/Q1 / Qx driver Gen4 #25
Labels
enhancement
Qx protocol driver
Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others
Milestone
Comments
zykh
added a commit
to zykh/nut
that referenced
this issue
Oct 16, 2013
New driver for Q* UPSes. Based on blazer, usbhid-ups and voltronic driver. This might address Issue networkupstools#25
clepple
added a commit
that referenced
this issue
Nov 4, 2013
Conflicts: (from voltronic un-merge) data/driver.list.in drivers/Makefile.am tools/nut-usbinfo.pl Should address GitHub Issue #25.
zykh
added a commit
to zykh/nut
that referenced
this issue
Nov 5, 2013
New driver for Q* UPSes. Based on blazer, usbhid-ups and voltronic driver. This might address Issue networkupstools#25
zykh
added a commit
to zykh/nut
that referenced
this issue
Nov 5, 2013
New driver for Q* UPSes. Based on blazer, usbhid-ups and voltronic driver. This might address Issue networkupstools#25
Update: Daniele is working on this (@zykh) |
thanks to @zykh, nutdrv_qx is now provided. |
aquette
pushed a commit
to aquette/nut
that referenced
this issue
Apr 25, 2016
DMF: Info_lkp_t referencing
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Oct 13, 2017
Problem: Need to fix published feed variables
Historic note: per 6b6ec95 this later became the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Qx protocol driver
Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others
Create the 4th generation driver to address all older Q1 and newer Q5 / QFS protocol variations.
The general idea is to have something between the current blazer* and usbhid-ups like claiming and data mapping structure.
A special care must be taken to old dumb things:
current parameters have to be kept, and a "force q1" should probably be added.
The text was updated successfully, but these errors were encountered: