System configuration
Select compressor models and I/O devices, connect their points and logic, and configure Modbus channels and register maps. Review the design, equipment, and protocol before activation.
Read the guideSupport
Configure your system. Test its response.
Understand system and plant configuration, controller testing, and Plant Test scenarios. Find the right license for your work and help for your next step.
The workflow
Four tasks. One connected project.
Configuration defines what you test. Testing applies conditions and checks the response.
Plant configuration
Arrange compressors, circuits, water loops, and heat-rejection equipment. Set design capacity, temperatures, fluid properties, and flows. Keep cooling capacity separate from electrical input.
Read the guideSystem testing
Verify commands, feedback, scaling, startup, proofs, staging, and recovery through the active controller connection. Follow the response in Home and Control Monitor.
Read the guidePlant Test
Apply timed Step or Ramp loads to the configured system. Define acceptance criteria, run the scenario, then inspect trends, events, and the report.
Read the guidePlant Test inherits the system design. In larger building/campus scenarios, water-loop demand, storage, and other-chiller contribution define the test environment; the machine rating stays in System design.
Project demonstrations
See a project from creation to results.
The ModbusSim YouTube channel includes introductory tutorials. We are preparing the complete project demonstrations below; video links will be added as they are published.
Create and test an air-cooled system
Configure compressors, circuits, water design, and fan banks; connect the controller and review a load test.
Video plannedRead the guideCreate and test a water-cooled system
Configure water loops and heat rejection, verify flow proofs and staging, then evaluate the test results.
Video plannedRead the guideTest a chiller within a larger plant load
Explore building/campus water-loop demand, storage, and other-chiller contribution alongside the tested machine.
Video plannedRead the guideFind a fault and verify the correction
Observe a supported fault case, revise the preparation under Engineering, and compare the next run with its evidence.
Video plannedRead the guideDeliver a project to a Test user
Create the project under Engineering, then open a copy under Test, run its saved scenario, and retain the results.
Video plannedRead the guide
Each demonstration will connect configuration, testing, and evidence to the work permitted by the license. Written guides are available now.
License selection
Choose the license for the work you do.
Every edition installs the same modules. The License page shows permitted actions; equipment count and project size are not edition limits.
Learn and evaluate
Permanent and free, with no activation key. Authoring tools remain available for learning and evaluation.
Run prepared projects
Open, copy, validate, activate, and run prepared projects. Adjust local TCP/serial settings, export evidence, and save tested copies with unchanged preparation. System and test authoring remain read-only.
Create and deliver projects
Create and edit systems, models, mappings, logic, and test/fault scenarios. Save changed preparation and deliver a project that another user can run.
When should I choose Engineering?
Choose Engineering when you create or change systems, equipment, behavior models, mappings, logic, or test scenarios for development and project delivery. Choose Test to execute prepared projects. Starter supports learning and evaluation.
Test and Engineering are priced by quotation. Duration, machine scope, release coverage, and support are agreed separately. An optional 14-day Engineering trial is issued manually for your Machine ID.
Describe your intended work, request a trial or quotation, then provide your Machine ID through the license-request process and activate the issued key.
Practical help
Find help for your current task.
Open a question below or press F1 in the application for the searchable offline manual.
How do I get started?
Request the Windows installer, then start in permanent Starter without a key. A trial or paid usage key is issued separately.
Read the guideHow do I check TCP or RTU communication?
Match the controller endpoint, Unit ID, and register map. For TCP, check address and port; for RTU, check COM port, baud rate, parity, and wiring. Compare live values and their units.
Read the guideWhen do I configure the plant?
Prepare the design and equipment in the draft. Validate, review, and explicitly activate it; confirm the required communications and controller readiness before a controller-driven run.
Read the guideWhy did validation or test preflight fail?
Read the first diagnostic. Check project identity, design changes, equipment bindings, signal ownership, and required connections. Correct the preparation under Engineering, or ask its author if you use Test.
Read the guideWhere are my results and test evidence?
Review Plant Test Results and each criterion, then export the report and retain the complete run evidence. A completed timeline alone does not establish a pass. Test can save a tested copy with unchanged preparation.
Read the guideContact
Tell us where you need help.
You can contact us before choosing a license or preparing a complete project.
Installation or license questions
Describe the question and your intended work. Include the application version if available; a project package is not required.
A technical issue
Start with the expected result, actual result, reproduction steps, and first error. Include the relevant project and report if available.
What to include for a project or test issue
- Application version, usage edition, and exact steps to reproduce the issue.
- A copy of the relevant .modbussim project. With Test, send the prepared project or tested copy with unchanged preparation.
- The complete relevant run evidence and report, including scenario, samples, events, and result.
- Relevant controller and connection context: endpoint, Unit ID, map, and logs. Remove license keys, credentials, and confidential customer data before sharing.
Keep the recorded run evidence separately: a later project save may contain newer settings. The external controller program is not automatically included in a .modbussim project.