Hive AutomationTools
All tools / H-Modbus / Installation
Protocol testing & simulation

Install H-Modbus

A Windows workbench for Modbus TCP/RTU and OPC UA/DA. Read real servers, simulate registers for a PLC and edit values directly in the register table.

  1. Download and extract

    Download the Windows x64 ZIP and extract the complete folder to a location you can keep. The .NET runtime is included; no separate runtime installation is needed.

    Download Windows ZIP

  2. Open H-Modbus

    Run H-Modbus.exe from the extracted folder. When updating, close the older app first and keep your saved .hmodbus workspaces. Use the Windows account that owns the activation.

  3. Activate your license

    Online once: enter your customer/company and device name, choose Request online, and ask your administrator to grant H-Modbus at lic.hiveautomation.in. Then choose Activate online.

    Completely offline: choose Export request. Transfer the .hiverequest file to your administrator, who imports it in License Manager and returns a signed .hivelicense file. Transfer it back and choose Import license.

    A perpetual activation runs offline without a grace period or recurring license check. Optional expiry dates still apply. Later license updates can be imported using the app's License button.

  4. Run a local test

    Click Run local loopback to start a local TCP simulator and client. Read holding register 40001, choose a Data Type and double-click its Value to edit. Enter or Tab applies an edit; Esc cancels it.

    The table shows Address, Data Type, Value and Health. Select normal Float32 / Float64 or Swapped Float32 / Swapped Float64 per address. Swapped floats reverse the 16-bit register words. Device writes verify readback.

  5. Connect your devices

    • Add named TCP profiles to connect and poll multiple servers independently.
    • Use separate COM ports for independent RTU master buses. Targets on one port share a serialized master; a physical RS-485 bus needs one active master.
    • Use OPC UA certificates for secure sessions. OPC DA uses Windows COM and requires suitable OPC Core Components; remote DA also needs the site's DCOM configuration.
    • Use Tools for trends, recording/replay, test sequences, reports, mappings and simulator faults.

    The software is ready for bench testing and commissioning. Verify physical PLC/RTU connections and remote OPC DA with the intended equipment before production use.