Our test-environment incorporates a TCP/IP device that requires two TCP/IP connections from the LabVIEW application - one created with "TCP Open Connection.vi", and one created with "TCP Listen.vi". When the LabVIEW application quits, it closes both connections using "TCP Close Connection.vi". However, it looks like LabVIEW and/or the OS (WinXP) continues to reserve resources even though we've explicitly closed the connection _and_ power-cycled the device! "Ill-formed address" errors are often returned by TCP Listen when subsequent executions of the application attempt to Listen for a connection (at the same port#). Repeatedly re-running the application and/or re-launching LabVIEW are our best cures for this problem. How might LabVIEW coerce the OS to let go of the port faster? (Like with a CIN/API call to the OS, maybe?)
Cheers, Bill C
