Equipment: 3206DMSO
Hardware version : 1
Serial : C0797/027
Firmware 1 : 1.2.0.0
Firmware 2 : 1.0.21.0
I want to measure the phase delay between two signals (Sine). Min. freq. = 100 kHz, max Frequ. = 600 kHz. The two signals are stepped through the frequency range in steps of 10 Hz. Because the expectes phase delay is between 4 and 8 nS (Measured in block mode ), I want to use the ETS mode to get a higher time resolution. My etsSampleFrequency is 100 pS and the minimum signal cycletime is 10 uS I want to get more samples from Picoscope (In this case 100.000)
The program works most of the time as in block mode, but the driver hangs at random times during the function (ps3000aRunBlock). This can be after 2 or 5, but also after 10.000 measurements. I tried several things, like:
- After each functioncall I checked the status variable. If status != 0 than report an error
- Several values of etsCycles and etsInterleave
- I changed the number of samples, which I wanted to recieve each measurement
- I inserted several timedelays in my program.
After several days of testing and changing it seems that a timedelay of 10 seconds after the functioncall ps3000aRunBlock has a positive effect on the 'hanging' problem. But now the program is very slow.
If you are building a 32-bit application, please try the ps3000a.dll and PicoIpp.dll files from the PicoScope 6.12 installation directory and see if this resolves the issue.
I copied the two files to the "C:\Program Files\Pico Technology\SDK\lib" folder. The program compiled correctly. When I ran the program, I got the following error window:
Get_Data - Application error
The application was unable to start correctly (0xc000007b). Click OK to close the the application.
I checked the C-drive with CHKDSK. No errors found.
I copied the two driver files (downloaded from your site) and the projectfiles to my laptop. I got the same result with the Windows error. After copying back the original files, I could execute the application. This is the same behaviour like my main computer.
Which development environment and operating system are you using?
Are you running the application from within the development environment or from the executable? Which version of the Microsoft .NET Framework do you have installed?
I ran the application out of Visual Studio 2013. After your question, I made a release version of the application and tried to start it from the command line. With the same messagebox from windows.
Ccleaner gives me these results for the . NET software tools.
- Microsoft .NET Framework 4.5 SDK version = 4.5.50710
- Microsoft .NET Framework 4.5.1 SDK version = 4.5.51641
- Microsoft .NET Framework 4.6.1 version = 4.6.01055
are you sure that you sent me 64-bit drivers ? According to the software tool PEBrowser Professional the old drivers are 64 bit drivers, but the new ones are 32 bit drivers ?
I tested the 'new' drivers. I got the same error window from Microsoft.
In my opinion these are the same drivers (at least with to the file size) as I downloaded yesterday. Furthermore these are also 32 bit drivers.
I'm just in the process of checking some drivers. Could you please send a response back on your e-mail support ticket and I'll then make these available to you depending on the testing.
Edit: Looks like it might be due to mismatch between the lib file and the dll - please respond to your support ticket as requested.