NI-9853 Controller Area Network (CAN) Interface

Power input not connected or voltage out of range (18–30VDC required).

Damaged power cable or poor interface contact.

Internal power circuit failure.

Check the output voltage of the power adapter with a multimeter to ensure it is within 18–30V.

Replace the power cable or re-plug the power interface to ensure good contact.

If the power supply is normal but the module still does not respond, contact NI technical support for hardware inspection

Input voltage exceeds 30VDC, or motor load is too high, causing current to exceed the rated value (5A continuous, 10A peak).

Motor or cable short circuit.

Disconnect the power supply, check if the input voltage is stable, and eliminate power fluctuation issues.

Measure the motor winding resistance with a multimeter to confirm short circuit; replace the motor or repair the cable if shorted.

Reset protection parameters in NI MAX or LabVIEW and restart the module.

Poor contact or damage to communication cables (e.g., USB, EtherCAT).

Incorrect installation or incompatible version of module driver.

Misconfigured communication parameters (baud rate, protocol).

Replace the communication cable and ensure the interface is secure; confirm if the module is recognized in NI MAX.

Uninstall and reinstall the latest NI drivers (e.g., NI-DAQmx, LabVIEW FPGA Module).

Check the communication parameter settings of the module in the project explorer to ensure consistency with the host computer (e.g., CANopen baud rate must match).

Bus termination resistors not connected (CANopen requires 120Ω resistors at both ends).

Excessively long bus cables or non-standard cabling causing signal interference.

Slave address conflicts or protocol configuration errors.

Check if bus termination resistors are correctly connected and use an oscilloscope to view stable bus waveforms.

Shorten the bus length, use shielded cables, and ground them to reduce electromagnetic interference.

Check slave addresses in configuration tools (e.g., CANopen configuration software) to ensure uniqueness; re-initialize the bus protocol.

Incorrect control mode setting (e.g., target value not input in position mode).

Abnormal encoder feedback leading to closed-loop control failure.

Incorrect motor wiring (phase sequence error, ground not connected) or driver output failure.

Confirm the control mode (position/speed/torque) and command input in LabVIEW, and try manually sending control signals (e.g., jog mode).

Check encoder cable connections and use an oscilloscope to measure encoder pulses; replace the encoder or cable if pulses are missing.

Reconnect cables according to the motor wiring diagram to ensure correct phase sequence; test whether the driver output port has voltage in NI MAX.

Unoptimized three-loop control parameters (PID) leading to system oscillation.

Uneven mechanical load or excessive transmission system clearance.

Insufficient encoder resolution or loose installation.

Use LabVIEW's PID tuning tool to gradually adjust proportional (P), integral (I), and derivative (D) parameters to suppress jitter (e.g., decrease P value, increase D value).

Inspect the mechanical structure, tighten components like couplings and guides to reduce clearance; add load balancing measures if necessary.

Confirm whether the encoder resolution meets requirements (e.g., incremental up to 20 MHz) and re-fix the encoder installation position.