JHogan Posted March 31, 2020 Report Share Posted March 31, 2020 I have a 2 state machines that are connected through user events. One of these is for taking measurements and writing data, the other is to control loading, moving and unloading the UUTs this is done through TCP communication (this is defined already from the vendor so I cant change that). With the the load there is a long wait time until I have a response over TCP and I dont want to have the measurement machine locked until I have a response. I would assume the best way would be just to ping the TCP read in a timeout loop with the TCP read timeout set to 100ms and clear the error until there is a response. This should give me the ability to response to other user events and keep the machine active. Again maybe I am on the right path for this and it is the best solution but something tells me there is a better option that I am not seeing. Anyone have a better solution? Quote Link to comment Share on other sites More sharing options...
Ashish Posted May 19, 2020 Report Share Posted May 19, 2020 You are on the right path. Further improvement suggestion: Asynchronous process instead of running the "timeout Event case" for checking response. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.