Sequence Global Run-Time Error

[Cimteker]

Hello,

My sequence is setup to ignore run-time errors. When I create a report file at the end of the sequence and the DVM was off (run-time error) it does not see this and creates a passed log file. How do I check for any run-time error in the sequence. Examples I found suggest to check a flag for a step that follows run-time error, but it can happen in any step and I'd like to avoid editing all 300+ tests. Is there a global flag?

Thanks

CT

[~jiggawax~]

I'm assuming that it's not a sequence setting but rather in the Station Options you have changed On Run-Time Error: to Ignore?

You can still use the SequenceFilePostStepRuntimeError callback to capture the result and do deterministing behavior.  You could also set a flag in there if you'd like.

Hope this helps,

[g_Ricky]

I've got the same behaviour but I have to check just the error which is generated from one specific step. I'd like to ignore this run-time error which is generated just in a specific case of this step but I'd like that the sequence is marked as Error or Failed. Which variable do you think I have to force on false to obtain that?

[dug9000]

What I would recommend in this case is to mark the step as ignoring the error and then creating a none-adapter passfail step immediately after it that is set to fail and give it the precondition of the previous step having an error. This will basically convert the error into a failure.

Why exactly do you want to ignore the error, yet also have it effect the status. That's somewhat unusual. Usually I'd expect someone to either want the error to not be ignored, or not want it to effect the status if the execution if they do want it to be ignored. Please help us understand your use case better. We might also then be able to propose a better solution.

-Doug

[g_Ricky]

---

dug9000 ha scritto:

[...]

Why exactly do you want to ignore the error, yet also have it effect the status. That's somewhat unusual. Usually I'd expect someone to either want the error to not be ignored, or not want it to effect the status if the execution if they do want it to be ignored. Please help us understand your use case better. We might also then be able to propose a better solution.

-Doug

---

The run-time error I got back is due to the driver of the instrument I'm using. The instrument is a Tecktronix Oscilloscope which if no waveform is triggered in single mode while you are trying to get a measure, it returns a run-time error. I think the error on the driver is right, but I prefer to set the step as FAILED because i think it is more appropriate for the logic of the test.

I hope this describtion help you to sotisfy your curiosity.
Moreover, I've solved the problem.

So, thank you for your support.

[dug9000]

---

@g_Ricky wrote:

---

dug9000 ha scritto:

[...]

Why exactly do you want to ignore the error, yet also have it effect the status. That's somewhat unusual. Usually I'd expect someone to either want the error to not be ignored, or not want it to effect the status if the execution if they do want it to be ignored. Please help us understand your use case better. We might also then be able to propose a better solution.

-Doug

---

The run-time error I got back is due to the driver of the instrument I'm using. The instrument is a Tecktronix Oscilloscope which if no waveform is triggered in single mode while you are trying to get a measure, it returns a run-time error. I think the error on the driver is right, but I prefer to set the step as FAILED because i think it is more appropriate for the logic of the test.

I hope this describtion help you to sotisfy your curiosity.
Moreover, I've solved the problem.

So, thank you for your support.

---

 Thanks for the info.

-Doug