8.2.9. How to Test TCP/IP
Warning
In Hardware version 1.2.3 and below, the PHY is enabled by default, which can cause issues when connecting the Ethernet cable. To avoid this, the pull-up resistors enabling the PHY should be removed. For more details, refer to Removing the Pull-up Resistor for the PHY.
Most of the configuration is already done in the foxBMS 2 implementation. If changes in the FreeRTOS port for TCP/IP are necessary, refer to How to Implement an Ethernet Port. To use TCP/IP, configure it as described in rtos.
To connect the BMS-Master with the Ethernet cable, refer to
TI TMS570-based BMS-Master v1.2.2 Pinout.
After the physical connection is established, the CAN message f_BmsState
sets PhyLinked to 1.
Now foxBMS 2 can be pinged or the echo server can be used.
Hint
It can be usefull to deactivate during testing other network connections as WiFi.
8.2.9.1. Debug the Network connection
For debugging purposed the UART interface can be used. The general configuration is described in debug.
8.2.9.2. How to Ping foxBMS 2
This section shows how to send a simple ping message to foxBMS 2.
In FreeRTOSIPConfig.h ipconfigREPLY_TO_INCOMING_PINGS is enabled.
This is why the TCP/IP stack answers ping messages by default without a
server being initialized.
To enable foxBMS 2 to respond to ping, some application code is
provided in src/app/application/ethernet/ethernet.c.
The interface descriptor is initialized with
pxTMS570_FillInterfaceDescriptor.
The IP address and other network parameters have to be set with
FreeRTOS_FillEndPoint.
To initialize the TCP/IP stack, FreeRTOS_IPInit_Multi is called.
The tasks that use the network are created in the
vApplicationIPNetworkEventHook hook function.
This hook function is called when the network connects.
8.2.9.2.1. Using Ping
Ping is a standard program for checking an ethernet connection.
The default IP Address is 169.254.107.24.
DHCP is currently not used, so static addresses need to be assigned.
All of the related configuration can be found in
src/app/application/config/ethernet_cfg.c.
When calling ping <ip address> it should return
PS > ping 169.254.107.24
Pinging 169.254.107.24 with 32 bytes of data:
Reply from 169.254.107.24: bytes=32 time<1ms TTL=255
Reply from 169.254.107.24: bytes=32 time=1ms TTL=255
Reply from 169.254.107.24: bytes=32 time=1ms TTL=255
Reply from 169.254.107.24: bytes=32 time<1ms TTL=225
Ping statistics for 169.254.107.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
With the parameter -n it is possible to choose the number of requests.
8.2.9.3. How to Test the Echo Sever
For testing the echo server the program Putty is used. The default IP Address is 169.254.107.24 and the echo server port is 7. It has to be configured as follows:
Putty configuration:
Session:Host Name:<foxBMS IP Address>
Session:Port:<foxBMS Echo Server Port>
Session:Connection Type:raw
For better readability:
Terminal:Implicit CR in every LF
Terminal:Implicit LF in every CR
When establishing the connection it should output
Connected to client
Started connection instance
With the tool Wireshark the TCP handshake can be observed. It should look like in the image below.
Fig. 8.4 TCP-handshake
Now every input to the Putty terminal is echoed back. The image below illustrates the data send.
Fig. 8.5 Log showing the TCP echo request and response
On closing the TCP connection another handshake is performed as shown in Fig. 8.6.
Fig. 8.6 Log showing the closing procedure of a TCP connection
