Design Workflow with a thread to handle c#

Question

0.00/5 (No votes)

See more:

Hello, I'm new in the design workflow.
I have a question:
I have a graphics interface unit, a desired workflow state machine and a thread that polls a hardware device and receives a response every 1 ms (approximately) via RS232.
These responses may alter the state machine.
The GID may modify the state machine.
I found lots of examples for host-workflow communication, but I do not know how to handle this thread.
Could you help me and give me some suggestions?
Bye

Posted 6-Jun-11 3:56am

Franck Tulli

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kim Togo · Answer 1 · 2011-06-06T07:21:00

Use a Queue<T>[^] to enqueue the received data and have another thread dequeue the data for processing.

If you are use .NET 4, then use the new ConcurrentQueue<T>[^] class. Check this link BlockingCollection and IProducerConsumerCollection[^]

Workflow can be:
1. Receive data on RS232 / Serial port.
2. Pre process data received.
3. Enqueue data in an Queue class.
4. Repeat, goto step 1

In another thread you then:
1. Dequeue an Queue class.
2. Post process data.
3. Do the your thing.
4. Repeat, goto step 1.

Sergey Alexandrovich Kryukov · Answer 2 · 2011-06-06T07:24:00

Solution 2

In addition to the solution by Kim:

Queue is not enough. Communication requires a blocking queue.
If you're not using .NET 4, or you are but want to know how to use it, please use my Tips/Trick article with full source code and detailed usage samples:
Simple Blocking Queue for Thread Communication and Inter-thread Invocation[^].

—SA

Posted 6-Jun-11 7:24am

Sergey Alexandrovich Kryukov

Comments

Kim Togo 6-Jun-11 14:25pm

My 5 for the good Tips/Tricks

Sergey Alexandrovich Kryukov 6-Jun-11 14:30pm

Thank you, Kim.
--SA

thatraja 6-Jun-11 23:41pm

It's a good Tip/Trick SA, Already in my bookmarks

Sergey Alexandrovich Kryukov 6-Jun-11 23:45pm

Thank you, Raja.
--SA