User manual

• On the remote host side (PC, etc.) open a TCP server that listens for incoming

connections on port 9761. Use any network tools (netcat, etc.) or special applications,

scripts (TCL, Python, etc.) to receive (and transmit) data files. • Set the PIC32 client side

address and port for the server to connect to, for example: tsrv4_c1

192.168.100.101 9761<CR>

• Start the PIC32 TCP client socket by issuing the console command: topen_c1<CR>

3. Start app3 – UDP server:

• Start the PIC32 UDP server socket that listens on port 32323 by issuing the console

command: uopen_s1<CR>

• On the client side (PC, etc.) open a client that connects over UDP to the PIC32 server

using port 32323. Use any network tools (netcat, etc.) or special applications, scripts

(TCL, Python, etc.) to transmit and receive data files.

4. Start app4 – UDP client:

• On the remote host side (PC, etc.) open a UDP server that listens for incoming

connections on port 32324. Use any network tools (netcat, etc.) or special applications,

scripts (TCL, Python, etc.) to receive (and transmit) data files. • Set the PIC32 client side

address and port for the server to connect to, for example: usrv4_c1

192.168.100.101 32324<CR>

• Start the PIC32 UDP client socket by issuing the console command: uopen_c1<CR>

5. Now that you have the TCP/IP tasks running you can check the progress at run time. These

commands give the RX and TX statistics showing the amount of data transferred by each task:

• tstat_s1<CR>

• tstat_c1<CR>

• ustat_s1<CR>

• ustat_c1<CR>

6. Once the data transfer is completed, close the TCP/IP sockets (if not already closed by the

remote party):

• tclose_s1<CR>

• tclose_c1<CR>

• uclose_s1<CR>

• uclose_c1<CR>

TCP/IP Task Descriptions and Commands

app1.c::TCP server