summaryrefslogtreecommitdiff
path: root/docs/rvalues.rst
diff options
context:
space:
mode:
authorRuben Undheim <ruben.undheim@gmail.com>2018-08-19 22:12:30 +0200
committerRuben Undheim <ruben.undheim@gmail.com>2018-08-19 22:12:30 +0200
commit9c5924b696b7c9fa626464a294c5c235ed166bf8 (patch)
treed84d390f71a9ebacf7e300838c535bcfb26e9ecc /docs/rvalues.rst
parent482f79d72e2e19442e33bc9db5b7b8b10661381e (diff)
New upstream version 1.9.1
Diffstat (limited to 'docs/rvalues.rst')
-rw-r--r--docs/rvalues.rst11
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/rvalues.rst b/docs/rvalues.rst
index aecb6a6..a8b909e 100644
--- a/docs/rvalues.rst
+++ b/docs/rvalues.rst
@@ -82,6 +82,17 @@ the IEEE convention. If your instrument uses HP data block you can pass
``header_fmt='hp'`` to ``read_binary_values``. If your instrument does not use
any header for the data simply ``header_fmt='empty'``.
+By default PyVISA assumes, that the instrument will add the termination
+character at the end of the data block and actually makes sure it reads it to
+avoid issues. This behavior fits well a number of devices. However some devices
+omit the termination character, in which cases the operation will timeout.
+In this situation, first makes sure you can actually read from the instrument
+by reading the answer using the ``read_raw`` function (you may need to call it
+multiple time), and check that the advertized length of the block match what
+you get from your instrument (plus the header). If it is so, then you can
+safely pass ``expect_termination=False``, and PyVISA will not look for a
+termination character at the end of the message.
+
Writing ASCII values
--------------------