Hi, Not as much of a question as it is a remark: Can you please make your API backwards compatible OR make breaking changes extremely clear? I've been working on picoscope support for about a decade, and in that time, I've had to fix how we pass the serial number to the API several times, because yo...
Never mind that, I'm still stuck. But at least now I have a specific baseline to base my question on. It's still about this function: PREF0 PREF1 PICO_STATUS PREF2 PREF3(ps6000aGetScalingValues) ( int16_t handle, PICO_SCALING_FACTORS_VALUES *scalingValues, int16_t nChannels ); This is no included in...
Is there any guidance you can provide on specific functions? My customers are expecting a functioning device driver. Provided that the entire 6000 series has been marked end-of-life, they are not happy buying an old model. I'm currently getting stuck on the following functions (64 bit mode): PREF0 P...
Hi, I'm writing a driver for the PS6000E, and I'm looking for a list of PIDs for all 6000E's. The one I have shows PID_1215, but there are a bunch more in the driver inf that are marked as "PicoScope 6000 series PC". The problem is that the old PS6000 series uses a different API, so I need to differ...
And by the way, you say that there is no 6000A SDK, but the dll is called ps6000a.dll, so it seems that the SDK is actually called 6000A, even thought it supports only the 6000E series.
I'm trying to write a support driver for the Pico6000E series (PS6000A API, because it's only a few letters away, right?). However, I can't find the programmers guide anywhere. Can somebody help me?
Thanks you for your reply. Indeed sending the S/N without the "/" does the job. Might be a nice thing to document in the developer manual
Or have the scope/driver return the serial without the "/" in the first place
Hi, Recently, the scopes we use (Pico3206D) have started rolling over from 10 into 11 digit serial numbers (AA000/1234). It seems that this is causing issues with the driver, as sending an 11 digit S/N with ps3000aOpenUnit() fails (i.e. returns PICO_NOT_FOUND). I already made sure that the string is...
Correct me if I'm wrong, but calling getUnitInfo() requires me to have opened the unit. What I'm asking is how to know which unit will be opened if I have multiple PicoScopes attached and I call openUnit().
Hi! I'm currently working on writing a wrapper for the PicoScope 5xxx native driver, but I can't seem to find a way to target a specific PicoScope for the openUnit() call. As far as I can tell openUnit() picks the scope that's connected to the lowest USB port/hub number, which means that connecting ...