search for: qx2nut

Hello again. Back in the day (2007) I wrote a USB-capable driver for my Masterguard/Phoenixtec UPSes (in case you locally archived this list, this very mail is a reply to a rather long thread from then), which I used ever since. However, the world has been going on since then and I need to get away with the old 2.0.4 binaries currently in use. These boxes (I use two A3000-19 and two A700-19) are

...eaking' that protocol): the first one to successfully claim (i.e. the 'claim()' function returns 1) the device wins. - From then on, nutdrv_qx uses that 'protocol' when communicating (e.g. updating the vars, sending instant commands, ...) with the device: the mapping in the 'qx2nut' table, the 'accepted'/'rejected' strings, etc. Now, onto communications (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......

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

...eaking' that protocol): the first one to successfully claim (i.e. the 'claim()' function returns 1) the device wins. - From then on, nutdrv_qx uses that 'protocol' when communicating (e.g. updating the vars, sending instant commands, ...) with the device: the mapping in the 'qx2nut' table, the 'accepted'/'rejected' strings, etc. Now, onto communications (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......