Frequency Converter With Modbus Rtu; Network Configuration; Modbus Rtu Message Framing Structure; Introduction - Danfoss VLT HVAC Basic Drive FC 101 Design Manual

RS485 Installation and Set-...
The response telegram of the slave device is also
constructed using Modbus protocol. It contains fields
confirming the action taken, any data to be returned, and
an error-checking field. If an error occurs in receipt of the
telegram, or if the slave is unable to perform the requested
action, the slave constructs and sends an error message.
Alternatively, a timeout occurs.
7.6.3 Frequency Converter with Modbus
RTU
The frequency converter communicates in Modbus RTU
format over the built-in RS485 interface. Modbus RTU
provides access to the control word and bus reference of
the frequency converter.
The control word allows the Modbus master to control
several important functions of the frequency converter:
•
Start.
•
Various stops:
- Coast stop.
- Quick stop.
-
DC brake stop.
- Normal (ramp) stop.
•
Reset after a fault trip.
•
Run at various preset speeds.
•
Run in reverse.
•
Change the active set-up.
•
Control built-in relay of the frequency converter.
The bus reference is commonly used for speed control. It is
also possible to access the parameters, read their values,
and, where possible, write values to them. Accessing the
parameters offers a range of control options, including
controlling the setpoint of the frequency converter when
its internal PI controller is used.

7.7 Network Configuration

To enable Modbus RTU on the frequency converter, set the
following parameters:
Parameter
Parameter 8-30 Protocol
Parameter 8-31 Address
Parameter 8-32 Baud Rate
Parameter 8-33 Parity / Stop Bits
Table 7.11 Network Configuration
MG18C702
Design Guide
Setting
Modbus RTU
1–247
2400–115200
Even parity, 1 stop bit
(default)
Danfoss A/S © 04/2016 All rights reserved.
7.8 Modbus RTU Message Framing
Structure

7.8.1 Introduction

The controllers are set up to communicate on the Modbus
network using RTU (remote terminal unit) mode, with each
byte in a telegram containing 2 4-bit hexadecimal
characters. The format for each byte is shown in Table 7.12.
Start Data byte
bit
Table 7.12 Format for Each Byte
Coding system 8-bit binary, hexadecimal 0–9, A–F.
2 hexadecimal characters contained in each
8-bit field of the telegram.
•
Bits per byte 1 start bit.
•
8 data bits, least significant bit sent first.
•
1 bit for even/odd parity; no bit for no
parity.
•
1 stop bit if parity is used; 2 bits if no
parity.
Error check field Cyclic redundancy check (CRC).
Table 7.13 Byte Details

7.8.2 Modbus RTU Telegram Structure

The transmitting device places a Modbus RTU telegram
into a frame with a known beginning and ending point.
This allows receiving devices to begin at the start of the
telegram, read the address portion, determine which
device is addressed (or all devices, if the telegram is
broadcast), and to recognize when the telegram is
completed. Partial telegrams are detected and errors set as
a result. Characters for transmission must be in
hexadecimal 00–FF format in each field. The frequency
converter continuously monitors the network bus, also
during silent intervals. When the first field (the address
field) is received, each frequency converter or device
decodes it to determine which device is being addressed.
Modbus RTU telegrams addressed to 0 are broadcast
telegrams. No response is permitted for broadcast
telegrams. A typical telegram frame is shown in Table 7.14.
Start Address Function
T1-T2-T3-
8 bits 8 bits
T4
Table 7.14 Typical Modbus RTU Telegram Structure
Stop/ Stop
parity
CRC
Data End
check
T1-T2-T3-
N x 8 bits 16 bits
T4
87
7 7