Cheers Hitesh, The division by zero was just to simulate an unknown error in coding, made while debugging. I have written an error trapping routine using ON ERROR (see attached file). This solves the problem of excel crashing, and it reports the description of the error, but it doesn't tell you wher...

Thanks Hitesh, it would be great if you could take a look. I expect there is not a solution, but I hope you can help. Attached is the spreadsheet/program. Clicking 'Communicate with scope' should correctly open the connection to the scope and get the unit's information. It then reads the two values ...

Many thanks Hitesh, I'll do that, Dave

Thanks Hitesh, Here's a few more details on the crashing behavior... While programming, after a crash in VBA (caused by an error in my program), you enter the debugger. You still have control over the spreadsheet, so you can save the file, it is the act of "resetting the debugger" (which you need to...

Thanks Hitesh, You're correct, explicitly disabling works, I'm now able to acquire with a 2ns interval by calling: Call ps3000aSetChannel(handle, 0, 1, 1, RangeA, 0) ' Ch A: enabled, DC Coupled, RangeA, 0.0V offset Call ps3000aSetChannel(handle, 1, 1, 1, RangeB, 0) ' Ch B: enabled, DC Coupled, Range...

Hi (Hitesh), I'm using a Picoscope 3406DMSO and am having trouble getting it to work faster than a 4ns time interval. I wonder if you can help? I'm measuring pulses from a scintillation-based radiation detector. I wish to measure the time of the pulse (relative to a trigger TTL signal) and the pulse...

Hi Hitesh, I believe the problem of excel crashing is solved: When I first communicate I do: status = ps3000aOpenUnit(handle, 0) deviceIndex = 0 status = initWrapUnitInfo(handle, deviceIndex) When I exit I must do: status = decrementDeviceCount(deviceIndex) Call ps3000aCloseUnit(handle) status = res...

Thanks Hitesh, yes, I'll do that.
Dave

Thanks very much for checking this out Hitesh! The device does not disappear and reappear in the USB devices list. However, I checked this a lot of times and I previously noted the audible beeps, when I retried the computer made no such beeps, so the behaviour has changed a little, I don't know why....

Thanks very much Hitesh, that was immensely helpful. Attached is the updated code which now works, the worksheet "Chart" shows a 1MHz sine wave and 100kHz sawtooth that I captured (I only plot the first 5000 datapoints to save on spreadsheet space, the acquisition size was 1,001,000 points, I was te...

Hi Hitesh, Thanks, I'm afraid this problem was only solved for a while, I'm still having a few problems, hope you can help? I wrote my own spreadsheet (attached) based very closely on PS3000aV2.xlsm. This program is giving strange results and your PS3000aV2.xlsm now crashes when run. I cannot get th...

Thanks very much Hitesh, the Picoscope 3406DMSO now works! Task manager reported that my Excel/Office 365 in Windows 10 is running 32 bit, so I installed the 32-bit Picoscope SDK as you suggested and it now works. Just so anyone else reading the forum knows, the files are in a slightly different pla...

Hello, I'm having a problem getting started with the example VBA spreadsheet. I have a Picoscope 3406DMSO, I'm using SDK version: "PicoSDK_64_10.6.10.22.exe" running Excel (Office 365) on Windows 10. I have tried the following: - Running the code in C:\PicoSDK\PS3000\ExcelPS3000.xls, I get the messa...