Below are presented the most frequent causes for communication errors reported by EasyMotion Studio:

1. Communication port is not working properly.
> Solution: Check the communication port settings.

2. Drive gets reset by the power supply voltage drop. This situation can appear if the same power supply is used to for the logic and the motor stage of the drive. If the current demanded by the drive to control the motor exceeds the nominal current of the power supply then the internal protections of the power supply can be triggered cutting the output voltage.
> Solution: Check the power supply for voltage drops with an oscilloscope.

3. Another software (Technosoft or not) is using the communication port at the same time with EasyMotion Studio.
> Solution: Make sure the communication port is used only by the EasyMotion Studio.

4. The drive resets itself due to programming mistakes. If the program contains motion sequences with incorrect structures, that from syntax point of view are correct (RET instruction executed ouside a TML function), will cause the drive to reset.
> Solution: Check the motion sequence for incorrect structures.

5. The baud rate of the drive is changed  – either by SCIBR instruction executed from the TML program or received from an external device, a host or another drive in CAN network
> Solution: Check if the the SCIBR instruction is included in the TMLprogram or sent by the host.

6. An incorrect TML instruction is sent to the drive via the serial link resulting in an internal reset of the board.
> Solution: Check the binary code of the TML instruction sent to the drive.

Remark:  Other causes for communication failure, grouped by communication channel, are presented in the online help of EasyMotion Studio accesible with Help | Help Topics | Communication | Setup menu.