Rockwell- IO Forcing management

dalporto

Lifetime Supporting Member
Join Date
Jun 2021
Location
Montreal, QC
Posts
258
Hi.


This is the first time I do a project with Rockwell PLC from scratch.


I started a bit just building some AOI for a couple things I need to be sure it was working against InTouch.


Now I'm looking into being able to force whatever I need to force during commissioning.


I mostly used M340 and M580 over the last 10 years and nowadays we can force whatever we please with a M580 so this isn't even is an issue anymore when we cannot get the actual status from the field to test a logic.



Rockwell is still quite different. I don't want to double-up every tag I have just in case I need it during commissioning. I'm not quite sure yet what I can force but it look mostly like only the physical IOs; if I have a tag in between that is being written somewhere I cannot do anything with it.


What are you best practices about that?


Thanks.
 
Personally I don't ever force IO.


For an input I branch around it and put XIC Toggle_To_Test_Input[200] and just toggle that bit to test.


To 'force' an output ON another branch around the whole rung with its test bit. To Force an output OFF I XIO another test bit right before the output.



To make sure nothing is left ON I create a conditionally called subroutine that unlatches each one I put in and then unlatches the bit I toggled to run that subroutine. When I'm done I toggle that to clear all forces.


Also, if something happens in the future and an IO needs forced until something is repaired I can toggle that bit (as long as it's not a safety issue)
 
Personally I don't ever force IO.


For an input I branch around it and put XIC Toggle_To_Test_Input[200] and just toggle that bit to test.


To 'force' an output ON another branch around the whole rung with its test bit. To Force an output OFF I XIO another test bit right before the output.


Yeah, that's what I did today on a live setup but I only had 2 to test.


It looks that I'd need a lot of these to build an "acceptable" simulator. But for wired IO I'm already covered with my remap blocks (I start the simulator and every 16 IO have an INT / WORD that I can modify). I'm looking more for some of the "software" bits in between.



What do you use for AI? In Schneider I use a selector block in a FBD section with a tag starting with SIM_ on each (I usually don't have many AI). I'm not sure how to proceed with Logix yet.
 

Similar Topics

I have a PH meter that I am trying to bring its data into 1756-L81. I have downloaded the Rockwell MODBUS AOI kit, but I am not sure if I need to...
Replies
5
Views
164
Hi all. Customer wants analog faceplates really bad, even if we explained that it doesn't make much sense in his process. What he wants to see...
Replies
5
Views
129
Hello, recently I saw a graphic from any Rockwell App, I cant identify which one is. Attached a SS. Its used to see dashboard from datapoints and...
Replies
2
Views
127
I'm working with a project that contains some routines in ST but mostly in ladder. Am I correct in assuming this 'rung': DB1001DO._01AV55_OPEN :=...
Replies
4
Views
114
I noticed in Rockwell AOIs, they add a BOOL Output parameter at the end of the "Parameters" list of each AOI that carries the same name as the...
Replies
1
Views
79
Back
Top Bottom