I am using the Windows Moku app to develop a Multi-Instrument configuration running on a Moku:Pro. In the past I’ve had no issue with this workflow, however recently I’ve experienced frequent problems. Selecting between different probe points within an instrument will elicit an hourglass symbol where the play/pause icon typically appears and signals in the scope no longer update. The device also becomes unresponsive: if I specify a voltage to be generated on an output the app registers the command but no voltage is detected when connecting separate devices to the specified output.
How can I ensure the reliable operation of the moku? Should I reinstall the windows app? Will the issues persist if I am using an API to interface with the device?
Hello @T_Hinds ,
I’m sorry to hear you are dealing with this issue. Is there a particular configuration or instrument that causes the issue? The hourglass typically will pop up when waiting for a trigger, so if your scope is in ‘Normal’ trigger mode, try switching to ‘Auto’ and see if that helps. Also, what device is being connected to the outputs? If you measure the voltage with a voltmeter does it read the correct voltage?
I am using the moku to implement PDH frequency locking using a waveform generator, lock-in amplifier, PID controller, and laser lock box. The hourglass appears in the LLB instrument, and I believe I have the trigger set to “auto.” Does the trigger setting change when using the auto-lock feature to select a zero-crossing to lock on to? If my memory serves right I can lock to a signal and see signals in the scope responding before freezing. Sometimes it works for minutes or hours at a time before freezing. The PID block is being used to generate a voltage at one of the analog outputs, which is connected to an arudino. The arduino does not register a voltage even when the windows app says the PID is outputting. Again this instrument can work for minutes/hours at a time and I can see signals on the arduino’s analog input before freezing.
Hello @T_Hinds ,
Can you please attach a screenshot of your configuration and I will attempt to replicate it on my end and get back to you. Thank you so much!
Here are a few screenshots which show the setup and some of the issues I’m having. Your suggestion for fixing the hourglass icon in the LLB scope worked, the trigger seems to change from “auto” to “normal” when selecting a zero crossing to lock to–thank you!
On to the Moku app freezing: it worked reliably for roughly a day, before freezing again. The app doesn’t show actions from mouse clicks, but I think they are being registered. The first two images show the PID instrument, which is outputting a voltage to an arduino, and the signal is plotted in orange. Pressing the enable/disable Out B button does result in a change in the voltage measured by the arduino, but the moku app does not indicate that the output is off–it is frozen in the on state. Similarly, if the PID output is disabled the output offset is measured by the arduino, but the moku app shows that the PID output is still enabled. The windows for the other instruments are frozen as well, and do not reopen properly, see attached figure. Closing all windows and reopening seems to fix the freezing issue.
