drew wrote:
Whenever we have the proc. in prog. not run or not connected the panelview keeps giving errors across the top. Is there a way to prvent this?
I don't think so. But, then again, isn't it nice to know why your panelview pushbuttons are not reacting to your presses?
A while back I learned the subtleties (sp?) of combining PLC driven and Operator Driven screen changes. The answer his buried in Ken's answer:
If it's a zero, the PanelView has control over it's own screen changes (using GOTO and RETURN buttons). If the address value is nonzero, the PanelView changes to that screen number.
Now, if you want it both ways, When you are done with your plc screen change, you have to put a zero back into the Screen Number Control Tag address when your PLC directed change is complete.
To do this I define the Screen Number
Status Tag as SCRN_DISP and the Screen Num
Control Tag as SCRN_REQ. Then add the following to the ladder.
+-----------------+ +--------------+
-----| EQU SCRN_REQ |---------[OSR]-------------| MOV 0 |
| SCRN_DISP | | SCRN_REQ |
+-----------------+ +--------------+
.
So if you need some screen to be controlled by the PLC for instance due to conditions required before changing to that screen you can do it and for the simple changes just use GOTO buttons or screen selector lists so you don't have to program every single screen change.
When you want a screen change in the PLC, MOV the screen number into the adderss for the SCRN_REQ tag. The PLC will change to the requested screen and set SCRN_DISP to match. Then your ladder will see that SCRN_REQ and SCRN_DISP are equal and plunk a 0 back into the SCRN_REQ address to allow for operator changes.
enjoy
beerchug