Regarding the charging pile networking issues, many customers have inquired. Every time the joint debugging of different platforms is carried out,
some compatibility issues may arise. If it is a protocol issue, you only need to check the official documents for processing.
Among these questions, the most frequently asked questions are about the initial networking of charging piles and whether they can establish a connection with the management platform.
Next, we will share the charging pile networking issues and deal with them.
If you are unable to connect, open the command running tool on your computer and use the ping command to detect the platform that needs to be connected.
You can view the corresponding IP address, delay, and packet loss rate.
If you are unable to connect due to high latency or packet loss, you can choose to try using a VPN to connect.
If it is inaccessible, it may be that the external network port of the platform is not open,
causing the inability to connect, or it may be that the platform does not have a ping function.
In this case, further communication is required with the customer to determine whether the customer has opened the external network.
Port access to solve the problem, the ping function does not affect the connection of the charging pile.
2. TCP connection
If there is no problem after PING detection, open any TCP connection tool and enter the customer’s IP and port to create a TCP connection.
If you cannot connect, it may be because the firewall is turned on. You can add the IP address to the firewall or turn off the firewall.
If TCP can create a connection, a test HTTP handshake command is sent.
Check whether the HTTP handshake is successful and determine the problem based on the status code result of the reply.
For example, the reply status code 101 means that the HTTP handshake is successful,
and the reply status code 400 means that the domain name of the page being accessed does not exist or the request is incorrect.
3. Data packet interception and viewing at the network data transmission layer
After ensuring that there are no problems in the first two steps,
it means that the connection conditions of the charging pile before sending protocol data have been met.
If the problem of being unable to connect or being disconnected occurs in the protocol command,
you need to find the corresponding command, use Wireshark to intercept the network layer data for detailed analysis,
and check the corresponding HTPP handshake and OCPP commands. Check whether each command received a correct reply.
If you see a reply alarm, analyze the data of that command. If you find that there is a command that did not receive a reply,
you will also analyze the data of that command.
Although this initial networking is a very simple problem, due to differences and compatibility issues between platforms, the probability of such problems is the highest.
We cannot ignore it because it is simple, and we cannot waste our experience in solving problems. We must analyze and process it well to improve processing efficiency.