B&R ACOPOS Drive Communication and Diagnostics (CP1584)

Overview

ACOPOS servo drives are B&R’s primary motion control platform for precision servo applications. On a CP1584-based machine, the PLC communicates with ACOPOS drives primarily over ETHERNET Powerlink (EPL) or CAN bus, using B&R’s proprietary ACP10/ACPOSmotion firmware. When you inherit a machine with no documentation, understanding how to monitor, diagnose, back up, and replace these drives is essential.

This document covers the ACOPOS drive family (8V1 single-axis, 8BVE ACOPOSmulti, and 8I7 ACOPOSinverter), communication architecture, fault diagnosis, parameter management, and replacement procedures — all from the perspective of a sole maintainer with zero OEM support.

ACOPOS Drive Family Overview

ACOPOS P3 Details (Newer Generation)

The ACOPOS P3 is B&R’s latest servo drive platform. If you’re maintaining a newer CP1684 or CP3686 system (or upgrading from a CP1584), you may encounter P3 drives:

• Form factors: 1-axis, 2-axis, and 3-axis in a single compact housing
• Power range: 0.6 kW to 64 kW per axis (up to 48A continuous)
• Communication: POWERLINK (primary), EtherCAT (optional)
• Key advantage: Up to 3 axes in one housing saves cabinet space significantly
• Firmware: Uses acp10sys same as 8V1 — configuration methodology is identical
• Safety: Integrated SafeMOTION (STO, SLS, SDI, SLP, SS1, SS2)
• Not backward compatible with 8V1 hardware — different form factor, different power connector
• Migration path: If upgrading from 8V1 to P3, motor and encoder cables may need adapters; acp10sys must be regenerated for P3 hardware targets

Note for CP1584 maintainers: The CP1584 can communicate with ACOPOS P3 drives via POWERLINK, but the combined cycle time budget may be tighter. The P3’s higher bandwidth demands more from the MN. Monitor cycle time carefully when mixing 8V1 and P3 drives on the same POWERLINK segment.

ACOPOSmulti (8BVE) Details

ACOPOSmulti uses a shared DC bus architecture for multi-axis systems:

• Common DC bus: Multiple axes share a single DC bus, allowing regenerative energy from one axis (decelerating) to feed another (accelerating)
• Module format: Power supply module + axis modules in a rack
• Communication: POWERLINK or CAN, same acp10sys approach
• Diagnostic note: A fault on one axis module does NOT necessarily indicate a problem with that specific axis — a DC bus overvoltage (7200) or undervoltage (7211) affects ALL axes on the shared bus
• Spare parts: Axis modules can be individually replaced without replacing the power supply module, but firmware versions must match across all modules in the rack

Performance Characteristics

• Communication cycle time: as low as 400 µs over POWERLINK
• Control loop update: as fast as 50 µs (8V1), faster on P3
• Peak current: typically 3x continuous for 2 seconds
• Auto-recognition of B&R motor parameters via embedded chip (HIPERFACE DSL encoders)
• Non-B&R motors: Manual parameter entry required — backup parameters from existing drive before replacement

Communication Architecture

How the CP1584 Talks to ACOPOS Drives

The CP1584 communicates with ACOPOS drives through one of these protocols:

1. ETHERNET Powerlink (EPL) — Most common on X20 systems. The CP1584 acts as the POWERLINK Managing Node (MN), and each ACOPOS drive is a Controlled Node (CN). Configuration happens through the acp10sys system file.

2. CAN bus — Used on older B&R systems (PP100, PP015 Power Panels). Requires a CAN interface module (8AC110.60-2) and node addressing.

3. EtherCAT (CoE) — Available on newer 8V1 drives as an alternative protocol.

The acp10sys Configuration File

This is the most critical file for ACOPOS drive operation. The acp10sys file contains:

• Drive-specific parameters (axis configuration, encoder settings, current limits)
• CAN/POWERLINK network node assignments
• Motor and encoder interface configurations
• Safety and limit parameters
• All drive parameters as a monolithic configuration blob

The CP1584 automatically downloads acp10sys to all connected ACOPOS drives on startup. Without a valid acp10sys, drives will not operate.

Critical gotcha: When replacing a drive, the new drive has factory defaults and NO configuration. It needs acp10sys downloaded from the controller before it will function. If the controller doesn’t have the correct acp10sys, you have a chicken-and-egg problem.

See powerlink-internals.md for EPL protocol details and cf-card-boot.md for how acp10sys fits into the boot sequence.

Hardware Interface: X2 Connector

The X2 connector on ACOPOS drives provides:

LED Status Diagnostics

ACOPOS drives have multi-color LEDs for quick visual diagnosis:

ACOPOS Error Code Reference

B&R ACOPOS drives generate numeric error/fault codes that identify the root cause of a failure. These codes are displayed on the drive’s front panel, logged by the PLC, and accessible via SDM.

Comprehensive error code reference: brtschi.ch/automation — This reference documents over 60 error codes (1 through 6047) with descriptions of the drive’s reaction, cause, and correction for each. It is one of the most complete publicly-available ACOPOS error code resources.

Common error code categories:

Community resources for ACOPOS troubleshooting:

• Wake Industrial: Common ACOPOS Error Scenarios
• B&R Community: ACOPOS 1090 servo drive issue
• B&R Community: PLCopen error 6021 and 29203

LED States

No LEDs Lit

If no LEDs are lit at all, the drive is not receiving 24V DC control power. Check:

• 24V DC supply to the X2 connector
• DC breaker or fuse for the 24V control circuit
• Wiring continuity from the 24V power supply

Complete ACOPOS Fault Code Reference

ACOPOS fault codes are numeric identifiers organized by category. Below is the comprehensive reference extracted from B&R error text modules. This is the complete list — when diagnosing a drive fault, look up the code here first.

Diagnostic/Status Codes (Low-Level)

These are returned during parameter access, data block operations, and firmware download:

1000-Series: Communication and Parameter Errors

4000-Series: Position Controller Errors

5000-Series: Motion, Homing, and Cam Errors

6000-Series: Power Stage, Controller Enable, and Hardware Errors

7000-Series: Encoder and Feedback Errors

7200-Series: DC Bus and Power Supply Errors

9000-Series: Temperature and Overload Errors

32000-Series: NC Manager and Network Configuration Errors

These are critical for diagnosing POWERLINK/CAN communication between the CP1584 and ACOPOS drives:

35000-Series: SMC Fail Safe (Safety) Errors

Quick Diagnostic Flowchart

When an ACOPOS drive faults on a CP1584 system:

Drive Fault?
├── Green blink (can't enable)?
│   ├── Check X2.6 enable signal (24V present?)
│   ├── Check three-phase power at power terminals
│   └── Check drive 24V DC supply
├── Red steady (active fault)?
│   ├── Note the fault code (SDM, AS online, or OPC-UA)
│   ├── Error 1012/1013? → Network communication lost
│   │   ├── Check POWERLINK cable
│   │   ├── Check drive node number
│   │   └── Check MN (CP1584) POWERLINK status
│   ├── Error 4007? → Following error / lag error
│   │   ├── Check encoder cable (codes 7029, 7032, 7039?)
│   │   ├── Check mechanical load (binding?)
│   │   ├── Check acceleration/torque settings
│   │   └── Check encoder alignment
│   ├── Error 7200/7225? → DC bus overvoltage
│   │   ├── Check braking resistor (open circuit?)
│   │   ├── Check deceleration rate
│   │   └── Check mains voltage
│   ├── Error 6021? → Enable signal unstable
│   │   ├── Check X2.6 wiring
│   │   ├── Check for ground loop
│   │   └── Add debouncing if noisy
│   ├── Error 70xx? → Encoder fault
│   │   ├── Replace encoder cable (most common fix)
│   │   ├── Check encoder power supply
│   │   ├── Check connector seating
│   │   └── See [encoder-diagnostics.md](encoder-diagnostics.md)
│   ├── Error 9000/9030? → Temperature
│   │   ├── Check cooling fan
│   │   ├── Check ambient temperature
│   │   ├── Reduce duty cycle
│   │   └── Check drive mounting/ventilation
│   └── Error 32013/32014? → Firmware mismatch
│       ├── Check drive firmware version
│       ├── Check acp10sys version
│       └── See [firmware-version-mgmt.md](firmware-version-mgmt.md)
├── Red blink (warning)?
│   ├── Check parameters in SDM
│   ├── May indicate approaching thermal or current limits
│   └── Review drive configuration
└── No LEDs?
    ├── Check 24V DC control power
    ├── Check DC breaker/fuse
    └── Check wiring from power supply

Common Error Scenarios

1. “ERROR IN PALA DRIVE” on the HMI — acp10sys is missing or corrupted, firmware version mismatch, or hardware failure. Error code 32013 (no OS) or 32014 (version mismatch).
2. Drive enables then immediately faults — Motor phasing wrong (6044), encoder disconnected (7032, 7053), or power supply issue (7215, 7221).
3. Drive won’t enable (green blink) — Enable signal (X2.6) not present (6021) or three-phase power missing (7215).
4. 24V breaker trips when enable applied — Enable input short circuit, internal drive fault, ground loop (6054, 7222).
5. Drive works intermittently, faults under load — Lag error (4007) from encoder cable degradation (7039, 7040), or thermal overload (9000, 9050).
6. All drives fault simultaneously — POWERLINK MN failure on CP1584 (1012), or DC bus issue (7200).
7. Drive faults only after warm-up — Thermal fault (9000, 9030) — check cooling, or encoder cable expanding with heat (7039).
8. PLCopen error 6021 (“Enable unstable”) — The enable signal at X2.6 is fluctuating. Common causes: marginal 24V supply at the enable input, ground loop causing voltage sag, loose terminal connection, or wiring running parallel to motor power cables picking up noise. Measure the enable voltage with a scope while the fault is active — it must be stable above the threshold (typically >18V). See grounding-emc.md for noise mitigation.
9. PLCopen error 29203 (“Drive not enabled”) — The PLC program is commanding motion (MC_MoveAbsolute, MC_MoveVelocity, etc.) but the drive’s enable chain is not complete. Check: (a) MC_Power function block has Enable=TRUE and Status=TRUE, (b) no active fault on the drive, (c) safety chain allows enable, (d) STO is released. This error means the software is trying to move before the hardware is ready.
10. Error 32280 (“Timeout during drive initialization”) — The ACOPOS drive is taking too long to boot on the POWERLINK network. This can be caused by excessive network traffic during startup, a damaged POWERLINK cable, or a drive with corrupted firmware. If it happens intermittently, check cable quality and POWERLINK cycle timing.

Monitoring Drive Status Without the Original Project

Method 1: SDM (System Diagnostics Manager)

Open a web browser and navigate to the CP1584’s IP address. The SDM web interface shows:

• Drive status (online/offline/fault)
• POWERLINK node status for each drive
• DC link voltage
• Motor current (per phase)
• Drive temperature
• Encoder feedback status
• Fault history

Method 2: Automation Studio Online Monitoring

Even without the project source, you can connect Automation Studio to the running PLC:

1. Create a minimal project with just the CP1584 CPU
2. Set the correct IP address
3. Go to Online → Login
4. Browse available variables in the Watch window
5. Look for motion-related variables (axis status, position, velocity, torque)

Method 3: OPC-UA Browsing

If OPC-UA is configured on the CP1584, use any OPC-UA client (UaExpert, Prosys) to browse the address space. Drive data typically appears under motion-related namespaces.

See opcua.md for setup details and cp1584-forensics.md for extracting information from an unknown PLC.

Method 4: PVI API

Use the B&R PVI library from a PC to programmatically access drive variables:

## Using PVI.py
from pvi import *

pvi = PviConnection()
line = pvi.add_line('LN1', 'TCP')
cpu = line.add_device('CP1584', 'TCP', '192.168.1.10')

## Browse available variables
vars = cpu.list_variables()

## Read axis position
pos = cpu.read_variable('gAxis1.Position')

See pvi-api.md for the complete PVI programming reference.

Parameter Backup and Restore

Backup Parameters Before Anything Else

If you do nothing else from this document, BACK UP YOUR DRIVE PARAMETERS NOW.

Method A: Export via Automation Studio

1. Connect to the PLC with the project that contains the drive configuration
2. Navigate to Hardware Configuration → Drive Parameters
3. Select all parameters → File → Export → XML
4. Save the XML file with the drive model number, serial number, date, and machine identifier

Method B: Export Individual Drive Parameters

1. In Automation Studio, expand Physical View → ACOPOS → Parameters
2. Right-click → Export Parameters
3. This creates a .par or .xml file specific to each drive

Method C: Backup the acp10sys File

The acp10sys file IS your complete drive system configuration. It’s stored in the Automation Studio project under:

Physical View → ACOPOS → System Files → acp10sys

Also found on the CF card as part of the deployed project. Make a copy of the entire CF card image (see cf-card-boot.md).

Method D: Backup via SDM

Some drive parameters can be exported through the SDM web interface under the drive diagnostics section.

What Parameters Are Critical to Back Up

Drive Replacement Procedure

Complete Step-by-Step Replacement

WARNING: Always de-energize and wait 5+ minutes for DC link capacitors to discharge before servicing servo drives. Measure DC link voltage to confirm < 50V.

Step 1: Backup Everything

1. Export all drive parameters to XML (see above)
2. Image the CF card from the CP1584
3. Photograph all wiring connections
4. Document the drive model number, firmware version, and slot configuration
5. Record the CAN/POWERLINK node address

Step 2: Remove the Failed Drive

1. Remove AC mains power
2. Wait 5 minutes, verify DC link < 50V
3. Disconnect: motor power, encoder cable, communication bus, X2 control signals, 24V supply
4. Label ALL cables with their source/destination
5. If the drive has a CF card or option modules in slots, remove them carefully and note slot positions

Step 3: Install the Replacement Drive

1. Verify the replacement drive is the exact same model (8V1016.00-2, etc.)
2. Install any option modules (encoder interface, communication) in the same slots as the original
3. Mount the drive and reconnect all cables per your labels
4. Do not apply power yet

Step 4: Restore Configuration

Option A — You have the Automation Studio project with acp10sys:

1. Power on the CP1584 and all drives
2. Download the project (including acp10sys) from Automation Studio
3. The acp10sys automatically provisions all drives
4. Verify: no error LEDs on the ACOPOS, SDM shows all nodes online

Option B — You don’t have the project (worst case):

1. If you have an XML parameter backup, you can load it via Automation Studio to a minimal project
2. If you only have the CF card image, you may be able to reconstruct a project from the configuration files (see project-reconstruction.md)
3. As a last resort, you can download acp10sys directly to the drive using a CAN interface (PCAN-USB or 8AC110.60-2), but the drive must be in bootloader mode (cycle power while holding MODE button)

Step 5: Verify and Re-zero

1. Check all drive LEDs — green steady is the target
2. Verify DC link voltage in SDM (should be ~1.35 × line voltage for 3-phase)
3. Verify motor nameplate data matches drive configuration
4. If using an absolute encoder (EnDat 2.2), position is retained — no re-zeroing needed
5. If using an incremental encoder, run the homing routine (MC_Home) to re-establish zero
6. Test axis movement in manual/jog mode at low speed
7. Verify emergency stop (STO) functions correctly

Re-zeroing Methods

Verification Checklist

Motor Parameter Recognition

B&R motors have an embedded parameter chip (EEPROM/HIPERFACE DSL memory) that contains:

• Motor type and model number
• Rated current and voltage
• Pole pairs
• Thermal time constants
• Inertia and friction data
• Encoder type and resolution
• Commutation offset (for EnDat 2.2 encoders) — stored in the encoder’s non-volatile memory

When an ACOPOS drive is connected to a B&R motor and powered on, the drive reads this chip and automatically configures the motor parameters. This auto-recognition feature means:

1. If you’re replacing a motor with an identical B&R motor, the drive will auto-configure
2. If you’re using a non-B&R motor, you MUST enter parameters manually (including commutation offset)
3. If the motor’s parameter chip is corrupted, the drive won’t recognize the motor
4. Commutation offset is critical for torque control — it defines the electrical angle relationship between the encoder zero position and the motor’s magnetic poles. For B&R EnDat 2.2 motors, this offset is stored in the encoder memory and is read automatically. For non-B&R motors or when using incremental/resolver encoders, the commutation offset must be determined via a phasing routine.

Commutation Offset for Non-B&R Motors

When using motors without embedded commutation data (e.g., third-party motors with incremental encoders), the ACOPOS drive must perform a phasing routine to determine the commutation offset:

1. Via Automation Studio: Motion → Axis → Parameters → Motor → Commutation Offset — set to 0 for resolver-based motors (commutation offset is always 0 for resolvers because resolver zero aligns with the magnetic pole)
2. Via acp10sys parameter: The commutation offset is stored as a signed integer in the motor parameter block
3. Phasing procedure: The drive energizes the motor windings in a known pattern, measures the rotor position from the encoder, and calculates the offset. This is done automatically by the ACOPOS during initial commissioning when “Auto Phasing” is enabled

Important: Per B&R training module TM460, phasing is NOT necessary when using B&R motors because the commutation offset is either 0 (resolver) or stored in the EnDat encoder memory. This is a significant advantage of B&R motors — if you need to replace a motor and can source a B&R equivalent, you avoid the entire commutation alignment process.

HIPERFACE DSL (HDSL) Single-Cable Technology

B&R motors with HIPERFACE DSL encoders use a single cable for both motor power and encoder communication:

• Encoder data is transmitted digitally over the same two cores that carry motor power
• Eliminates the separate encoder cable — reduces wiring complexity and failure points
• Fully digital signal transmission, immune to analog interference
• Supports safety data transmission (HDSL Safety) with a firmware update on the drive
• Cable length up to 100m supported

Diagnostic note: If an HDSL motor shows encoder errors (70xx codes), the single-cable design means the fault could be in either the power cable or the encoder itself. Test with a known-good cable to isolate. See encoder-diagnostics.md for full procedures.

Manual Motor Parameter Entry

In Automation Studio, navigate to:

Hardware Configuration → ACOPOS → Parameters → Motor

Enter: rated current, rated voltage, pole pairs, encoder resolution, inertia. The drive will use these for current control and commutation.

Drive Firmware Management

Checking Firmware Version

1. Via SDM: Browse to the drive in the SDM web interface — firmware version displayed
2. Via Automation Studio: Online → System Diagnostics → ACOPOS firmware version
3. Via drive LEDs: bootloader mode shows version during startup (red/green alternating)

Updating Firmware

Firmware updates are distributed as part of the Automation Studio installation or from B&R’s download portal. The update process:

1. Download the new firmware files to the CF card or via Automation Studio
2. Power cycle the drive while holding the MODE button (enters bootloader)
3. Automation Studio detects the drive in bootloader mode
4. Online → Download → Firmware Update
5. Wait for completion (red/green alternating LEDs)
6. Do not power off during update — this can brick the drive

Version Compatibility

Mismatched versions are a common cause of “drive won’t work after replacement.” Always match the Automation Studio version to the original project version.

Encoder Diagnostics

Supported Encoder Types

Diagnosing Encoder Problems

1. Encoder loss fault — Check encoder cable continuity, connector seating, and cable routing (keep away from motor power cables)
2. Position jumping — Signal interference (EMC issue) or failing encoder — see grounding-emc.md
3. Wrong direction — Encoder A/B channels swapped or commutation offset incorrect
4. Following error exceeds limit — Encoder resolution mismatch, mechanical binding, or tuning issue

See encoder-diagnostics.md for detailed encoder troubleshooting procedures.

Common ACOPOS Problems and Solutions

Problem: Drive Won’t Enable

Symptoms: Green blinking LED, Ready output (X2.5) not active

Diagnosis sequence:

1. Verify 24V DC at X2.1/X2.6 (enable input)
2. Verify three-phase power is present at the drive input
3. Check that acp10sys is loaded and valid
4. Check the PLC program is asserting the enable (MC_Power function block)
5. Check safety chain — STO may be preventing enable
6. Verify no active faults on the drive (check SDM)

Problem: Drive Faults Immediately After Enable

Symptoms: Green briefly, then red steady with fault code

Diagnosis sequence:

1. Note the fault code — look it up in the ACOPOS manual or error code list
2. Check motor cable connections (U, V, W phases) for correct order
3. Verify encoder cable is connected and seated
4. Check that motor parameters match the actual motor
5. Measure motor insulation resistance (megger test)
6. If fault code indicates DC link issue, check braking resistor

Problem: Following Error / Position Deviation

Symptoms: Drive moves but position error grows, or motor oscillates

Diagnosis sequence:

1. Reduce velocity and acceleration to see if it stabilizes
2. Check mechanical system for binding or excessive friction
3. Verify load inertia settings match actual load
4. Check encoder signal quality (scope the encoder signals if possible)
5. Verify controller gains haven’t been accidentally changed
6. Check for EMC interference on encoder cables

Problem: DC Link Overvoltage

Symptoms: Fault on deceleration or during rapid speed changes

Diagnosis sequence:

1. Check braking resistor — measure resistance (should not be open circuit)
2. Verify braking resistor is connected to the correct terminals
3. Check that regenerative energy isn’t exceeding drive capacity
4. Reduce deceleration rate or add external braking resistor

Problem: Phase Current Imbalance

Symptoms: Motor runs rough, excess heat, vibration

Diagnosis sequence:

1. Measure motor current per phase in SDM or with clamp meter
2. If imbalance > 5%, suspect:
   • Motor winding fault (megger test)
   • IGBT failure in drive (need drive repair)
   • Loose connection in motor cable
3. Run motor disconnected from mechanical load to isolate drive vs mechanical issue

Safety Features

Safe Torque Off (STO)

Most ACOPOS drives support STO (STO per IEC 61800-5-2). When STO is activated:

• Drive power stage is disabled immediately
• Motor coasts to stop (no regenerative braking from drive)
• This is NOT the same as an emergency stop — the drive does not actively brake

SafeMOTION (B&R Extended Safety)

Newer ACOPOS drives and the CP1584 with SafeLOGIC support:

• Safe Limited Speed (SLS)
• Safe Direction (SDI)
• Safe Stop (SS1, SS2)
• Safe Position (SLP)

See safe-io-diagnostics.md for safety system diagnostics.

Finding Spare Parts and Replacement Drives

Identifying the Drive

B&R part numbers follow the pattern: 8V1016.00-2

• 8V = ACOPOS single-axis series
• 1016 = Current rating (10A continuous, 16A model)
• .00-2 = Version/revision

Sourcing Replacements

When the OEM is gone:

1. B&R direct — Requires active service contract or B&R portal account
2. Third-party refurbishers — Companies like Wake Industrial, Roc Industrial, and various servo repair shops stock and repair ACOPOS drives
3. Used/surplus market — eBay, industrial surplus dealers — verify firmware compatibility
4. Cross-reference — No direct cross-reference exists to other brands; ACOPOS is proprietary

Firmware Matching Is Critical

A replacement drive from stock may have different firmware than your system. You MUST:

1. Check the replacement drive’s firmware version (SDM or bootloader mode)
2. If it doesn’t match your system, update firmware BEFORE installing
3. Or use an Automation Studio version that supports the drive’s firmware

ACOPOS D1 — Next-Generation Servo Drive (2026)

B&R announced the ACOPOS D1 servo drive at Innovation Days 2026 (Pune, India, March 2026). This is a new generation of servo drives positioned alongside (not replacing) the ACOPOS P3. As of mid-2026, detailed technical specifications have not been publicly released beyond marketing announcements. Key information known:

What We Know

What This Means for CP1584 Machine Maintainers

1. ACOPOS D1 does NOT replace your existing 8V1/P3 drives — it is a new product line. Existing 8V1 drives remain supported and available.
2. If sourcing replacement 8V1 drives becomes difficult (long-term), the D1 may become an alternative. However, migration from 8V1 to D1 will require:
   • New drive hardware with different form factor
   • Updated acp10sys (or equivalent configuration methodology)
   • Possible motor/encoder cable changes
   • Automation Studio version that supports D1 (likely AS 6.x+)
3. Edge intelligence is a key differentiator — the D1’s built-in “predictive uptime” capabilities suggest integrated condition monitoring that could reduce unplanned downtime. If this proves valuable, retrofitting may justify the migration cost.
4. Monitor the B&R product catalog for D1 specifications. When detailed technical data (power range, communication protocols, safety certifications, form factor dimensions) becomes available, this section will be updated.

Status: This section will be updated as B&R releases technical specifications for the ACOPOS D1. Check B&R’s product page at br-automation.com/en-us/products/motion-control/acopos/ and the B&R Community forum for announcements.

Sources: B&R Innovation Days 2026 Pune (press coverage), LinkedIn posts from Florian Schneeberger (B&R/ABB), Industrial Automation Magazine India.

Key Findings

1. The acp10sys file is everything — Without it, ACOPOS drives are paperweights. Back it up religiously. It’s part of the Automation Studio project and also on the CF card.

2. LEDs tell you 90% of the story — Green steady = good. Green blink = no enable. Red steady = fault (look up the code). Red blink = warning. Off = no power.

3. Drive replacement is plug-and-play ONLY if you have the configuration — Move CF card, move option modules to same slots, reload acp10sys. Without configuration, you’re doing reverse engineering.

4. Version matching is the #1 cause of replacement failure — The new drive’s firmware must match the acp10sys version from the original project. Mismatched versions cause communication failures.

5. Motor auto-recognition only works with B&R motors — If you’re using third-party motors, you must have the manual parameter values. Back them up.

6. Encoder problems are the most common intermittent fault — Signal degradation, cable damage, and EMC interference cause position errors that manifest as drive faults. See encoder-diagnostics.md and grounding-emc.md.

7. SDM is your best friend without the project — The System Diagnostics Manager web interface shows drive status, fault history, and live data without needing Automation Studio or any project files.

Cross-References

• powerlink-internals.md — EPL communication protocol between CP1584 and drives
• cf-card-boot.md — How acp10sys is loaded during boot
• encoder-diagnostics.md — Encoder troubleshooting for motion systems
• pvi-api.md — Programmatic drive access from a PC
• opcua.md — OPC-UA access to drive data
• safe-io-diagnostics.md — Safety system (STO, SafeMOTION) diagnostics
• grounding-emc.md — EMC troubleshooting for encoder/drive signal quality
• project-reconstruction.md — Rebuilding a project when the original is lost
• cp1584-forensics.md — Extracting information from an unknown CP1584
• custom-diagnostic-tools.md — Building diagnostic programs that run on the PLC