I have studied various third-party libraries and approaches for low latency serial communications in .NET. I read enough that now I have come to the full circle and know as little as I, when I started, because of the many conflicting opinions.
For example, functionality in the Framework was ruled out due to some convincing articles that said: "that the solution Microsoft provided was not stable in versions of the framework and has no functionality."
I found articles beating many of the old COM libraries. I found articles that beat the idea of a low-latency .Net application in general due to garbage collection.
I also read articles demonstrating how P / Invoking for Windows API functions to ensure low latency is unacceptable.
THIS RULES ONLY ON ANY APPROACH THAT I CAN THINK!
I would really appreciate some words from those who were there / made this experience. Ideally, I could find a solid library / partner and not create my own communications library. I have the following simple goals:
- Long session low latency communication in C # / VB.Net
- 32/64 bit
- Well documented (if the solution is third-party)
- Relatively unimpacted (communication and latency) garbage collection.
- Flexible (I have no idea what I will have to deal with in the future!) The only requirement that I have is that I need to be able to interact with many different industrial devices, such as linear drives based on RS485, serial / microcontroller sensors and ModBus devices (also RS485).
, , , , !