I think I may know what your issue is!!
The module you're using has external TCP/IP input/output connections - Are you using these, attaching them to a TCP Client in the Device Symbol section??
If so, that's your issue - Those connections don't actually connect to ANYTHING inside the module!!? (Yes!? you may scream now!!!)
Thus, your TCP client symbol is trying to connect but is not being properly processed...
OR, it may just be that your processor is trying to make two connections at the same time to the same IP/Port - one via the TCP client and one via the module's Direct Socket connection, and the AVR or processor doesn't like it
Try Deleting or commenting out your TCP Clients and just use the IP address and Port # (default=50000d) parameters on the module.
Latch the Connect input of the module High when your program starts.
Note: I generally don't use a '1' on the connects, as I have had some modules that didn't behave well with it - if you don't have a delayed start signal in your program, I would use a '1' to trigger a DELAY symbol, wait 10s, and use the output for the connect.
Let me know if this fixes the issue...
HTH, Chris K
