03-25-2009 02:59 AM
Hello,
03-27-2009 05:37 AM
Hi VdG,
Thanks for posting on the National Instruments Forum.
Can you post your code? Like that we will be able to help you to investigate the issue.
03-27-2009 09:21 AM
Hi,
here's a screenshot of the communication part of the RIO vi, and a vi that sum up the communication part of the host vi (the Host application is quite huge, and not very well documented...).
Mainly the RIO periodically calls TCP_Listen with a short timeout, and the host periodically tries to initiate a connexion with TCP_Open. This works fine, but the RIO vi froze when the connexion establish. Maybe the RIO (sender) have to wait a for a while, between the connexion open and the first writings ?
Regards,
Vincent
04-03-2009 11:43 AM
Hi VdG,
Sorry for the late answer but I was unavailable this week. Well, on the cRIO controller there is a RT OS and normally we don't consider the communication with the host as a high priority task. You can implement Producer/Consumer architecture on your RT Target where the Producer contains the high priority task and the consumer the communication task with a less high priority. If you implement the communication in the highest priority loop it will cause the cRIO VI will wait for the communication is establish to run anything else.
You can find here good programming practices for RT application.
Hope this helps and feel free if you have any other questions.