Installation or license request
For installer access and 14-day trial keys, use the Download page. The trial key is generated after the Machine ID is reviewed.
The support page should handle installation and first launch, network and Modbus connection checks, TT versus VT setup, behavior model guidance, CSV trend-preview review, and where to send reports or logs when direct help is needed.
The fastest support path is a clear description, the release number, the active compressor type, and screenshots or exported reports from the test.
For installer access and 14-day trial keys, use the Download page. The trial key is generated after the Machine ID is reviewed.
For connection or behavior questions, send a short support package so the issue can be reproduced or reviewed without several back-and-forth emails.
These FAQ items should become the base support stack. Keep the same questions in every language and localize only the wording, screenshots, and video links.
Confirm Windows 10 or Windows 11, install the current release, keep the configuration folder available, and start with the Quick Start guide before connecting a real controller.
Start the Modbus server, confirm the IP address and port, allow the application through the firewall if needed, then read a known live register from the external controller or a test client.
Check the COM port, baud rate, parity, data bits, stop bits, station address, and cable adapter. Use one known register read before running a full compressor scenario.
Choose the compressor family that matches the controller project. TT and VT have different behavior data, limits, warning/fault mappings, and setup details.
Use it for normal engineering validation when the external controller must see believable startup, running, unload, warning, fault, and reset responses.
Use Open CSV for the selected behavior source. In Open Trend of Selected CSV, check the demand-based trends for smooth RPM, power, pressure, temperature, and superheat movement. Reject files with repeated vertical bands, jumps, heavy oscillation, mixed states, or staging transitions; ask for a cleaner service log when the trend cannot support believable behavior.
Use replay when you need to reproduce one recorded event as a reference. It is not the best choice when the controller must freely change demand outside the captured sequence.
Use it as a fast connection and coarse response check when the behavior model is not ready. Do not treat it as the final compressor realism target.
Send release number, compressor type, controller/client used, scenario, expected result, actual result, exported report, relevant logs, configuration files, and screenshots of the active view.
The install and first launch, Modbus TCP, and Modbus RTU tutorials are available now. More video tutorials will be added as they are published; use the written guides and send a support request when a project needs direct help.
Use these tutorials to review installation, first launch, controller connections, behavior setup, CSV source review, monitoring, and support-package workflows.
Show the first-use path from installer to first communication check.
Walk through TCP setup, controller connection, and the first visible live values.
Walk through RTU setup, serial connection checks, and the first visible live values.
Explain the practical modeling strategy, when a prepared CSV is good enough to train, and where estimated anchors are useful.
Show the key differences that matter for the first working scenario.
Focus on signal presets, event timing, and what pass, watch, and fail mean.
Show which files, screenshots, and descriptions make remote support efficient.
Visitors should be able to move from support to quick-start docs, pricing clarification, or download without losing context.