Quote:
Originally Posted by RoboRealm
We are working with another team on exactly this issue. It seems to be related just to the C++ version on the CRio and was believed to be a issue with CRio high CPU load but that looks less likely now. Additional tests have revealed that it might be something with the laptop in use since changing to a different machine does not exhibit the same issue.
For now, if you look at the interface, there is a delay text box that will cause the signals to be grouped every X ms before sending. A value of 40ms seems to reduce this problem.
Alternatively, if you have another laptop, do a quick test with that.
We are continuing to investigate the issue.
STeven.
|
its not a C++ issue, my java-flashed cRIO is printing the errors also.