9/6/2014 9:06 PM | |
Joined: 9/28/2010 Last visit: 11/27/2024 Posts: 43 Rating: (8) |
It's #2 - at least I think we mean the same. Heading on top of every screen where operator can see some text with screen name. Thanks for advice with text list. Text list can surely be easily localized. but... The text list must have some "process tag" and the tag must be linked to screen number. Here it seems that only way how to get screen number to script variable is read it from PLC (and the PLC must read it from HMI device area pointer). I don't have the physical HW (PLC+TP1200) here, so I cannot test it. And I'm not sure if it will work correctly. When the screen is changed in HMI, the TitleUpdater script is triggered. Also the new screen number is transfered to PLC via area pointer. And then the screen number is transfered back to HMI via Tag (Am I wrong here?). So the it takes some time for the new screen number to get to my HMI Tag. Can I be absolutely sure, that the TitleUpdater script will always use the screen number of the new screen and not the old number of the previous screen (before the screen change)? Even when there is heavy communication load on the PLC-HMI bus? I guess this cannot be reliable. Yes, then there is this way - have all screen names starting with screen number (like 01_Main menu). That would surely work, but I'm afraid of some future inconsitency in the screen numbers. I mean that the screen name prefix number and the "genuine" screen number can be different - And it will surely happen after few future project modifications by some other programmer. |
Follow us on