EvoControl Ventilation Touch Display

ModBus can be used to communicate with the unit, it can be read and written.

Because it is needed:

• One ModBus programme or another way to run ModBus (there are many available to download online; see example).
• IP addresses to the unit: found in System info on the unit or on EvoCloud.
• Which register the person you want to read to or write to: can be found in parameter list.
• For writing: Which value to write: found in parameter list.
• For reading: how many records you want to read at a time.
• Modbus via TCP/IP (RJ45), std. port 502.

Parameter list

In the parameter list there is a column “ModBus” which tells you which type of register the parameter belongs to (3 or 4) and whether the parameter is available for ModBus.

• 3 = Input register (Read).
• 4 = Holding register (Read / Write).

For address to register in ModBus, the following applies:

• Register address = Parameter id +1
• (Ex. id 1000 => address 1001).

Example to change the operating mode to Comfort:

• IP address: 192.168.1.54
• Port: 502
• Register address: 1011
• Value: 3

Extraction from the parameter list:

Values are normally sent as int16.

Some parameters with larger numbers (int32) utilise the next higher parameter id number as high number, marked with “ModBus” in the parameter list.

For example, if you want to read the operating time below, you have to read both parameter 1200 and 1201, as the value spans both.

Values with decimal are shown as the value*10 (1 decimal place), marked with “Decimal” in the parameter list (Ex Temperature TL, id 1110 sends value 210 for 21.0°C).

The function codes are defined on modbus.org.

EvoControl can use the following function codes:

See parameter list for more.

New parameter Id for “Time clock” (Id 8000->) and “Alarm / Alarm history” (Id 9000->) as of 2024-10-22.

Blocks of parameters cannot be read out if any parameter in the block is missing!

Troubleshooting:
Check that the network is up and running and you have an IP address in the unit.
Try pinging the unit and see if you get a response.
Try with one parameter at a time, e.g. Exhaust air temperature id 1111.
Try reducing the intervals between each reading.

Only one connection (socket)!

If no communication with EvoControl is made within about two minutes, the connection is closed and ModBus is reinitialised to establish a new connection. Re-initialisation also occurs if the connection is broken incorrectly.