Well, don't know what else to say other than I have no idea where to go with this one, being that it is an undefined error. Error 11 on the TCP Wait On Listener. I didn't catch this error earlier because it is occurring a little later after it's been running for 10 minutes or more usually.
I attached my VI, the TCP logic is in the furthest upper right hand loop. LabVIEW 2020 and a cRIO 9053.
Solved! Go to Solution.
This seems pretty weird because error 11 is usually "Too many files open". I don't have 2020 installed to look at your VI to see if you're also doing any file operations in that area, but I'd check that and check to see if you're closing them after you're done with them.
Networking error codes should be limited to what's in this list so I really don't have a better idea.
I had forgotten to connect these wires circled in red through this case statement in my main loop, I wonder if that was it. So far so good. But kinda weird if it fixes it though because this is not related to the TCP logic in any sort of way (that I'm aware of).
I may be wrong but I think references are supposed to be kept live in a shift register, if you are going to re-use them from one cycle of a while loop to another.
I think I have a new lead. It only seems to throw error 11 when my client is connected to it. Otherwise, the server just sits there and runs on the cRIO just fine.
Here's my client (VI also attached):
Putting shift registers into the client tcp references gives me an error, Error 1. I'm pretty sure none of the examples/tutorials I've looked at used shift registers either, but I could be wrong. But I think it's because the connection ID is always changing