Hello xpc target users (or more realistically, hello Gordon Weast), xPC target is a powerful, but fickle beast of burden that will turn on a lesser warrior without warning. Recently, it has developed a taste for my soul. I am using an xPC target application to communicate with a .net program through a COM interface. My .net program uses the target_obj.GetSignal() function to periodically query a few signals in my model. Normally, the communication between the host computer and the target computer is fast enough that it is not noticeable, but every few seconds the roundtrip time for the communication jumps up to around .3 seconds. This is enough of a delay to momentarily bring my program to it's knees. It's driving m crazy and I think that it's hurting my program's feelings. The host computer and the target computer are directly connected to one another, and there is no other traffic on their network.
After snooping around a bit in the network traffic, I found out that the delay is occurring because the request from the host computer to the target computer is not being received. This is causing the host computer to wait around and then eventually resend the message.
Do you have any idea why the target computer might be missing messages? Have you ever observed this tactic of the beast before, and if so do you know of any way to defend against it? Is there yet any hope?
I would appreciate any and all insights. thank you, Justin
