Allen-Bradley Studio 5000 Add-On Instructions explained

For Allen-Bradley Studio 5000 Logix Designer V35+.

Add-On Instructions are how Studio 5000 reuses logic. This page covers what an AOI is, when to use one, and how to build, parameterise, and version one. This page is the working engineer's read — what the menu paths actually are in Studio 5000 Logix Designer V35+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program ControlLogix / CompactLogix ourselves, daily; we are not a Allen-Bradley sales channel.

What this is and when you need it

Add-On Instructions are how Studio 5000 reuses logic. This page covers what an AOI is, when to use one, and how to build, parameterise, and version one. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of Studio 5000 Logix Designer V35+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Decide if an AOI is the right tool

Add-On Instructions are reusable, encapsulated logic blocks with their own private tag scope. Use one when: (a) you have logic that runs more than once in the same controller (motor start-stop, valve open-close, alarm latch), or (b) you want to version a piece of logic separately from the program that calls it. Don't use an AOI for one-shot logic — a Periodic Task or a tag-scoped routine is lighter.

2. Create the AOI in the Logical Organizer

Right-click 'Add-On Instructions' in the Controller Organizer > 'New Add-On Instruction'. Give it a name like Motor_Start_AOI. The dialog asks for revision, language (ladder is default; ST and FBD are options), and a vendor string. Click OK and the AOI editor opens — it looks like a routine but with three tag scopes: InOut, Input, Output, plus Local for internal state.

// Tag layout for Motor_Start_AOI
// InOut: MotorRef (UDT)
// Input: StartPB (BOOL), StopPB (BOOL), OL_Trip (BOOL)
// Output: RunCmd (BOOL), Fault (BOOL)
// Local: SealLatch (BOOL)

3. Parameterise the AOI

On the Parameters tab, define every input, output, and InOut tag the AOI exposes. Use InOut for UDTs you want to mutate by reference (a Motor UDT with status, command, and fault fields). Use Input for booleans and ints passed by value. Use Output for booleans the AOI sets. Required: tick 'Required' on parameters that must be wired at every call site — Studio 5000 will refuse to compile a call missing a required parameter.

4. Write the logic

Open the Logic tab. Inside an AOI, you reference parameters by name without prefixes — StartPB not Tag.StartPB. Local tags persist between scans (one set per AOI instance). Build the seal-in latch, the fault logic, the run command. Use the standard XIC, XIO, OTE ladder elements. AOIs can call other AOIs but recursion is not allowed.

// Pseudo-ladder for Motor_Start_AOI
// Rung 1: SealLatch = (StartPB OR SealLatch) AND NOT StopPB AND NOT OL_Trip
// Rung 2: RunCmd = SealLatch
// Rung 3: Fault = OL_Trip

5. Call the AOI from a routine

In MainRoutine or any task routine, drag the AOI from the Add-On Instruction toolbar group onto a rung. Studio 5000 prompts for an instance tag — create one of type Motor_Start_AOI per call site. Wire the parameters: drag tags onto the AOI block's pins. Compile (Ctrl+F8). Errors flag missing required parameters or type mismatches. Download via Communications > Download.

Common mistakes

• Putting persistent state in Input parameters instead of Local — the state survives between scans because Input pins are static, but you lose the ability to test the AOI in isolation
• Forgetting to mark a parameter Required — call sites compile with an unwired pin and the AOI behaves unpredictably at runtime
• Using AOIs for logic that only runs once per program — overhead is real and the indirection makes troubleshooting slower
• Bumping the AOI revision in production without testing each call site — Studio 5000 lets two revisions coexist but the call sites stay pinned to the older revision until manually updated

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

Allen-Bradley Studio 5000 Add-On Instructions explained is one of the building blocks. The full Allen-Bradley curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Allen-Bradley is the right call versus a different brand — see the brand hub. For region-specific context on where Allen-Bradley dominates the SA install base, see the relevant city pages under /brands/allen-bradley/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Allen-Bradley curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Allen-Bradley expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Allen-Bradley's own documentation is the canonical reference once you are working on real hardware: Rockwell Automation Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Allen-Bradley programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Allen-Bradley's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running allen-bradley studio 5000 add-on instructions explained in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Allen-Bradley curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Allen-Bradley install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Allen-Bradley programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. Allen-Bradley Studio 5000 Add-On Instructions explained fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.