Re: Break Error
"Michael Jones" <Michael.e.Jones-S0/[email protected]> Wed, 18 May 2016 12:54:40 +0200
| Newsgroups | gmane.comp.hardware.microcontrollers.ethernut |
|---|---|
| Message-ID | <[email protected]> |
There is no such thing as an "break error" - only people that weren't around when the break condition was still widely in use. Yet there is some truth in it: often a break condition is an error when it happens without the protocol specifying or using it. Also, sometimes you would strap an resistor across the RX pin and GND to induce an break to indicate that the cable is not plugged in. Cu, Michael -----Original Message----- From: en-nut-discussion-bounces-inJ12LbcDfezQB+pC5nmwQ@public.gmane.org [mailto:en-nut-discussion-bounces-inJ12LbcDfezQB+pC5nmwQ@public.gmane.org] On Behalf Of Uwe Bonnes Sent: Mittwoch, 18. Mai 2016 11:16 To: Ethernut User Chat (English) <[email protected]> Subject: Re: [En-Nut-Discussion] Break Error >>>>> "Michael" == Michael Jones <Michael.e.Jones-S0/[email protected]> writes: Michael> Hello Uwe, The break condition is issued when the signal is Michael> held low longer than die total frame length. The Frame error on Michael> the other side indicates that e.g. the parity bit is Michael> invalid. The break state is often used in old protocols to act Michael> as a 257th character mostly as begin-of-frame or out of band Michael> data indicator. If I understand right, you explain a break condition. But what is a "break error"? Bye -- Uwe Bonnes bon-1JbLm1bU5j5ZIx36JBfelj3+ndqKAYMe9FMPySWZwLkb1SvskN2V4Q@public.gmane.org Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 --------- _______________________________________________ http://lists.egnite.de/mailman/listinfo/en-nut-discussion _______________________________________________ http://lists.egnite.de/mailman/listinfo/en-nut-discussion