PC –> Loopback – PC communicating with itself for testing.What is presented below is as close as I have come to THE answer. As I worked with different devices I kept searching for THE answer to receiving data. The difficulty people have using the serial port tends to be with receiving data. Threading.Monitor Enter, TryEnter, and Exit.Windows form controls can only be manipulated from the UI thread, and UI control updating is inherently slow.You must know the protocol of the device you are communicating with.polled - the device that is attached to the serial port sends messages only in response to the receipt of a message from the application.As soon as it is connected it starts sending NMEA messages. This means that the device that is attached to the serial port sends messages without being asked to. non-polled – the serial port receives data unsolicited.SerialPort communication can take one of three forms.SerialPort reads are blocking except ReadExisting.This is a common forum question and one that used to stumped me. When the SerialPort DataReceived event fires there may or may not be an entire protocol data unit (PDU or message) available.Only one SerialPort event handler can execute at a time.

Modern PC’s have multiple cores and can execute multiple threads at the same time.It is not meant to insult your intelligence just bear in mind that not all readers of this have the same knowledge level. This is some basic information that you know, or should know to use this code. Removes part of the complexity, and leaves only a discussion of the protocol. Taking the approach presented to serial data reception Questions that are asked on Forums about serial ports are complicated because of the many approaches taken with device communication and / or not having a clear understanding of the device protocol.

Gambas Serial Port Send