Modbus 模擬器 - 文檔
Simulation Modes — From Simple to Digital Twin
The Modbus System Simulator offers three simulation modes, representing a progression from the simplest approach to the full system digital twin:
Figure 4 — Training workflow and three simulation modes — from Formula to Digital Twin
Formula-Based (default)
Uses mathematical equations to calculate register values from demand input. No training data is required. This mode is available immediately after installation and is suitable for basic connectivity testing and initial SCADA development. Think of it as one step above a static Modbus tool — the values change with demand, but they follow generic equations, not your system's real behaviour.
Table-Driven
Loads a CSV file exported from your real system and replays it row by row in real time. Every recorded value is placed into the corresponding Modbus register exactly as it was captured. This mode reproduces a specific operational recording perfectly, but it can only replay what was recorded — it cannot respond to new demand inputs or create new scenarios.
State-Based (the full Digital Twin — recommended)
The most powerful mode. Your CSV logs are processed by the training engine, which analyses the data, detects operational states, and builds interpolation tables that capture the real relationships between all parameters. At runtime, a six-state machine drives the simulation — responding dynamically to demand changes, producing realistic start-up ramps, steady-state variation with load regimes, and coast-down profiles. This is the digital twin of your system.
The progression is intentional: Formula-Based gets you started immediately; Table-Driven lets you replay real data; State-Based creates a living copy that responds to any scenario.
5. The State Machine — Living Behavior
When State-Based Simulation is enabled, each compressor unit operates through a six-state machine that enforces realistic operational sequences:
Figure 5 — Compressor state machine — six states with transition conditions and timing rules
|
State |
What Happens |
Data Source |
|
IDLE |
System is off. Ambient conditions, zero RPM and power. Pressures equalize. |
Demand-based lookup |
|
STARTING |
Start-up ramp. RPM, power, and pressures rise from standstill to operating levels. |
Time-based lookup |
|
RUNNING |
Steady-state operation. All values respond dynamically to demand percentage. |
Demand-based lookup |
|
STOPPING |
Coast-down. Values decay from running levels to ambient. |
Time-based lookup |
|
FAULT |
Protective shutdown. Interlock opens, RPM decays. |
Deterministic |
|
POWER_INTERRUPTING |
Voltage loss. RPM coasts down with no electrical braking. |
Deterministic |
A real compressor does not jump instantly between states. The state machine reproduces these real transition dynamics, including stability detection, minimum dwell times, transition blending, and per-signal dynamics.
Simulation Modes — From Simple to Digital Twin
The Modbus System Simulator offers three simulation modes, representing a progression from the simplest approach to the full system digital twin:
Figure 4 — Training workflow and three simulation modes — from Formula to Digital Twin
Formula-Based (default)
Uses mathematical equations to calculate register values from demand input. No training data is required. This mode is available immediately after installation and is suitable for basic connectivity testing and initial SCADA development. Think of it as one step above a static Modbus tool — the values change with demand, but they follow generic equations, not your system's real behaviour.
Table-Driven
Loads a CSV file exported from your real system and replays it row by row in real time. Every recorded value is placed into the corresponding Modbus register exactly as it was captured. This mode reproduces a specific operational recording perfectly, but it can only replay what was recorded — it cannot respond to new demand inputs or create new scenarios.
State-Based (the full Digital Twin — recommended)
The most powerful mode. Your CSV logs are processed by the training engine, which analyses the data, detects operational states, and builds interpolation tables that capture the real relationships between all parameters. At runtime, a six-state machine drives the simulation — responding dynamically to demand changes, producing realistic start-up ramps, steady-state variation with load regimes, and coast-down profiles. This is the digital twin of your system.
The progression is intentional: Formula-Based gets you started immediately; Table-Driven lets you replay real data; State-Based creates a living copy that responds to any scenario.
5. The State Machine — Living Behavior
When State-Based Simulation is enabled, each compressor unit operates through a six-state machine that enforces realistic operational sequences:
Figure 5 — Compressor state machine — six states with transition conditions and timing rules
|
State |
What Happens |
Data Source |
|
IDLE |
System is off. Ambient conditions, zero RPM and power. Pressures equalize. |
Demand-based lookup |
|
STARTING |
Start-up ramp. RPM, power, and pressures rise from standstill to operating levels. |
Time-based lookup |
|
RUNNING |
Steady-state operation. All values respond dynamically to demand percentage. |
Demand-based lookup |
|
STOPPING |
Coast-down. Values decay from running levels to ambient. |
Time-based lookup |
|
FAULT |
Protective shutdown. Interlock opens, RPM decays. |
Deterministic |
|
POWER_INTERRUPTING |
Voltage loss. RPM coasts down with no electrical braking. |
Deterministic |
A real compressor does not jump instantly between states. The state machine reproduces these real transition dynamics, including stability detection, minimum dwell times, transition blending, and per-signal dynamics.
Simulation Modes — From Simple to Digital Twin
The Modbus System Simulator offers three simulation modes, representing a progression from the simplest approach to the full system digital twin:
Figure 4 — Training workflow and three simulation modes — from Formula to Digital Twin
Formula-Based (default)
Uses mathematical equations to calculate register values from demand input. No training data is required. This mode is available immediately after installation and is suitable for basic connectivity testing and initial SCADA development. Think of it as one step above a static Modbus tool — the values change with demand, but they follow generic equations, not your system's real behaviour.
Table-Driven
Loads a CSV file exported from your real system and replays it row by row in real time. Every recorded value is placed into the corresponding Modbus register exactly as it was captured. This mode reproduces a specific operational recording perfectly, but it can only replay what was recorded — it cannot respond to new demand inputs or create new scenarios.
State-Based (the full Digital Twin — recommended)
The most powerful mode. Your CSV logs are processed by the training engine, which analyses the data, detects operational states, and builds interpolation tables that capture the real relationships between all parameters. At runtime, a six-state machine drives the simulation — responding dynamically to demand changes, producing realistic start-up ramps, steady-state variation with load regimes, and coast-down profiles. This is the digital twin of your system.
The progression is intentional: Formula-Based gets you started immediately; Table-Driven lets you replay real data; State-Based creates a living copy that responds to any scenario.
5. The State Machine — Living Behavior
When State-Based Simulation is enabled, each compressor unit operates through a six-state machine that enforces realistic operational sequences:
Figure 5 — Compressor state machine — six states with transition conditions and timing rules
|
State |
What Happens |
Data Source |
|
IDLE |
System is off. Ambient conditions, zero RPM and power. Pressures equalize. |
Demand-based lookup |
|
STARTING |
Start-up ramp. RPM, power, and pressures rise from standstill to operating levels. |
Time-based lookup |
|
RUNNING |
Steady-state operation. All values respond dynamically to demand percentage. |
Demand-based lookup |
|
STOPPING |
Coast-down. Values decay from running levels to ambient. |
Time-based lookup |
|
FAULT |
Protective shutdown. Interlock opens, RPM decays. |
Deterministic |
|
POWER_INTERRUPTING |
Voltage loss. RPM coasts down with no electrical braking. |
Deterministic |
A real compressor does not jump instantly between states. The state machine reproduces these real transition dynamics, including stability detection, minimum dwell times, transition blending, and per-signal dynamics.
Simulation Modes — From Simple to Digital Twin
The Modbus System Simulator offers three simulation modes, representing a progression from the simplest approach to the full system digital twin:
Figure 4 — Training workflow and three simulation modes — from Formula to Digital Twin
Formula-Based (default)
Uses mathematical equations to calculate register values from demand input. No training data is required. This mode is available immediately after installation and is suitable for basic connectivity testing and initial SCADA development. Think of it as one step above a static Modbus tool — the values change with demand, but they follow generic equations, not your system's real behaviour.
Table-Driven
Loads a CSV file exported from your real system and replays it row by row in real time. Every recorded value is placed into the corresponding Modbus register exactly as it was captured. This mode reproduces a specific operational recording perfectly, but it can only replay what was recorded — it cannot respond to new demand inputs or create new scenarios.
State-Based (the full Digital Twin — recommended)
The most powerful mode. Your CSV logs are processed by the training engine, which analyses the data, detects operational states, and builds interpolation tables that capture the real relationships between all parameters. At runtime, a six-state machine drives the simulation — responding dynamically to demand changes, producing realistic start-up ramps, steady-state variation with load regimes, and coast-down profiles. This is the digital twin of your system.
The progression is intentional: Formula-Based gets you started immediately; Table-Driven lets you replay real data; State-Based creates a living copy that responds to any scenario.
5. The State Machine — Living Behavior
When State-Based Simulation is enabled, each compressor unit operates through a six-state machine that enforces realistic operational sequences:
Figure 5 — Compressor state machine — six states with transition conditions and timing rules
|
State |
What Happens |
Data Source |
|
IDLE |
System is off. Ambient conditions, zero RPM and power. Pressures equalize. |
Demand-based lookup |
|
STARTING |
Start-up ramp. RPM, power, and pressures rise from standstill to operating levels. |
Time-based lookup |
|
RUNNING |
Steady-state operation. All values respond dynamically to demand percentage. |
Demand-based lookup |
|
STOPPING |
Coast-down. Values decay from running levels to ambient. |
Time-based lookup |
|
FAULT |
Protective shutdown. Interlock opens, RPM decays. |
Deterministic |
|
POWER_INTERRUPTING |
Voltage loss. RPM coasts down with no electrical braking. |
Deterministic |
A real compressor does not jump instantly between states. The state machine reproduces these real transition dynamics, including stability detection, minimum dwell times, transition blending, and per-signal dynamics.
© 2026 modbussim.com
