Serial communication errors enumeration type. It can be one or more of the following values.
Namespace: ZylSoft.SerialAssembly: ZylSerialPort (in ZylSerialPort.dll) Version: 1.83.8519.34486
Syntax [FlagsAttribute]
public enum SerialErrors
<FlagsAttribute>
Public Enumeration SerialErrors
[FlagsAttribute]
public enum class SerialErrors
[<FlagsAttribute>]
type SerialErrors
/** @attribute FlagsAttribute */
public enum SerialErrors
ZylSoft.Serial.SerialErrors = function();
ZylSoft.Serial.SerialErrors.createEnum('ZylSoft.Serial.SerialErrors', true);
[FlagsAttribute]
enum SerialErrors
No code example is currently available or this language may not be supported.
Members Member name | Value | Description |
---|
RxOver | 1 |
An input buffer overflow has occurred. There is either no room in the input buffer, or a character was received after the end-of-file (EOF) character.
|
Overrun | 2 |
A character-buffer overrun has occurred. The next character is lost.
|
RxParity | 4 |
The hardware detected a parity error.
|
Frame | 8 |
The hardware detected a framing error.
|
Break | 16 |
The hardware detected a break condition.
|
Remarks
You can sometimes get errors at the beginning of the communication. The problem is probably that you are opening the port while the remote device is in the middle of transmitting.
This can cause your serial port to miss-detect the start bit of the data byte, causing corrupted data (framing errors) until
there is a gap in the communication and the UART can resynchronize with the next start bit in the data stream.
See Also