cmarcus Posted March 6, 2012 Report Share Posted March 6, 2012 (edited) Hello Everyone, I have been using Unitronics products for nearly a decade now and have very few gripes. I love how the team actually listens and reacts to their customers needs. With that said, there is one thing that drives me nuts! It's the interaction between using a key value to jump from display A to display B, and having that same key value perform a (ladder) function while display B is displaying. I've attached attached a few images to illustrate what I'm talking about. I have main menu (display A) that uses SB41 (key 1) to jump to display B I have reset menu (display B ) that gives the operator the ability to reset the count by pressing any one of the buttons preceeding the lane. I have the ladder function that states, On rise of SB41 (key 1), While SI252 (current display) = #49 HMI info display number for reset menu (display B ), Reset Lane 1 count (ML1) So when I run my program, the act of pressing SB41 while displaying display A to move to display B, actually resets my count in display B. I've also tried using the same code but moving my ladder to a new subroutine and linking it to the "While Displaying" and I still get the same result. It appears the PLC processes the jump condition first, then perfoms the ladder scan. Is there any reason why it is done in this order? Wouldn't it make more sense to reverse this and perform a display jump condition at the end of the ladder scan, so that the rising edge of buttons that are used to perform the jump don't interact with any ladder funtions that are supposed to occur after the jump has completed? Thanks, Edited March 6, 2012 by Simon Removed auto Smileys :-) Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.