??? 08/19/10 06:59 Modified: 08/19/10 07:04 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#178111 - Find out Why Responding to: ???'s previous message |
Praveen Kumar said:
These errors occur 5-10 times in a day. Praveen - I do believe that you should strive to identify the reason you see the 5-10 times per day error. Error discovery and recovery that you design into a product should be there to cover the cases of things that happen that you have little or no control over. On the other hand the failures you seem to be describing sound like they are something that you may very well have the ability to ferret out and fix!! I think if I were you that the goal should be to see no errors in the lab test setup environment. You were asked several questions regarding the multi-drop interface you are trying to use on the RxD path back to the Master controller. (I posted one of them). You did not seem to answer that at all - and I would like to see your response to that as there may be some bus line contention that is buggering your communications. I'd like to also ask that you put some consideration toward telling us what consideration that you've put toward the TxD signal path from the Master unit down to the multiple slaves. Have you considered all the issues that can affect signal integrity of such a multi-drop line. Have you applied proper termination schemes? Do you have stubs in the wiring path that create reflections and thus increased noise to a level that becomes marginal for communications to proceed reliably? You know, you probably need to at least instrument up a batch of oscilloscope checks of the bus in operation and check the SI (signal integrity) to make sure that the proper margins are maintained. Let me relate one type of SI that could be one that leads to occasional failures. If at some point along the bus you have a signal overshoot that causes the serial I/O pin at a microcontroller to pulse down below -0.8V or so this could cause on-chip upset to occur. An upset could cause a momentary misbehavior of the UART in the MCU. It could cause the MCU to fetch wrong code from time to time or it could cause some data read/write to operate incorrectly. Here is a waveform of a signal with a lot of overshoot: I'd be particularly on the look out for the overshoots that go below the GND level. Years ago I had an 8051 design that failed due to signals going below GND and making the MCU fetch its code incorrectly. After _lots_ of hard work I was able to trace the problem to the signal pin going below GND whenever a relay on the board was switched from its ON state to the OFF state. Michael Karas |