I use the following equipment:
PicoScope 3403D
PicoScope 6.11.10.1608
Win 7 (64-bit)
USB 3.0.
When the parameter "Number of Samples" => 40kS then measurements displayed at the bottom of the screen show zero or nothing (see attached Measurements_NOK.png) - Measurements -> Add measurement -> ....
When this parameter is 30kS or less a correct value is displaed (see attached Measurement_OK.png).
Can you tell me why measurements are zero for Number of samples =>40kS or am I missing something?
If you go to Views->ViewProperties this will open up a panel on the right hand side of the screen that will show exactly how the scope is set up, the 30kS and 40kS are just what you are requesting, what you actually get will vary.
Can you then post a psdata file for each situation using File->Save, we can then take a look at the data.
Please find attached the requesed *.psdata files:
1.Measurements_OK_30kS.psdata (Number of Samples = 30kS)
2.Measurements_NOK_40kS.psdata (Numer of Samples = 40kS)
Note to (2)
Interestingly, measurements in the "offline" data i.e. in "Measurements_NOK_40kS.psdata" file are present, but are not visible in PicoScope software in "online" measurements (see my screenshots in previous post).
Is it a bug in the software or is some kind of parameter incorrectly set?
I would try File->Open , load the 40k file, and then re run the test. If this works then all well and good, if not then close the software, navigate to
and make a copy of your preferences.xml file, before deleting it. Re start the software and repeat the test, and if this still fails then send the preferences file to support@picotech.com, or post it here.
I sent my preferences.xml file on the given email address.
I could not post it on the forum. I kept receiving information it was not possible...
I deleted and restarted software as suggested but it did not help.
I ran my PicoScope on a different laptop with a different software version 6.10.18.1052 (have no idea if it matters) and Measurements are shown correctly.
I have now been able to replicate the issue. I have discussed this with the development team and they have already addressed the problem in the upcoming beta release of the software.