Open NitramC opened 3 years ago
What is the problem you're trying to solve? Do you have some other instrument that's accidentally being recognized as a FemtoFiber
?
Yes, exactly; when running list_instruments
it occured once.
I am working with another serial instrumemt that does not recognize *IDN?. It also will reply to any unrecognized command with somthing like "unknown command xxxx".
I agree that a change like the one you suggest would be a good one, we just need to find what the string(s) should be.
In the meantime, if you've written a driver for the conflicting instrument, you could give it an earlier _INST_PRIORITY_
so it is tried before the femto ferb driver.
Currently the femto_ferb driver will assign the FemtoFiber class to any instrument that responds to the query '(param-ref system-type)', whether or not that respose is valid. It would be good to modify the _check_visa_support method such that is parses the respose and looks for certain keywords. Unfortunately, the documentation does not provide an example response, so someone who has the insturment would need to make the changes, or one would have to contact Toptica to ask.
Something like this would probably work if we know what the search pattern ???? should be: