Running sequence in test uut mode causes StationGlobal.ini modified problem

[Hiren]

When I run the operator interface in test uut mode. After running some execution it comes up with the dialog that the StationGlobal.ini has been modified by other application. When you say not to save the changes it will go in error mode and you have to close the operator interface and reopen it.

[RayFarmer]

Hi Hiren,

This dialog usually appears when you have two applications that have opened and modified the stationglobals.ini, such as having the operator interface and the SeqEditor open at the same time.
If you could answer a few questions it might help to pin point the problem

What TestStand version are you using?

Are you using the default Operator Interface?

In your StationGlobals.ini file read only, or have restricted access from your network administrator?

Briefly, what is your sequencefile performing before the dialog appears.
Do you have any other applications open that have opened the StationGlobals.ini?

Regards
Ray Farmer

[Hiren]

Hello Ray,

I am using TestStand version 2.0 aqnd 3.0.
I have a customised operator interface.
StationGlobals.ini is not a read only file.

And I don't have any other application running when I run the sequence.

It works fine up to few execution and then it puts out this messege.

[David Mc]

Hello Hiren,

Are you running the TestStand Engine version 2.0 or 3.0? Please try running with the default operator interface and see if this problem occurs. This will help us to narrow down if the problem is in the customized operator interface code.

David Mc.
NI Applications Engineer

[RayFarmer]

Hi Hiren,

Can you give the error thats reported when you enter for no change?

Regards
Ray Farmer

[Scott_Richardson]

Hiren -
In addition, can you post the file before and after the request to reload the file. I am interested in what the differences are in the files and please verify that the directory timestamps of the files are different.

Scott Richardson (NI)

[Hiren]

Thank you so much for your support and response.
I have finally figured out the problem. It wasn't the operator interface but the actual sequence file was creating the problem.

I had a string buffer that was declared for 4096.
If you run the sequnce in single pass it was ok but when you run it in uut loop it was getting full at some point of time and the problems started from there.

It took me a while to get this. And the strange thing is TestStand wasn't calling out the same error all the time. It may be exception error one time and stationgloble.ini other time or it will just hang.

Thanks alot one more time.

Hiren