Deployment and troubleshooting of Softing CAN-AC2-PCI interface card

System deployment and hardware installation specifications

Due to the particularity of the PCI interface, deploying such boards requires strict system specifications to be followed.

PC hardware resource allocation

According to the technical specifications, the PC side needs to allocate 4kB of high-end memory address space (Upper memory area) and one idle interrupt (IRQ) for the board. Although modern motherboards typically support Plug and Play for PCI devices, IRQ conflicts or address space mapping errors may still occur in some industrial motherboards or outdated BIOS. If the board cannot be correctly recognized by the device manager, it is recommended to enter BIOS settings, check the resource allocation of the PCI slot, or try replacing the PCI slot.

Power supply and power consumption

This card is directly powered by the PCI slot of the PC (5V), with a typical current consumption of about 410mA. Before installation, it is necessary to ensure stable power supply to the PCI slot of the motherboard. When plugging or unplugging the board, the PC power must be completely cut off, and live plugging is strictly prohibited to avoid damaging the PCI bus controller or board.

Cable connection and terminal matching

Connect the vehicle network using a standard DB9 male adapter cable. Key note: There must be a terminal resistance of 120 ohms at both ends of the CAN bus. If the test bench does not have a built-in terminal resistor, it must be manually connected to the terminal resistor at the end node of the physical network, otherwise the communication signal will undergo severe reflection, resulting in a sharp increase in bit error rate.

Common troubleshooting and on-site maintenance

In old test benches, CAN-AC2-PCI failures are often caused by hardware aging, system upgrades, or configuration errors. The following are typical troubleshooting directions:

Phenomenon 1: The board cannot be found in the device manager or displays a yellow exclamation mark

Troubleshooting approach: Firstly, check if the driver program is installed correctly and matches the operating system version. Secondly, confirm whether the PCI slot is disabled or not enough IRQ resources are allocated in the BIOS. For old motherboards, try cleaning the PCI gold finger oxide layer and replacing the slot for testing.

Phenomenon 2: The board can recognize, but the upper computer software reports "unable to open channel" or "channel initialization failure"

Troubleshooting approach: Check if multiple software are simultaneously occupying the channel (APIs usually have exclusivity). Secondly, check if the power supply is sufficient (if multiple cards are inserted, an external auxiliary power supply may be required). Finally, confirm whether the underlying hardware configuration files (such as bit rate settings in the registry or configuration software) are consistent with the bus network.

Phenomenon 3: CAN communication is intermittent and error frames occur frequently

Troubleshooting approach: This is a typical physical layer issue. Firstly, use a multimeter to measure the resistance between CAN-H and CAN_L, which should be approximately 60 ohms (two 120 ohms in parallel). If the resistance value is abnormal, check whether the cable is broken and whether the terminal resistance is missing. Secondly, check if the shielding layer is single ended grounded, or if common mode interference has occurred between the PC and the rack due to a lack of electrical isolation. Although the board comes with isolation, improper wiring of external harnesses (such as parallel with high-voltage lines) can still introduce interference.

Phenomenon 4: Need to connect to low-speed fault-tolerant CAN network, but unable to establish communication

Troubleshooting strategy: CAN-AC2-PCI only supports high-speed CAN (ISO 11898-2) by default. If the target network is low-speed CAN, CAN-AC2-PCI-LS (Piggyback expansion board) must be installed on the corresponding channel, and the channel must be configured as low-speed mode in the software API, and the baud rate may be set according to the actual network situation (such as 125kbps or lower).

Phenomenon 5: System crashes or communication interruption without reason in high temperature environment

Troubleshooting strategy: The operating temperature range of this board is 0~+55 ℃, and the storage temperature is -20~+70 ℃. If the internal heat dissipation of the test chassis is poor, resulting in high temperatures near the PCI slot, it can easily cause thermal stability issues with the components. Suggest enhancing the air duct heat dissipation inside the chassis to ensure that the ambient temperature is within the compliant range.