I. Solutions for Physical Network Layer Faults
Cable/RJ45 Connector Failure: Replace the cable with a spare shielded industrial network cable, re-crimp the RJ45 connector, and verify that the Link indicator light on the network port is illuminated.
Switch Port Failure: In an effort to re-establish connectivity, switch the communication cable to a spare, unused port, reconfigure the port VLAN, and bypass the faulty port.
Electromagnetic Interference Packet Loss: Quickly decrease the link packet loss rate by replacing the cable with a high-grade shielded industrial network cable, adjusting the cable routing to avoid power lines.
Network Loop/Broadcast Storm: Disable the switch loop detection function, disconnect redundant links, and release saturated network bandwidth.
II. Solutions for Faults in the Communication Protocol Layer
Protocol Version Incompatibility: Restore the handshake connection by upgrading or downgrading the OPC UA/MQTT driver version on one end to match the firmware version on the other end.
Firewall-Blocked Port: Implement a rule to permit access to the industrial firewall's designated port for RC calibration data; communication can be re-established without the need to restart the firewall.
Security Policy Incompatibility: To prevent the rejection of handshake connections, it is necessary to unify the security policies and encryption levels of the OPC UA on both endpoints. Modify the conflicting IP address to an available network segment, reconfigure routing rules, and restore network connectivity at both endpoints in the event of an IP address conflict.
III. Solutions for Faults in the Data Mapping Layer
Point Address Misalignment: To eliminate the necessity for manual register address modification, import a pre-backed-up RC parameter point mapping configuration file to overwrite incorrect configurations with a single click.
Data Format Mismatch: In order to resolve distorted characters in the data, invoke a preset RC calibration data format conversion script to automatically align the numerical types and decimal places on both sides.
Benchmark File Version Deviation: Utilise a one-click synchronisation script to transfer the most recent RC calibration benchmark parameters from the MES to the SCADA, ensuring that the version alignment is completed within one minute.
Data Semantic Missing: Assign data quality identifiers to RC calibration data to guarantee that synchronised data can be directly utilised for process judgement.
IV. Fault Solutions for the Service Operation Layer
Crash of the Synchronisation Service Process:** Restore service operation within 30 seconds by restarting the SCADA data acquisition service and MES synchronisation scheduling service with a single click, without the need to restart the entire machine.
Message Queue Accumulation: Temporarily clear non-core historical production data messages to prioritise the consumption channel for RC calibration data and alleviate queue congestion.
The database connection pool service has reached its maximum capacity. To release idle connections and promptly resume write operations for synchronised data, restart the service.
Insufficient system resources: Temporarily suspend non-core background statistics tasks to free up CPU and memory resources, thereby ensuring priority scheduling for RC calibration data synchronisation tasks.
V. Solutions for Faults in the Concurrent Timing Layer
Synchronisation request congestion: To prevent the timing pandemonium that can result from concurrent conflicts, it is recommended that the upload times of RC calibration data from multiple devices be staggered.
Excessive timestamp deviation: Enable the PTP/NTP unified time synchronisation mechanism to regulate the time deviation between MES and SCADA within 1ms, thereby guaranteeing the precise matching of interrupted data transmission.
Low priority of synchronisation tasks: In order to prevent the preemption of RC calibration data synchronisation tasks by ordinary production data acquisition tasks, set the priority of these tasks to the highest possible level.
High polling load: Reduce system load by enabling the data change notification mechanism to initiate synchronisation only when RC calibration data changes.
VI. Long-Term Preventive Optimisation Solution
Implement a real-time monitoring dashboard to monitor the synchronisation status, which will immediately activate audible and visual alarms in the event of an abnormal synchronisation link. This will enable the early detection of potential issues.
Establish an automatic resume mechanism that will automatically retransmit any missing data following a network recovery, without the need for manual intervention.
Regularly conduct comprehensive RC calibration data reconciliation to identify data discrepancies early and prevent the escalation of faults that could affect production..
