Skip to content

Noted that SKE devices work with the nutdrv_qx driver.#1451

Merged
jimklimov merged 3 commits intonetworkupstools:masterfrom
oxagast:master
Jun 23, 2022
Merged

Noted that SKE devices work with the nutdrv_qx driver.#1451
jimklimov merged 3 commits intonetworkupstools:masterfrom
oxagast:master

Conversation

@oxagast
Copy link
Copy Markdown
Contributor

@oxagast oxagast commented Jun 19, 2022

I've created this pull for a change in documentation to reflect that SKE (specifically the SK600, maybe others) devices will work with the nutdrv_qx driver.

Note:
Seems to work with this configuration in /etc/nut/ups.conf:

[SK600]
        driver = "nutdrv_qx"
        port = "auto"
        vendorid = "0001"
        productid = "0000"
        bus = "003"

@jimklimov
Copy link
Copy Markdown
Member

jimklimov commented Jun 21, 2022 via email

@jimklimov
Copy link
Copy Markdown
Member

Also seems the docs/nut.dict should be updated.

@oxagast
Copy link
Copy Markdown
Contributor Author

oxagast commented Jun 23, 2022

Requested changes have been made to data/drivers.list.in as well as docs/nut.dict.

@jimklimov jimklimov merged commit d522fed into networkupstools:master Jun 23, 2022
@Hoover49
Copy link
Copy Markdown

nutdrv_qx driver does not work with a SK1500 UPS. I receive the following:

Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
USB communication driver 0.33
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 nutdrv_qx).

@jimklimov
Copy link
Copy Markdown
Member

@Hoover49 : a bit too little to go on: did you specify the (bogus) vendorid/productid values like in the sample above?

Did you try with "an up-to-date version of NUT" (2.7.4 is now 7.5 years old... although for that matter, the original post did not clarify if it was on 2.8.0+, either)?

Can you try starting the driver with higher debug verbosity to check what it disliked? e.g.

nutdrv_qx -a myupsname -DDDDDD -d1

@Hoover49
Copy link
Copy Markdown

Hoover49 commented Oct 26, 2023

I upgraded to version 2.8 and now everything appears to be working. Thanks for your advice.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants