Select devices, define the shared System design, and establish controller exchange first. Then compile and activate the integrated plant, run the Plant Test stored in the same project, review its evidence, and analyze completed behavior before proposing draft tuning.
System Integration defines and activates the HVAC system; Plant Test verifies that exact system with a scenario stored in the same portable project.
Use one .modbussim project to compose compressor, circuit, economizer, water-confirmation, I/O, protocol, alarm, and monitoring logic without duplicating fixed logic views.
Open GuideUse the Plant Test scenario stored in the active .modbussim project, run deterministic Step and Ramp phases, evaluate measurable criteria, preserve the complete evidence bundle, and analyze completed behavior before proposing draft tuning.
Open GuideUse Quick Start for the first PLC endpoint, Engineering Workflow for the release path, Control Quality Monitor for observation, Behavior Model for tuning, and Release and Migration Checks for baseline protection.
Install ModbusSim, select the devices, bind a physical, virtual, or loopback adapter, and confirm the first controller-facing Modbus endpoint.
Open GuideUse one portable .modbussim file as the normal engineering package. It carries the shared System design, equipment, communication, behavior assets, and current Plant Test scenario; standalone .modbustest files remain available for import and evidence snapshots.
Open GuideUse Control Quality Monitor for live trends, timing, and event investigation. The Plant Test runner remains responsible for timed phases, measurable criteria, and the acceptance outcome.
Open GuideBehavior editing is a supporting engineering task, not the first plant-workflow page.
Open GuideRepeat integration, simulation, and acceptance testing after code, topology, migration, behavior, or communication changes; each approved .modbussim project keeps its own Plant Test scenario.
Open GuideContinue through the matching product, download, or support path.