Get two controllers talking. Message instructions, produced and consumed tags, how to choose between them, and what each one does when the network drops.
About this course
Machines rarely run alone. This course covers the two ways Logix controllers share data over EtherNet/IP, and, more usefully, when to reach for each.
You configure MSG instructions properly, including the sequencing that stops messages stacking up on each other, then set up produced and consumed tags and see what a scheduled connection buys you. Along the way: addressing, the dual-port embedded switch, ring topologies, and what a CIP connection actually costs the controller.
The lab has two controllers exchanging a handshake and a block of production data, with the link broken on purpose so you see exactly how each method fails and what your logic has to do about it.
What you work through
Addressing and subnets, the dual-port embedded switch, linear and device-level ring topologies, and what a CIP connection actually is.
The MSG instruction end to end: CIP Data Table Read and Write, configuring the path, and sequencing messages so they cannot stack up on each other.
Scheduled connections instead of triggered reads: setting up producer and consumer, choosing an RPI, and using connection status in your logic.
MSG against produce/consume on latency, connection count and network load, plus the error handling and watchdogs each one needs.
Two controllers exchanging a handshake and a block of production data, with the link broken on purpose so you see how each method fails.
Lab times are approximate: they are a guide to how long the hands-on part usually takes, not a limit. You can ask for more lab time whenever you need it.
This course is in development. The module list is the curriculum plan, the slides, labs and knowledge checks are still being built, which is why every module reads COMING SOON.
The controller itself is in the lab and working. Other hardware is being added over time as the lab grows, and no course here opens for booking until both its hardware and its material are ready.
This one also needs a second controller on the bench before the lab can run, which is part of what the lab is being built up to.