Issue Reading and Writing to Serial Port

[BubbaGeeNH]

I've written a managed class that handles the serial communication to a laser using ascii text. My problem is if my GUI makes too many calls to the functions in the laser communication class I get the wrong responses back from the laser. They are valid responses but it appears as if the response from the first call is being replaced by the response from the second call. I've attempted to control the usage of the serial port by using 'Mutex.WaitOne' but that doesn't seem to have an affect. All the calls to the laser are being generated by Windows' messages within the GUI. Does anyone know of a way to control the flow of calls to the laser class? I'm using Visual Studio 2008 and Managed C++. Thanks, George

George

[Rick Shaub]

Why don't you try sending one command and waiting for the response before sending the next command?

[BubbaGeeNH]

If I run my class as part of a Console application I have no problems with it communicating correctly and getting the correct responses. My problem is when I try to run it as part of a Windows GUI application. It seems as though the compiler is making my application a multi-threaded application and it is putting the writing and reading of portions of the class into different threads.

George

[Luc Pattyn]

Hi, you can use synchronous calls such as SerialPort.Read() and SP.Write() any way you like; the thread executing the call will process the data, obviously. However some event handlers, such as DataReceived, will fire on another thread (what else could they do?). You may want to read this article[^]. And that is exactly the same for Console and WinForms applications. :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages

---