Table of Contents
Advertisement
10.11.3
Configuring Socket Client for Calling a Socket Listener on
Another Host
The example assumes that a connection profile has been created as explained in Section
10.1.2.
Configure the client's service profile 1 for calling a Socket listener on another host:
at^siss=1,srvType,socket
OK
at^siss=1,conId,0
OK
at^siss=1,address,"socktcp://
10.10.0.187:65534"
OK
10.11.4
Socket Client Sends Data via TCP Connection (Polling Mode)
The example uses service profile 0 configured for Socket service and TCP.
AT^SISO=0
OK
AT^SISI=0
^SISI: 0,3,0,0,0,0
OK
AT^SISI=0
^SISI: 0,4,0,0,0,0
OK
AT^SISW=0,10
^SISW: 0,10,10
0123456789
OK
AT^SISW=0,10,1
^SISW: 0,0,10
OK
AT^SISW=0,10,1
^SISW: 0,10,20
0123456789
OK
AT^SISW=0,0,0
^SISW: 0,0,10
OK
AT^SISI=0
^SISI: 0,5,0,20,10,10
OK
MC55_ATC_V04.00
Confidential / Released
Select service type Socket.
Select connection profile 0.
The service profile of the client contains the IP
address and the TCP port of the remote host.
The host opens service profile 0.
Note: URC ^SISW:0, 1 does not appear! The host
must poll the service state by means of AT^SISI until
the service is in
The service is still in
The service is now in
ready to accept data.
The host requests to write 10 bytes.
Response that 10 bytes can be sent and are unac-
knowledged.
The host requests to write next 10 bytes and enables
the end-of-data flag.
But the service refuses the request, even the end-of-
data flag remains without effect.
Next try (polling).
Response that the service accepts 10 bytes and this
data and the previously sent data are unacknowl-
edged.
Polling to request unacknowledged data.
There are 10 bytes still unacknowledged.
Polling for
"Down").
20 bytes are transfered via serial interface, 10 bytes
are acknowledged by remote peer, 10 bytes are on
the way.
Page 257 of 475
10.1.1
"Up".
<srvState>
"Connecting".
<srvState>
<srvState>
change ("Closing" ->
<srvState>
or Section
"Up" and is
3/17/06
Advertisement
Table of Contents
