2962 views|3 replies

27

Posts

0

Resources
The OP
 

Communication failure [Copy link]

This post was last edited by cgu on 2020-3-3 14:45

The terminal prompts that the driver has a communication failure. The power supply is 24V5V and the communication line has been checked. The MAX491E RS422 has been replaced, but the problem remains the same. When the driver is powered on normally, after about 8 seconds, the relay (1) controlled by the 3rd pin of the MCU hears a traction sound. After 2 seconds, the relay (2) also tractions to charge the main drive capacitor with current limiting. The red indicator light is on and the green light flashes. Now, after power is turned on, it takes more than ten minutes for relay 1 to traction 2. The indicator light is also normal, but the system also reports a communication failure. How can I distinguish whether it is a problem with the system software or hardware or a problem with the driver itself? Is the chip DS26C32 related here? Please also tell me the pin conditions for the normal operation of the MCU. Thank you. DMD is the driver and CCP is the motherboard.

This post is from MCU

Latest reply

First, confirm whether the timing of the closing action of relay 1 is consistent with that of a known normal device. If it is consistent, it means that the problem occurs after the closing of relay 1. Check the circuit action after the closing of relay 1 and analyze the reasons for the abnormal timing of the action of relay 2. In most cases, this type of failure is a hardware problem. Software problems are only possible when an error code is written during an upgrade or firmware reflashing. If the software is not rewritten, this possibility can be completely ruled out.   Details Published on 2020-3-4 11:40
 

1w

Posts

142

Resources
2
 

First, confirm whether the timing of the closing action of relay 1 is consistent with that of a known normal device. If it is consistent, it means that the problem occurs after the closing of relay 1. Check the circuit action after the closing of relay 1 and analyze the reasons for the abnormal timing of the action of relay 2.

In most cases, this type of failure is a hardware problem. Software problems are only possible when an error code is written during an upgrade or firmware reflashing. If the software is not rewritten, this possibility can be completely ruled out.

This post is from MCU
 
Personal signature上传了一些书籍资料,也许有你想要的:http://download.eeworld.com.cn/user/chunyang
 

27

Posts

0

Resources
3
 
chunyang posted on 2020-3-4 11:40 First confirm whether the timing of the pull-in action of relay 1 is consistent with that of the known normal device. If it is consistent, it means that the problem occurs after relay 1 is pulled in. ...

Thank you. There is only one such driver, the relay should be normal

This post is from MCU
 
 
 

27

Posts

0

Resources
4
 
This post was last edited by cgu on 2020-3-4 14:30

Can you guide me to solve this problem? Master, please give me a price

This post is from MCU
 
 
 

Guess Your Favourite
Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号