Communication Test
This section describes how to test the communication function of custom communication services.
Communication Test Process
This section provides a simulation test process to verify whether trigger logic and communication link configuration are correct. It does not involve integrated debugging with real production-line devices.
|
Simulation Test for TCP Server/TCP Client Services
Applicable to: TCP Server and TCP Client.
-
Open the Mech-MSR solution and start custom communication services.
-
Use a simulated peer-side tool to establish a connection (for example, a TCP debugging assistant).
-
Send request data from the simulated peer side according to negotiated protocol specifications.
-
Check software status, logs, or result outputs to confirm that the project is triggered and executed.
-
Confirm on the simulated peer side whether response data that matches negotiated protocol specifications is received.
-
Repeat Steps 3-5 to verify whether repeated triggering behavior meets expectations.
Simulation Test for PLC-Type Services
Applicable to: Siemens S7 Client, Modbus TCP Slave, and Mitsubishi MC Client.
-
Use a PLC simulator or register simulator to emulate the communication peer side.
-
Open the Mech-MSR solution and start custom communication services to establish a communication connection.
-
On the simulated peer side, write valid trigger values to trigger registers and write measurement parameters to other registers.
-
Check software status, logs, or result outputs to confirm that the project is triggered and executed.
-
Confirm on the simulated peer side whether feedback data that matches negotiated protocol specifications is read (such as status bits, result registers, or response flags).
-
Repeat Steps 3-5 to verify whether repeated triggering behavior meets expectations.