Hi I have just upgraded Picoscope from 6.0.12.2 to 6.0.13.3 and I can't get it to trigger.
I figured that it may be because of the upgrade as we have the same version running using a 3206 unit and it works without any problems. So I tried to install it on a clean computer with same result. The scope software keeps saying collection data, but nothing happens.
I have tried to reinstall the old version and everything works. Then I upgraded again without changing the measurement setup, but now nothing seems to work.
Hi, yes I can send you a settings file, I can't send you a data file as I can't get a trigger but I can send you a sample file from the previous version
I am trying to trigger on a PWM encoded datastream at aprox 84 kbps or an I2C datastream running 500 kHz.
I have the exact same problem. I just upgraded to .13. I'm working with a 5204, too. My probe was not yet connected to the circuit. It says "capture" and nothing else happens. Downgraded to .12 again and everything works fine.
Something else: I can't find the change log on the homepage - is it not yet up or am I doing something wrong?
I have tried the latest software and I seem to have no problem. The only reason why it would say collecting is if it is in streaming mode, so say 1second per division, it will take 10 secconds to collect the data from one whole sceen shot. Am I missing someting?
I just upgraded PicoScope on my laptop to 6.0.13.3. Same problem as the others mentioned. Also my own C code doesn't work anymore. Here is a fragment where it goes wrong:
/* Start it collecting, then wait for completion*/
g_ready = FALSE;
status = ps5000RunBlock(handle, 0, BUFFER_SIZE, timebase, 1, &timeIndisposed, 0, CallBackBlock, NULL);
printf("...Press a key to abort\n");
while (!g_ready && !_kbhit())
{
Sleep(0);
}
Obviously it doesn't call the CallBackBlock funtion. Release 6.0.12 had on problems. I don't use triggered functions in my own software, but ik looks like the function is waiting for a trigger.
Strange thing is that it does work on my desktop PC (after rebooting the PC)
Ok, while verifying what I wrote, it suddenly starts working. I had the USB port disconnected and did a scope power cycle. My own software comes to life again, and so does PicoScope.
So there may be some incompatible firmware in the scope left when upgrading? Maybe suggest customers to shut down the scope's power while upgrading?
Yes like you pointed out Reinier, since you did a new installation and there are new drivers the scope has to be powered down and on again to allow the new firmware to upload.