DOCSEARCHbyAlgolia
Submit Docs

MHO Engineering Documentation

website·Indexed 31 days ago

https://docs.mhoeng.com

Technical documentation for MHO Engineering products, including the MHO Keeper 3 IoT/IIoT acquisition line (models KP308A and KP316A), SPD1-2S surge protection devices, and various simulation tools like the 4DIDO digital I/O simulator and DevKit1.

Tokens
47K
Snippets
234
Records
421
Agent score
50%

What's inside MHO Engineering

  1. Overview of MHO Cloud Telemetry Solution

    MHO Cloud is an IoT-based telemetry solution designed for electrical panels (protection or control). It provides a scalable system for remote monitoring of small to large systems, characterized by low installation complexity. The ecosystem consists of two primary components: the MHO Cloud cloud platform and the MHO Keeper line of data acquisition products.

  2. Overview of MHO SPD1-2S Surge Protection Line

    The SPD1-2S line provides two-stage protection (gas discharge tube + TVS) against atmospheric discharges and surges for devices in LPZ 0-2 installations or higher. These ultra-slim modules (7mm width) are designed for IoT/IIoT and industrial automation applications, covering serial communications, analog signals, and digital signals. They comply with international standards IEC 61643-21, EN 61643-21, and GB/T 18802.21.

  3. Overview of MHO Keeper 3 IoT Equipment

    MHO Keeper 3 is a line of IoT equipment designed for data acquisition and writing. It is used for telemetry, monitoring, and control, making it suitable for any application in control or protection panels that requires remote or local monitoring and control capabilities.

  4. Overview of SPD1-2S-5RS-3W-I Surge Protection Device

    The SPD1-2S-5RS-3W-I is a surge and lightning protection device specifically designed for RS-422 and RS-485 communication ports. It protects three lines plus a shield (A, B, COM, and shield) and is commonly used to protect the RS-485 port of MHO Keeper or similar industrial devices. It features a two-stage protection mechanism consisting of a gas spark gap and TVS (Transient Voltage Suppressor).

  5. Overview of SPD1-2S-24-3W-I Surge Protection Device

    The SPD1-2S-24-3W-I is a surge protection device designed for systems up to 24V with up to 3 non-grounded lines. It is specifically used to protect devices utilizing 2 or 3 cables, such as 4-20 mA loops or 24V digital signals. It is recommended for protecting AI, DI, and DO ports on the MHO Keeper (protecting 3 lines + shield: +, -, SIGNAL, and shield).

  6. Overview of Effluent Pumping Station (EEE) Automation

    The automation of effluent pumping stations involves using the MHO Keeper as an edge controller for data collection and local control, integrated with MHO Cloud for remote visualization and management. The primary goal is to monitor effluent levels, pump status, and failure alarms to ensure operational efficiency.

  7. Overview of SPD1-2S-24-2W Surge Protection Device

    The SPD1-2S-24-2W is a surge protection device designed to protect two individual non-grounded lines in 24V systems with a direct connection to ground. It is typically used to protect devices utilizing two cables, such as 4-20 mA loops or 24V digital signals (transmitters/sensors). For indirect grounding applications, it must be used in conjunction with the SPD1-2S-24-3W-I.

  8. Overview of MHO Cloud M2M Communication

    Machine-to-Machine (M2M) communication in the MHO ecosystem occurs via MQTT through the MHO Cloud platform. It allows direct communication between devices with data context isolation to ensure information is only exchanged between permitted devices.

    Key Characteristics:

    • Scalability: No limit on the number of devices.
    • Range: Works globally as long as devices have internet access.
    • Architecture: Asynchronous Pub/Sub model.
    • Latency: Typical latency is 1 to 5 seconds (approximately 3 seconds average).

    Usage Constraint: Due to the internet-based processing via MHO Cloud, this should only be used for slow systems or those that can tolerate a delay of up to 5 seconds. For real-time requirements, local communication protocols like Modbus RTU are recommended.

  9. Understand the platform hierarchy and permission model

    The platform uses a tree-based hierarchy of clients and sub-clients. Permissions are granted from the top down: a superior entity has access to all inferior entities, but inferior entities cannot access superior ones or peer entities at the same level. Each block in this hierarchy contains three primary entity types: Devices, Users, and Dashboards.

  10. Configure MHO Keeper as a Modbus Server

    The MHO Keeper can be configured as a Modbus Server to act as a bridge for remote monitoring and configuration. In this mode, a Modbus Client (typically a PLC) sends telemetry requests, reads data, and commands the Keeper's I/O.

    Data Interpretation Requirements for Clients:

    • Addressing: Uses base 0. If the client device uses a different base, addresses must be shifted accordingly.
    • Endianness: Data is transmitted in big-endian format. Clients using different formats must implement Word-Swap or Byte-Swap manipulations.

  12. Configure MHO Keeper as a Modbus RTU Server

    The MHO Keeper can be configured as a Modbus Server (Slave) to allow a Modbus Client to monitor and configure the device remotely.

    Key Technical Specifications:

    • Addressing: Base 0 (addresses start at 0 in the Modbus request message).
    • Endianness: Big-endian by default. Word-swap, byte-swap, and doubleword-swap options are available to enable little-endian or other formats.
    • Data Sync: Digital characteristics are sent to the server (MHO Cloud or private server) instantly; analog characteristics are sent based on a configured time interval.