Question about using a NIDCPower HW-timed sequence with SMU (PXIe-4141)

[AJ3D]

Hello,

I'm just getting familiar with HW-timed sequences using NIDCPower to take measurements on a PXIe-4141 in order to avoid the overhead of using SW loops.

From what I understand, I need to do the following steps:

1. Set the sequence using the NIDCPower Set Sequence VI
2. Start the sequence using the NIDCPower Initiate VI
3. Wait for the SMU Sequence Engine to be done using the NIDCPower Wait For Event VI (event = Sequence Engine Done Event)

However, I would like to stop the HW sequence when a measurement threshold value has been reached (before the end of the sequence). Is it possible to create a trigger event that would stop the HW-sequence based on the measurement output? I know this can be done in SW by breaking out of a for loop, but I want to take advantage of HW-timed sequence approach.

Thank you in advance.

[Tepig]

Hi AJ3D, I struggled with the same question previously. But as my conclusion, No.

Once we begin HW-timed sequence, there is no feature which allows measurement-based aborting.

I visited NI office and tested with SE but we couldn't find a solution. Finally, we gave up to implement the feature.

[AJ3D]

Hi Emboar,

That's disappointing. 
What about creating an advanced sequence where the sequence only advances if the measurement is under a certain value? Is that possible?

What approach did you end up settling for?

Thanks

[Tepig]

Your application requires following sequence for instance.

Case Number	Source Type	Voltage	Current Limit	Lower	Upper
1	Voltage	1.5V	100mA	0.5	1.5
2	Current	2V	10mA	0mA	10mA
3	Voltage	5V	10mA	3	5

Let's assume that at case2, the measurement was 20mA and the test was fail,

you would like to abort the sequence.

But unfortunately you cannot. You just only know the result when you call Read or Fetch function on VI,

it's SW based timing. Then, you can compare the result with limitation values.

Such as FGEN device, scripting feature would be a solution but SMU doesn't have it.

On our project, we didn't care each test did pass or fail, ran all sequence anyway.

And as final operation, compared all results with limitation values.