Installation or license request
The installer link is sent after review. Starter needs no key. Trial and paid usage keys are issued separately after the Machine ID and requested scope are confirmed.
Support
Prepare one project, its Plant Test evidence, and the report together.
Before contacting Support, validate and save the current .modbussim project with its System design and Plant Test scenario. Send that project, the report, and the communication context required to reproduce the result.
First Response
Support first-response topics
Choose the path that matches the current question.
Technical support
Use Documentation first, then email the exact scenario and evidence if the problem remains.
Support Preparation Order
Prepare, validate, save, and send one reproducible engineering package.
Follow this order so Support can rebuild the same compressor system, run the Plant Test stored in the project, and compare the same result.
1. Prepare the portable project
- In Live System, select the exact compressor manufacturer, family, and model.
- Verify the engineering points and point mappings required by that compressor model.
- Set the number of compressors and define the circuits, water loops, and system topology.
- Apply the topology and compile the System project.
- Complete System Equipment assignments and confirm every required engineering point.
- Configure System Communication: protocol, adapter, endpoint, Unit ID, and register map.
- Review and activate the intended System, then save the shared design, configuration, and current Plant Test scenario in one .modbussim file.
2. Prepare and run Plant Test
- Open the saved .modbussim project that Support must reproduce and activate its reviewed System.
- Confirm the inherited design, then define timed Step or Ramp phases, mapped stimuli, optional alarm/fault or communication-error scenarios, and measurable acceptance limits.
- Validate the Plant Test preflight against the active System in the same project.
- Save the updated Plant Test scenario back into the .modbussim project before execution.
- Run the Plant Test and export the test report and complete evidence bundle.
3. Send to Support
- Selected compressor manufacturer, family, model, and total compressor count.
- Validated and saved .modbussim project containing the shared System design and current Plant Test scenario.
- Plant Test report and evidence bundle, including the frozen plan snapshot, trends, events, warnings, faults, and communication logs.
- For communication-error tests, identify the targeted adapter or endpoint, injection mode, Unit ID, expected response, and unaffected units used as controls.
- Application version, license scope, expected result, actual result, and exact reproduction steps.
- Sanitized connection details without credentials, private addresses, Machine IDs, or customer identifiers.
Common Questions
Cover the first support questions before email is needed.
These answers connect directly to the permanent guides.
What should I check before the first launch?
Confirm installation, the selected compressor and connection settings. Starter runs without activation; a key is needed only for the agreed paid usage or Engineering trial.
How do I confirm Modbus TCP communication?
Verify IP address, port, Unit ID, point map, and live values in Quick Start.
How do I confirm Modbus RTU communication?
Verify COM port, baud rate, parity, address, point map, and wiring path.
When should I use TT or VT setup?
Use the compressor family and model specified by the engineering data.
When should I use Compressor Behavior Model?
Use it for realistic, repeatable engineering validation with the selected compressor model.
How do I check a behavior CSV?
Review units, signal mapping, coverage, trends, and approved operating regions.
When can Configure Plant start?
Start it after I/O modules and compressors are selected and communication is live.
How do I validate system integrity?
Review and activate the intended System, then run the Plant Test stored in the same project and inspect its measurable criteria and evidence.
Can I use a virtual Modbus TCP adapter?
Yes. Use an isolated or loopback virtual adapter to bridge external PLC or controller modules to the configured Modbus TCP endpoints, and record its endpoint, Unit ID, and map.
Why does Plant Test report a project or design mismatch?
Plant Test uses the active System and shared design from the current .modbussim project. Activate the intended project, review any changed design reference, and run preflight again.
What belongs in a support request?
Include the version, final .modbussim project, endpoint and map, expected result, actual result, reproduction steps, report, and evidence bundle.
Are video tutorials available?
Use the published video cards below together with the related written guides.
What can I do with Test, and where do I see its limits?
Open License → What you can do with this license. Green Permitted badges identify available actions; amber Engineering required badges identify authoring actions. You can load prepared .modbussim projects, copy and run them, execute saved tests and export evidence. System design and test-scenario editing are read-only.
Can Test save a .modbussim file?
Yes. Copy prepared project preserves the source file unchanged. Save tested project adds completed test evidence to unchanged tested preparation. Saving a new system or changed preparation requires Engineering.
Video Answers
Published videos and the growing list of videos to prepare.
Published YouTube thumbnails keep their current logo. Planned topics use copies of the related application screenshots so a YouTube icon can be added later without changing pictures on other pages.
PublishedInstall and first launch
Request the Windows installer, install it, and open ModbusSim in permanent Starter with all tools. Activate a key only for a paid usage license or the optional Engineering trial.
PublishedStart Modbus TCP and connect a controller
Configure TCP and confirm the first live connection.
PublishedStart Modbus RTU and connect a controller
Configure RTU and confirm serial communication.
PublishedConfigure Compressor Behavior Model
Select and verify the compressor behavior used by the System project.
PlannedCreate the System project topology
Compose compressors, circuits, water loops, and plant modules in System Integration.
PlannedAssign System Equipment and engineering points
Map equipment, connections, and compressor-related engineering points.
PlannedInspect the Signal Logic canvas
Review compiled signal paths, transformations, and output ownership.
PlannedConfigure System Communication
Set protocol channels, endpoints, Unit IDs, maps, and controller exchange.
PlannedCompile and activate the System project
Apply topology, compile, review, and explicitly activate the intended project.
PlannedDefine the Plant Test and criteria
Use the inherited System design, then create the project scenario with timed phases, optional fault injections, and measurable acceptance criteria.
PlannedRun the project's Plant Test
Execute deterministic phases and retain synchronized evidence.
PlannedCheck the Plant Test result
Review criterion outcomes, trends, events, and the exported report.
PlannedAnalyze and tune the plant system
Compare bounded candidates and export an inactive tuning draft.
PlannedPackage a reproducible Support request
Send one .modbussim project, its Plant Test report and evidence, and the reproduction context together.
Next Step
Support connects back to documentation and the commercial path.
Use Quick Start for setup, Pricing for license choices, and Download for installer or trial requests.