懂串口的大神进来~~~~

[sharp0077]

OVERLAPPED os ;
WaitCommEvent( m_idComDev, &dwEvtMask, &os ) ；

用串口转USB线后，
if ((dwEvtMask & EV_ERR) == EV_ERR)
走到这里了报错了

串口接受端 读数据时调以下函数
ClearCommError( m_idComDev, &dwErrorFlags, &ComStat ) ;
其中有一次 dwErrorFlags 返回0x0008 （CE_FRAME）


网上查了下EV_ERR有以下三种
CE_FRAME 0x0008 The hardware detected a framing error.
CE_OVERRUN 0x0002 A character-buffer overrun has occurred. The next character is lost.
CE_RXPARITY 0x0004 The hardware detected a parity error.

网上这3个错误的解释太少，求大神解答下，什么原因会出现这3种错误！！！

[schlafenhamster]

搜索“Universal asynchronous receiver-transmitter“

[schlafenhamster]

Special transceiver conditions[edit] Overrun error[edit] An "overrun error" occurs when the receiver cannot process the character that just came in before the next one arrives. Various devices have different amounts of buffer space to hold received characters. The CPU or DMA controller must service the UART in order to remove characters from the input buffer. If the CPU or DMA controller does not service the UART quickly enough and the buffer becomes full, an Overrun Error will occur, and incoming characters will be lost. Underrun error[edit] An "underrun error" occurs when the UART transmitter has completed sending a character and the transmit buffer is empty. In asynchronous modes this is treated as an indication that no data remains to be transmitted, rather than an error, since additional stop bits can be appended. This error indication is commonly found in USARTs, since an underrun is more serious in synchronous systems. Framing error[edit] A "framing error" occurs when the designated "start" and "stop" bits are not found. As the "start" bit is used to identify the beginning of an incoming character, it acts as a reference for the remaining bits. If the data line is not in the expected state (hi/lo) when the "stop" bit is expected, a Framing Error will occur. Parity error[edit] A Parity Error occurs when the parity of the number of 1 bits disagrees with that specified by the parity bit. Use of a parity bit is optional, so this error will only occur if parity-checking has been enabled. Break condition[edit] A "break condition" occurs when the receiver input is at the "space" (logic low, i.e., '0') level for longer than some duration of time, typically, for more than a character time. This is not necessarily an error, but appears to the receiver as a character of all zero bits with a framing error. The term "break" derives from current loop signaling, which was the traditional signaling used for teletypewriters. The "spacing" condition of a current loop line is indicated by no current flowing, and a very long period of no current flowing is often caused by a break or other fault in the line. Some equipment will deliberately transmit the "space" level for longer than a character as an attention signal. When signaling rates are mismatched, no meaningful characters can be sent, but a long "break" signal can be a useful way to get the attention of a mismatched receiver to do something (such as resetting itself). Unix-like systems can use the long "break" level as a request to change the signaling rate, to support dial-in access at multiple signaling rates. The DMX512 protocol uses the break condition to signal the start of a new packet.

[worldy]

CE_FRAME 0x0008 The hardware detected a framing error.//帧错误，比如位数不足或者超过 CE_OVERRUN 0x0002 A character-buffer overrun has occurred. The next character is lost. //缓冲区溢出，缓冲区满之后，就不再接收数据 CE_RXPARITY 0x0004 The hardware detected a parity error.//硬件奇偶校验出错，校验位的值和数据不符合