Hi jaray, If you have PicoScope 6 (including the Beta) version installed on the PC then it's location will be in the PATH environment variable and hence the dlls from the install directory will be picked up. If that is not the case, are there are any other locations in the PATH environment variable...

So I decided to play around with how I am including the libraries in my software. I once again downloaded the most up to date 5244B SDK. I didn't want to depend on the path variable, so I removed the portion pointing to the SDK directory. In the root of my development directory I have a lib folder w...

Hi jaray, Are the dlls in the same directory as your exe when you refer to the root directory? If not, then the PicoScope 6 installation directory is likely to be found first in your search path. For the external trigger, there is a fixed maximum count value to scale against. On the channels this w...

I should note that I also fixed my triggering issue. It was not related to the SDK. Instead I was triggering on the EXT input but was calculating my ADC values using the current ADC Voltage level Channel A instead of a set Voltage level.

I think that may be the issue. On my release computer I use for testing, I do not have PicoScope 6 installed, so it is requiring I have both of those dlls. However on my development computer I do have PicoScope 6 installed. This computer is 64bit but I am developing targeting 32bit. I am surprised t...

I've been successfully using my PicoScope 5244B with my C++ software for several months now. I've been having issues with the device not triggering properly recently, so I wanted to see if updating the libraries helped. I've been using the windows 32bit drivers dated 1/13/15. I've been using the sta...

Hitesh's method is essentially how I am doing it. I have an arm button that when pressed sets up the function generator, run block, and another piece of hardware I am using. Once I want to collect data I tell the run block to start, trigger my other piece of hardware, then trigger the arbitrary func...

I found that in the SDK and wanted to delete this post before it went up. I'll leave it up in case anyone else has the same issue.

I've finally gotten my code to a point where I am wanting to try it on different machines. The machine I have been testing on has the picoscope 6 software installed, so I have had no trouble communicating with the device using the libraries provided by the SDK. After deploying my application and mov...

Sure, I will do it now.

I designed my software around the C example for capturing a block of data. Everything works except the first block of data I capture always starts with a slight positive DC offset that decays as the record continues. The scope channel is set for AC coupling. The major difference between my code and ...

So I set up several debug statements to watch variables as I need them. Turns out I had awgBufferSize in my UNIT struct defined as a short instead of an unsigned short so using PS5X44A_MAX_SIG_GEN_BUFFER_SIZE caused the variable to turn negative because it is larger than 32767. I found an example on...

I was able to get the function to work by creating a signal that had the max number of samples. I am going to investigate further into varying sample sizes to see how it changes.

I responded in the email, but I will do it here also in case anyone else runs into the same issues. Upon using the new dll and lib you sent to my email, I received this email upon compiling: *** A stack buffer overrun occurred in C:\Users\Jason\Documents\Development\Qt\build-CrackDetection-Desktop_Q...

Thanks, Hitesh, I just received the email and will try these out momentarily. Currently playing around with reading in the csv file. I checked the contents of the array I was passing, and things were not quite right.