Bendix ACom Diagnostic Software: Install, Connect, and Start Testing (Step-by-Step)

Looking up how to get Bendix® ACom® Diagnostic Software working and talking to your ABS, stability, or Wingman systems? Here’s a walkthrough of how to do it.

Step-By-Step Install Guide: Download Here
Software Download Link: Download Here

What ACom Is (and Isn’t)

What the ACom Software Can Do:

  • Provide a view of ECU/system status with current user settings, safety parameters, and active/inactive configurations.
  • Provide a view of any active Diagnostic Trouble Codes (DTCs).
  • Clear the DTCs if the problem is resolved.
  • Provide access to user-programmable settings.
  • Provide access to configure certain system and safety settings.
  • Record and print diagnostic reports and event records.
  • Log background safety and user data including past DTCs, system alerts, and major events.
  • Calibrate certain systems, such as radar and camera devices.
  • Provide, as applicable, diagnostics of onboard sensors.
  • Support changing of the sensor configuration.
  • Support software-based addition or removal of sensors.
  • Allow activation or deactivation of alerts.
  • Support changing of in-cab display configurations, such as units and menu items.
  • Provide sound output control for certain ECUs/devices/systems.
  • Support self-diagnostics and simulated performance tests.
  • Simulate alerts, blink codes, sounds, etc., to verify system functions and auxiliary devices such as lights and speakers.
  • Examples of applications include Bendix® Wingman® Advanced – A Collision Mitigation Technology, Bendix® Wingman® Fusion™, SmarTire® Tire Pressure Monitoring System (TPMS), Bendix® ESP® Full-Stability Technology, Bendix® Antilock Brake Systems (ABS), Bendix® Trailer Antilock Air Brake Systems (TABS), etc.

What the ACom Software Cannot Do:

  • Repair electrical or mechanical hardware issues.
  • Allow access to more than one ECU, device, or system at a time.
  • Run multiple versions of the ACom software at the same time.
  • Connect to more than one data link or PLC adapter at a time.
  • Display recorded videos.
  • Change or deactivate system-critical alerts and functions.
  • Allow the reduction of safety parameters beyond reasonable measure.
  • Delete system-critical records.
  • Alter previously recorded event data or alerts.
  • Change device serial numbers.

Safety First (before you touch the vehicle)

Block wheels, key OFF for under-hood work, drain air system pressure before air-brake work, follow OEM procedures to safely de-energize, wear PPE, and replace damaged components rather than repair unless approved. (Includes ATC/traction and Wingman radar notes.)

Minimum Requirements (before you install)

  • Windows: Vista, 7, 8, or 10 (not 95/98/XP).
  • PC specs: ≥1 GHz CPU, 2 GB RAM, 1 GB free disk, USB, IE 8+, Adobe Acrobat, 800×600 min (1024×768 recommended).
  • Latest ACom installed (download per doc).
  • RP1210 or PLC adapter with current drivers/firmware. We recommend the Nexiq USB Link 3.
  • Powered, working J1939 or PLC diagnostic port; vehicle battery charged (or a tender) for extended key-ON.

Computer Requirements

  • Runs on Windows Vista, 7, 8, and 10.
    Note: Windows 95, 98, and XP are not supported.
  • 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor.
  • 2 GB RAM.
  • 1 GB free disk space.
  • Microsoft Internet Explorer 8+.
  • Adobe Acrobat (latest recommended).
  • USB communication port.
  • VGA graphics with 800×600 minimum (1024×768 recommended).
  • Windows-compatible keyboard and mouse.

Connect & Launch

  1. Key ON (Run/On, not Start). Wait ~40 seconds (finish chuff test if equipped).
  2. Plug the J1939 diagnostic harness into the vehicle port (typically under-dash left/knee area or left).
  3. Confirm the Data Link Adapter shows power ON (J1939 light may blink). Connect the DLA to your PC.
  4. Launch Bendix ACom from the desktop.

First Screen: Starter Interface

  1. Click Communication Device → pick your RP1210 or PLC adapter (installed drivers required). Press ✅ to save.
  2. On the main list, select the ECU you want to diagnose. If you don’t see it, press Detect ECU (ECU must be powered and on the J1939 bus).
  3. Click Start with ECU and let ACom connect. It may take a few minutes depending on CAN traffic/ECU state.
  4. If you see “ECUtalk Platform Error” during load, verify drivers, connections, ports, and CAN load (see troubleshooting below).

After You’re Connected

Expect access to status, DTCs (active/inactive), clears, programmable settings, safety configuration, logs/reports, sensor support, calibrations (where applicable), alert simulations, and self-tests. Features vary by ECU (ABS, ESP, TABS, Wingman, Fusion, camera, TPMS, etc.).

Need to know which ECU is which? See the ECU table (EC-60/EC-80 ABS/ATC/ESP, Wingman ACB/Advanced/Fusion, VS-500/VS-400, FLC-20 camera, SafetyDirect processor, SmarTire/Trailer-Link, TABS-6 variants, EC-30/EC-17, Gen 4/5 ABS, EC-30T/MC-30/A-18). Each entry states its purpose.

Common Connection Error: “ECUtalk Platform Error”

Work these checks (J1939 examples shown in the guide):

  • Update RP1210 driver/firmware and ACom to latest.
  • Reseat adapter harness; ensure correct, dedicated harness (no mixing harnesses or adapters).
  • Some OEMs require proprietary DLAs or special Y-harnesses (e.g., MCI).
  • Verify diagnostic port power (12/24V) and network integrity (J1939 High/Low pinout, presence of two 120-ohm terminators).
  • Check for address conflicts or CAN bus overload; temporarily pull fuses for other CAN systems to test.
  • Make sure you’re interfacing Bendix systems with genuine parts (non-Bendix devices can trigger errors).

Extra Starter Options

  • Start in demo mode to practice without an ECU.
  • Options… to enable encrypted background logging and pass language/auto-start/close preferences to the diagnostic app.
  • Auto-troubleshoot on failed ECU detection; optionally show device settings before detection/starting.