CAN-bus Communication Troubleshoots

If the CAN-bus communication does not operate properly, EasyMotion Studio will issue an error message and you’ll see displayed on the status bar (the bottom line) of the EasyMotion Studio the text “Offline”.

1.	If the error message is “Cannot find board with selected Axis ID”, click “Cancel” button, then check the following:

•	CAN Baud rate selected in the Communication \| Setup dialogue for the CAN-bus interface. It should be the same with the drives/motors baud rate, which is set by default at power on at 500kbps.

•	CAN-bus cable connections and the presence of the 120 ohms terminal resistors at the two ends of the network

•	If the CAN-bus supply is on

•

In EasyMotion Studio project, the “Axis Number” of the selected application. This should match with the Axis ID of one of the drives from the network. As e general rule, the axis number of each application must correspond with the axis ID of one drive from the network. Each drive must have a different axis ID. No drive can have the same axis ID value as that set as Axis ID of PC.

•	The setup of the CAN-bus interface on your PC

•	Drive/motor hardware settings for CAN-bus communication (see CAN-bus Setup)

2.	If the error message is “Cannot load interface with PEAK SYS xxxx devices (PCAN_XXXX.DLL)”, click “Cancel” button, and then copy the file “PCAN_XXXX.DLL” from the Peak System CD (or other storage media) in the folder where EasyMotion Studio was installed.

3.	If the error message is “Invalid Parameter”, click “Cancel” and check the CAN-bus interface selected in the Communication \| Setup dialogue. This message occurs when the selected interface is not installed and/or configured on your PC.

If the communication operates usually but gives communication errors from time to time, in “Communication | Setup” click on Advanced… button and increase the Send message timeout (when present) and Receive message timeout parameters. Note that for these parameters, usually, the default values do not need to be modified.

After you fix the problem, execute menu command “Communication | Refresh” to restore the communication.