According to this very good article http://www.innovatic.dk/knowledg/SerialCOM/SerialCOM.htm
It points out that there is lots of flaws in .NET 2.0/3.5 that make serial communications unreliable.
But my though goes than directly to how about invoking WIN32 API Calls instead?
Shouldn't that be more reliable to the statement?
Im planning to create an apps for communication with an datalogger in C#,
But this makes me a bit skeptic if i should bother at all.
Has anyone a tip or experience in this one using Serial with WIN32 API??
That could help me abit before i get dirty on this one, it would be much appreciated
Thanks!
Loading
Brian AderianPosted Oct 6, 2009, 2:21 AM
And no i will not blaim anyone if i blow up a whole universe now :-) *lol*
I have more exciting questions based also in what you said, but i guess that is another issue or threads.
Thx
Danatas GerviPosted Oct 4, 2009, 4:29 AM
The article is overloaded – too many about too many different things….
You may know nothing about voltage and UART futures for successful using the SerialPort class.
Just made all settings the same (Stop bit, rate, parity …) on both sides – and it will send and receive data.
:-)
Brian AderianPosted Oct 2, 2009, 5:53 AM
And yes feels much safer if its true that you are saying.
But should that article really be ignored than?
Perhaps it is some flaws in it, but maby its also because how people write there handler routine for it also, right?
I mean if you have to sync or perhaps you using async or threads, it "almost" always give some flaws as an result
because its behaviours in the hardware. Correct me if im wrong.
Thanks
Danatas GerviPosted Oct 1, 2009, 9:24 AM
The article is written in too emotionally style. The real situation is not so critical.
The class SerialPort works perfect. I made number of programs (kind of gateway) for real automated warehouses, it mean – constant work 24 hours in day. No problem on level of serial port.
Your own program, with using Win32 API will not be better.