The VI below is a simple one that works well under ideal conditions. But as mentioned there in real life there are issues to address. OK one method is to have a logic implemented to do this :
1. Sense the error status.
2. On Error, close the Serial session and then restart the session.
But I just want a basic clarification... I think the Serial Start / Write / Read functions are blocking type ? Meaning till the intended functions completes or Time out happens the loop is frozen .
I would like o know if there any way of making these non-block type. Like I just initiate a Serial Read and then go do something else . Once the function completes it lets me know and I do something with the data just received. For those from the embedded world this is a normal way with Processor Interrupts but I am not sure about the Windows world !! Any tips on this ?
