octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58252] [octave forge] (instrument-control) us


From: John Donoghue
Subject: [Octave-bug-tracker] [bug #58252] [octave forge] (instrument-control) ustmc_read() does not read all the waveform data from oscilloscope
Date: Tue, 28 Apr 2020 21:58:35 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763

Follow-up Comment #4, bug #58252 (project octave):


The  instrument control toolkit just uses the default values of the device,
and does no processing or anything, just calls read and write to the device
fd.

So the entry the log further indicates to me that its not a instrument control
issue (as such), but rather driver or new firmware related.

Since instrument control is using default, perhaps it is timing out before it
gets all the data, or the driver doesn't support the amount data being sent.

I don't use the usmtcm driver myself, so maybe someone else has used it and
can answer better.

I see on keysite that there is an old driver with some additional tools for
setting timeouts etc that may be useful (assuming they still compile)

https://www.keysight.com/upload/cmc_upload/All/usbtmc.htm?&cc=US&lc=eng

Or possibly could change the device open instrument code to set a different
timeout value if supported.

If you set lower resolution is there a setting that does work, that would at
least prove everthing else is working?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58252>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]