-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Reading (query) from TCPIP device always gets Timeout error #410
Comments
I've traced this with tcpdump. The working version (ds2000-shell, a c++ app based on librevisa) does not append '\r\n' to the command sent while pyvisa-py apparently automagically appends '\r\n' to my command. So far I see no further difference in the packets, it seems with carriage-return and newline appended my oscilloscope simply refuses to provide any output. Note that the timeout error is produced on the oscilloscope side -- the answer returned by the read command contains the error. Is there a way to turn off the auto-append of '\r\n' in pyvisa-py? |
Hypothesis confirmed, my device doesn't like the
[Serial number in device output censored] |
Changing the default is likely to cause more churn than it is worth. I advise to always set explicitly the desired read and write termination. |
Thanks for the quick feedback. |
I've submitted a pull request #411 for updating the index.rst in the docs. |
Opening a TCPIP resource works partially: Some commands can be sent (and have an effect on a Rigol DS2072 oscilloscope) but trying to read anything (e.g. with 'query') produce a timeout. Running a tcpdump in the background sees packets going to and from the device. Even when I specify a long timeout (30s) as second argument to query, I'm still getting a timeout. The name
oszi
is the DNS name of my oscilloscope.To Reproduce
Output of
pyvisa-info
The text was updated successfully, but these errors were encountered: