liquidinstruments / moku-matlab Goto Github PK

Looking at the examples and the commits in last few years it doesn't seem that anything has been added for addressing individual instruments in Moku:Pro's multi-instrument mode. We might like to implement this for automated loop measurments in our lab.

Are there any prospects of this making into either the Matlab or Python API any time soon?

I'm trying to grab a sample of data from the oscilloscope instrument using the Matlab API.

Here I'm using the get_realtime_data to get a decimated block of points. I run the example script below, it works on the first time on fresh boot of Matlab but produces an error on every second run of the script.

% Tester delete me later

%{
Test script that produces an error "Error using moku/mokuctl (line 118)"
on every second run of the script. 
Author: Andrew Wade
Date: 13 Nov 2020
%}

% Configure moku IPs
ip_WFG = '192.168.30.241';

% Connect to wavefunction generating Moku
wfg = MokuOscilloscope(ip_WFG);  % a different option that allows readback
wfg.set_frontend(1, 'fiftyr', false, 'atten', false, 'ac', false);
wfg.set_precision_mode(true); % Set to decimate rather than downsample
wfg.set_xmode('sweep');
wfg.set_timebase(-0.01,0); % Grab 0.01 seconds of data

for ii = 1:5
out = wfg.get_realtime_data('timeout', 10.0)
median(out.ch1)
end

The error returned is

Error using moku/mokuctl (line 118)


Error in MokuOscilloscope/get_realtime_data (line 252)
            mokuctl(obj, 'get_realtime_data', params);

Error in test (line 21)
out = wfg.get_realtime_data('timeout', 10.0)

Are we supposed to be closing a connection between runs of the above script? Documentation says no, but clearly there is something that needs reseting to get the same result every time.

I also tried restarting matlab between runs of the above script. On first run it works fine, then every second run I get the above error. So seems like an issue with the state on the Moku side (not matlab).

Are you able to reproduce this?