The SCPI lib does not know how SRQ handling in USBTMC has to happen.
I don't know either.
To ease later development, and to take this burden away from the SCPI lib, I made the SCPI lib call a placeholder function in the USBTMC part of the code.
No functional change, but clarification of responsibillities.
the new setControlReply() function doesn't do anything,
but I put in the comments my trial code, based on reading specs and opinions.
The SCPI lib does not know how SRQ handling in USBTMC has to happen.
I don't know either.
To ease later development, and to take this burden away from the SCPI lib, I made the SCPI lib call a placeholder function in the USBTMC part of the code.
No functional change, but clarification of responsibillities.
the new setControlReply() function doesn't do anything,
but I put in the comments my trial code, based on reading specs and opinions.