I had problem triggering PS2205 from my own program. So I was playing around with both PicoScope5 and 6 to find the similarities between PicoScope functions and programming API. Then I realized something:
1. It's almost impossible to get stable trigger if trigger level is set at about 10% (or less) of selected vertical scale above lower signal peak value (if trigger on rising edge) or below upper one (if trigger on falling edge). I got same results with both PS5, 6 and my program. Is that hardware constraint or software (API) error?
2. If channel A is switched off and trigger is set on channel B, then PS6 always get steadily triggered at some level, regardless of where the trigger reference point is set, event if trigger level is set above max. signal value or below min. signal value. This doesn't happen with PS5 and my program. So I think this is a bug in PS6.
Could you please check and give me some clarification.
My testing condition:
- PS2205 (Hardware Version: 16) on Windows XP SP3
- PicoScope 6 version 18.104.22.168 (Driver Version: 2, 0, 8, 3)
- PicoScope 5 version 5.20.8 (Driver Version: 2, 0, 8, 2)
- My program developed in Delphi 5 with DLL from PS6 (Driver Version: 2, 0, 8, 3)