Simulating Network Failures in Multi-PLC Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional PLC software simulators do not support simulation of multiple PLCs in a network, lacking the ability to test applications before real network installation and failing to generate network-related failures for communication monitoring and testing.
Innovation Solution
A method to simulate multiple PLCs in a network, allowing for monitoring and testing of communication between nodes, including the generation of network-related failures such as single node failures, wire failures, and communication overloads, using a graphical network view interface to induce and manage these conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional PLC software simulators are used, then single PLC simulation is possible, but multiple PLCs in a network cannot be simulated
Solution Approach 1:
The system segments the network simulation into individual node simulations, where each PLC is simulated as a separate entity with its own processor and I/O modules. These segmented nodes are then interconnected through a virtual network backbone, allowing multiple PLCs to be simulated independently yet cooperatively within the same network environment.
Solution Approach 2:
The simulator implements a universal node structure that can represent different PLC types (e.g., S7-300, S7-400, S7-1200) through a common interface framework. Each node type inherits from a base class, enabling the same simulation engine to handle diverse PLC architectures, communication protocols, and I/O configurations through a unified multi-functional platform.
2Reliability
If network simulation is implemented, then communication testing is enabled, but the ability to generate and monitor network failures is lost
Solution Approach 1:
The network connection objects implement dynamic state management, allowing connections to transition between normal, degraded, and failed states. Failure conditions can be programmed into the connection logic, enabling automatic failure generation and recovery scenarios. The system dynamically adjusts connection status based on simulated error conditions, providing realistic failure modeling for reliability testing.
Solution Approach 2:
The simulator incorporates comprehensive feedback mechanisms that monitor communication status between all network nodes in real-time. Error detection and diagnosis systems provide feedback about network health, allowing operators to observe failure propagation, test error handling procedures, and verify system resilience. Communication monitoring feedback enables detailed analysis of network behavior under various failure conditions.
3Manufacturing precision
If pre-installation testing is performed, then installation errors can be detected, but extensive network equipment is required
Solution Approach 1:
The system creates virtual copies of physical PLCs, network devices, and communication infrastructure within the simulation environment. These digital twins replicate the electrical and communication behavior of actual hardware, enabling comprehensive pre-installation testing without requiring physical equipment. The virtual network model preserves all critical interaction characteristics needed for valid installation verification.
Solution Approach 2:
The simulator allows dynamic modification of network parameters such as communication speeds, packet sizes, timing characteristics, and error rates. These parameter changes enable testing of various network configurations and stress conditions without physical reconfiguration. Users can adjust simulation parameters to match different hardware scenarios, providing flexible pre-installation validation across multiple equipment types.
Data Source
AI summary
A system and method for simulating a stress or failure in a network of a plurality of simulated networked program logic controllers includes simulating a plurality of networked program logic controllers in a network, the networked program logic controllers each having network information defining a node, the network information being selected from a type of program logic controller, an I/O connected to the program logic controller and a type of connection for the program logic controller; providing an interface in communication with each of the networked program logic controllers for simulating a network error; and activating the interface for inducing one of a stress or failure in the network.