The safety side of the controller: safety tasks and safety tags, CIP Safety I/O, light curtains and area scanners, standard-to-safety tag mapping, and validating a safety program properly.
About this course
The 1769-L33ERMS is a safety controller, and its safety side is a different discipline from the standard side: different rules, different instructions, and a great deal less room to improvise.
The course starts where a real safety project starts: hazard identification, risk assessment and what a safety function is as something you can write down and test against. Then the controller, the safety task, safety tags, the safety signature and what safety-locking changes about working online.
From there it is hardware and logic: adding CIP Safety I/O, safety network numbers and configuration ownership, and building emergency stop, dual-channel monitoring and guard locking from the certified instructions rather than hand-rolled ladder. Light curtains and area scanners get their own module, including safety distance calculation and where muting and blanking are legitimate.
There is a module on standard-to-safety tag mapping specifically, because it is the place where the boundary between the two sides of the controller is most easily undermined, and the course finishes with validation: a test plan, every safety function proven against it, and the signature and documentation the system ships with.
This course teaches how a Compact GuardLogix safety system is configured, programmed and validated. It is not a substitute for a competent safety assessment of your own machine, and it does not certify anyone to sign one off.
What you work through
Hazard identification and risk assessment, performance level and SIL, the safety lifecycle, and what a safety function is as a thing you can write down.
The safety task and safety tags, what the safety signature is for, safety-locking a controller, and what changes about going online once it is locked.
Safety input and output modules, safety network numbers and configuration ownership, test outputs and pulse testing, and proving a channel really is being monitored.
Emergency stop, dual-channel input monitoring, guard locking and reset-with-feedback, built from the certified instructions rather than hand-rolled logic.
Selecting and mounting, calculating safety distance, muting and blanking and when each is legitimate, then wiring, configuring and proving the safety function.
What mapping exists for, the one thing it must never be used for, how to configure it, and the review discipline that keeps that boundary intact.
Write a test plan, verify every safety function against it, generate and record the safety signature, and produce the documentation the system has to ship with.
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.
The safety I/O, light curtain and area scanner this course is built around are not in the lab yet. Of everything in this program, this is the course whose hardware matters most. A safety function you have only read about is not one you have learned.