Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

How can I access global area pointer of HMI (Screen number) by PLC?

Created by: Pipo75 at: 11/15/2012 3:55 PM (1 Replies)

Rating (1)

Thanks 0

2 Entries

11/15/2012 3:55 PM	Rate (0)
Pipo75 Posts: 3 Rating: (0)	Pegaia Hi, you must create the area pointer as a DB (not symbolic only), and as array [1..4] of word. Here there is a sample program. Attachment:change screen.zip (180 Downloads) Hi Pegaia! I tried your sample program and it works fine. My problem is that i'd like to prevent user to go to some screens if the bit in PLC is not set to 1. When user is moving through screens with F1 and F2 buttons and if "manual" button on machine is not pressed, user should not access certain screens. I'd also like to know (by PLC) which screen is currently active. If I press F1 or F2 key new screen number is not sent back to Job Mail Box array. How can I access global area pointer of HMI (Screen number) by PLC? Thanx, Primož
Pipo75 Posts: 3 Rating: (0)	Last edited by: O_Moderator at: 11/19/2012 12:00 PM new subject after splitting from /tf/WW/en/Posts/41628#top
Suggestion To thank Quote Answer

11/15/2012 4:13 PM	Rate (1)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 10/11/2024 Posts: 15292 Rating: (2427)	Pipo75 Hi Pegaia! I tried your sample program and it works fine. My problem is that i'd like to prevent user to go to some screens if the bit in PLC is not set to 1. When user is moving through screens with F1 and F2 buttons and if "manual" button on machine is not pressed, user should not access certain screens. I'd also like to know (by PLC) which screen is currently active. If I press F1 or F2 key new screen number is not sent back to Job Mail Box array. How can I access global area pointer of HMI (Screen number) by PLC? Thanx, Primož There are a couple of things to consider. If your template provides several buttons to always function, you will need to remove them from the template or not use the template on the screens where buttons are to be inhibited. Your program logic can also monitor the current screen and automatically progress to the next screen. Your program logic can also set bits that allow buttons to become visible at the proper moment to allow navigation. I use the visiblity option for buttons during initialization and setup procedures all the time. There may be easier ways, but once you have your first button configured the way you need, you can copy/paste to a new screen, make necessary changes and now it will function quite nicely and have the same look/feel throughout the project.
	science guy
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on