Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

B&R CP1584 Master Troubleshooting Index

A scenario-based index mapping common B&R CP1584 diagnostic problems to the research documents that solve them. For an engineer who has inherited an undocumented B&R machine and needs to diagnose a specific problem, start here.


How to Use This Index

  1. Identify your symptom from the categories below
  2. Follow the linked document(s) for step-by-step diagnostic procedures
  3. Cross-reference the “See Also” links for related diagnostic paths

Scenario 1: Machine Won’t Boot / PLC Won’t Start

SymptomPrimary DocumentSecondary
PLC shows no LEDs after power-oncp1584-hardware-ref.md — power supply and hardware checksgrounding-emc.md
STATUS LED flashing red/yellow patterncp1584-hardware-ref.md — LED decode tablediagnostics-sdm.md
PLC stuck in BOOT modebootloader-recovery.md — full recovery proceduresaccess-recovery.md
PLC enters SERVICE mode after startupbootloader-recovery.md — SERVICE mode causesar-rtos.md — crash/exception handling
CF card not detected / CF LED errorcf-card-boot.md — CF card contents and diagnosticsfirmware.md
Battery dead, PLC loses settingsretentive-data.md — battery replacement procedurecp1584-hardware-ref.md
firmware corrupted / unknown versionfirmware-version-mgmt.md — version identification and updatebootloader-recovery.md
CP1584 completely unresponsive (brick)bootloader-recovery.md — unbrick procedurescp1584-hardware-ref.md
Error 25314 (page fault) on startupar-rtos.md — exception handling and backtraceprogram-reverse-engineering.md

Scenario 2: Can’t Connect to the PLC from Automation Studio

SymptomPrimary DocumentSecondary
Don’t know the PLC’s IP addressaccess-recovery.md — network discovery via BOOT modecp1584-forensics.md
AS password required / unknownaccess-recovery.md — all credential recovery methodsbootloader-recovery.md
PLC not found in Auto Searchnetwork-architecture.md — network discoveryaccess-recovery.md
“PLC module stuck in BOOT mode: Service”bootloader-recovery.md — BOOT:Service recoveryaccess-recovery.md
Connection drops intermittentlynetwork-architecture.md — network diagnosticsgrounding-emc.md
ANSL port (11169) not respondingpvi-api.md — PVI line configurationnetwork-architecture.md
Migrating from AS4 to AS6, PVI brokenremanufacturing.md — AS4→AS6 migration toolspvi-api.md

Scenario 3: Program Running But Machine Behaving Wrong

SymptomPrimary DocumentSecondary
Outputs not turning on/off correctlyio-card-hardware.md — IO module diagnosticsmemory-map.md — verify addressing
Analog readings wrong / driftinganalog-calibration.md — calibration proceduresio-card-hardware.md
Cycle time violations / watchdog errorsexecution-model.md — task scheduling analysisar-rtos.md — scheduler internals
Intermittent sensor glitchesio-sniffing.md — fieldbus traffic capturegrounding-emc.md
POWERLINK communication errorspowerlink-internals.md — EPL diagnosticsio-sniffing.md
X2X bus errors / IO module diagnosticsx2x-protocol.md — X2X protocol analysisio-card-hardware.md
CAN bus communication failuresif2772-canopen.md — CANopen diagnosticsio-sniffing.md
Servo drive / motor problemsacopos-drives.md — drive diagnosticsencoder-diagnostics.md
Encoder faults on motion axisencoder-diagnostics.md — full encoder diagnosticsacopos-drives.md

Scenario 4: Need to Understand What the PLC Program Does (No Project Files)

GoalPrimary DocumentSecondary
Extract variables from running PLCpvi-api.md — PVI variable enumerationopcua.md — OPC-UA browsing
Browse all IO mappingcp1584-forensics.md — forensic analysismemory-map.md
Read the CF card contentscf-card-boot.md — CF card file layoutftp-web-interface.md
Reverse-engineer compiled codeprogram-reverse-engineering.md — binary analysismemory-map.md
Reconstruct a functional AS projectproject-reconstruction.md — full methodologycp1584-forensics.md
Understand task structureexecution-model.md — task classes and schedulingar-rtos.md
Read alarm/event historyalarm-logging.md — alarm log analysisdiagnostics-sdm.md

Scenario 5: Need to Make Changes Without Stopping the Machine

GoalPrimary DocumentSecondary
Change a setpoint or parameteronline-changes.md — runtime modificationpvi-api.md
Force an output on/offonline-changes.md — force/override techniquesmemory-map.md
Modify running program logiconline-changes.md — online downloadexecution-model.md
Save changes persistentlyonline-changes.md — save to CF cardcf-card-boot.md
Change via OPC-UA from external systemopcua.md — variable write via OPC-UApython-diagnostics.md
Change via PVI from Pythonpvi-api.md — PVI Python accesspython-diagnostics.md
Rollback a bad online changeonline-changes.md — rollback procedurescf-card-boot.md

Scenario 6: Adding Monitoring / Remote Visibility

GoalPrimary DocumentSecondary
Add SNMP monitoringiiot-retrofit.md — SNMP setupebpf-telemetry.md
Add OPC-UA data exportopcua.md — server configurationiiot-retrofit.md
Add MQTT data pipelineiiot-retrofit.md — full MQTT setupcustom-diagnostic-tools.md
Build Grafana dashboardiiot-retrofit.md — dashboard stackpython-diagnostics.md
Trend variables over timesystem-variables.md — system variable monitoringpython-diagnostics.md
Send email/SMS alertsalarm-logging.md — alarm notificationiiot-retrofit.md

Scenario 7: Safety System Problems

SymptomPrimary DocumentSecondary
Safe IO module faultsafe-io-diagnostics.md — safe IO diagnosticsio-card-hardware.md
SafeLOGIC program faultsafe-io-diagnostics.md — safe program analysisexecution-model.md
SIL rating verificationsafe-io-diagnostics.md — SIL assessmentaccess-recovery.md
Safety parameter backupsafe-io-diagnostics.md — parameter backupretentive-data.md
E-stop circuit issuesio-card-hardware.md — digital input diagnosticsgrounding-emc.md

Scenario 8: Physical Layer / Signal Quality Problems

SymptomPrimary DocumentSecondary
Intermittent errors from EMIgrounding-emc.md — EMC troubleshootingphysical-layer-sniffing.md
Cable/connector problemsphysical-layer-sniffing.md — wire-level diagnosticsio-card-hardware.md
Shield/ground problemsgrounding-emc.md — grounding auditphysical-layer-sniffing.md
Oscilloscope signal analysisphysical-layer-sniffing.md — scope techniquesanalog-calibration.md
Encoder signal qualityencoder-diagnostics.md — encoder signal analysisphysical-layer-sniffing.md
Analog signal noiseanalog-calibration.md — analog signal conditioninggrounding-emc.md

Scenario 9: Networking Problems

SymptomPrimary DocumentSecondary
Can’t reach PLC on networknetwork-architecture.md — network discoveryaccess-recovery.md
VLAN/firewall blocking PLCnetwork-architecture.md — network architecturear-rtos.md — security posture
POWERLINK timing violationspowerlink-internals.md — cycle timing analysisexecution-model.md
Modbus communication failuresmodbus-gateway.md — Modbus diagnosticsserial-diagnostics.md
PLC-to-PLC communication issuesplc-to-plc.md — inter-PLC diagnosticspowerlink-internals.md
Time sync / timestamp problemstime-sync.md — NTP/SNTP configurationdiagnostics-sdm.md
Serial port (RS232/RS485) problemsserial-diagnostics.md — serial diagnosticsconfig-file-formats.md

Scenario 10: Hardware Degradation / Aging System

SymptomPrimary DocumentSecondary
CPU running hot / thermal throttlinghardware-monitoring.md — temperature monitoringcp1584-hardware-ref.md
Fan failurehardware-monitoring.md — fan monitoringcp1584-hardware-ref.md
Memory (RAM/CF) degradationhardware-monitoring.md — memory healthcf-card-boot.md
Deciding: repair vs replaceremanufacturing.md — decision matrixspare-parts.md
Direct drop-in CPU upgrade (CF-compatible)remanufacturing.md — X20CP1585/CP1684 upgrade pathfirmware-version-mgmt.md
Next-gen ARM migration (X20EM, multicore)cp1584-hardware-ref.md — X20EM ARM platformremanufacturing.md — AS 6.5 multicore
Spare parts identificationspare-parts.md — part number decodingcp1584-hardware-ref.md
Migration to newer B&R hardwareremanufacturing.md — migration paths (includes AS 6.5 multicore + ST-OOP benefits)project-reconstruction.md
Migration to non-B&R platformremanufacturing.md — CODESYS/Siemens/Beckhoffprogram-reverse-engineering.md
License issueslicense-mgmt.md — license recoveryaccess-recovery.md

Scenario 11: No OEM Support — Complete Documentation Reconstruction

GoalPrimary DocumentSecondary
Systematic documentation approachdocumentation-reconstruction.md — methodologycp1584-forensics.md
IO mapping from scratchdocumentation-reconstruction.md — IO documentationmemory-map.md
Wiring diagram from inspectiondocumentation-reconstruction.md — wiring docsphysical-layer-sniffing.md
Program logic documentationproject-reconstruction.md — logic reconstructionprogram-reverse-engineering.md
Maintenance manual creationdocumentation-reconstruction.md — manual creationspare-parts.md
Building a diagnostic workstationdiagnostic-workstation.md — workstation setupdocumentation-reconstruction.md

Scenario 12: Security Vulnerability Assessment

ConcernPrimary DocumentSecondary
Check all known CVEs for CP1584ar-rtos.md §14 — complete CVE table with 50+ entriesfirmware.md — AR version landscape
ANSL DoS (CVE-2025-11044, CVSS v4.0 8.9)ar-rtos.md §14.9 — ANSL flooding vulnerability (race condition; shorter cycle times increase exploitability)network-architecture.md
SDM data deletion (CVE-2025-3450, CVSS 7.5)ar-rtos.md §14.22 — critical SDM vulnerabilitydiagnostics-sdm.md
SDM XSS/session takeover (SA25P003)ar-rtos.md §14.15-14.17 — SDM web vulnerabilitiesftp-web-interface.md
FTP weak TLS (CVE-2024-5800)ar-rtos.md §14.23 — weak DH groups in AR 4.xftp-web-interface.md
SSL/TLS broken crypto (CVE-2024-8603)ar-rtos.md §14.21 — broken cryptographic algorithmftp-web-interface.md
AS certificate bypass (CVE-2025-11043)ar-rtos.md §14.19 — AS TLS validationaccess-recovery.md
PVI credential logging (CVE-2026-0936)ar-rtos.md §14.18 — PVI logfile leakpvi-api.md
Configure firewall rules for PLCar-rtos.md §14.25 — recommended firewall rulesnetwork-architecture.md
CRA (Cyber Resilience Act) compliancear-rtos.md §14.24 — CP1584 marked CRA non-compliantaccess-recovery.md
SA26P009/010 (XZ Utils, Linux kernel)ar-rtos.md §14.25-14.26 — NOT affected (VxWorks-based)remanufacturing.md
Network isolation strategynetwork-architecture.md — VLAN designar-rtos.md — security posture summary
Full system hardening plancybersecurity-hardening.md — complete hardening guidear-rtos.md — CVE table
Firewall rules for CP1584cybersecurity-hardening.md §4 — complete firewall referencear-rtos.md §14.27
Secure remote access setupcybersecurity-hardening.md §7 — VPN + bastion architecturenetwork-architecture.md
Security incident responsecybersecurity-hardening.md §8 — detection and recoverysafe-io-diagnostics.md
OPC-UA security configurationopcua.md — certificates, encryption, access controlaccess-recovery.md
PPT30 OPC-UA DoS (SA25P006, CVE-2025-11482)opcua.md — concurrent connection handling limitscybersecurity-hardening.md — firewall rules for OPC-UA
XZ Utils impact on B&R (SA26P009) — CP1584 NOT affectedar-rtos.md §14.25 — confirms VxWorks-based PLCs unaffectedcybersecurity-hardening.md
Linux kernel vulns (SA26P010) — CP1584 NOT affectedar-rtos.md §14.26 — confirms VxWorks-based PLCs unaffectedremanufacturing.md — Linux PCs need patching
AS cert validation bypass (SA25P004, Jan 2026)cybersecurity-hardening.md §9.2 — update AS to 6.5firmware-version-mgmt.md — AS 6.5 details
ANSL flooding DoS (SA25P005, CVE-2025-11044)cybersecurity-hardening.md §1.1 — patched in R4.93network-architecture.md — ANSL firewall rules
mapp auth bypass (SA22P014)cybersecurity-hardening.md §9.2 — open on AR 4.xopcua.md — restrict OPC-UA access
SDM multiple new CVEs (SA2025P003)cybersecurity-hardening.md §3.3 — block SDM at firewalldiagnostics-sdm.md

Scenario 13: Machine Just Powered On After Long Storage / Downtime

SymptomPrimary DocumentSecondary
Battery dead, retentive data lostretentive-data.md — battery replacement and data recoverycp1584-hardware-ref.md
CF card not detected or read errorscf-card-boot.md — CF card diagnostics and replacementbootloader-recovery.md
PLC boots to SERVICE mode after long idlebootloader-recovery.md — SERVICE mode causesar-rtos.md — crash analysis
Network settings lost (battery died)access-recovery.md — BOOT mode network confignetwork-architecture.md
IP address unknown, can’t connectaccess-recovery.md — DIP switch default IPcp1584-forensics.md
Motion axes don’t move (encoder lost)encoder-diagnostics.md — encoder realignmentacopos-drives.md
Calibration drift on analog sensorsanalog-calibration.md — recalibration proceduresio-card-hardware.md
OPC-UA certificates expiredopcua.md — certificate renewallicense-mgmt.md
Safety system fault after startupsafe-io-diagnostics.md — safety reset procedureio-card-hardware.md
Need full backup before running machineftp-web-interface.md — CF card backupcf-card-boot.md
Firmware version check before productionfirmware-version-mgmt.md — version auditar-rtos.md §14 — CVE check

External Tools Quick Reference

ToolPurposeUsed In
brwatch (github.com/hilch/brwatch)Watch, change, log variables; set IP; rebootpvi-api.md, access-recovery.md
brsnmp (github.com/hilch/brsnmp)SNMP discovery, IP config, inventoryiiot-retrofit.md, access-recovery.md
systemdump.py (github.com/hilch/systemdump.py)Create/load system dumps from CLIebpf-telemetry.md, diagnostics-sdm.md
Pvi.py (github.com/hilch/Pvi.py)Python wrapper for B&R PVIpvi-api.md, python-diagnostics.md
UaExpert (free from Unified Automation)OPC-UA client for browsing PLC variablesopcua.md, project-reconstruction.md
Wireshark with POWERLINK dissectorCapture and analyze EPL trafficpowerlink-internals.md, io-sniffing.md
as6-migration-tools (github.com/br-automation-community)AS4 to AS6 project migration scriptsremanufacturing.md, firmware-version-mgmt.md
paho.mqtt.c-ar (github.com/br-automation-community)MQTT client library for B&R ARiiot-retrofit.md, custom-diagnostic-tools.md
SystemDumpViewerGUI viewer for SystemDump.xml filesdiagnostics-sdm.md
systemdump.py (github.com/hilch/systemdump.py)CLI: create, upload, delete, inventory system dumps without browserdiagnostics-sdm.md, cp1584-forensics.md
Automation Studio ProfilerTask timing and CPU profilingexecution-model.md, ar-rtos.md
SDM (built-in web UI at /sdm)Browser-based hardware diagnosticsdiagnostics-sdm.md, system-variables.md
B&R VS Code Tools (github.com/br-automation-com/vscode-brautomationtools)Edit, build, transfer AS projects from VS Code (AS 4.x compatible)remanufacturing.md, custom-diagnostic-tools.md
Automation Studio Code (bundled with AS 6.3+)Official B&R VS Code-based editor with AS Copilot AI (AS 6.x only)remanufacturing.md, firmware-version-mgmt.md
AS Copilot (B&R, cloud service)AI assistant for ST code generation within AS Code (free until end 2025)remanufacturing.md
BR.AS.LibraryExporter.exe (bundled with AS 6.5+)CLI tool for exporting libraries from AS projects (-P -n -o -c syntax)remanufacturing.md
ST VS Code extension (Serhioromano.vscode-st)IEC 61131-3 syntax highlighting in VS Coderemanufacturing.md
Loupe Package Manager (loupeteam.github.io)CLI for managing Loupe packages in ASremanufacturing.md
SafeDODiag (github.com/br-automation-community/SafeDODiag)AS library: diagnoses why safe digital outputs are not enabled (mapp Safety, Safety Release, X20SO21x0/X20SO41x0)safe-io-diagnostics.md
openSAFETYLogbrowser (github.com/banickn/openSAFETY-logbrowser)Electron app: log browser for openSAFETY protocolsafe-io-diagnostics.md
acopos-cheat-sheet (github.com/hilch/bar-acopos-cheat-sheet)Quick reference for ACOPOS servo drive parameters and commandsacopos-drives.md
TrakDiag (github.com/hilch/TrakDiag)AS library: ACOPOStrak linear motor system diagnosisacopos-drives.md
BrSecurity (hilch.github.io/BrSecurity)AS library: Password, Encrypt, Decrypt functionsaccess-recovery.md, cybersecurity-hardening.md
OMJSON (github.com/loupeteam/OMJSON)AS library: WebSocket + JSON communication from PLCiiot-retrofit.md, custom-diagnostic-tools.md
OMSQL (github.com/loupeteam/OMSQL)AS library: SQL database communication from PLCiiot-retrofit.md
TCPComm / UDPComm (github.com/loupeteam)AS libraries: Simplified wrappers for AsTCP/AsUDPcustom-diagnostic-tools.md
PLC-data-trace (github.com/hilch/PLC-data-trace)AS project: Records PLC variables in high-priority task, saves to CSVcustom-diagnostic-tools.md, python-diagnostics.md
mappRemoteShell (github.com/br-automation-community/mappRemoteShell)Sample project: Execute shell commands on remote PC via OPC-UA + Pythoncustom-diagnostic-tools.md
ListAllBurPLCs (github.com/Chihing/ListAllBurPLCs)Lists all B&R PLCs on the networknetwork-architecture.md, access-recovery.md
demo-br-asyncua (github.com/hilch/demo-br-asyncua)Python example: Access B&R PLC with asyncua (asyncio OPC-UA)opcua.md, python-diagnostics.md
OpcUaSamples (github.com/br-automation-community/OpcUaSamples-sample-AS)OPC-UA configuration and coding samples from AS4.1 to newest ASopcua.md
easyuaclient-as-project (github.com/br-automation-community/easyuaclient-as-project-dev)Easy OPC-UA client wrapper library for ASopcua.md
canopen-message-interpreter (github.com/hilch/canopen-message-interpreter)Python script: Interpret CAN traces as CANopen (CiA DS301)if2772-canopen.md
Persist (github.com/loupeteam/Persist)AS library: Store any variable type to permanent memoryretentive-data.md
CSVFileLib (github.com/loupeteam/CSVFileLib)AS library: Read/write variable values to CSV filescustom-diagnostic-tools.md
mappPanel (github.com/br-automation-community/mappPanel)Sample: PLC to T-Panel communication over OPC-UAhmi-integration.md
B&R DevOps Package (github.com/br-automation-community/BnR-DevOps-Package)DevOps practices for AS project developmentdocumentation-reconstruction.md
BuildVersion (github.com/br-na-pm/BuildVersion)Git commit + AS build info captured in variable declarationsdocumentation-reconstruction.md
FindUsbStickOnBAndRPlc (github.com/hilch/FindUsbStickOnBAndRPlc)AS library: Find and use USB sticks on PLC for file I/Ocustom-diagnostic-tools.md, cf-card-boot.md
mappCleanUp (github.com/br-automation-community/mappCleanUp)AS sample: Delete old files from PLC directory by criteriacf-card-boot.md
UserLog (github.com/tmatijevich/UserLog)AS library: Synchronous user logbook writingalarm-logging.md
LogThat (github.com/loupeteam/LogThat)AS library: Easy diagnostic info into CPU Loggerdiagnostics-sdm.md
MyDiag (github.com/hilch/MyDiag)AS library: Wrapper around ArEventLog and AsArSdm for CPU loggerdiagnostics-sdm.md

The “I Just Inherited This Machine” Checklist

NEW: For a complete step-by-step first-hour playbook, see first-60-minutes.md.

For an engineer walking up to a B&R CP1584 machine with zero documentation:

  1. Physical: Read CPU label → cp1584-hardware-ref.md
  2. Network: Discover PLC on network → access-recovery.md, network-architecture.md
  3. Diagnostics: Open SDM in browser → diagnostics-sdm.md
  4. Variables: Browse via OPC-UA or PVI → opcua.md, pvi-api.md
  5. Config: Read CF card via FTP → ftp-web-interface.md, cf-card-boot.md
  6. Program: Understand running logic → project-reconstruction.md
  7. Safety: Assess safety system → safe-io-diagnostics.md
  8. Document: Build maintenance manual → documentation-reconstruction.md
  9. Secure: Review access controls AND check firmware version against CVE table → access-recovery.md, ar-rtos.md §14
  10. Monitor: Set up remote visibility → iiot-retrofit.md, python-diagnostics.md

Scenario 14: Migrating from Automation Studio 4 to AS 6

GoalPrimary DocumentSecondary
Analyze AS4 project for AS6 compatibilityremanufacturing.md §5 — migration analysisfirmware-version-mgmt.md
Run automated migration analysisUse as6-migration-tools (github.com/br-automation-community/as6-migration-tools) — detects deprecated libs, unsupported hardware, breaking changesremanufacturing.md §5.3
Handle deprecated INA2000 in PVI codepvi-api.md §2 — PVI 6.x drops INA2000, ANSL migrationpython-diagnostics.md
Update OPC-UA client code for AR 6opcua.md — AR 6.x OPC-UA changesremanufacturing.md
Hardware upgrade with AS6 supportremanufacturing.md — target CPU comparison tablecp1584-hardware-ref.md
CP1584 is obsolete (SN 2022/54, LTB Feb 2023)remanufacturing.md — discontinuation notice and spare parts strategyspare-parts.md
Migrate mappMotion code to mappMotion 6remanufacturing.md — mappMotion update helperacopos-drives.md
Check mapp technology license requirementslicense-mgmt.md — license checker toolremanufacturing.md
AS 6.5 multicore + ST-OOP benefitsremanufacturing.md — AR 6.5 featuresexecution-model.md

Document Cross-Reference Map

cp1584-hardware-ref.md ──── cp1584-forensics.md ──── cf-card-boot.md
        │                        │                       │
        ├── firmware.md ────────├── config-file-formats.md ──┘
        ├── hardware-monitoring.md │                        │
        ├── grounding-emc.md       │                        ├── bootloader-recovery.md
        │                        │                        │
        └── io-card-hardware.md ───┘                        └── access-recovery.md
                                                                │
ar-rtos.md ──── execution-model.md ───── memory-map.md ────────┘
     │                                    │
     ├── diagnostics-sdm.md ──── system-variables.md
     │
     └── ebpf-telemetry.md ────── custom-diagnostic-tools.md
                                     │
network-architecture.md ──── powerlink-internals.md ── io-sniffing.md
        │                                    │               │
        ├── plc-to-plc.md ──────────────────┘               │
        │                                                    │
        ├── if2772-canopen.md ────────────────────────────────┘
        │
        ├── modbus-gateway.md
        │
        └── serial-diagnostics.md

pvi-api.md ──── python-diagnostics.md ─── opcua.md ── iiot-retrofit.md
                                                     │
                                                     ├── ftp-web-interface.md
                                                     │
time-sync.md ──── alarm-logging.md ──────── safe-io-diagnostics.md
                                         │
                                         └── hmi-integration.md

cybersecurity-hardening.md ── ar-rtos.md ── network-architecture.md
          │                        │
          ├── access-recovery.md ├── firmware-version-mgmt.md
          │                        │
          └── diagnostics-sdm.md ── ftp-web-interface.md

program-reverse-engineering.md ── project-reconstruction.md
                                              │
acopos-drives.md ── encoder-diagnostics.md ──── analog-calibration.md
                                                    │
                                                    └── x2x-protocol.md

online-changes.md ── retentive-data.md ──── license-mgmt.md
                                          │
                                          └── firmware-version-mgmt.md

remanufacturing.md ── spare-parts.md ──── remanufacturing.md
                                      │
                                      └── cp1584-hardware-ref.md

access-recovery.md ── documentation-reconstruction.md ── diagnostic-workstation.md

Scenario 15: IO Module LED Patterns — Quick Decode

LED PatternMeaningPrimary DocumentAction
All modules: ‘r’ blinking continuouslyX2X bus communication lostx2x-protocol.md — X2X diagnosticsCheck X2X cable, terminator, CPU RUN state
Single module: ‘e’ blinking, ‘r’ steady greenI/O power supply missing to that moduleio-card-hardware.md — power supply diagnosticsCheck PS module terminal 1-5, verify jumpers
Single module: ‘e’ double flashX2X power overloaded or I/O power too lowio-card-hardware.md — LED decodeCheck total station current, reduce load
‘e’ steady red + green flashInvalid firmware on modulefirmware-version-mgmt.mdUpdate module firmware
PS module: ‘l’ red steadyX2X Link power supply overloadedio-card-hardware.md — power budgetReduce number of modules or add PS
PS module: ‘r’ single flashModule in RESET modeio-card-hardware.mdCheck reset trigger, re-initialize
ACOPOS: Green steadyDrive running normallyacopos-drives.md — LED referenceNone
ACOPOS: Green blinkDrive can’t enableacopos-drives.md — enable diagnosticsCheck X2.6 enable, 3-phase power
ACOPOS: Red steadyActive fault — note codeacopos-drives.md — fault code tablesLook up code, fix cause, reset
ACOPOS: Red/Green alternatingBootloader modeacopos-drives.md — firmware updateDo NOT power off during update
ACOPOS: All LEDs offNo 24V DC control poweracopos-drives.md — power diagnosticsCheck 24V supply, fuse, wiring
CPU: R/E green steadyApplication runningcp1584-hardware-ref.md — CPU LED tablesNone
CPU: R/E red steadyBOOT or SERVICE modecp1584-hardware-ref.md — mode switchCheck mode switch, logbook
CPU: R/E red blink + RDY/F yellow blinkLicense violationlicense-mgmt.md — license checkCheck TG dongle/container
CPU: S/E off/off (POWERLINK)Interface not active or misconfiguredcp1584-hardware-ref.md — PLK statesCheck AS config, cable
CPU: S/E off, red blinkingSystem stop with error codecp1584-hardware-ref.md — stop error codesCount blink pattern (RAM or HW error)
CPU: DC redBackup battery emptyretentive-data.md — battery replacementReplace Renata CR2477N within 1 min

Key Findings

  1. This index is the fastest way to find the right document for any CP1584 problem. Organized by symptom and diagnostic scenario, it maps common problems to the specific research documents that contain the solution procedures.

  2. Start with the LED and error code tables. For any hardware fault, the LED pattern on the CPU, IO modules, or ACOPOS drives points directly to the relevant diagnostic document and the likely root cause.

  3. Most intermittent problems require protocol-level diagnostics. If a problem can’t be reproduced consistently, check the “Intermittent Problems” scenarios for protocol sniffing approaches that capture evidence without disturbing the running system.

  4. Security scenarios are critical for network-connected CP1584 systems. With 20+ unpatchable CVEs on AR 4.x, any CP1584 on a network should be hardened according to cybersecurity-hardening.md.

  5. The first-60-minutes.md playbook covers emergency response. For a machine that just went down with no documentation, start with first-60-minutes.md for the immediate recovery workflow, then use this index for deeper investigation.


Scenario 16: Engineering Workstation Security — AS and PVI Vulnerabilities

ConcernPrimary DocumentSecondary
AS certificate bypass (CVE-2025-11043, SA25P004)cybersecurity-hardening.md §9.4 — AS accepts invalid certs, MitM riskaccess-recovery.md
AS SQLite critical vulns (25 CVEs, CVSS 9.8, SA25P007)cybersecurity-hardening.md §9.4 — code execution via crafted project filesfirmware-version-mgmt.md §11.2
PVI credential logging (CVE-2026-0936, SA26P001)pvi-api.md §16 — credentials in plaintext log filescybersecurity-hardening.md §9.4
Isolating the engineering workstationcybersecurity-hardening.md §7 — VPN + bastion architecturenetwork-architecture.md
PVI log files as credential source for recoverypvi-api.md §16.5 — search workstations for PVI logsaccess-recovery.md

Scenario 17: HMI Panel and OPC-UA Server Security

ConcernPrimary DocumentSecondary
PPT30 OPC-UA DoS (CVE-2025-11482, CVSS v4.0 8.7, SA25P006)opcua.md §13 — permanent OPC-UA crash via resource exhaustioncybersecurity-hardening.md §9.2
OPC-UA anonymous access left enabledopcua.md §13 — hardening checklistaccess-recovery.md
OPC-UA self-signed cert expiredopcua.md §6 — certificate regenerationcybersecurity-hardening.md §5
HMI panel OS version unknownhmi-integration.md — panel identificationspare-parts.md
SDM web interface XSS (CVE-2025-3448, CVE-2025-11498)diagnostics-sdm.md §15 — SDM securitycybersecurity-hardening.md §9.2

Last updated: July 2026 (added Scenario 17: HMI/OPC-UA security; added SA25P006 CVE-2025-11482 and SA2025P003 CVE details to cybersecurity-hardening.md and opcua.md; added CISA republication dates for ICSA-26-125-03 and ICSA-26-141-04)