When we use “Message Blocks”, we’ll only need to program the Local to perform the READ and WRITE between the two Local and Remote PLCs.
First, under the Controller Organizer, we created a new Program named “Explicit Messaging”. Then we created a new ladder Routine named ME_READ_WRITE_REMOTE.
We scheduled the MainProgram and “Explicit_Mesaging” programs. Scheduling tells the program to run these programs at the schedule interval set in the Configuration tab.
Within the Configuration tab, there are several types used for the frequency of how often the program will run. We will use the Continuous type and leave the watchdog set to 500 milliseconds.
We will use the CIP Data Table Read Message Type.
Under the Communication tab, we will set the path to RealPars_ProduceConsume_PLC2 the Remote PLC.
We will use the CIP Data Table Write Message Type. The Source Element tag will be MSG_ME_to_REMOTE_DINT and the Destination Element will be MSG_REMOTE_to_ME_DINT using one element. These tags were previously created in both the Local and Remote PLCs as 32-bit integers.
Under the Communication ta...
Let’s download our two PLC programs into the Studio 5000 Logix Emulate software so we can test the “Produce Consume” and “Explicit Message Block” communication methods.
With both programs running Online, we’ll enter a value in the Local PLC1 ME_to_REMOTE_DINT tag of 1111 and observe the communic...
We can see the timers running and the timer done bits energizing the rungs for both READ and WRITE message blocks.
We’ll enter a value in the Local PLC1 MSG_ME_to_REMOTE_DINT tag of 3333 and observe the communication to Remote PLC2 MSG_REMOTE_to_ME_DINT tag value changed to 3333.
In this case, ...
2 Comments