After experience of C&I Dpt. within some years of operation with GE 9FA & MarkVI system we'd like to setup several new watch windows with I/O signals that can be easily traced & forced by any operator of the plant.
Trying to create any new watch windows we've noticed that even if you create a new one with all appropriate signals this one disappears if for any instance Toolbox is closed & reopened.

Can someone help out on how can I create permanent watch windows that will remain after closing & re-opening of application program?

 

Have you used the Toolbox 'Help' feature to see if there is some step you are missing?

I have seen a similar problem once before, where a particular user (Oper) was prevented from saving changes to the .m6b file (these kinds of displays are saved to the .m6b file, and can cause there to be a mismatch between the file and the Mark VI version--which is a stoopid little annoyance of Toolbox (one of many)). This was because someone had set the MS-Windows file properties to prevent the Oper user from making changes to the .m6b file.

I believe you have to save the Watch Window you create, by giving it a unique name, and then when you open Toolbox again, and open the Watch Window utility (I like to use Ctrl+W, a keyboard shortcut) you can select from the saved Windows or create a new. You should also be able to add or modify existing Windows--provided the user you are logged in as has the appropriate permissions, both in Toolbox and in MS-Windows.

So, it might be that the version of Toolbox you are using requires a certain password level to save Watch Windows, or it might be that you are not completing the process correctly, or it might be some that well-intentioned soul has inadvertently set the MS-Windows file properties to prevent the user you are logged in as from making changes to the file.

Lastly, are you sure you are making changes to the "Master" .m6b file? And then opening the "Master" .m6b file to view the changes? Some sites still have multiple copies of .m6b files on multiple HMIs--which is NOT recommended.

Hope this helps!

Please write back to let us know how you resolve the issue.