04-29-2013 03:55 PM
Hi, please would you clarify step by step how to give some delay in my cRIO TCP?
Thanks a lot
04-30-2013 11:44 PM
Can't you just put a wait VI in the send loop?
05-01-2013 01:56 AM
Thank you TIM-C for your reply, but please could you explain how to do that, step by step.
Thanks again.
05-03-2013 12:44 AM
Just add the wait (ms) vi to your send loop and wire a constant to it that represents the number of milliseconds you want to wait.
06-24-2013 05:05 PM
I was seeing a similar problem with LabVIEW 7.1 and Windows 7. Had a VI talking to our T7-Pro device over WiFi that did a TCP Write immediately followed by some TCP Reads. I was getting the "not enough memory ..." error ~10 seconds after I did something to interrupt the connection such as block my WiFi signal. I put a little sequence structure with a 0s Wait between the write and read and the problem seems to have gone away.
06-25-2013 09:03 AM
When you look at Task Manager check the number of Threads used by the Server you are connecting to. This is one of those Microsoft errors that are nor reported clearly. Different Operating systems allow different numbers of process threads per application. For Windows XP and older the limit was 2024 threads less about 300 that wer reserved for the OS to use. In Win 2k3 and newer the number of threads is limited by the amount of RAM that is availalbe and the number of processes that are running.
06-25-2013 12:18 PM
The 0s Wait after that first TCP Write mostly solved the problem, but I still saw it occasionally. I now have added 0s Waits after every TCP Write and Read in that VI and have not seen the problem since.
04-01-2020 03:49 PM
We've been having this same issue with a few executables that run on our servers. For all of the programs where this pops up, the "Enable Debugging" feature has been enabled. When we turn that off, we don't see the issue anymore.
We like having that feature turned on as it helps with troubleshooting, but not if it is affecting the programs and causing this memory error.
09-22-2021 02:54 PM
Turns out that we are still seeing the error pop up when debugging is turned off. back to the drawing board.