search for: qx_command

...ons (entirely in 'nutdrv_qx.c')... For serial devices: - given that, so far, all supported devices shared similar settings and I/O modus operandi, operations are done directly without much fanfare... - setup is done directly in `upsdrv_initups()`, - ditto for subsequent communications, in `qx_command()`. For USB devices: - `qx_usb_id` lists the various VID:PID pairs (with, optionally and only if needed, the iManufacturer and iProduct strings) of each supported device, coupled with a function ('fun()' from now on) that will set `subdriver_command` to point to the function ('command(...

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see drivers that uses the VID

...ons (entirely in 'nutdrv_qx.c')... For serial devices: - given that, so far, all supported devices shared similar settings and I/O modus operandi, operations are done directly without much fanfare... - setup is done directly in `upsdrv_initups()`, - ditto for subsequent communications, in `qx_command()`. For USB devices: - `qx_usb_id` lists the various VID:PID pairs (with, optionally and only if needed, the iManufacturer and iProduct strings) of each supported device, coupled with a function ('fun()' from now on) that will set `subdriver_command` to point to the function ('command(...