05-31-2007 03:50 AM
05-31-2007 04:16 AM
Hi,
It's probably due to the fact that the Test Entry button's only appears if there is a sequence file loaded which has a process model sequence file associated with it.
When you logged logout, did you log back in to teststand?
Regards
Ray Farmer
05-31-2007 06:16 AM
Thank you for your reply,
I just click the "termination" button, even I don't have a button to close the sequence, so I think the sequence file is still there, btw, I use the sequential process model.
Is there other possibility?
05-31-2007 06:47 AM
Hi,
Does that mean your Operator Interface application is still running?
If it is then you will have to login to Teststand. If you haven't got a button or menu item to Login. Then you will have to exit the application and relaunch the Operator Interface again.
Regards
Ray Farmer
05-31-2007 07:40 AM
The OI is running, but the sequence execution is terminated. And there is no Test UUTs button,
I can still login and logout, but it will not make the button shown up again.
If I quit the OI, and restart it will happen again. (First run of sequence ok, but disappear the button later.)
05-31-2007 08:02 AM
Hi,
It looks like you are unloading your sequence file when you log out but when you log back in you are not reloading the sequencefile.
You need to relook at the OI code and make sure you are performing the Open Sequence File with the correct parameters for your sequence file. Maybe its been cleared as a result of the logout.
Regards
Ray Farmer
05-31-2007 07:56 PM
Yes, you are right, when I log out, the sequence file is unloaded automatically (although I don't know why)
I guess that TestStand has a mechanism to avoid the existance of sequence file when there is no user?
I change the cmdKind fo connect command for the button from "CommandKind_LoginLogout" to "CommandKind_Login" in the subvi "Configure Application Manager.vi"
and it works fine.
Thank you.