B&R X20CP1584 Complete Hardware Reference

Overview

The B&R X20CP1584 is a mid-range PLC CPU module in the X20 system family, based on the Intel Atom E640T processor. It is a headless controller (no integrated display) designed for industrial automation applications requiring POWERLINK real-time networking, Gigabit Ethernet, and modular I/O expansion via the X2X Link bus. This document consolidates all hardware specifications, physical details, and practical information needed for physical inspection, spare parts procurement, and hardware configuration of a CP1584 in the field.

Key identifiers:

• Order number: X20CP1584
• Coated variant: X20cCP1584 (identical electronics, conformal coating for harsh environments)
• B&R ID code: 0xC370

CPU Specifications

Memory Architecture

The SRAM is backed by a lithium battery (Renata CR2477N, 3V/950mAh). Actual usable user RAM = 1 MB minus configured remanent variable space. See retentive-data.md for battery management and data retention procedures.

Interfaces

IF1 - RS232 (Serial)

The RS232 interface shares the X20TB12 terminal block with the CPU/I/O power supply. The RS232 pins are on the bottom row (pins 7-12 area):

Wiring for serial console (DB9 null-modem cable to PC):

• PLC TX → PC RX (pin 2 on DB9)
• PLC RX → PC TX (pin 3 on DB9)
• PLC GND → PC GND (pin 5 on DB9)

Note on “900 m max distance”: B&R rates the RS232 interface at 900 m. This exceeds the TIA-232 standard maximum of ~15 m at 115.2 kbit/s. B&R’s rating likely assumes RS422/RS485 line driver/receiver equipment is used at the far end. For standard RS232 point-to-point wiring, observe the standard limits. See grounding-emc.md for serial cable EMC considerations.

Important: The factory default baud rate is 57600 bps. While rates up to 115.2 kbit/s are supported, the default must be assumed when connecting to an unknown PLC. See bootloader-recovery.md for serial console usage.

IF2 - Ethernet (Gigabit)

This is the primary interface for:

• Automation Studio online connection (ANSL/PVI)
• OPC-UA server
• FTP server
• Web server (SDM)
• SNMP
• General TCP/IP communication

The INA2000 station number is set using the two hex switches on the front panel.

IF3 - POWERLINK (Real-Time Ethernet)

Important: POWERLINK mode only operates in half-duplex. The interface cannot be used for POWERLINK and standard Ethernet simultaneously. When POWERLINK is active, IF2 (Ethernet) must not use an IP address in the POWERLINK address range (192.168.100.x). See powerlink-internals.md for protocol details.

IF4 and IF5 - USB

Critical limitations:

• USB interfaces CANNOT be used for online communication (no ANSL/PVI over USB)
• Only ground-isolated USB devices are permitted
• B&R only guarantees functionality of B&R-branded USB devices

IF6 - X2X Link (I/O Bus)

The X2X Link connects to X20 bus couplers and base modules for I/O expansion. See x2x-protocol.md for protocol details.

Electrical Isolation

All three network interfaces are galvanically isolated from each other and from the PLC:

• Ethernet (IF2) - isolated
• POWERLINK (IF3) - isolated
• X2X Link (IF6) - isolated

RS232 (IF1) and USB (IF4/IF5) are NOT galvanically isolated.

Power Supply

CPU and X2X Link Power Supply

X2X Link Power Output

I/O Power Supply

Terminal Block Pinout (X20TB12)

The 12-pin terminal block provides power connections and RS232:

Wiring specifications:

• Wire type: copper only (no aluminum)
• Solid wire: 0.08 - 2.50 mm2 (28-14 AWG)
• Stranded wire: 0.25 - 2.50 mm2 (24-14 AWG)
• Strip length: 7-9 mm

Physical Specifications

Operating Conditions

Overtemperature Shutdown

Logbook errors:

• Error 9204: PLC restart triggered by CPU temperature monitoring
• Error 9210: Warning: Halt/Service after watchdog or manual reset

Certifications

• CE, UKCA
• ATEX Zone 2 (II 3G Ex nA nC IIA T5 Gc IP20)
• UL/cULus E115267 (Industrial control equipment)
• HazLoc cCSAus 244665 (Class I, Div 2, Groups ABCD, T5)
• DNV (maritime: Temperature B, Humidity B, Vibration 4g, EMC B)
• ABS, BV, CCS, KR, EAC

Front Panel Layout

  [1]  [2]     [3]    [4]
  |    |        |      |
  | Top-hat rail latch
  | Select application memory (CF card select switch)
  | Slot for CompactFlash
  | LED status indicators (R/E, RDY/F, S/E, PLK, ETH, CF, DC)
  |
  [5] [6]           [7]
  |   |               |
  | IF6 - X2X Link
  | IF1 - RS232 (via terminal block)
  | Slot for interface module (1 slot on CP1584)
  |
  [8]         [9]  [10]   [11]  [12]
  |            |    |      |     |
  | Terminal block (power + RS232)
  | IF5 - USB
  | IF4 - USB
  | Reset button
  | Battery compartment
  |
  [13]  [14]
  |     |
  | IF3 - POWERLINK (RJ45)
  | IF2 - Ethernet (RJ45)
  |
  [15]
  |
  Ethernet station address (hex switches)

LED Status Indicators

CPU Status LEDs

S/E LED - POWERLINK Interface States

Ethernet mode:

POWERLINK V1 mode:

POWERLINK V2 mode - Blink patterns:

POWERLINK V2 state transition for CN (controlled node):

BASIC_ETHERNET ──(EPL detected)──→ PRE_OPERATIONAL_1 ──(SoC received)──→
PRE_OPERATIONAL_2 ──(command)──→ READY_TO_OPERATE ──(command)──→
OPERATIONAL

Key diagnostic note: If the S/E LED is off with no green or red, and the R/E LED shows green (application running), the POWERLINK interface may be configured as Ethernet-only (not POWERLINK) in Automation Studio. Check the interface module configuration or the CPU’s IF3 settings.

Power Supply LEDs

System Stop Error Codes

When S/E blinks red, the error code is a sequence of 4 phases (150 ms = short, 600 ms = long), repeated every 2 seconds:

Operating Mode Switch

The CP1584 has a three-position operating mode switch:

Important: Any switch position other than the three listed is not permitted.

Reset Button

The reset button is located below the USB interfaces on the bottom of the housing. It can be pressed with a small pointed object (paper clip, etc.).

Pressing the reset button causes a hardware reset:

• All application programs are stopped
• All outputs are set to zero
• The PLC starts up in SERVICE mode by default (configurable in AS)

Ethernet Station Address (Hex Switches)

Two hex rotary switches set the INA2000 station number for Ethernet (IF2) and optionally the POWERLINK node number (IF3).

When used for Ethernet (IF2), the station number maps to the default IP address formula: 192.168.1.<station_number> in some configurations. For POWERLINK, the switch directly sets the node number.

CompactFlash Card

The CF card slot accepts industrial-grade CompactFlash cards. CF cards are ordered separately and are not included with the CPU.

Supported CF Cards (B&R part numbers)

All cards are extended temperature rated. Only B&R-approved CF cards should be used; consumer CF cards may fail in industrial conditions.

See cf-card-boot.md for CF card contents, boot sequence, and imaging procedures.

Battery

The battery buffers:

• Remanent variables
• User RAM
• System RAM
• Real-time clock

Battery replacement:

1. Discharge ESD at top-hat rail or ground (do not touch power supply)
2. Slide battery cover down and away
3. Push empty battery out of holder
4. Insert new battery “+” side up on right part of holder
5. Press battery into holder (use plastic tweezers, never metal)
6. Replace cover
7. Must complete within 1 minute if PLC is voltage-free

Warning: Only Renata CR2477N batteries are permitted. Other batteries may present fire or explosion hazard. See retentive-data.md for full procedures.

Interface Module Slot

The X20CP1584 has 1 slot for modular X20 interface modules. This allows adding:

• Additional fieldbus interfaces (Modbus TCP/RTU, PROFINET, EtherCAT, CANopen)
• Serial interfaces (RS485, additional RS232)
• Other communication modules

Compatible Interface Modules (selected)

Important: Some interface modules require a hardware upgrade when migrating from X20CPx48x to X20CPx58x CPUs. Check the minimum hardware revision column above. See firmware-version-mgmt.md Section 4.4 for the complete migration compatibility table.

Interface Module Upgrade Requirements (CPx48x to CPx58x)

When upgrading from X20CP1484 to X20CP1584 (or from CPx48x to CPx58x generation), these interface modules require specific firmware or hardware revisions:

Modules not listed are compatible as-is without any upgrade. Requires Automation Studio V3.0.90.20 minimum. See spare-parts.md Section 10 for the full migration checklist.

See if2772-canopen.md for CANopen details and modbus-gateway.md for Modbus configuration.

X2X Link and I/O Station Architecture

X2X Link Bus Interface (IF6)

The X2X Link is B&R’s proprietary deterministic I/O bus connecting the CPU to I/O stations. On the CP1584, the X2X interface uses a dedicated connector on the bottom of the housing.

X2X Link Connector Details

The X2X Link connectors on the X20 system use a proprietary push-pull connector with two ports per module (IN and OUT) for daisy chaining. The connectors are keyed to prevent incorrect insertion.

X2X cable pin assignments:

The X2X bus uses synchronous communication with a dedicated clock line. Each I/O module receives timing from the upstream module and re-transmits to the downstream module. This creates a deterministic timing chain where all modules in a station sample inputs and update outputs synchronously.

X2X Bus Timing and Configuration

Practical impact on machine performance: The X2X cycle time directly affects I/O response time. A 200 us X2X cycle means a minimum of 200 us between an input changing and the CPU seeing that change. For high-speed applications, reduce the X2X cycle time, but be aware that shorter cycles increase CPU interrupt load.

See x2x-protocol.md for wire-level frame format and io-sniffing.md for sniffing techniques.

X2X Bus Couplers and Base Modules

The CPU connects to X20 I/O stations via X2X Link through bus couplers:

Station Structure

A typical X20 I/O station consists of:

1. Bus coupler/base module (X20BC or X20BB series) - connects to CPU via X2X Link
2. Power supply module (X20PS series) - provides I/O power
3. I/O modules (X20DI, X20DO, X20AI, X20AO, X20AT, X20PT series) - signal processing

Each station is a daisy chain on the X2X Link bus. See network-architecture.md for topology details and x2x-protocol.md for bus protocol internals.

Three-Part Module Architecture

Every X20 I/O slot is actually three separate physical components stacked together:

  +-------------------+
  | Terminal Block     |  <- X20TB06 or X20TB12 (field wiring)
  | (removable)        |
  +-------------------+
  | Electronic Module  |  <- X20DI9371, X20AO4622, etc.
  | (hot-swappable)    |     The "smart" part with FPGA/MCU
  +-------------------+
  | Bus Module         |  <- X20BM01, X20BM31
  | (fixed to rail)    |     Backplane connector
  +-------------------+

Key practical points:

• Terminal blocks are universal within their pin-count class (all X20TB06 work with all 6-pin modules)
• Bus modules must match the voltage class (24V vs 240V)
• Electronic modules are independent of bus/terminal – any module plugs into any matching-width slot
• The controller identifies modules via the B&R ID code (0x hex) automatically
• Electronic modules are hot-swappable in most configurations

Maximum I/O Capacity

The X20CP1584 supports:

• Multiple X2X stations per controller
• Up to 253 X2X nodes per link segment
• Power budget: 7 W X2X Link output (derated to 5 W above 55 C)
• I/O power: separate supply via terminal block (10 A max)
• Total I/O points: limited by X2X cycle time and CPU memory, not a hard count

The practical limit depends on the number of I/O modules, their power consumption, and X2X Link timing. See io-card-hardware.md for module power specifications.

Interface Module Slot Details

The X20CP1584 has 1 slot for modular X20 interface modules. This slot is located on the right side of the CPU housing and accepts any single-width X20 interface module.

Slot mechanics:

• The interface module slides into a guide rail on the CPU housing
• A latch mechanism secures the module
• The module connects to the CPU’s internal PCI Express or local bus
• Hot-swap is NOT supported for interface modules – power cycle required

Electrical isolation: The interface module slot is galvanically isolated from the CPU core and from the X2X Link. This means faults on the fieldbus side of an interface module cannot propagate to the CPU logic.

X20CP158x Family Comparison

The X20CP358x series is identical but has 3 interface module slots instead of 1.

Firmware and Software Compatibility

Supported Software Versions

Automation Studio Version Requirements by Feature

Interface Module Compatibility by AR Version

Not all interface modules work with all AR versions on the CP1584. The table below shows minimum requirements for common modules:

Key point: If you add an interface module to a CP1584 running older firmware, and the module requires a newer minimum AR version, you may need to upgrade the AR before the module will be recognized. This is a chicken-and-egg problem if you only have one CPU and no spare — always upgrade AR first, then add new modules.

CP1584 Upgrade Paths to Newer Hardware

X20CP1684 specific note (from B&R Community): The X20CP1684 requires Automation Studio 4.7 minimum (or AS 6.0). It is NOT yet supported in AS 4.3. When upgrading from CP1584 to CP1684, the new CPU must appear in the Hardware Catalog under Tool_Box before you can configure it. See remanufacturing.md for the full migration workflow.

See firmware.md and firmware-version-mgmt.md for detailed firmware download and installation procedures.

Practical Inspection Checklist

When encountering an unknown X20CP1584 in the field:

1. Verify the model: Read the label on the side of the module. Order number should be X20CP1584 or X20cCP1584.
2. Check battery LED (DC): Red = battery depleted. Replace immediately before power loss.
3. Check CF card: Green LED = card present. No CF card = PLC will not boot to RUN.
4. Check mode switch: Should be in RUN position for normal operation.
5. Note hex switch settings: Record the station address values for network documentation.
6. Check interface module: Identify any module in the expansion slot (look up order code).
7. Note LED states: All status LEDs provide diagnostic information (see tables above).
8. Check X2X link: Verify daisy chain connections to I/O stations.
9. Check power wiring: Verify 24 VDC on both CPU/X2X and I/O supply terminals.
10. Record serial numbers: Found on the module label, useful for license tracking and spare parts.

Common Replacement Scenarios

Replacing a Failed CP1584

1. Record all settings (hex switches, mode switch, battery date)
2. Image the CF card before removal: dd if=/dev/sdX of=cp1584-backup.img bs=4M
3. Replace CPU on DIN rail
4. Insert CF card
5. Set hex switches and mode switch to match original
6. Apply power and verify boot sequence
7. See project-reconstruction.md if configuration is unknown

Upgrading from X20CP1484

The CP1584 is the direct upgrade path from the older X20CP1484 (Celeron-based). Migration requires:

• Automation Studio 3.0.90.20 or later
• Hardware upgrade for some interface modules (see compatibility table above)
• CF card with compatible AR version
• Project reconfiguration for the new CPU target

Key Findings

1. The X20CP1584 is headless - no integrated display, no panel functionality. It is purely a CPU controller.
2. The RS232 interface runs at 57600 bps factory default, not 115200 bps. Always try 57600 first.
3. Only 1 interface module slot (not 3 like the CP3584). Plan fieldbus needs accordingly.
4. The hex switches serve dual purpose: Ethernet INA2000 station number AND POWERLINK node number.
5. POWERLINK is half-duplex only on IF3. Ethernet mode on IF3 supports full-duplex.
6. Battery must be replaced within 1 minute of power loss to prevent SRAM data loss.
7. Integrated fuse is non-replaceable - if the fuse blows, the entire CPU must be replaced.
8. B&R ID code 0xC370 is useful for SNMP discovery and software identification.
9. The CP1584 supports both POWERLINK V1 (node 0x00 = MN) and V2 (node 0xF0 = MN) with different node ranges.
10. Operating temperature derating above 55 C reduces X2X Link power output from 7 W to 5 W.
11. Fanless design with overtemperature protection at 110 C (CPU) and 95 C (board) — the PLC enters reset state, not a graceful shutdown. Logbook error 9204 indicates temperature-triggered restart.
12. 256 MB DDR2 SDRAM is split between AR OS, task execution, and libraries. If memory usage approaches capacity, task cycle times will degrade. Monitor via system-variables.md and hardware-monitoring.md.
13. Shortest achievable task class cycle time is 400 µs (CP1584 with Atom E640T at 0.6 GHz). For comparison: CP1583 = 800 µs, CP1585 = 200 µs, CP1586 = 100 µs. This determines the minimum POWERLINK cycle time the CP1584 can sustain as MN. Typical instruction cycle time is 0.0075 µs per the official datasheet. The integrated I/O processor handles I/O data point processing in the background, offloading this from the main CPU.
14. Overtemperature shutdown thresholds are 110°C (processor) and 95°C (board) — the CPU enters reset state (not graceful). Logbook errors 9204 (temperature restart) and 9210 (halt/service after watchdog) indicate thermal events. No fan is present — rely on cabinet ventilation and ambient temperature control. See hardware-monitoring.md for temperature monitoring procedures.

Practical Hardware Diagnostic Commands

Via FTP (if enabled)

# Connect to the CP1584 FTP server
ftp 192.168.10.1
# Username: (varies, may be anonymous or empty)
# Password: (varies, may be empty or set by OEM)

# Useful directories:
# /System/     - AR system files, firmware, logs
# /Card/       - CF card contents (user application)
# /Temp/       - Temporary files
# /Log/        - Logbook and diagnostic files

# Download the AR logbook for error analysis
get /System/Log/Logbook.txt

Via SNMP (if enabled)

# Query the CP1584 via SNMP for hardware health
snmpwalk -v2c -c public 192.168.10.1 1.3.6.1.2.1.1

# B&R enterprise OID for hardware-specific data
snmpwalk -v2c -c public 192.168.10.1 1.3.6.1.4.1.28639

# Check interface status (IF2 Ethernet)
snmpget -v2c -c public 192.168.10.1 ifDescr.2 ifOperStatus.2

Via OPC-UA (if configured)

# Connect to OPC-UA server on the CP1584 to read system variables
# See [opcua.md](opcua.md) and [system-variables.md](system-variables.md)
# for the full variable list and connection details

Via Serial Console (Bootloader)

# Serial console settings for bootloader mode:
# Baud: 57600 (factory default)
# Data: 8 bits
# Parity: None
# Stop: 1 bit
# Flow: None

# Connect with minicom or picocom:
picocom -b 57600 /dev/ttyUSB0

# After connecting, press Enter to get the bootloader prompt
# Available commands depend on AR version:
#   help          - list available commands
#   dir           - list files
#   mem           - memory dump
#   info          - hardware info
# See [bootloader-recovery.md](bootloader-recovery.md) for full procedure

Physical Inspection Quick-Reference Card

When walking up to an unknown CP1584 in a cabinet:

[ ] Label side: read order number (X20CP1584 or X20cCP1584)
[ ] Coated variant? X20cCP1584 = conformal coating for harsh environments
[ ] Read serial number from label (for spare parts and license tracking)
[ ] Read B&R ID code (0xC370) if visible
[ ] Check DC LED: green = power OK, red = battery depleted
[ ] Check CF LED: green = card present, yellow = card access
[ ] Check R/E LED: green solid = running, red = BOOT/SERVICE
[ ] Check ETH LED: green = Ethernet link active
[ ] Check PLK LED: green = POWERLINK link active
[ ] Check mode switch: should be RUN for normal operation
[ ] Record hex switch positions (station address for network documentation)
[ ] Identify interface module in expansion slot (read its order code)
[ ] Count X2X stations connected (daisy chain physical trace)
[ ] Verify 24 VDC on both CPU/X2X (pin 11-12) and I/O (pin 7-8) power terminals
[ ] Check battery compartment: is battery present? date code?
[ ] Check for corrosion or physical damage on terminals

References

• B&R X20CP1584 Product Page: https://www.br-automation.com/en-us/products/plc-systems/x20-system/x20-plc/x20cp1584/
• X20CP158x Data Sheet V1.56: https://www.multiwaycontrol.com/multiway/X20CPx58x-en_V1.56.pdf
• X20(c)CP158x and X20(c)CP358x Technical Manual: https://www.all4sps.com/mediafiles/Sonstiges/X20CP1586.pdf
• X20TB12 Terminal Block Data Sheet: https://www.nexinstrument.com/assets/images/pdf/X20TB06__X20TB12-ENG_V266.pdf
• X20 System User’s Manual: https://www.br-automation.com/en-us/downloads/control-and-io-systems/x20-system/x20-system-users-manual/
• B&R Community Forum: https://community.br-automation.com/
• B&R X20CP1684 Product Page: https://www.br-automation.com/en-us/products/plc-systems/x20-system/x20-plc/x20cp1684/

Successor: X20CP1684

B&R has released the X20CP1684 as the direct in-family successor to the CP1584. This is a drop-in compatible replacement with significant hardware improvements:

Key migration notes for CP1584 to CP1684:

1. All X20 IO modules, bus modules, and terminal blocks are fully compatible. The X2X bus, POWERLINK, and interface module slot are identical. No IO hardware changes needed.

2. No more CompactFlash. The CP1684 uses 1 GB internal flash instead of removable CF cards. This eliminates CF card failures (the most common failure mode on CP1584) but means backup must be done via FTP, Automation Studio transfer, or mapp Backup. See ftp-web-interface.md for FTP backup procedures.

3. Minimum AS version is 4.7. B&R recommends Automation Studio 6.0+ for the CP1684. If you have an AS4 project, you may need to open it in AS4.7 first, verify it compiles, then optionally migrate to AS6 for CRA compliance. See remanufacturing.md for the full AS4→AS6 migration guide.

4. AR 5.x/6.x runtime. The CP1684 runs AR 5.x or later. Some AS4-era libraries may need updates for AR 5+ compatibility. Use the community as6-migration-tools to check your project.

5. Hardware tree update only. In Automation Studio, the migration is straightforward: replace the CPU module in the hardware tree from X20CP1584 to X20CP1684, re-address if needed (usually automatic), recompile, and download. The IO mapping remains unchanged.

6. Production deployment: See firmware-version-mgmt.md for the production deployment checklist when changing CPU hardware. Estimated downtime: 4-8 hours for a direct CPU swap with the same IO configuration.

Order code: X20CP1684 (standard), X20cCP1684 (conformal-coated variant for harsh environments).

Beyond CP1684: X20EM ARM Edge Controllers

B&R has introduced the X20EM series as the next-generation X20 controller platform. These use ARM-based processors instead of Intel Atom, and represent B&R’s long-term direction for the X20 ecosystem. The X20EM is relevant for CP1584 maintainers planning long-term migration.

What we know about X20EM:

Migration implications for CP1584 maintainers:

1. X20EM requires AS 6.x exclusively — if you migrate to X20EM, you MUST also migrate the project to AS 6. There is no AS 4.x support for ARM targets.

2. X20 IO modules are compatible — the X2X bus is unchanged, so all your existing IO modules, bus modules, terminal blocks, and interface modules work with X20EM.

3. Compiled code is architecture-specific — .BR files compiled for Intel x86 will NOT run on ARM. You must recompile the entire project from source. If you only have compiled code (no project file), X20EM migration requires full project reconstruction first (see project-reconstruction.md).

4. Multicore is a significant advantage — AR 6.5 on X20EM allows assigning cyclic task classes to specific CPU cores, eliminating cycle time contention between motion control and logic processing.

5. Not a direct drop-in replacement — unlike CP1684, the X20EM has a different CPU architecture and requires a complete software rebuild. Plan for full bench testing before production deployment.

6. When to consider X20EM over CP1684: When the machine has complex multi-axis motion that hits cycle time limits, when you need OPC UA over TSN, or when CRA compliance requires AR 6.x with multicore isolation for security domains.

Status: X20EM specifications are evolving. Check B&R’s product page at https://www.br-automation.com/en-us/products/plc-systems/x20-system/ for the latest models and specifications. The X20 system user’s manual (January 2025 revision) covers System Generation 4 controllers including ARM-based options.

New Apollo Lake I Generation (2025)

B&R has expanded the X20 PLC family with new controllers based on Intel Apollo Lake I processors. These controllers add OPC UA over TSN support and can function as field-level masters in TSN networks — a capability the CP1584 cannot provide.

Why this matters for CP1584 maintainers: If you are planning a migration to meet CRA 2027 compliance (see cybersecurity-hardening.md §9.3), these new controllers provide a modern, patchable AR 6.x platform with TSN capabilities — while maintaining X20 IO bus compatibility.

Source: B&R “Expanded X20 PLC generation” — https://www.br-automation.com/en/products/plc-systems/innovations/

Related Documents

• ar-rtos.md — Automation Runtime (VxWorks-based) that runs on this CPU
• memory-map.md — CPU memory layout including SRAM, DDR2, and IO mapping
• firmware.md — AR firmware architecture and boot process
• firmware-version-mgmt.md — Firmware versions, downgrade paths, compatibility
• cf-card-boot.md — CF card contents and boot sequence details
• retentive-data.md — Battery-backed SRAM management and data retention
• x2x-protocol.md — X2X Link wire-level protocol details
• powerlink-internals.md — POWERLINK protocol on IF3
• if2772-canopen.md — CANopen via X20IF2772 interface module
• modbus-gateway.md — Modbus TCP/RTU via X20IF1082 interface module
• io-card-hardware.md — X20 I/O module signal processing and diagnostics
• network-architecture.md — Network topology and device enumeration
• spare-parts.md — Replacement hardware identification and ordering
• bootloader-recovery.md — Serial console bootloader and firmware recovery
• access-recovery.md — Password recovery and admin access restoration
• system-variables.md — AR system variables for runtime monitoring
• hardware-monitoring.md — Temperature, voltage, and hardware health monitoring
• grounding-emc.md — Grounding and EMC considerations for installation
• ftp-web-interface.md — Remote file access via FTP and web server
• diagnostic-workstation.md — Building a diagnostic workstation for CP1584 systems
• remanufacturing.md — Repair vs. replace evaluation and migration paths
• license-mgmt.md — License management tied to this hardware’s B&R ID code