Home/ Questions/Q 824811
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T03:09:17+00:00

I can use some help for a designing my COMport connection classes. I have

  • 0

I can use some help for a designing my COMport connection classes.

I have a device with a microcontroller (which I programmed) connected to my comport.
Whenever I send a message to it, it should send an acknowledge.

So whenever I send something over the comport, it should wait for an acknowledge before continuing.
Ofcourse, I dont want something like a while(!ack) wait().

When a ack is not received in 1 second or so, it should send the command again.
The Ack looks different for each type of command (note: only the type, no message-specific id).
The connected device also sends messages (apart from ACKs), which need to be handled by the application itself.

Does anybody has suggestions about an easy and flexible way (a design pattern maybe? a sample?) to fix this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’ll probably want a dedicated thread that handles the communications. You’ll need a Queue on which the client code can push a message, protect it with a ReaderWriterLockSlim. No need for the DataReceived event, just call SerialPort.Read() directly. Detect timeouts with the ReadTimeout property. If you get responses that need to go back to the client code then use an event.

    Watch out designing the protocol, it isn’t that easy to get right. You’ll protect against loss of bytes with your scheme, but it is just as likely for the ACK to be lost. The microcontroller will see the same command twice. Now you need a “message number” to suppress duplicates and a way for both ends to synchronize them. Take a look at RFC 916.

    • 0