I’m trying to use the SM5100 to connect to a Linux box. I can get the thing to register and connect. I can also send some data, although it’s not always clear that the send completes totally successfully. The show-stopper problem is terminating the connection. When I send a at+sdatastart=1,0, the server doesn’t close the connection and the 5100 goes into a hung state. That is, it responds to every command with a cme error: 4 (not supported). In order to clear, I have to turn off the 5100 and kill the server (it stays in a connection established state). The server is really simple; it simply listens to a port and when something connects it simply echoes everything it receives to stdout. I have a client program that runs on the same box; it connects and disconnects OK. So, I’m assuming that the 5100’s tcp/ip stack is causing the problem. So, has anyone actually gotten a tcp socket to connect, transfer data and disconnect?
I’m trying to use the SM5100 to connect to a Linux box. I can get the thing to register and connect. I can also send some data, although it’s not always clear that the send completes totally successfully. The show-stopper problem is terminating the connection. When I send a at+sdatastart=1,0, the server doesn’t close the connection and the 5100 goes into a hung state. That is, it responds to every command with a cme error: 4 (not supported). In order to clear, I have to turn off the 5100 and kill the server (it stays in a connection established state). The server is really simple; it simply listens to a port and when something connects it simply echoes everything it receives to stdout. I have a client program that runs on the same box; it connects and disconnects OK. So, I’m assuming that the 5100’s tcp/ip stack is causing the problem. So, has anyone actually gotten a tcp socket to connect, transfer data and disconnect?
Please reply to this message (I forgot to check the notify when a reply is posted box on the original message)