8286

Category: Alarm

Cause

1. Incorrect master communication configuration; the communication synchronization clock is not configured correctly.
2. The EtherCAT communication IN and OUT ports are reversed
3. The slave controller chip is damaged.
4. An MCU pin is damaged.

Corrective action

1. Replace the master with another, such as a Beckhoff or Omron plc, for comparative testing. Correct the master communication configuration problem.
2. Check the IN and OUT ports and confirm that they are not reversed. Wire the IN and OUT ports in the correct order.
3. If replacing the master does not solve the problem, use an oscilloscope to measure the synchronization signal generated by the slave controller chip. If there is no signal, the slave controller chip is damaged. Return it to the manufacturer for repair and replacement of the slave controller chip.
4. Use an oscilloscope to test the synchronization signal generated by the slave controller chip. If a signal is present, the mcu chip pin is damaged. Return it to the manufacturer for repair and replacement of the MCU chip.