search for: usbsubdriv

...ow on) that will set `subdriver_command` to point to the function ('command()' from now on) later used to communicate with the device. - When nutdrv_qx starts, in `upsdrv_initups()`, it will either pick the USB subdriver (whose name must be mapped to its relative 'command()' in the `usbsubdriver` list) directly if it was explicitly provided by the user or, for each available USB device, traverse the `qx_usb_id` lists, until it finds a match (VID:PID + iManufacturer/iProduct) and then call its 'fun()' function -- in both cases, the result is that, if a supported device is found, `...

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

...ow on) that will set `subdriver_command` to point to the function ('command()' from now on) later used to communicate with the device. - When nutdrv_qx starts, in `upsdrv_initups()`, it will either pick the USB subdriver (whose name must be mapped to its relative 'command()' in the `usbsubdriver` list) directly if it was explicitly provided by the user or, for each available USB device, traverse the `qx_usb_id` lists, until it finds a match (VID:PID + iManufacturer/iProduct) and then call its 'fun()' function -- in both cases, the result is that, if a supported device is found, `...