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

Armac UPS uses trinary logic. Sometimes. #2405

Open
blaa opened this issue Apr 16, 2024 · 1 comment
Open

Armac UPS uses trinary logic. Sometimes. #2405

blaa opened this issue Apr 16, 2024 · 1 comment
Labels
impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) 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
Milestone

Comments

@blaa
Copy link

blaa commented Apr 16, 2024

Hello.

I've placed my UPS in it's new destination and it seems to be using internal autotrafo to decrease the voltage. Probably. It reads 247V and outputs 214V. AUTO icon is enabled on the screen.

BUT. This seems to create new type of message which kills bit parsing:

cruiser /etc/nut # /lib/nut/nutdrv_qx -a armac -D -D -D -x subdriver=armac  
Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.8.0)
USB communication driver (libusb 1.0) 0.43
   0.000000     [D3] main_arg: var='subdriver' val='armac'
   0.000070     [D1] debug level is '3'
   0.000654     [D1] upsdrv_initups...
   0.008479     [D2] Checking device 1 of 5 (0925/1234)
   0.013773     [D2] - VendorID: 0925
   0.013820     [D2] - ProductID: 1234
   0.013831     [D2] - Manufacturer: ?
   0.013841     [D2] - Product: UPS USB MON V1.4
   0.013851     [D2] - Serial Number: unknown
   0.013861     [D2] - Bus: 001
   0.013870     [D2] - Device: unknown
   0.013879     [D2] - Device release number: 0001
   0.013888     [D2] Trying to match device
   0.013899     [D3] match_function_regex: matching a device...
   0.014075     [D2] Device matches
   0.014088     [D2] Reading first configuration descriptor
   0.014110     [D3] libusb_kernel_driver_active() returned 0
   0.014153     [D2] Claimed interface 0 successfully
   0.014169     [D3] nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
   0.014224     [D2] armac: unsupported cmd: QGS
   0.014239     [D2] qx_process_answer: short reply (input.voltage)
   0.014253     [D2] armac: unsupported cmd: QGS
   0.014265     [D2] qx_process_answer: short reply (input.voltage)
   0.014277     [D2] armac: unsupported cmd: QGS
   0.014289     [D2] qx_process_answer: short reply (input.voltage)
   0.014302     [D2] armac: unsupported cmd: M
   0.014315     [D2] voltronic_qs_protocol: invalid protocol [M]
   0.014327     [D2] armac: unsupported cmd: M
   0.014339     [D2] voltronic_qs_protocol: invalid protocol [M]
   0.014350     [D2] armac: unsupported cmd: M
   0.014361     [D2] voltronic_qs_protocol: invalid protocol [M]
   0.014373     [D2] armac: unsupported cmd: M
   0.014386     [D2] voltronic_qs_hex_protocol: invalid protocol [M]
   0.014398     [D2] armac: unsupported cmd: M
   0.014409     [D2] voltronic_qs_hex_protocol: invalid protocol [M]
   0.014420     [D2] armac: unsupported cmd: M
   0.014432     [D2] voltronic_qs_hex_protocol: invalid protocol [M]
   0.014444     [D2] armac: unsupported cmd: QS
   0.014455     [D2] qx_process_answer: short reply (input.voltage)
   0.014466     [D2] armac: unsupported cmd: QS
   0.014477     [D2] qx_process_answer: short reply (input.voltage)
   0.014488     [D2] armac: unsupported cmd: QS
   0.014499     [D2] qx_process_answer: short reply (input.voltage)
   0.014510     [D2] armac: unsupported cmd: D
   0.014521     [D2] qx_process_answer: short reply (input.voltage)
   0.014532     [D2] armac: unsupported cmd: D
   0.014542     [D2] qx_process_answer: short reply (input.voltage)
   0.014553     [D2] armac: unsupported cmd: D
   0.014563     [D2] qx_process_answer: short reply (input.voltage)
   0.016036     [D3] armac command Q1 response read: ''
   0.016066     [D2] qx_process_answer: short reply (input.voltage)
   0.026020     [D3] armac command Q1 response read: ''
   0.026098     [D2] qx_process_answer: short reply (input.voltage)
   1.232971     [D3] armac command Q1 response read: 'rrrrrrj'
   1.233026     [D2] qx_process_answer: short reply (input.voltage)
   2.441931     [D3] armac command Q1 response read: '(247.0 140.0 214.0 006 50.3 54.0 28.0 00201000'
   2.442006     [D2] armac: unsupported cmd: QPI
   2.442023     [D2] qx_process_answer: short reply (ups.firmware.aux)
   3.649684     [D3] armac command Q1 response read: '(247.0 140.0 214.0 006 50.0 54.0 28.0 00201000'
   3.649755     [D2] armac: unsupported cmd: QPI
   3.649765     [D2] qx_process_answer: short reply (ups.firmware.aux)
   4.857561     [D3] armac command Q1 response read: '(247.0 140.0 214.0 006 50.0 54.0 28.0 00201000'
   4.857634     [D2] armac: unsupported cmd: QPI
   4.857646     [D2] qx_process_answer: short reply (ups.firmware.aux)
   6.065485     [D3] armac command Q1 response read: '(247.0 140.0 214.0 005 50.0 54.0 28.0 00201000'
   7.244301     [D3] armac command I response read: '#                           Ver1.00   '
   7.244359     Using protocol: Megatec 0.06
   7.244386     [D1] upsdrv_initinfo...
   8.452162     [D3] armac command Q1 response read: '(247.0 140.0 214.0 006 50.0 54.0 28.0 00201000'
   8.452267     [D3] blazer_process_status_bits: unexpected value 2@40->2
   8.452286     Can't initialise data from the UPS
   8.452297     [D1] upsdrv_cleanup...

I'll probably look into it later and maybe create a patch to support this, but wanted an issue to anchor the problem somewhere and be able to gather info.

@jimklimov jimklimov added Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) labels Apr 16, 2024
@jimklimov jimklimov added this to the 2.8.3 milestone Apr 16, 2024
@jimklimov
Copy link
Member

Thanks for the report, and a PR would be much appreciated :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) 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

No branches or pull requests

2 participants