PicoScope 7 Software
Available on Windows, Mac and Linux
ps3000aSetSimpleTrigger() outputs a status of PICO_AUTO_TRIGGER_TIME_TOO_LONG
ps3000aSetSimpleTrigger() outputs a status of PICO_AUTO_TRIGGER_TIME_TOO_LONG
From the function ps3000aSetSimpleTrigger() I get a status code of 0x4000. According to the file PicoStatus.h this is "PICO_AUTO_TRIGGER_TIME_TOO_LONG". This is not one of the possible status outputs for this function as given in:
https://www.picotech.com/download/manua ... -guide.pdf
A screen shot of the call to ps3000aSetSimpleTrigger() is attached. As can be seen I have the auto trigger time set to a value of 1. This is the lowest value possible. How can it possibly be too long?
The goal of this call to ps3000aSimpleTrigger() is to set up the PicoScope 3205D to trigger to do its captures immediately,- without waiting for a trigger.
The documentation states that only one channel is allowed to have its trigger enabled. Will ps3000aSetSimpleTrigger() automatically close all other channels? Or must this be explicitly done?
https://www.picotech.com/download/manua ... -guide.pdf
A screen shot of the call to ps3000aSetSimpleTrigger() is attached. As can be seen I have the auto trigger time set to a value of 1. This is the lowest value possible. How can it possibly be too long?
The goal of this call to ps3000aSimpleTrigger() is to set up the PicoScope 3205D to trigger to do its captures immediately,- without waiting for a trigger.
The documentation states that only one channel is allowed to have its trigger enabled. Will ps3000aSetSimpleTrigger() automatically close all other channels? Or must this be explicitly done?
- Attachments
-
Re: ps3000aSetSimpleTrigger() outputs a status of PICO_AUTO_TRIGGER_TIME_TOO_LONG
Hi,
I ran our block example for the 3000a API - https://github.com/picotech/picosdk-ni- ... leBlock.vi
I get a different error code to you-
PICO_INVALID_PARAMETER - code 13 Dec - 0x0D Hex
I only get this error when setting the "Trigger Direction" to "Above" (0) or "Below"(1). I don't think these are supported for the external trigger input. And works fine otherwise.
I also notice the red Coercion dot for the "Trigger Source" data type, not sure if this would cause an issue. (your data type is wrong, function is correct)
The enum value for the external trigger should be 4.
Why don't you just disable the trigger? Using the "enabled" input in the function.
ps3000aSetSimpleTrigger() will not automatically disable all other channels.You need disable channels that you don't want to use.
If you use advanced triggers these can use multiple channels for triggering.
I ran our block example for the 3000a API - https://github.com/picotech/picosdk-ni- ... leBlock.vi
I get a different error code to you-
PICO_INVALID_PARAMETER - code 13 Dec - 0x0D Hex
I only get this error when setting the "Trigger Direction" to "Above" (0) or "Below"(1). I don't think these are supported for the external trigger input. And works fine otherwise.
I also notice the red Coercion dot for the "Trigger Source" data type, not sure if this would cause an issue. (your data type is wrong, function is correct)
The enum value for the external trigger should be 4.
Why don't you just disable the trigger? Using the "enabled" input in the function.
ps3000aSetSimpleTrigger() will not automatically disable all other channels.You need disable channels that you don't want to use.
If you use advanced triggers these can use multiple channels for triggering.
Regards Andrew
Technical Specialist
Technical Specialist