Diehl Metering Diehl Metering SHARKY 775 Modbus RTU template

Diehl Metering SHARKY 775

Ultrasonic heat and cooling meter for energy, power, flow, volume and flow and return temperatures.

The Diehl Metering SHARKY 775 is an ultrasonic compact heat and cooling meter that measures thermal energy, power, flow and flow and return temperature, for example for greenhouse heat from CHP, geothermal and district heating. This Modbus RTU template reads energy, power, flow, temperatures, volume, tariff registers and the error code, and lets you set the module address, serial settings and update period from ModbusCloud.

Protocol
Modbus RTU
Connection
RS485, 9600 baud
Registers
108, read and write
Key readings
Energy · Power · Flow rate · Volume · Flow temperature · Return temperature · Temperature difference · Error code
Available commands
Modbus slave ID · Baud rate, parity and stop bits · Meter data update period · Periodic log 0
Compatible models
SHARKY 775 · SCYLAR INT 8 · Diehl Metering Modbus RTU communication module for SHARKY 775 and SCYLAR INT 8
Last updated

Registers (108)

108 read, 7 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
EnergyRead
Energy CoefficientRead
Energy UnitRead
Energy Unit CodeRead
Energy FloatRead
VolumeRead
Volume CoefficientRead
Volume UnitRead
Volume Unit CodeRead
Volume FloatRead
PowerRead
Power CoefficientRead
Power UnitRead
Power Unit CodeRead
Power FloatRead
FlowRead
Flow CoefficientRead
Flow UnitRead
Flow Unit CodeRead
Flow FloatRead
Flow Temperature°CRead
Flow Temperature UnitRead
Flow Temperature Unit CodeRead
Flow Temperature Float°CRead
Return Temperature°CRead
Return Temperature UnitRead
Return Temperature Unit CodeRead
Return Temperature Float°CRead
Temperature DifferenceKRead
Temperature Difference UnitRead
Temperature Difference Unit CodeRead
Temperature Difference FloatKRead
Error CodeRead
Tariff 1 EnergyRead
Tariff 1 Energy CoefficientRead
Tariff 1 Energy UnitRead
Tariff 1 Energy Unit CodeRead
Tariff 1 Energy FloatRead
Tariff 1 VolumeRead
Tariff 1 Volume CoefficientRead
Tariff 1 Volume UnitRead
Tariff 1 Volume Unit CodeRead
Tariff 1 Volume FloatRead
Tariff 2 EnergyRead
Tariff 2 Energy CoefficientRead
Tariff 2 Energy UnitRead
Tariff 2 Energy Unit CodeRead
Tariff 2 Energy FloatRead
Tariff 2 VolumeRead
Tariff 2 Volume CoefficientRead
Tariff 2 Volume UnitRead
Tariff 2 Volume Unit CodeRead
Tariff 2 Volume FloatRead
Tariff 3 EnergyRead
Tariff 3 Energy CoefficientRead
Tariff 3 Energy UnitRead
Tariff 3 Energy Unit CodeRead
Tariff 3 Energy FloatRead
Tariff 3 VolumeRead
Tariff 3 Volume CoefficientRead
Tariff 3 Volume UnitRead
Tariff 3 Volume Unit CodeRead
Tariff 3 Volume FloatRead
Tariff 4 EnergyRead
Tariff 4 Energy CoefficientRead
Tariff 4 Energy UnitRead
Tariff 4 Energy Unit CodeRead
Tariff 4 Energy FloatRead
Tariff 4 VolumeRead
Tariff 4 Volume CoefficientRead
Tariff 4 Volume UnitRead
Tariff 4 Volume Unit CodeRead
Tariff 4 Volume FloatRead
Pulse Input 1 VolumeRead
Pulse Input 1 Volume CoefficientRead
Pulse Input 1 Volume UnitRead
Pulse Input 1 Volume Unit CodeRead
Pulse Input 1 Volume FloatRead
Pulse Input 2 VolumeRead
Pulse Input 2 Volume CoefficientRead
Pulse Input 2 Volume UnitRead
Pulse Input 2 Volume Unit CodeRead
Pulse Input 2 Volume FloatRead
Periodic Log 0 DayRead
Periodic Log 0 MonthRead
Periodic Log 0 YearRead
Periodic Log 0 EnergyRead
Periodic Log 0 Energy CoefficientRead
Periodic Log 0 Energy UnitRead
Periodic Log 0 Energy Unit CodeRead
Periodic Log 0 Energy FloatRead
Periodic Log 0 VolumeRead
Periodic Log 0 Volume CoefficientRead
Periodic Log 0 Volume UnitRead
Periodic Log 0 Volume Unit CodeRead
Periodic Log 0 Volume FloatRead
Meter ID NumberRead
Meter ID ASCIIRead
Slave ID AddressRead and write
Meter Data Update PeriodsRead and write
Baud RateRead and write
Data BitsRead and write
ParityRead and write
Stop BitsRead and write
Periodic Log 0 EnableRead and write
Module Serial NumberRead
Module Model NumberRead
Module Firmware VersionRead

Loading registers…

Send your device list

If a device is not in the library yet, we build the template for free as soon as we have the register data.

Number of installations (optional)

Use cases

  • Show heat power, flow and flow and return temperature of each heat meter on a dashboard, for example per CHP unit, geothermal well or district heating connection.
  • Keep a year of energy and volume history to compare daily and monthly heat use per greenhouse section or heating circuit.
  • Get an email alert when the error code is no longer zero, so air in the flow sensor, a sensor fault, a leak or an empty battery is noticed quickly.
  • Set an alarm when the temperature difference or the power drops below a threshold you choose, for example to spot a heat source that delivers too little.
  • Download energy and volume readings as CSV for your own heat delivery reports.
  • Read the meter ID and module serial number remotely to match each meter to its location in your documentation.

Installation

  1. Fit the Modbus RTU module in a free module slot of the SHARKY 775 or SCYLAR INT 8 and connect it to the meter with the ribbon cable.

  2. Power the module from its own 12 to 24 V AC/DC SELV supply on terminals 60 and 61, with a cable shorter than 1 m and preferably a 100 mA fuse.

  3. Wire terminals 90 (+) and 91 (-) to the RS485 port of the ModbusCloud Gateway with twisted pair cable. Leave the shield unconnected and terminate both ends of the bus with 120 Ohm.

  4. Switch on before you close the meter. The status LED blinks once. With automatic addressing the slave ID is the last three digits of the meter serial number, for example 026 gives 26.

  5. In ModbusCloud, add a Modbus device with protocol RTU, that slave ID and 9600 8N1, import this template and compare Energy Float and the temperatures with the meter display.

Things to watch for

The module does not answer. What should I check?

Check the module supply on terminals 60 and 61 and the RS485 wiring on 90 (+) and 91 (-). The default is 9600 baud, 8 data bits, no parity, 1 stop bit. With automatic addressing meter 51241026 answers on 26. Endings above 247 use the last two digits, and 000, 247 to 250 or 00 give 247. Holding the module button for at least 15 seconds restores the defaults.

Why do energy, volume, power and flow have no unit?

The module reports each value in the unit that follows from the meter resolution, which is not always the unit on the display. A meter that shows 12.345 GJ can report 12345 MJ. Read the Unit or Unit Code register of that value once, for example 3 = kWh, 8 = MJ, 19 = l, 27 = m³/h or 34 = kW, and enter that unit on the register in ModbusCloud.

Should I use the integer values or the float values?

The integer values are exact, but you multiply them by the Coefficient register of the same value. The float values are calculated by the module and can differ slightly from the display, but they are ready to use. For dashboards and alarms the float is the easiest choice, for billing use the integer.

The meter display shows error 5 or the Error Code reads E-5. What now?

The module reads the meter once per update period, 60 seconds by default. On a battery powered meter, set Meter Data Update Period above 3 minutes, so a value above 1800. A longer period also solves E-5, a data buffer overflow. A period of 0 stops the meter reading, so the values no longer change.

Can I change the address or serial settings from ModbusCloud?

Yes, the configuration registers are writable. Read them first. After a change of slave ID, baud rate, parity or stop bits, set the same values on the Modbus device in ModbusCloud, otherwise the module no longer answers. A static address 5 is the value 5, with automatic addressing off. Writing is off per gateway by default, so request it for the gateway in the portal first.

More RTU templates

Want to see how it works?

Electrician working in an open distribution board