Hi Tony,
I'm sorry, it seems my first response was indeed a little hasty. In this case, it is the polling thread on the receiver that shows you the buffering behavior. As I explained before, this thread runs at the same priority as the main VI thread. I will show you how you can raise the priority on this thread. It is also then necessary to add some delay to it so it doesn't starve the main VI thread. This code can be found in:
<LabVIEW 2009>\Targets\Keil\Embedded\RealView\Drivers\RL-ARM\TCP\RLARM_TCPWrapper.c
The thread is spawned on this line with the default priority:
os_tsk_create_user (tcp_task, DEFAULT_PRIORITY, &tcp_stack, sizeof(tcp_stack));
You can change the DEFAULT_PRIORITY to (DEFAULT_PRIORITY + 10)
Now we can add the delay in tcp_task, which is the function that actually processes the received packets
__task void tcp_task (void) {
/* Main Thread of the TcpNet. This task should have */
/* the lowest priority because it is always READY. */
while (1) { os_mut_wait(stackMutx, (-1)); // Get stack mutex...
main_TcpNet();
os_mut_release(stackMutx); // Release stack mutex...
os_tsk_pass();
}
}
You can add os_dly_wait(1); as the last line of the while loop. The function argument is the delay in milliseconds. This way, the thread will poll the socket at every one ms. Your main VI might be slightly starved but you can play with the delay to get the behavior that you need.
Your final code should look like this:
__task void tcp_task (void) {
/* Main Thread of the TcpNet. This task should have */
/* the lowest priority because it is always READY. */
while (1) { os_mut_wait(stackMutx, (-1)); // Get stack mutex...
main_TcpNet();
os_mut_release(stackMutx); // Release stack mutex...
os_tsk_pass();
os_dly_wait(1); //wait one ms
}
}
Rebuild the project once you have made these changes
Hope this helps,
Jaidev
Message Edited by Jaidev on 12-09-2009 04:29 PM
Message Edited by Jaidev on 12-09-2009 04:30 PM
Senior Product Manager
National Instruments
