Bug: Windows app MokuPro datalogger voltage depending on sampling rate

Moku model: Moku:Pro
Operating system: Windows 10
Software version: 4.0 (I believe)

Bug or support request description:
Hello,
I recently encountered a strange bug in the Moku Windows software.
When changing the sampling rate, the detected voltage in the datalogger also changed, and by orders of magnitude. For some sampling rates, it reported a couple of millivolts (the correct value), and for others, it went as high as 50 volts.

It appears to be a software bug. I am not sure how to reproduce it yet.
The moku had already been running for quite some time when the problem arose. Restarting only the software completely fixed the issue, and now it is reporting the same voltage levels for all sampling rates again.
This is probably a very rare issue and not a significant problem, but I wanted to bring it to your attention.

With kind regards,
Ruben

Hi @Ruben ,

Thank you for reaching out to Liquid Instruments! When you noticed the voltage changing, was this in the app or did you export the data first? The Data Logger plot updates at a much slower rate than the set sample rate, which can make the signal look aliased. Exporting and plotting the data shows the true trend of the data.

I’m looking forward to hearing from you!

-Dylan

Hi @Dylan ,

Thank you for your reply!

We saw the changing voltage in the app itself. It was immediately clear that something had gone wrong. When the sampling rate was changed from 100Sa/s to 1000Sa/s, the voltage changed from tens of mV to tens of Volts. We were not applying any signal to the input.
We have just restarted the software, and after doing so, it displayed the correct values again for every sampling rate.
Unfortunately, we did not export any data at that time. However, I suspect that you are right and the issue lies purely in the visualization in the app, and that the values would indeed be stored correctly.

This happening seems very rare. I have been using the Moku:Pro for a long time, and I have only observed this behavior once.
If it ever happens again, I will record some data at different sampling rates and let you know!

Ruben