PLC Simulator
Allen-Bradley cheat sheet

Allen-Bradley addressing and tag cheat sheet

Logix controllers address data by tag name. The legacy PLC-5, SLC 500 and MicroLogix families use file addresses instead. Both styles are in use on real sites, so this sheet covers each and then shows how this browser editor maps them.

Logix tags (ControlLogix and CompactLogix)

Logix tags (ControlLogix and CompactLogix)
ItemSyntaxMeaning
Controller-scoped tagMotor_RunA named variable that every program in the controller can use.
Program-scoped tagMotor_RunSame style of name, but visible only inside the program that owns it.
Bit of a whole-number tagStatus_Word.5Bit 5 of a DINT, counting from 0.
Array elementPressures[3]The fourth element, because arrays count from 0.
User-defined type memberPump_1.SpeedA member of a structure tag.
Timer membersPump_Timer.PRE .ACC .EN .TT .DNPreset and accumulated time in milliseconds, plus enabled, timing and done bits.
Counter membersPart_Count.PRE .ACC .CU .CD .DN .OV .UNPreset and count, with count-up, count-down, done, overflow and underflow bits.

Common Logix data types

Common Logix data types
ItemSyntaxMeaning
BOOLBOOLOne bit, 0 or 1.
Whole numbersSINT INT DINT LINT8, 16, 32 and 64-bit signed integers. DINT is the usual default.
Floating pointREAL32-bit floating point.
StructuresTIMER COUNTER CONTROLBuilt-in structured types with named members.

I/O tags created by the module configuration

The exact tag names come from the I/O configuration in the project. Open the controller organizer and copy the names from there. The form shown is for a digital module; analog and specialty modules use other member names.

I/O tags created by the module configuration
ItemSyntaxMeaning
Input bit, local chassis moduleLocal:1:I.Data.0Slot 1, input data, bit 0.
Output bit, local chassis moduleLocal:2:O.Data.0Slot 2, output data, bit 0.

Legacy file addresses (SLC 500 and MicroLogix)

The file numbers shown (B3, N7, T4, C5, F8) are the usual defaults. A project can add files or use other numbers, so check the data file list in your own program.

Legacy file addresses (SLC 500 and MicroLogix)
ItemSyntaxMeaning
Input bitI:1/0Input file, slot 1, bit 0.
Output bitO:2/3Output file, slot 2, bit 3.
Binary (bit) fileB3:0/5File B3, word 0, bit 5.
Integer fileN7:0File N7, element 0, a 16-bit integer.
Timer fileT4:0 T4:0.ACC T4:0.DNTimer element with its accumulated value and done bit.
Counter fileC5:0 C5:0.ACC C5:0.DNCounter element with its count and done bit.
Floating-point fileF8:0File F8, element 0.

In this browser editor

In this browser editor
ItemSyntaxMeaning
Input tagTAG START I:0/0 BOOLDeclares START on input word 0, bit 0, which the editor maps to the IEC address %I0.0.
Output tagTAG LAMP O:0/0 BOOLDeclares LAMP on output word 0, bit 0, mapped to %Q0.0.
Internal bitTAG TURN_ON BOOLA BOOL with no I/O address.
Timer or counter instanceTAG T_PUMP TON / TAG CNT CTUAn instance; read its done output as T_PUMP.Q.

What this sheet leaves out

  • Produced and consumed tags, and tag aliases.
  • Add-On Instruction parameters.
  • Remote I/O module tag names, which depend on the module profile and firmware.

Always confirm addresses and ranges against the manual for your exact controller and software version. Want to see these addresses used in logic? Read the Allen-Bradley instruction reference.

Frequently asked questions

What is the difference between tag-based and file-based addressing?

Logix controllers use named tags that you create, such as Motor_Run, with a data type. SLC 500 and MicroLogix controllers use fixed file addresses, such as B3:0/5, where the letter and number give the file type and position. The same logic reads very differently in the two styles.

How do I address a timer's done bit?

In Logix write the timer tag, a dot and DN, for example Pump_Timer.DN. In an SLC 500 or MicroLogix write the element and the bit, for example T4:0.DN. The browser editor reads the done output as T_PUMP.Q.

Can I copy these addresses straight into a project?

Use them as a guide to the format. I/O tag names in a Logix project come from the module configuration, and file numbers in an SLC project can be changed, so always check the names in your own project.

Training material. Follow your site procedures, local electrical code and the manufacturer's instructions. Lockout/tagout and a qualified person are required for real equipment.