How Do I set SeqFilePostErrorCallbackEnabled at run time ?

[Rupert Hewitt]

Im trying to disable an error callback in some sequences in a sequence file, I  thought I could simpliy use SeqFilePostErrorCallbackEnabled = false in an TS activeX action step.

Using RunState.Execution as the activex reference

Testsand 2.0 api

Object class Execution

But I just get a runtime error :-

An exception occurred accessing 'SeqFilePostErrorCallbackEnabled' in 'Execution' of 'TestStand API 2.0'
Unknown member ID [97].
Source: TSAPI

-17803; Unknown member ID.

I'm using TS 2.0.1f1

???

[SachaE]

Hi,

  unfortunately this error has been noted in our systems in the past, and the feature in that format doesn't exist in the later versions of TestStand.

In Teststand 3.5, there's an enable callbacks method which takes in a parameter to say which callback to enable / disable.

The only workaround is to add a step to the callback that exits the callback if it should have been disabled. By default the callbacks are enabled so the callbacks are called if at least one step is added to the callback sequence. An end-user unfortunately cannot define steps in a callback in TestStand 2.0 and then turn off the callback programatically to improve performance when they are not needed. Once the steps are defined in the callback, they always get called.

Sorry

Thanks

For TestStand 3.5, you can use the attached sequencefile as a roadmap for implementation

Sacha Emery
National Instruments (UK)

[RayFarmer]

Sacha,

In looking at this problem, I was using TS 3.5 and was still seeing the error. I noticed that this was down as obsolete in the help, so I tried the new method.

Although it didn't error, it didn't appear to disable the callback????

(I'll try your example later)

Note: I didn't a search on the NI website, but couldn't find anything about this being a problem!!!

Regards

Ray Farmer

[Rupert Hewitt]

Hi Sacha,

thanks for your reply, unfortunately im stuck on the older version of teststand for a while yet, too many testers to update and validate.

Ive coded around it !

thanks

Rupert

[SachaE]

Hi Ray,

  this is something which is held internally to National Instruments.

Unfortunately we're unable to put up every item we come across onto the external website, due to space and sensitivity and relevance reasons.

If you could let me know if you can / can't get my example code to run that would be great.

Thanks

Sacha Emery
National Instruments (UK)

[RayFarmer]

Hi Sacha,

I tried your example last night and everything is ok.

I dont know what I was doing wrong the first time, I might even have been confusing myself because the standard error dialog was still being displayed and I wasn't expecting it.

Regards

Ray Farmer