IXXAT IPC-I 320/ISA V2.10 Retrofit ISA Interface Module

IXXAT IPC-I 320/ISA V2.10: Retrofit-Compatible ISA Interface Module for Legacy Industrial PC Systems

The IXXAT IPC-I 320/ISA V2.10 is a ruggedized ISA-bus industrial PC interface module engineered for demanding automation environments where legacy control infrastructure must remain operational. As a direct retrofit solution for aging industrial PC platforms, this module bridges the gap between discontinued ISA-slot hardware and modern fieldbus communication requirements — enabling engineers to extend the service life of existing control cabinets without a full system overhaul.

Designed and manufactured by IXXAT Automation GmbH (an HMS Networks company), the IPC-I 320/ISA V2.10 delivers reliable CAN bus connectivity through a standard ISA expansion slot. It is widely deployed in legacy machine controllers, embedded industrial PCs, and retrofit control panels where ISA-bus architecture remains the only viable interface option. The V2.10 firmware revision ensures compatibility with a broad range of host software environments, including IXXAT’s own VCI (Virtual Communication Interface) driver stack.

Upgrade Compatibility Table

Retrofit Planning for Existing Automation Systems

When integrating the IXXAT IPC-I 320/ISA V2.10 into an existing automation environment, a structured retrofit plan is essential to minimize risk and ensure continuity of production. The following considerations apply across the most common legacy upgrade scenarios.

Control Cabinet and Backplane Assessment: Before installation, audit the host industrial PC for available ISA slots. Many legacy control cabinets built around platforms such as the Advantech IPC-610 or Siemens SIMATIC Microbox PC retain ISA backplane support, making the IPC-I 320/ISA V2.10 a direct drop-in candidate. Where the host IPC has already migrated to a PCI-only backplane, engineers should evaluate the IXXAT IPC-I 165/PCI as the equivalent PCI-bus CAN interface, preserving the same VCI driver stack and CANopen configuration tools.

Power Supply Capacity Verification: ISA-bus cards draw power directly from the host IPC’s internal power supply. When retrofitting a control cabinet that already carries multiple ISA expansion cards — such as a legacy IXXAT IPC-I 04/ISA multi-channel CAN card or a serial communication card — the total power budget of the IPC’s PSU must be recalculated. A 300W industrial-grade PSU is typically sufficient for a fully populated ISA backplane, but aging PSUs in legacy systems may require replacement before adding new interface cards.

CAN Network Wiring and Terminal Adaptation: The IPC-I 320/ISA V2.10 uses a standard DB9 CAN connector following CiA 303-1 pin assignment. During retrofit, verify that the existing CAN cable harness — connecting field devices such as CANopen I/O modules, servo drives, or frequency inverters — uses the correct CAN_H (pin 7), CAN_L (pin 2), and shield/GND (pin 3) wiring. Incorrect pin mapping is a leading cause of communication failure during first power-on after card replacement.

Protocol Migration and Baud Rate Alignment: The IPC-I 320/ISA V2.10 supports CAN 2.0A and 2.0B at baud rates from 10 kbps to 1 Mbps. When migrating from an older CAN interface card — such as a discontinued IXXAT CAN-PCI/331 or a third-party ISA CAN card — confirm that the replacement card is configured to the same baud rate as the existing CAN network. A baud rate mismatch will prevent all nodes on the network from communicating, including connected CANopen slaves, safety modules, and HMI panels that rely on CAN-based process data exchange.

Software and Driver Compatibility: The IXXAT VCI (Virtual Communication Interface) driver is the standard software layer for all IPC-I series cards. The IPC-I 320/ISA V2.10 is supported under VCI 3.x for Windows XP/7 environments and VCI 4.x for Windows 10/11. Applications built on IXXAT’s canAnalyser, CANopen Magic, or third-party SCADA platforms using the VCI API will continue to function without modification after card replacement, provided the driver version matches the host OS. For Linux-based IPCs, the card is accessible via the SocketCAN interface layer.

HMI Screen and Program Logic Preservation: In systems where an HMI panel (such as a Siemens TP700 or Pro-face GP series) communicates with the host IPC over a CAN or serial link, the retrofit of the CAN interface card should be transparent to the HMI application layer. No HMI screen reconfiguration is required if the CAN node address and baud rate of the IPC-I 320/ISA V2.10 are set to match the previous card’s configuration. PLC program logic stored in the host controller — whether a Beckhoff CX series embedded PC or a standalone soft-PLC — does not require modification for a like-for-like card replacement.

I/O Address and IRQ Configuration: The IPC-I 320/ISA V2.10 supports software-configurable I/O base addresses and hardware interrupt (IRQ) lines. In legacy ISA systems where multiple expansion cards share the same bus — including digital I/O cards, analog input modules, or serial communication cards — it is critical to assign a unique I/O address range and IRQ to the CAN interface card to prevent resource conflicts. The IXXAT configuration utility provides a guided setup procedure for address assignment.

Downtime Control During System Migration

Minimizing unplanned downtime is the primary concern during any CAN interface card replacement in a live production environment. The following approach is recommended for controlled migration using the IXXAT IPC-I 320/ISA V2.10.

Pre-Swap Preparation: Before removing the existing CAN interface card, capture a full backup of the host IPC’s software configuration, including VCI driver settings, CAN node address assignments, baud rate parameters, and any application-layer CANopen SDO/PDO mapping tables. If the host system runs a soft-PLC such as CODESYS or Beckhoff TwinCAT, export the current project and I/O configuration to a safe location. This backup ensures that the system can be restored to its last known good state if the retrofit encounters unexpected issues.

Staged Replacement Procedure: Where production schedules allow, perform the card swap during a planned maintenance window. Power down the IPC, remove the legacy CAN card, install the IPC-I 320/ISA V2.10 in the same ISA slot, and reconnect the existing CAN cable harness. On first power-up, use the IXXAT VCI configuration tool to verify that the card is recognized by the OS and that the CAN bus is active. A short loopback test using IXXAT canAnalyser or an equivalent CAN bus analyzer confirms physical layer integrity before reconnecting field devices.

Parallel Operation for Critical Systems: In systems where continuous CAN communication is required — such as safety-critical conveyor controls or process monitoring loops — consider a brief parallel operation phase where both the old and new cards are installed simultaneously (if slot space permits) to validate the new card’s communication before cutting over. This approach eliminates the risk of extended downtime caused by unexpected compatibility issues.

Field Commissioning and Verification: After card installation and driver configuration, perform a full network scan to confirm that all CAN nodes — including remote I/O modules, drives, and sensors — are visible and responding correctly. Verify that PDO transmission rates and SDO response times are within expected parameters. Document the final configuration for future reference and update the control cabinet’s maintenance log.

Every IXXAT IPC-I 320/ISA V2.10 unit supplied by us undergoes pre-shipment functional testing to verify CAN bus communication, driver recognition, and hardware integrity before dispatch. This reduces on-site commissioning time and lowers the risk of DOA (dead-on-arrival) failures in critical retrofit projects.

Retrofit Support FAQ

Q1: Is the IXXAT IPC-I 320/ISA V2.10 a direct replacement for earlier IPC-I 320/ISA revisions?
Yes. The V2.10 is backward-compatible with V1.x hardware revisions. The physical form factor, DB9 CAN connector pinout, ISA slot interface, and VCI driver stack are identical. Existing wiring harnesses and software configurations can be reused without modification. No changes to CAN node addresses or baud rate settings are required for a like-for-like swap.

Q2: What driver version is required, and is it compatible with my current operating system?
The IPC-I 320/ISA V2.10 is supported by IXXAT VCI 3.x (Windows XP, Windows 7) and VCI 4.x (Windows 10, Windows 11). Linux systems can use the SocketCAN driver layer. If your host IPC runs an older OS, confirm the correct VCI version before ordering. We can advise on driver compatibility based on your OS version and existing application software.

Q3: How do I verify CAN bus wiring compatibility before installing the replacement card?
Use a CAN bus analyzer or multimeter to verify CAN_H and CAN_L signal levels on the existing cable harness before card installation. Confirm that the DB9 connector follows CiA 303-1 pin assignment (CAN_H on pin 7, CAN_L on pin 2). Check that the CAN network termination resistors (120Ω at each end of the bus) are in place. Incorrect termination or wiring is the most common cause of communication failure after card replacement.

Q4: What warranty and pre-shipment testing is included with this unit?
Every IXXAT IPC-I 320/ISA V2.10 unit is covered by a 12-month warranty from the date of shipment. Prior to dispatch, each unit undergoes functional pre-shipment testing including CAN bus communication verification, driver recognition under Windows, and hardware integrity checks. Units that do not pass testing are not shipped. In-stock units are available for immediate dispatch to minimize retrofit project lead times.