I. Rapid Troubleshooting of the Physical Network (Completed in the Space of Five Minutes)
Observe the Link/Act light status of the MES server, SCADA industrial control computer, and industrial switch to make an initial judgement based on network port indicator lights. The physical link is disrupted when the Link indicator is off. Prioritise the examination of network cables, RJ45 connectors, and network port hardware faults.
Accurate Connectivity Test: Verify that the MAC addresses of MES and SCADA are learning normally by logging in to the switch's backend and reviewing the ARP table. A failed ping does not necessarily indicate a link abnormality in the industrial environment if ICMP is disabled; prioritise the verification of security policy configurations.
Rapid Network Environment Verification: Ensure that there are no broadcast storms or network loops, that power lines and communication network cables are routed separately, and that there is no link packet loss caused by intense electromagnetic interference.
II. Rapid Communication Protocol Layer Troubleshooting (Completed in 10 minutes)
Verification of Protocol Compatibility: Ensure that the MES and SCADA interfacing protocols are entirely consistent, and that the OPC UA/MQTT driver version is compatible with the system firmware version to prevent handshake failures caused by version incompatibility.
Port Status Verification: Ensure that the dedicated communication ports for RC calibration data on both parties are open and not blocked by industrial firewalls, and that no other processes are occupying the ports.
Security Mode Verification: Ensure that the security policies and encryption levels of both ends of the OPC UA protocol are fully compatible to prevent connection rejection as a result of inconsistent security configurations.
III. Data Mapping Layer Quick Troubleshooting (Completed in 10 minutes)
Verification of Point Mapping: Ensure that the RC parameter register addresses and point IDs on both the MES and SCADA sides are fully aligned, with no address misalignment issues.
Data Format Verification: Ensure that the numerical type, unit, and decimal places of the RC calibration data on both sides are entirely consistent to prevent data parsing failures and garbled characters caused by format discrepancies.
Verification of Benchmark File Consistency: Compare the versions of the RC calibration benchmark parameters on both sides to verify that the pass thresholds and judgement rules are fully synchronised, with no version deviations.
IV. Rapid Troubleshooting of the Service and Application Layers (Completion in 10 minutes)
Service Status Check: Verify that the SCADA-side data acquisition service and the MES-side synchronisation scheduling service are functioning properly, with no process failures or frequent restarts.
Message Queue Status Check: Confirm that there are no queue congestion or message loss issues for RC calibration data by verifying the lag metrics of Kafka/RabbitMQ.
Database Status Check: Verify that there are no synchronisation timeouts, slow query backlogs, or connection pool exhaustion caused by lock contention.
V. Rapid Troubleshooting at the Concurrency Timing Layer (Completed in 5 minutes)
Synchronisation Task Priority Verification: Ensure that the RC calibration data synchronisation task is prioritised above the standard production data collection task and that there are no resource preemptions resulting in synchronisation delays.
Concurrency Conflict Troubleshooting: Verify that the polling interval configuration is reasonable and that there is no synchronisation request congestion while checking for timing conflicts caused by multiple devices simultaneously uploading data.
Log Backtracking and Location: Obtain the synchronisation service logs to directly identify the error code of the most recent synchronisation failure, thereby accurately identifying the root cause.
The RC calibration data synchronisation link can be rapidly restored by avoiding ineffective operations such as blindly restarting devices and unplugging and plugging network cables, and the entire troubleshooting process can complete 99% of synchronisation fault location within 40 minutes.
