I am trying to send motion messages at 100Hz over TCP. When I set the timestamp field in the motion message to "-", to establish the time-of-validity as the time PosApp receives the message, I get a response from PosApp in approximately 2 milliseconds. However, when I set the timestamp field in the motion message to a properly formatted string containing the actual time-of-validity of the data contained in the message, i.e. ("00:00:03.01000"), PosApp appears to take upwards of 600 milliseconds to send a response to my message. Has anyone seen this behavior before? Is it possible that the update rate of the simulation could have something to do with that? Is it possible that my string is not formatted correctly and that is making PosApp lag? When looking at the PosApp logs, I do not see any errors reported, but I do see my messages with correct data and timestamps in the message log. Thanks in advance for any help!