major-ai-skills/skills/rockwell-studio-5000/gemini.md

Installable agentic skills / AI agent skills (SKILL.md) for Claude Code, Cursor, Codex CLI, Gemini CLI & Antigravity - 402+ professional app, token-efficiency, and common-sense skills. SEO/GEO ready.

---

title: "Rockwell Studio 5000 Logix Designer AI Skill Guide (Gemini)"
description: "Comprehensive operational skill specification for Google Gemini to visually diagnose, automate, script, and troubleshoot Studio 5000 Controller Organizer trees, Ladder Logic rung energization, Tag Monitor tables, and I/O Configuration trees."
category: "Allen-Bradley PLC Programming & Control Design"
tags: ["rockwell-studio-5000", "controller-organizer", "ladder-diagram-ui", "gemini", "tag-monitor", "io-tree-ui", "online-edits"]
---


# Rockwell Studio 5000 Logix Designer AI Skill Guide (Gemini)

## Overview & Engine Architecture
Rockwell Studio 5000 Logix Designer provides a visual control engineering workspace centered around the **Controller Organizer Project Tree**, the **Ladder Logic editor with real-time green power rail energization highlights**, the **Monitor / Edit Tags database grid**, and the **I/O Configuration tree**. Gemini acts as an AI Industrial Controls Reviewer and PLC Safety Systems Auditor, specializing in **multimodal Controller Organizer tree inspection**, **Ladder Logic power flow diagnostics**, **Online Edit zone verification (i/r/d markers)**, and **I/O module connection status validation**.

### Visual Analytics & Industrial Control Workspace Stack

```
┌─────────────────────────────────────────────────────────────┐
│                 Studio 5000 Visual Operations               │
│                                                             │
│  Project Navigation & Logic Viewports                       │
│  ├── Controller Organizer Tree (Tasks, Programs, Routines)  │
│  ├── Ladder Logic Editor (Green Power Rails, XIC/XIO/OTE)   │
│  ├── Online Edit Indicators ('i' Insert, 'r' Replace, 'd')  │
│  └── Function Block Diagram (FBD Wire Dataflows & Pins)     │
│                                                             │
│  Database, Diagnostics & Hardware Matrix                    │
│  ├── Monitor Tags / Edit Tags Grid (Data Types, Radix, Force│
│  ├── I/O Configuration Tree (Chassis, 1756 Modules, Drives) │
│  └── Controller Status HUD (RUN/PROG/FAULT LED Indicators)  │
└─────────────────────────────────────────────────────────────┘
```

---


## Operational Capabilities & Agent Directives

1. **Multimodal Controller Organizer Inspection**: Analyze screenshots of the project organizer tree to verify task priorities, identify inhibited I/O modules, and detect yellow warning triangles across the EtherNet/IP tree.
2. **Ladder Logic Power Flow Diagnostics**: Review active ladder rungs during online monitoring to ensure Examine If Closed (XIC `-[ ]-`) and Examine If Open (XIO `-[/]-`) instructions evaluate true (highlighted green) to energize output coils (Output Energize `-( )-`).
3. **Online Edit Status Tracking**: Guide users through the three stages of Rockwell Online Editing:
  - *Insert Rung (`i` zone)*: Draft new logic.
  - *Test Edits (`I` and `R` active)*: Test logic in real-time execution.
  - *Assemble Edits (`Finalized`)*: Permanently commit rungs into controller flash.
4. **Tag Monitor & Force Verification**: Review Tag Monitor tables to identify active I/O Forces (Amber `FORCE` LED on controller front plate) and ensure safe commissioning states.

---


## Production Python Automation: Automated Studio 5000 L5X XML Tag & AOI Auditor

Run this script to inspect exported Studio 5000 `.L5X` XML project files and audit tag memory definitions:

```python
"""
Studio 5000 L5X XML Project & Tag Auditor
Parses Allen-Bradley L5X XML project files to list Controller Tags, UDTs, and AOIs.
"""

import sys
import os
import xml.etree.ElementTree as ET

def inspect_l5x_project(l5x_path: str):
    if not os.path.exists(l5x_path):
        print(f"Error: L5X project file '{l5x_path}' not found.")
        return

    print(f"--- [INSPECTING STUDIO 5000 L5X XML: {l5x_path}] ---")
    try:
        tree = ET.parse(l5x_path)
        root = tree.getroot()

        target_name = root.attrib.get("TargetName", "Unknown Controller")
        software_rev = root.attrib.get("SoftwareRevision", "vXX.XX")
        print(f"• Controller Target: {target_name}")
        print(f"• Studio 5000 Rev:   {software_rev}\n")

        # 1. Audit Controller-Scoped Tags
        tags = root.findall(".//Controller/Tags/Tag")
        print(f"• Controller Tags:   {len(tags)} tag(s) defined")

        # 2. Audit Add-On Instructions (AOI)
        aois = root.findall(".//AddOnInstructionDefinitions/AddOnInstructionDefinition")
        print(f"• Add-On Instructions:{len(aois)} AOI(s) defined")
        for aoi in aois:
            aoi_name = aoi.attrib.get("Name", "Unnamed")
            rev = aoi.attrib.get("Revision", "1.0")
            print(f"  • AOI: {aoi_name:<20} | Rev: {rev}")

        # 3. Audit User-Defined Types (UDT)
        udts = root.findall(".//DataTypes/DataType")
        print(f"\n• User-Defined Types: {len(udts)} UDT(s) defined")
        for udt in udts[:5]:
            print(f"  • UDT: {udt.attrib.get('Name')}")

        print("\n✅ L5X XML structure validated successfully.")

    except Exception as e:
        print(f"Failed to parse L5X XML: {e}")

if __name__ == "__main__":
    if len(sys.argv) < 2:
        print("Usage: python3 inspect_l5x.py <ProjectExport.L5X>")
        sys.exit(1)
    inspect_l5x_project(sys.argv[1])
```

---


## Technical Troubleshooting Matrix

| Issue & Visual Signature | Root Cause Analysis | Diagnostic & Resolution Pathway |
| :--- | :--- | :--- |
| **Ladder Rung Displays Lowercase `e` on Left Rail** | Rung contains syntax error or unresolved tag name. | Click **Verify Rung** (checkmark icon) to view error description in Output window. |
| **I/O Tree Module Shows Yellow Warning Triangle** | Module connection faulted (e.g. Ethernet cable disconnected, incorrect IP, or electronic keying mismatch). | Right-click faulted module $\rightarrow$ Properties $\rightarrow$ **Connection** tab $\rightarrow$ Read Module Fault code (e.g. `Code 16#0204 Connection Timed Out`). |
| **Controller Front LED Shows Amber `FORCE`** | An engineer left a hardware I/O point forced in the tag table. | In Studio 5000 $\rightarrow$ *Logic $\rightarrow$ Forces $\rightarrow$ I/O Forces*, click **Remove All Forces**. |
| **Tag Shows Yellow Highlight in Monitor Table** | Tag is being actively written to by multiple asynchronous tasks simultaneously. | Use `UID` / `UIE` (User Interrupt Disable) instructions to protect shared critical data sections. |

---


## Command Line Syntax & Server Control

```bash
# Launch Studio 5000 Logix Designer
"C:\Program Files (x86)\Rockwell Software\Studio 5000\Logix Designer\ENG\LogixDesigner.exe"

# Export Studio 5000 Project to L5X Format (via GUI File -> Save As -> .L5X)
```

### Key Configuration Locations
- **Project Files**: `*.ACD`, `*.L5X`
- **EDS Hardware Files**: `C:\Users\Public\Documents\Rockwell Automation\EDS\`

---


## Agent Operational Directive
> **MANDATORY**: Before putting a production line back into operation, always verify that all Online Edits are assembled (`Test Edits -> Assemble Edits`) and no active I/O Forces remain in the controller.