New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPIB bad settings #360
Comments
You can set the read and write termination character using the |
python returns.. with read_termchar="\n" or "\r" or "\r\n" still waiting for full time of set query_delay |
|
Yes, but 11 s is to much.. when in labview the response is immidietly, maybe 1 s... Its sticking point.. |
So what's different? |
If you do not specify a query_delay the command fail is that right ? Could you send the log of the failure along with your script ? You can try to set query delay to 0.01 or 0.1 in which case the delay will be far less noticeable. |
with but when I call common command ddd.. |
Closing since the root problem of the issue what the finite time the instrument needed to handle some particular command. Feel free to reopen if necessary. |
When I call X device in the labview, X will respond immediately. When I call X device in the Python,
X device responds to the query_delay argument at the set time. If the query delay turns off, python reports time expired. I think, that instrument under python doesn't able to read a termination from X device. Do not you know how it could be set in Python? Thanks.
The text was updated successfully, but these errors were encountered: