vacon 100 industrial

vacon 100 flow

®

vacon 100 hvac

®

vacon 100 x
®

ac drives

modbus tcp / modbus rtu

user manual
 vacon • 1

Table of Contents
Document: DPD00156C
Version release date: 5.2.16

1. Safety................................................................................................................2
1.1 Danger.................................................................................................................................2
1.2 Warnings .............................................................................................................................3
1.3 Earthing and earth fault protection ....................................................................................4
2. Modbus - general info .......................................................................................5
3. Modbus technical data ......................................................................................7
3.1 Modbus RTU protocol .........................................................................................................7
3.2 Modbus TCP protocol..........................................................................................................7
3.3 Cable length ........................................................................................................................7
4. Installation........................................................................................................8
4.1 Installation in Vacon® 100..................................................................................................8
4.1.1 Prepare for use through ethernet ......................................................................................9
4.1.2 Prepare for use through RS485........................................................................................11
4.2 Installation in Vacon® 100 X.............................................................................................15
4.2.1 Prepare for use through Ethernet ....................................................................................15
4.2.2 Prepare for use through RS485........................................................................................16
5. Programming..................................................................................................18
5.1 Modbus RS-485 parameters and monitoring values .......................................................19
5.2 Modbus TCP parameters and monitoring values.............................................................20
5.2.1 Ethernet common settings ...............................................................................................20
5.2.2 Modbus TCP settings ........................................................................................................20
5.3 Modbus RTU parameter descriptions...............................................................................22
5.3.1 Modbus RTU Parameters..................................................................................................22
5.3.2 Modbus RTU monitoring values........................................................................................22
5.4 Modbus TCP parameter descriptions...............................................................................25
5.4.1 Ethernet common settings ...............................................................................................25
5.4.2 Modbus TCP settings ........................................................................................................25
5.4.3 Modbus TCP monitoring values........................................................................................26
6. Communications .............................................................................................28
6.1 Data addresses in Modbus messages ..............................................................................28
6.2 Supported Modbus Functions ...........................................................................................28
6.3 Modbus data mapping.......................................................................................................30
6.3.1 Coils registers...................................................................................................................30
6.3.2 Discrete inputs ..................................................................................................................30
6.3.3 Holding registers and input registers ..............................................................................30
6.4 Example messages ...........................................................................................................40
7. Fault tracing ...................................................................................................45
7.1 Typical fault conditions .....................................................................................................45
7.2 RS-485 bus biasing ...........................................................................................................45
7.3 Other fault conditions .......................................................................................................46
8. Quick setup .....................................................................................................48
9. Annex..............................................................................................................49

24-hour support +358 (0)201 212 575 • Email: [email protected]

 vacon • 2 Safety

1. SAFETY
This manual contains clearly marked cautions and warnings which are intended for your personal
safety and to avoid any unintentional damage to the product or connected appliances.
Please read the information included in cautions and warnings carefully.
The cautions and warnings are marked as follows:

Table 1. Warning signs

= DANGER! Dangerous voltage

9000.emf

= WARNING or CAUTION
13006.emf

= Caution! Hot surface

9001.emf

1.1 Danger

The components of the power unit are live when the drive is connected to mains
potential. Coming into contact with this voltage is extremely dangerous and may
9000.emf

cause death or severe injury.

The motor terminals U, V, W and the brake resistor terminals are live when the
9000.emf
AC drive is connected to mains, even if the motor is not running.
After disconnecting the AC drive from the mains, wait until the indicators on the
keypad go out (if no keypad is attached see the indicators on the cover). Wait 5
more minutes before doing any work on the connections of the drive. Do not open
9000.emf
the cover before this time has expired. After expiration of this time, use a mea-
suring equipment to absolutely ensure that no voltage is present. Always ensure
absence of voltage before starting any electrical work!
The control I/O-terminals are isolated from the mains potential. However, the
relay outputs and other I/O-terminals may have a dangerous control voltage
9000.emf

present even when the AC drive is disconnected from mains.

Before connecting the AC drive to mains make sure that the front and cable cov-
9000.emf
ers of the drive are closed.
During a ramp stop (see the Application Manual), the motor is still generating
voltage to the drive. Therefore, do not touch the components of the AC drive
before the motor has completely stopped. Wait until the indicators on the keypad
9000.emf

go out (if no keypad is attached see the indicators on the cover). Wait additional 5
minutes before starting any work on the drive.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
1
Safety vacon • 3

1.2 Warnings

The AC drive is meant for fixed installations only.

13006.emf

Do not perform any measurements when the AC drive is connected to the mains.
13006.emf

The earth leakage current of the AC drives exceeds 3.5mA AC. According to stan-
dard EN61800-5-1, a reinforced protective ground connection must be ensured.
See chapter 1.3.
13006.emf

If the AC drive is used as a part of a machine, the machine manufacturer is

responsible for providing the machine with a supply disconnecting device (EN
60204-1).
13006.emf

Only spare parts delivered by Vacon can be used.

13006.emf

At power-up, power brake or fault reset the motor will start immediately if the
start signal is active, unless the pulse control for Start/Stop logic has been selected.
Futhermore, the I/O functionalities (including start inputs) may change if param-
eters, applications or software are changed. Disconnect, therefore, the motor if
13006.emf

an unexpected start can cause danger.

The motor starts automatically after automatic fault reset if the auto restart
13006.emf
function is activated. See the Application Manual for more detailed information.
Prior to measurements on the motor or the motor cable, disconnect the motor
13006.emf
cable from the AC drive.
Do not touch the components on the circuit boards. Static voltage discharge may
13006.emf
damage the components.
Check that the EMC level of the AC drive corresponds to the requirements of your
13006.emf supply network.

24-hour support +358 (0)201 212 575 • Email: [email protected]

1
 vacon • 4 Safety

1.3 Earthing and earth fault protection

13006.emf
CAUTION!

The AC drive must always be earthed with an earthing conductor connected to the earthing terminal
marked with .
The earth leakage current of the drive exceeds 3.5mA AC. According to EN61800-5-1, one or more
of the following conditions for the associated protective circuit shall be satisfied:
b) The protective conductor shall have a cross-sectional area of at least 10 mm2 Cu or 16
mm2 Al, through its total run.
c) Where the protective conductor has a cross-sectional area of less than 10 mm2 Cu or 16
mm2 Al, a second protective conductor of at least the same cross-sectional area shall be
provided up to a point where the protective conductor has a cross-sectional area not less
than 10 mm2 Cu or 16 mm2 Al.
d) Automatic disconnection of the supply in case of loss of continuity of the protective conduc-
tor.
The cross-sectional area of every protective earthing conductor which does not form part of the
supply cable or cable enclosure shall, in any case, be not less than:
- 2.5mm2 if mechanical protection is provided or
- 4mm2 if mechanical protection is not provided.
The earth fault protection inside the AC drive protects only the drive itself against earth faults in the
motor or the motor cable. It is not intended for personal safety.
Due to the high capacitive currents present in the AC drive, fault current protective switches may
not function properly.

Do not perform any voltage withstand tests on any part of the AC drive. There is
a certain procedure according to which the tests shall be performed. Ignoring this
procedure may result in damaged product.
13006.emf

NOTE! You can download the English and French product manuals with applicable safety,
warning and caution information from
http://drives.danfoss.com/knowledge-center/technical-documentation/.
REMARQUE Vous pouvez télécharger les versions anglaise et française des manuels produit
contenant l’ensemble des informations de sécurité, avertissements et mises en garde
applicables sur le site http://drives.danfoss.com/knowledge-center/technical-documentation/
.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
1
Modbus - general info vacon • 5

2. MODBUS - GENERAL INFO

Modbus is a communication protocol developed by Modicon systems. In simple terms, it is a way of
sending information between electronic devices. The device requesting the information is called the
Modbus Master (or the Client in Modbus TCP) and the devices supplying information are Modbus
Slaves (in Modbus TCP servers). In a standard Modbus network, there is one Master and up to 247
Slaves, each with a unique Slave Address from 1 to 247. The Master can also write information to
the Slaves. Modbus is typically used to transmit signals from instrumentation and control devices
back to a main controller or data gathering system.
The Modbus communication interface is built around messages. The format of these Modbus
messages is independent of the type of physical interface used. The same protocol can be used
regardless of the connection type. Because of this, Modbus gives the possibility to easily upgrade
the hardware structure of an industrial network, without the need for large changes in the software.
A device can also communicate with several Modbus nodes at once, even if they are connected with
different interface types, without the need to use a different protocol for every connection.

Master’s Slave
message response

Start Start
Address Address
Function Function
Data Data
CRC CRC
End End

9325.emf

Figure 1. Basic structure of Modbus frame

On simple interfaces like RS485, the Modbus messages are sent in plain form over the network. In
this case the network is dedicated to Modbus. When using more versatile network systems like TCP/
IP over Ethernet, the Modbus messages are embedded in packets with the format necessary for the
physical interface. In that case Modbus and other types of connections can co-exist at the same
physical interface at the same time. Although the main Modbus message structure is peer-to-peer,
Modbus is able to function on both point-to-point and multidrop networks.
Each Modbus message has the same structure. Four basic elements are present in each message.
The sequence of these elements is the same for all messages, to make it easy to parse the content
of the Modbus message. A conversation is always started by a master in the Modbus network. A
Modbus master sends a message and—depending of the contents of the message—a slave takes
action and responds to it. There can be more masters in a Modbus network. Addressing in the
message header is used to define which device should respond to a message. All other nodes on the
Modbus network ignore the message if the address field does not match their own address.
Your Vacon® 100 drive is equipped with Modbus support as standard.

24-hour support +358 (0)201 212 575 • Email: [email protected]

2
 vacon • 6 Modbus - general info

Ethernet

Modbus TCP
Switch

Modbus
RTU
master

Modbus RTU

9326.emf

Figure 2. Principal example diagram of Modbus

If you need to contact Vacon service in problems related to Modbus, send a description of the
problem together with the Drive Info File to [email protected].

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
2
Modbus technical data vacon • 7

3. MODBUS TECHNICAL DATA

3.1 Modbus RTU protocol

Table 2.
Interface RS-485
Data transfer method RS-485 MS/TP, half-duplex
STP (Shielded Twisted Pair), type Belden
Transfer cable
9841 or similar
Connector 2.5 mm2
Connections and Electrical isolation Functional
communications As described in “Modicon Modbus Proto-
Modbus RTU
col Reference Guide”
300, 600, 1200, 2400, 4800, 9600, 19200,
Bitrate 38400, 57600, 76800, 115200 and 230400
bits/s
Addresses 1 to 247

3.2 Modbus TCP protocol

Table 3.
Interface 100BaseTX, IEEE 802.3 compatible
Data transfer method Ethernet half/full -duplex
Data transfer speed 10/100 MBit/s, autosensing
Protocol Modbus TCP
Connections and
Connector Shielded RJ45 connector
communications
Cable type CAT5e STP
As described in Modbus Messaging
Modbus TCP
Implementation Guide
Default IP Selectable: Fixed or DHCP (AutoIP)

3.3 Cable length

The maximum allowed length of a single CAT5 Ethernet cable is 100 meters.
The maximum length of an RS-485 cable depends on the bitrate used, the cable (gauge, capacitance
or characteristic impedance) and the number of devices in the bus. The Modbus RTU specification
states that the maximum cable length is 1000 meters when using max 9600 bits/second bitrate and
AWG26 or wider gauge cable. The actual cable length which can be used in an installation can be
lower than this number depending on the aforementioned parameters.

24-hour support +358 (0)201 212 575 • Email: [email protected]

3
 vacon • 8 Installation

4. INSTALLATION
4.1 Installation in Vacon® 100

Open the cover of the AC drive.

M4x55

9174.emf

The relay outputs and other I/O-terminals may have a dangerous control voltage
present even when the AC drive is disconnected from mains.
9000.emf

Open the inner cover of the drive.

9235.emf

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
4
Installation vacon • 9

4.1.1 Prepare for use through ethernet

Connect the Ethernet cable (see specification in Chapter 3.2) to its terminal as
shown in figure below.

3 Ethernet
cable

9316.emf

24-hour support +358 (0)201 212 575 • Email: [email protected]

4
 vacon • 10 Installation

Protection class IP21: Cut free the opening on the AC drive cover for the Ether-
net cable.
Protection class IP54: Cut the rubber grommets open to slide the cables
through. Should the grommets fold in while inserting the cable, just draw the
cable back a bit to straighten the grommets up. Do not cut the grommet open-
ings wider than what is necessary for the cables you are using.
NOTE! To meet the requirements of the enclosure class IP54, the connection
between the grommet and the cable must be tight. Therefore, lead the first bit of
the cable out of the grommet straight before letting it bend. If this is not possi-
ble, the tightness of the connection must be ensured with insulation tape or a
cable tie.

9068.emf

Remount the AC drive cover.

NOTE! When planning the cable runs, remember to keep the distance between
the Ethernet cable and the motor cable at a minimum of 30 cm. See figure below.

Ethernet
cable
9265.emf

IP21 IP54

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
4
Installation vacon • 11

4.1.2 Prepare for use through RS485

Strip about 15 mm of the RS485 cable (see specification in Chapter 3.1) and cut
off the grey cable shield. Remember to do this for both bus cables (except for the
last device).
Leave no more than 10 mm of the cable outside the terminal block and strip the
cables at about 5 mm to fit in the terminals. See picture below.

10

9189.emf

5
Also strip the cable now at such a distance from the terminal that you can fix it to
1 the frame with the grounding clamp. Strip the cable at a maximum length of 15
mm. Do not strip the aluminum cable shield!

m m
15

9188.emf

24-hour support +358 (0)201 212 575 • Email: [email protected]

4
 vacon • 12 Installation

Then connect the cable to its appropriate terminals on Vacon 100 drive standard
terminal block, terminals A and B (A = negative, B = positive). See figure below.

Using the cable clamp included in the delivery of the drive, ground the shield of
the RS485 cable to the frame of the AC drive.
NOTE! This can be done in all drives if there is no difference in PE potentialbe-
tween the drives. However, if there is PE potential difference then the shield-
should be connected to PE only at one point in the system. The shields of
thecables shall be joint but not connected to several PE points with different
poten-tial.
NOTE! This is only a principle drawing and the actual drive may look different.

3
Cable clamp

3020.emf

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
4
Installation vacon • 13

If Vacon 100 is the last device on the bus, the bus termination must be set.
Locate the DIP switches to the right of the control keypad of the drive and turn
the switch for the RS485 bus termination resistor to position ON. Biasing is built
in the termination resistor. See also step 6 on page 14.

RS-485 bus termination

OFF
ON

9110.emf

Unless already done for the other control cables,

cut free the opening on the AC drive cover for the
RS485 cable (protection class IP21).

NOTE! This is only a principle drawing and the

actual drive may look different.

5
9201.emf

Remount the AC drive cover and run the RS485

cables as shown in picture.
NOTE! When planning the cable runs, remember
to keep the distance between the fieldbus cable
and the motor cable at a minimum of 30 cm.

Fieldbus
cables

9202.emf

24-hour support +358 (0)201 212 575 • Email: [email protected]

4
 vacon • 14 Installation

The bus termination must be set for the first and the last device of the fieldbus
line. See picture below. See also step 3 on page 13. We recommend that the first
device on the bus and, thus, terminated was the Master device.

Vacon 100 Vacon 100 Vacon 100 Vacon 100 Vacon 100

7
Termination
activated

Fieldbus cable Termination

activated with
Termination jumper
= Bus termination deactivated
3007.emf

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
4
Installation vacon • 15

4.2 Installation in Vacon® 100 X

The AC drive can be connected to fieldbus either through RS485 or Ethernet. The connection for
RS485 is on the standard I/O terminals (A and B) and the connection for Ethernet is left to the control
terminals.

RS485
terminals

12 13 14 15 16 17 18 19 30 A B

1 2 3 4 5 6 7 8 9 10 11

Ethernet
connection

Figure 3.

4.2.1 Prepare for use through Ethernet

Connect the Ethernet cable (see specification in Chapter 3.2) to its terminal and
1 run the cable through the conduit plate.

Remount the powerhead.

2 NOTE: When planning the cable runs, remember to keep the distance between
the Ethernet cable and the motor cable at a minimum of 30 cm.
For more detailed information, see the user’s manual of the fieldbus you are using.

24-hour support +358 (0)201 212 575 • Email: [email protected]

4
 vacon • 16 Installation

4.2.2 Prepare for use through RS485

Strip about 15 mm of the RS485 cable (see specification in Chapter 3.1) and cut
off the grey cable shield. Remember to do this for both bus cables (except for the
last device).
Leave no more than 10 mm of the cable outside the terminal block and strip the
cables at about 5 mm to fit in the terminals. See picture below.

10

9189.emf

5
Also strip the cable now at such a distance from the terminal that you can fix it to
the frame with the grounding clamp. Strip the cable at a maximum length of 15
1 mm. Do not strip the aluminum cable shield!

m m
15

9188.emf

Then connect the cable to its appropriate terminals on VACON® 100 X AC drive
2 standard terminal block, terminals A and B (A = negative, B = positive). See
Figure 3.

Using the cable clamp included in the delivery of the drive, ground the shield of
3 the RS485 cable to the frame of the AC drive.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
4
Installation vacon • 17

If VACON® 100 X AC drive is the last device on the bus, the bus termination must
be set. Locate the DIP switches to the top of the control unit (see figure below).

Turn the right most switch to position “1”. Biasing is built

in the termination resistor. See also step 6.
NOTE: When planning the cable runs, remember to keep
the distance between the fieldbus cable and the motor
cable at a minimum of 30 cm.

The bus termination must be set for the first and the last device of the fieldbus
line. See picture below and step 4. We recommend that the first device on the bus
and, thus, terminated, was the Master device.

Vacon 100 Vacon 100 Vacon 100 Vacon 100 Vacon 100

5
Termination
activated

Modbus RTU Termination

activated with
Termination DIP switch
= Bus termination deactivated

24-hour support +358 (0)201 212 575 • Email: [email protected]

4
 vacon • 18 Programming

5. PROGRAMMING
For basic information on how to use the control keypad, see the corresponding drive Application
Manual.

The navigation path to the fieldbus parameters may differ from application to application. The
exemplary paths below apply to the Vacon® 100 drive.

Navigate: Main Menu > I/O and Hardware > RS-485 OR Ethernet > Common
settings > Protocol (P5.x.1.1) > Edit > (Choose protocol)

1. First ensure that the right fieldbus protocol is selected.

Navigate: Main Menu > Quick Setup > Rem. Ctrl. Place (P1.15)
OR
Navigate: Main Menu > Parameters > Start/Stop Setup > Rem. Ctrl. Place
2. Select ‘Fieldbus control’ as the Remote Control Place.
3. Choose source of reference.
Navigate: Main Menu > Parameters > References

4. Set fieldbus parameters. See below.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
5
Programming vacon • 19

5.1 Modbus RS-485 parameters and monitoring values

Table 4. Parameters related with Modbus used through RTU

Code Parameter Min Max Unit Default ID Description

PARAMETERS
P5.X.3.1.1 Slave address 1 247 1 2320 Unique slave device address.
Communication speed
300
600
1200
2400
4800
P5.X.3.1.2 Baud rate 300 230400 bd 6 2378 9600
19200
38400
57600
76800
115200
230400
0 = Even
P5.X.3.1.3 Parity type 0 2 0 2379 1 = Odd
2 = None
1 = 1 stop bit
P5.X.3.1.4 Stopbits 1 3 3 2380 2 = 1.5 stop bits
3 = 2 stop bits
Communication
P5.X.3.1.5 0 65535 s 10 2321 0 = Not used
time-out
0 = Slave
P5.X.3.1.6(1) Operate Mode 0 1 0 2374
1 = Master
P5.x.3.1.7.1-30 IDMap IDs 0 65535 0 IDMap IDs

MONITORING VALUES
0 = Init
Fieldbus protocol 1 = Stopped
P5.X.3.2.1 1 3 1 2381
status 2 = Operational
3 = Faulted
0-99 Number of messages
with errors
Communication sta-
P5.X.3.2.2 0.0 99.999 0.0 2382 0-999 Number of messages
tus
without communication
errors
P5.X.3.2.3 Illegal functions 0 2383 See page 23.
Illegal data
P5.X.3.2.4 0 2384 See page 23.
addresses
P5.X.3.2.5 Illegal data values 0 2385 See page 23.
P5.X.3.2.6 Slave device busy 0 2386 See page 23.
P5.X.3.2.7 Memory parity error 0 2387 See page 23.
P5.X.3.2.8 Slave device failure 0 2388 See page 23.
P5.X.3.2.9 Last fault response 0 2389 See page 23.
P5.X.3.2.10 Control word hex 2390 See page 33 and page 36.
P5.X.3.2.11 Status word hex 2391 See page 33 and page 36.
1)
This feature is not supported in Vacon 100 HVAC. The default Vacon 100 application supports only
Slave mode. A special application is required for Master functionality.

24-hour support +358 (0)201 212 575 • Email: [email protected]

5
 vacon • 20 Programming

5.2 Modbus TCP parameters and monitoring values

5.2.1 Ethernet common settings

Table 5. Common settings for Modbus TCP (Ethernet)

Code Parameter Min Max Unit Default ID Description
P5.X.1.1 IP address mode 2482 See page 25.
P5.X.1.2 IP address 2483 See page 25.
P5.X.1.3 Subnet mask 2484 See page 25.
P5.X.1.4 Default gateway 2485 See page 25.
P5.X.1.5 MAC address 2486 See page 25.

5.2.2 Modbus TCP settings

Table 6. Parameters related to Modbus TCP

Code Parameter Min Max Unit Default ID Description

PARAMETERS (Common settings )

Number of allowed con-
P5.X.2.1.1 Connection limit 0 3 2 2446
nections
Unit identifier See chapter 5.4.2 Mod-
P5.X.2.1.2 0 255 1 2447
number bus TCP settings
Communication
P5.X.2.1.3 0 65535 s 0 2448 0 = Not used
time-out
P5.9.2.1.4.1-
IDMap IDs 0 65535 0 IDMap IDs
30

MONITORING VALUES (Connection 1, Monitoring *

1 = Stopped
Fieldbus protocol
P5.X.2.2.1.1 1 3 2449 2 = Operational
status
3 = Faulted
0-99 Number of mes-
sages with errors
Communication
P5.X.2.2.1.2 0.0 99.999 0.0 2450 0-999 Number of mes-
status
sages without communi-
cation errors
P5.X.2.2.1.3 Illegal functions 0 2451 See page 26.
Illegal data
P5.X.2.2.1.4 0 2452 See page 26.
addresses
P5.X.2.2.1.5 Illegal data values 0 2453 See page 26.
P5.X.2.2.1.6 Slave device busy 0 2454 See page 26.
P5.X.2.2.1.7 Memory parity error 0 2455 See page 26.
P5.X.2.2.1.8 Slave device failure 0 2456 See page 27.
P5.X.2.2.1.9 Last fault response 0 2457 See page 27.
P5.X.2.2.1.10 Control word hex 2458 See page 33.
P5.X.2.2.1.11 Status word hex 2459 See page 36.

MONITORING VALUES (Connection 2, Monitoring)*

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
5
Programming vacon • 21

Code Parameter Min Max Unit Default ID Description

1 = Stopped
Fieldbus protocol
P5.X.2.2.1.1 1 3 2460 2 = Operational
status
3 = Faulted
0-99 Number of mes-
sages with errors
Communication
P5.X.2.2.1.2 0.0 99.999 0.0 2461 0-999 Number of mes-
status
sages without communi-
cation errors
P5.X.2.2.1.3 Illegal functions 0 2462 See page 26.
Illegal data
P5.X.2.2.1.4 0 2463 See page 26.
addresses
P5.X.2.2.1.5 Illegal data values 0 2464 See page 26.
P5.X.2.2.1.6 Slave device busy 0 2465 See page 26.
P5.X.2.2.1.7 Memory parity error 0 2466 See page 26.
P5.X.2.2.1.8 Slave device failure 0 2467 See page 27.
P5.X.2.2.1.9 Last fault response 0 2468 See page 27.
P5.X.2.2.1.10 Control word hex 2469 See page 33.
P5.X.2.2.1.11 Status word hex 2470 See page 36.

MONITORING VALUES (Connection 3, Monitoring)*

1 = Stopped
Fieldbus protocol
P5.X.2.2.1.1 1 3 2471 2 = Operational
status
3 = Faulted
0-99 Number of mes-
sages with errors
Communication
P5.X.2.2.1.2 0.0 99.999 0.0 2472 0-999 Number of mes-
status
sages without communi-
cation errors
P5.X.2.2.1.3 Illegal functions 0 2473 See page 26.
Illegal data
P5.X.2.2.1.4 0 2474 See page 26.
addresses
P5.X.2.2.1.5 Illegal data values 0 2475 See page 26.
P5.X.2.2.1.6 Slave device busy 0 2476 See page 26.
P5.X.2.2.1.7 Memory parity error 0 2477 See page 26.
P5.X.2.2.1.8 Slave device failure 0 2478 See page 27.
P5.X.2.2.1.9 Last fault response 0 2479 See page 27.
P5.X.2.2.1.10 Control word hex 2480 See page 33.
P5.X.2.2.1.11 Status word hex 2481 See page 36.

* Will appear only after connection has been established

24-hour support +358 (0)201 212 575 • Email: [email protected]

5
 vacon • 22 Programming

5.3 Modbus RTU parameter descriptions

5.3.1 Modbus RTU Parameters

P5.X.3.1.1 SLAVE ADDRESS

Each slave must have a unique address (from 1 to 247) so that it can be addressed independently
from other nodes.

P5.X.3.1.2 BAUD RATE

Select the communication speed for the network. The default value is 9600 baud.

P5.X.3.1.3 PARITY TYPE

Users can select the parity type for the network.
Modbus RTU specifies the stop bit configuration shown in table 7. The user can modify this stop bit
configuration manually using parameter P5.X.3.1.4.

Table 7. Parity type

Table 8.

Parity type Stopbits

Even 1
Odd 1
None 2

P5.X.3.1.4 STOP BITS

User can select the stop bit amount for the Modbus RTU network.

P5.X.3.1.5 COMMUNICATION TIME-OUT

Modbus initiates a communication error for a time defined with this parameter. ‘0’ means that no
fault is generated.

P5.X.3.1.6 OPERATE MODE

Used to select the operate mode of the Modbus RTU protocol (slave / master). This feature is not
supported in Vacon 100 HVAC. The default Vacon 100 application supports only Slave mode. A
special application is required for Master functionality.
• 0 = Slave
• 1 = Master

P5.8.3.1.7.1-30 IDMAP IDS

See Chapter 6.3.3.4.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
5
Programming vacon • 23

5.3.2 Modbus RTU monitoring values

P5.X.3.2.1 FIELDBUS PROTOCOL STATUS

Fieldbus Protocol Status tells the status of the protocol.

Table 9. FB protocol statuses

INITIALIZING Protocol is starting up
STOPPED Protocol is timeouted or not used
OPERATIONAL Protocol is running
Major fault in protocol, requires restarting.
FAULTED
If fault remains contact [email protected]

P5.X.3.2.2 COMMUNICATION STATUS

The Communication status shows how many error and how many good messages the AC drive has
received. The Communication status includes a common error counter that counts CRC and parity
errors and a counter for good messages.
Only messages to the current slave in use are counted in the good messages.

Table 10.
Good messages
Number of messages received with-
0…999
out errors
Bad Frames
Number of messages received with
0…99
errors

P5.X.3.2.3 ILLEGAL FUNCTIONS

This value counts error situations.The function code received in the query refers to an unallowed
action for the server (or slave). This corresponds to Modbus fault code 01h.

P5.X.3.2.4 ILLEGAL DATA ADDRESSES

This value counts error situations. The data address received in the query refers to an unallowed
address for the server (or slave). This corresponds to Modbus fault code 02h.

P5.X.3.2.5 ILLEGAL DATA VALUES

This value counts error situations. A value contained in the query data field refers to an unallowed
value for server (or slave). This corresponds to Modbus fault code 03h.

P5.X.3.2.6 SLAVE DEVICE BUSY

This value counts error situations. The server (or slave) is engaged in processing a long–duration
program command. The client (or master) should retransmit the message later when the server (or
slave) is free. This corresponds to Modbus fault code 06h.

P5.X.3.2.7 MEMORY PARITY ERROR

This value counts error situations.The server (or slave) attempted to read record file but detected
a parity error in the memory.This corresponds to Modbus fault code 08h.

24-hour support +358 (0)201 212 575 • Email: [email protected]

5
 vacon • 24 Programming

P5.X.3.2.8 SLAVE DEVICE FAILURE

This value counts error situations. An unrecoverable error occurred while the server (or slave) was
attempting to perform the requested action. This corresponds to Modbus fault code 04h.

P5.X.3.2.9 LAST FAULT RESPONSE

Shows the last fault response as Fault code.

P5.X.3.2.10 CONTROL WORD

Shows the Control Word received from the bus.

P5.X.3.2.11 STATUS WORD

Shows the current Status Word that is sent to the bus.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
5
Programming vacon • 25

5.4 Modbus TCP parameter descriptions

5.4.1 Ethernet common settings

P5.X.1.1 IP ADDRESS MODE

Selectable alternatives are DHCP (Dynamic Host Configuration Protocol) and Fixed.
DHCP protocol gives IP addresses to new devices connecting to local network. This address is valid
for a certain period of time. If no DHCP server is found an automatic random IP is given.
A fixed IP address is specified manually and it does not change.
When the mode is changed from DHCP to Fixed the addresses will read
IP: 192.168.0.10
Subnet mask:255.255.0.0
Default gateway: 192.168.0.1

P5.X.1.2 IP ADDRESS
An IP address is a series of numbers (like above) specific to the device connected to the Internet.

P5.X.1.3 SUBNET MASK

The network mask marks all the bits of an IP address for the identification of the network and the
subnetwork.

P5.X.1.4 DEFAULT GATEWAY

Gateway address is the IP address of a network point that acts as an entrance to another network.

P5.X.1.5 MAC ADDRESS

The MAC address of the control board.
MAC address (Media Access Control) is a unique address given to each network host. It is not
editable.

5.4.2 Modbus TCP settings

5.4.2.1 Common settings

P5.X.2.1.1 CONNECTION LIMIT

Defines how many clients can access the server simultaneously.

P5.X.2.1.2 UNIT IDENTIFIER

The Modbus ‘slave address’ field usually used on Modbus Serial Line is replaced by a single byte
‘Unit Identifier’.
On TCP/IP, the Modbus server is addressed using its IP address; therefore, the Modbus Unit
Identifier is useless.

P5.X.2.1.3 COMMUNICATION TIME-OUT

Modbus initiates a communication error if the Ethernet connection is lost. Communication time-out
parameters define the minimum delay between packages received from the client. The timer is
reset and started after each received package. This parameter can be used if the client is
periodically polling the slaves.

P5.9.2.1.4.1-30 IDMAP IDS

See Chapter 6.3.3.4.

24-hour support +358 (0)201 212 575 • Email: [email protected]

5
 vacon • 26 Programming

5.4.3 Modbus TCP monitoring values

These values will not appear before the connection is established.

5.4.3.1 Connection 1

P5.X.2.2.1.1 FIELDBUS PROTOCOL STATUS

Fieldbus Protocol Status tells the status of the protocol.
Table 11. FB protocol statuses
INITIALIZING Protocol is starting up
STOPPED Protocol is timeouted or not used
OPERATIONAL Protocol is running
Major fault in protocol, requires restarting.
FAULTED
If fault remains contact [email protected]

P5.X.2.2.1.2 COMMUNICATION STATUS

The Communication status shows how many error and how many good messages the AC drive has
received. The Communication status includes a common error counter that counts errors and a
counter for good messages.

Table 12. Communication status

Good messages
Number of messages received with-
0…999
out errors
Bad Frames
Number of messages received with
0…99
errors

P5.X.2.2.1.3 ILLEGAL FUNCTIONS

This value counts error situations. The function code received in the query refers to an unallowed
action for the server (or slave). This corresponds to Modbus fault code 01h.

P5.X.2.2.1.4 ILLEGAL DATA ADDRESSES

This value counts error situations. The data address received in the query refers to an unallowed
address for the server (or slave). This corresponds to Modbus fault code 02h.

P5.X.2.2.1.5 ILLEGAL DATA VALUES

This value counts error situations. A value contained in the query data field refers to an unallowed
value for server (or slave). This corresponds to Modbus fault code 03h.

P5.X.2.2.1.6 SLAVE DEVICE BUSY

This value counts error situations. The server (or slave) is engaged in processing a long–duration
program command. The client (or master) should retransmit the message later when the server (or
slave) is free. This corresponds to Modbus fault code 06h.

P5.X.2.2.1.7 MEMORY PARITY ERROR

This value counts error situations.The server (or slave) attempted to read record file but detected
a parity error in the memory. This corresponds to Modbus fault code 08h.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
5
Programming vacon • 27

P5.X.2.2.1.8 SLAVE DEVICE FAILURE

This value counts error situations. An unrecoverable error occurred while the server (or slave) was
attempting to perform the requested action. This corresponds to Modbus fault code 04h.

P5.X.2.2.1.9 LAST FAULT RESPONSE

Shows the last fault response as Fault code.

P5.X.2.2.1.10 CONTROL WORD

Shows the Control Word received from the bus.

P5.X.2.2.1.11 STATUS WORD

Shows the current Status Word that is sent to the bus.

5.4.3.2 Connection 2

The monitoring values display the same pieces of information as for Connection 1 (Chapter 5.2.2),
for the 2nd and 3rd connections".

5.4.3.3 Connection 3

The monitoring values display the same pieces of information as for Connection 1 (Chapter 5.2.2),
for the 2nd and 3rd connections".

24-hour support +358 (0)201 212 575 • Email: [email protected]

5
 vacon • 28 Communications

6. COMMUNICATIONS
Features of the Modbus-Vacon interface:
• Direct control of Vacon drive (e.g. Run, Stop, Direction, Speed reference, Fault reset)
• Full access to all Vacon parameters
• Monitor Vacon status (e.g. Output frequency, Output current, Fault code)

6.1 Data addresses in Modbus messages

All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item
is addressed as item number zero. For example:
• The coil known as ‘Coil 1’ in a programmable controller is addressed as ‘Coil 0000’ in the
data address field of a Modbus message.
• Coil 127 decimal is addressed as ‘Coil 007E hex’ (126 decimal).
• Holding register 40001 is addressed as register 0000 in the data address field of the mes-
sage. The function code field already specifies a ‘holding register’ operation. Therefore the
‘4XXXX’ reference is implicit.
• Holding register 40108 is addressed as register 006B hex (107 decimal).

6.2 Supported Modbus Functions

The Vacon variables and fault codes as well as the parameters can be read and written from
Modbus. The parameter addresses are determined in the application. Every parameter and actual
value have been given an ID number in the application. The ID numbering of the parameter as well
as the parameter ranges and steps can be found in the application manual in question. The
parameter value must be given without decimals. If several parameters/actual values are read with
one message, the addresses of the parameters/actual values must be consecutive.

Table 13. Supported functions

Address
Function Function Access
Modbus Function Name TCP/RTU range
(dec) (hex) type
(hex)

Discrete 00000-
1 1 Read coils TCP only
(1-bit) 0FFFF
Discrete 10000-
2 2 Read Discrete Inputs TCP only
(1-bit) 1FFFF
Register 40000-
3 3 Read Holding Registers TCP&RTU
(16bit) 4FFFF
Register 30000-
4 4 Read Input Registers TCP&RTU
(16bit) 3FFFF
Discrete 00000-
5 5 Write Single Coils TCP only
(1-bit) 0FFFF
Register 40000-
6 6 Write Single Register TCP&RTU
(16bit) 4FFFF

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 29

Address
Function Function Access
Modbus Function Name TCP/RTU range
(dec) (hex) type
(hex)

Discrete 00000-
15 F Write Multiple Coils TCP only
(1-bit) 0FFFF
Register 40000-
16 10 Write Multiple Registers TCP&RTU
(16bit) 4FFFF
Read/Write Multiple Regis- Register 40000-
23 17 TCP&RTU
ters (16bit) 4FFFF
NOTE! Broadcasting not supported in TCP.
Broadcast supported with function code 06 and 16 in RTU

The address ranges of the different function codes are in many cases not relevant to the user and
can be ignored. The targeted information type (coil, register etc.) can be selected separate from the
address.

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 30 Communications

6.3 Modbus data mapping

6.3.1 Coils registers

A "coil" in Modbus is a single-bit binary data item which can be both read and written. In Vacon® 100
the coils refer to some bits in the fieldbus control word." See page 33.

Table 14. Defined coil registers

Address Function Purpose

0001 RUN/STOP Control Word, bit 0

0002 Direction Control Word, bit 1
0003 Fault reset Control Word, bit 2

6.3.2 Discrete inputs

A "discrete input" in Modbus is a single-bit binary data item which is read-only. In Vacon 100 the
discrete inputs refer to the fieldbus status word bits. See page 36.

Table 15. Defined Input Discrete

Address Function Purpose

10001 Ready Status Word, bit 0

10002 Run Status Word, bit 1
10003 Direction Status Word, bit 2
10004 Fault Status Word, bit 3
10005 Alarm Status Word, bit 4
10006 At reference Status Word, bit 5
10007 Zero speed Status Word, bit 6
10008 Flux ready Status Word, bit 7

6.3.3 Holding registers and input registers

An "input register" in Modbus is a 16-bit value which is read-only. A "holding register" in Modbus is
a 16-bit value which can be both read and written. Holding and input registers are accessed using
different function codes, and the address ranges are different. In Vacon 100 the same information
can be accessed as input registers and holding registers, i.e. input register X refers to the same 16-
bit value as the holding register X.
The Modbus registers are mapped to the Vacon 100 drive as follows

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 31

Table 16. Vacon 100 input and holding registers

Register Access
Purpose See
number type

0001 - 2000 Vacon Application ID´s 16bit Table 16

2001 - 2050 FBProcessDataIN 16bit Table 19
2051 - 2099 FBProcessDataIN 32bit Table 19
2101 - 2150 FBProcessDataOUT 16bit Table 19
2151 - 2199 FBProcessDataOUT 32bit Table 19
2200 - 10000 Vacon Application ID´s 16bit Table 16
10501 - 10530 IDMap 16bit Table 29
10601 - 10630 IDMap Read/Write 16bit Table 30
10701 - 10760 IDMap Read/Write 32bit Table 30
20001 - 40000 Vacon Application ID's 32bit Table 16
40001 - 40007 Operation day counter 16bit Table 32
Resettable operation day
40101 - 40107 16bit Table 33
counter
40201 - 40203 Energy counter 16bit Table 34
40301 - 40303 Resettable energy counter 16bit Table 35
40401 - 40430 Fault history 16bit Table 36

Table 17. Maximum lengths of Modbus Read and Write requests

Address range Type R/W #

0001-2000 Vacon application id’s 30/30

2001-2011 FBProcessDataIN 11/11
11/0
2101-2111 FBProcessDataOUT
Read only
10501-10530 IDMap table parameter IDs 30/30
10601-10630 IDMap table parameter values 30/30
30/30
40401-40430 Fault history
Read only

Accessing unsupported values returns the error code "Illegal Data Address".

6.3.3.1 Vacon Application ID’s

Application ID's are parameters that depend on the AC drive's application. These parameters can
be read and written by pointing the corresponding memory range directly or by using the so-called

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 32 Communications

ID map (Chapter 6.3.3.4). It is easiest to use a straight address if you want to read a single parameter
value or parameters with consecutive ID numbers. It is possible to read 12 consecutive ID
addresses.

Table 18. Application ID’s

Register Application
Purpose
number ID

0001-2000 Application parameters 1-2000

2200-10000 Application parameters 2200-10000

6.3.3.2 FB Process data IN

The process data fields are used to control the drive (e.g. Run, Stop , Reference, Fault Reset) and to
quickly read actual values (e.g. Output frequency, Output current, Fault code). The fields are
structured as follows:

Process Data Master -> Slave (max 22 bytes)

Table 19. Fieldbus Process Data IN
Address
Name Range/Type
16-bit* 32-bit

2051 = High data

2001 FB Control Word Binary coded
2052 = Low data
2002 - Reserved Binary coded
2053 = High data 0…100.00 %
2003 FB Speed Reference
2054 = Low data unit 0.01%
2055 = High data
2004 FB Process Data In 1 See Chapter 9.
2056 = Low data
2057 = High data
2005 FB Process Data In 2 See Chapter 9.
2058 = Low data
2059 = High data
2006 FB Process Data In 3 See Chapter 9.
2060 = Low data
2061 = High data
2007 FB Process Data In 4 See Chapter 9.
2062 = Low data
2063 = High data
2008 FB Process Data In 5 See Chapter 9.
2064 = Low data
2065 = High data
2009 FB Process Data In 6 See Chapter 9.
2066 = Low data
2067 = High data
2010 FB Process Data In 7 See Chapter 9.
2068 = Low data
2069 = High data
2011 FB Process Data In 8 See Chapter 9.
2070 = Low data
*. In Vacon 100, the Control Word and the Status Word are formed of 32 bits. Only the initial 16
bits can be read in the 16-bit area.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 33

Control word bits

The Control word is composed of 32 bits. Meanings of bits are described below. Unused bits have
to be set to zero.

Table 20. Control Word bits

Table 21:
Bit Name Value = 1 Value = 0 Vacon 100 HVAC Vacon 100
B0 Start/Stop Start request Stop request Supported Supported
B1 Direction Reverse Forward Supported Supported
Fault
B2 Reset faults No action Supported Supported
reset
Coast Stop mode is coast-
B3 Normal stop mode Supported Supported
Stop Mode ing
Ramp Stop mode is ramp-
B4 Normal stop mode Supported Supported
Stop Mode ing
Short
Ramp stop time is Normal ramp stop
B5 Ramp Supported
shortened time
Time
Freeze Drive does not accept Drive follows
B6 Fieldbus new fieldbus refer- changes in fieldbus Supported Supported
Ref ence reference
Force
Fieldbus Fieldbus reference is
B7 No action Supported
Ref. to forced to zero
Zero
Force
Fieldbus control Normal control
B8 Fieldbus Supported Supported
place is forced place
Control
Force
Fieldbus reference is
B9 Fieldbus Normal reference Supported Supported
forced
Reference
Jogging
Activates jogging ref-
B10 Refer- No action Supported
erence 1
ence 1
Jogging
Activates jogging ref-
B11 Refer- No action Supported
erence 2
ence 2
Quick
B12 Drive does quick stop No action Supported
Stop
B13-
Reserved Not used
B31

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 34 Communications

6.3.3.3 FB Process data OUT

Process Data Slave -> Master (max 22 bytes)

Table 22. Fieldbus Process Data Out

Address
Name Range/Type
16-bit 32-bit

2151 = High data

2101 FB Status Word Binary coded
2152 = Low data
2102 - Reserved Binary coded
2153 = High data 0…100.00,
2103 FB Actual Speed
2154 = Low data unit 0.01%
2155 = High data
2104 FB Process Data Out 1 See Chapter 9.
2156 = Low data
2157 = High data
2105 FB Process Data Out 2 See Chapter 9.
2158 = Low data
2159 = High data
2106 FB Process Data Out 3 See Chapter 9.
2160 = Low data
2161 = High data
2107 FB Process Data Out 4 See Chapter 9.
2162 = Low data
2163 = High data
2108 FB Process Data Out 5 See Chapter 9.
2164 = Low data
2165 = High data
2109 FB Process Data Out 6 See Chapter 9.
2166 = Low data
2167 = High data
2110 FB Process Data Out 7 See Chapter 9.
2168 = Low data
2169 = High data
2111 FB Process Data Out 8 See Chapter 9.
2170 = Low data

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 35

Table 23.

Table 24.
Vacon 100
Bit Name Value=1 Value=2 Vacon 100
HVAC
Ready for opera-
Bit 0 Ready Not Ready Supported Supported
tion
Bit 01 Run Running Stopped Supported Supported
Bit 2 Direction Counterclockwise Clockwise Supported Supported
Bit 3 Fault A fault is active No fault active Supported Supported
Bit 4 Alarm An alarm is active No alarm active Supported Supported
Reference fre-
Reference fre-
Bit 5 At Reference quency is not Supported Supported
quency is reached
reached
Motor is at zero Motor is at non-
Bit 6 Zero Speed Supported Supported
speed zero speed
Motor is magne- Motor is not
Bit 7 Flux Ready Supported Supported
tized magnetized
Bit 8-28 Reserved Not used Supported Supported

Status Word bits

The Status word is composed of 32 bits. The meanings of bits are described below.

Table 25. Status Word bits B1-B28

Table 26:
Bit Name Value = 1 Value = 0 Description
Indicates whether the drive is
B0 Ready Ready Not ready
ready or not
Indicates whether the drive is
B1 Run Running Stop
running or stopped
Indicates the rotation direc-
B2 Direction Counterclockwise Clockwise
tion of the motor
B3 Fault Faulted Not faulted Indicates if a fault is active
B4 Alarm Alarm No alarm Indicates if an alarm is active
B5 AtReference True False Reference frequency reached
B6 ZeroSpeed True False Motor running at zero speed
B7 FluxReady True False Motor is magnetized
B8-B28 Not used

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 36 Communications

Table 27. Status Word bits B29-B31, descriptions of bit connections

Table 28:
B29 B30 B31
Description
Control place Control place Control place
0 0 1 Fieldbus
0 1 0 Keypad
0 1 1 PC tool
1 0 0 I/O terminals

The use of process data depends on the application. In a typical situation, the device is started and
stopped with the ControlWord (CW) written by the Master and the Rotating speed is set with
Reference (REF). With PD1…PD8 the device can be given other reference values (e.g. Torque
reference).
With the StatusWord (SW) read by the Master, the status of the device can be seen. Actual Value
(ACT) and PD1…PD8 show the other actual values.

6.3.3.4 ID map

Using the ID map, you can read consecutive memory blocks that contain parameters whose ID's are
not in a consecutive order. The address range 10501 - 10530 is called 'IDMap', and it includes an
address map in which you can write your parameter ID's in any order. The address range 10601 to
10630 is called 'IDMap Read/Write,' and it includes values for parameters written in the IDMap. As
soon as one ID number has been written in the map cell 10501, the corresponding parameter value
can be read and written in the address 10601, and so on.
IDMap IDs can be also configured from the panel or VaconLive PC tool. IDmap menu is located under
Modbus TCP and Modbus RTU settings. See details in chapters 5.1 and 5.2.2.

Parameter ID’s
ID
699
700
Address Data 701
10501 700
10502 702
702
10503 707 703
10504 704 704
705
706
707
9328.emf 708

Table 29. IDMap initialization

Once the IDMap address range has been initialized with any parameter ID number, the parameter
value can be read and written in the IDMap Read/Write address range address IDMap address + 100.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 37

Table 30. Parameter Values in 16-bit IDMap Read/Write registers

Address Data

10601 Data included in parameter ID700

10602 Data included in parameter ID702
10603 Data included in parameter ID707
10604 Data included in parameter ID704

If the IDMap table has not been initialized, all data fields are showing the value '0'. Once the IDMap
table has been initialized, the parameter ID's are stored in the Vacon 100 flash memory.

Example of 32Bit IDMap

Table 31. Example of parameter values in 32-bit IDMap Read/Write registers

Address Data

10701 Data High, parameter ID700

10702 Data Low, parameter ID700
10703 Data High, parameter ID702
10704 Data Low, parameter ID702

6.3.3.5 Operation day counter

Table 32. Operation day counter

Address Purpose

40001 Years
40002 Days
40003 Hours
40004 Minutes
40005 Seconds

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 38 Communications

6.3.3.6 Resettable operation day counter

Reset the counter by writing “1” for parameter ID2311.

Table 33. Resettable operation day counter

Address Purpose

40101 Years
40102 Days
40103 Hours
40104 Minutes
40105 Seconds

6.3.3.7 Energy counter

The last number of the Format field indicates the decimal point place in the Energy field. If the
number is bigger than 0, move the decimal point to the left by the number indicated. For example,
Energy = 1200, Format = 52. Unit = 1. Energy = 12.00kWh.

Table 34. Energy counter

Address Purpose

40201 Energy
40202 Format
Unit
1 = kWh
40203 2 = MWh
3 = GWh
4 = TWh

6.3.3.8 Resettable energy counter

Reset the counter by writing “1” for parameter ID2312.

Table 35. Resettable energy counter

Address Purpose

40301 Energy
40302 Format
Unit
1 = kWh
40303 2 = MWh
3 = GWh
4 = TWh

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 39

6.3.3.9 Fault history

The fault history can be viewed by reading from address 40401 onward. The faults are listed in
chronological order so that the latest fault is mentioned first and the oldest last. The fault history
can contain 29 faults at the same time. The fault history contents are represented as follows.
Table 36. Fault history
Address Register Purpose

40401 440401
40402 440402
40403 440403
... ...
40429 440429

6.4 Example messages

Example 1
In this example the speed reference of the drive is set to 50% and the drive is commanded to run.
The Process Data IN registers 2001…2003 are written to achieve this. The data to the control word
is 0001h (run request) and the data to the speed reference is 1388h (5000d). The Modbus function
used to write the values is 16 (Write Multiple Registers).
Write the process data 42001…42003 with command 16 (Preset Multiple Registers).
Command Master - Slave:

Table 37.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 10 hex Function 10 hex (= 16)
DATA Starting address HI 07 hex Starting address 07D0 hex (= 2000)
Starting address LO D0 hex
No. of registers HI 00 hex
No. of registers LO 03 hex Number of registers 0003 hex (= 3)
Byte count 06 hex Byte count 06 hex (= 6)
Data HI 00 hex Data 1 = 0001 hex (= 1). Setting control word run bit to 1.
Data LO 01 hex
Data HI 00 hex Data 2 = 0000 hex (= 0).
Data LO 00 hex
Data HI 13 hex Data 3 = 1388 hex (= 5000), Speed Reference to 50.00%
Data LO 88 hex
ERROR CRC HI C8 hex CRC field C8CB hex (= 51403)
CHECK CRC LO CB hex

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 40 Communications

Message frame:

Table 38.
01 10 07 D0 00 03 06 00 01 00 00 13 88 C8 CB

The reply to Preset Multiple Registers message is the echo of 6 first bytes.
Answer Slave - Master:

Table 39.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 10 hex Function 10 hex (= 16)
DATA Starting address HI 07 hex Starting address 07D0 hex (= 2000)
Starting address LO D0 hex
No. of registers HI 00 hex Number of registers 0003 hex (= 3)
No. of registers LO 03 hex
ERROR CRC HI 80 hex CRC 8085 hex (= 32901)
CHECK CRC LO 85 hex

Reply frame:

Table 40.
01 10 07 D0 00 03 80 85

Example 2:
In this example the actual speed and the first Process Data OUT variable of the drive is read. The
Process Data OUT registers 2103 and 2104 are read to achieve this. The Modbus function used to
read the values is 4 (Read Input Registers).
Read the Process Data 42103…42104 with command 4 (Read Input Registers).
Command Master - Slave:

Table 41.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 04 hex Function 4 hex (= 4)
DATA Starting address HI 08 hex
Starting address LO 36 hex
No. of registers HI 00 hex Number of registers 0002 hex (= 2)
No. of registers LO 02 hex
ERROR CRC HI 93 hex CRC field 93A5 hex (= 37797)
CHECK CRC LO A5 hex

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Communications vacon • 41

Message frame:

Table 42.
01 04 08 36 00 02 93 A5

The reply to the Read Input Registers message contains the values of the read registers.
Answer Slave - Master:

Table 43.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 04 hex Function 4 hex (= 4)
DATA Byte count 04 hex Byte count 4 hex (= 4)
Data HI 13 hex Speed reference = 1388 hex (=5000 => 50.00%)
Data LO 88 hex
Data HI 09 hex Output Frequency = 09C4 hex (=2500 =>25.00Hz)
Data LO C4 hex
ERROR CRC HI 78 hexCRC field 78E9 hex (=30953)
CHECK CRC LO E9 hex

Reply frame:

Table 44.
01 04 04 13 88 09 C4 78 E9

Example of an exception response

In an exception response, the Slave sets the most-significant bit (MSB) of the function code to 1.
The Slave returns an exception code in the data field.
Command Master - Slave:

Table 45.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 04 hex Function 4 hex (= 4)
DATA Starting address HI 17 hex Starting address 1770 hex (= 6000)
Starting address LO 70 hex
No. of registers HI 00 hex Invalid number of registers 0005 hex (= 5)
No. of registers LO 05 hex

24-hour support +358 (0)201 212 575 • Email: [email protected]

6
 vacon • 42 Communications

Table 45.
ERROR CRC HI 34 hex
CHECK CRC LO 66 hex CRC field 3466 hex (=13414)

Message frame:

Table 46.
01 04 17 70 00 05 34 66

Exception response:
Answer Slave - Master:

Table 47.
ADDRESS 01 hex Slave address 1 hex (= 1)
FUNCTION 84 hex Most significant bit set to 1
ERROR CODE 04 hex Error code 04 => Slave Device Failure
ERROR CRC HI 42 hex CRC field 42C3 hex (= 17091)
CHECK CRC LO C3 hex

Reply frame:

Table 48.
01 84 04 42 C3

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
6
Fault tracing vacon • 45

7. FAULT TRACING
When an unusual operating condition is detected by the AC drive control diagnostics, the drive
initiates a notification visible, for example, on the keypad. The keypad will show the ordinal number
of the fault, the fault code and a short fault description.
The fault can be reset with the Reset button on the control keypad or via the I/O terminal. The faults
are stored in the Fault history menu which can be browsed. The different fault codes you will find in
the table below. This fault table presents only the faults related to the fieldbus in use.
NOTE! When contacting distributor or factory because of a fault condition, always write down all
texts and codes on the keypad display and send a description of the problem together with the Drive
Info File to [email protected].

7.1 Typical fault conditions

Table 49. Typical fault conditions

Fault condition Possible cause Remedy
Install termination resis-
Termination
Missing or excessive termination resistor. tors at both ends of the
resistor
fieldbus line.
• Supply or motor cables are located
too close to the fieldbus cable
Cabling
• Wrong type of fieldbus cable
• Too long cabling
Ensure grounding in all
Grounding Inadequate grounding.
points on the net
Faulty connections.
• Excessive stripping of cables
Connections
• Conductors in wrong terminals
• Too loose connections of conductors
• Faulty address
• Overlapping slave addresses
Parameter
• Wrong baud rate
• Wrong control place selected

7.2 RS-485 bus biasing

When none of the devices on the RS-485 bus is sending data, all devices are in idle status. This being
the case, the bus voltage is in indefinate state, usually near 0 V due to the termination resistors. This
may cause problems in character reception because the single characters in serial communication
begin with start bit referring to bus status '0' with voltage of less than -200mV whereas the bus
status '1' corresponds to bus voltage of more than +200mV. The RS-485 standard considers the
voltage interval -200mV...+200mV as undefined state. Bus biasing is therefore needed to maintain
the voltage in status ‘1’ (above +200mV) also between the messages.
To bias the bus you will have to add a separate active termination resistor specifically designed for
the RS-485 bus (e.g. Siemens active RS 485 terminating element (6ES7972-0DA00-0AA0)).

24-hour support +358 (0)201 212 575 • Email: [email protected]

7
7
7.3
vacon • 46

Drive does not Check communi- Is the device in Is fieldbus selected Does Master give
start from the bus cation status (par. READY state? as control place? RUN command?
5.7.3.2.1/5.8.3.2.2)

Counter does not Check the led on Check parameter

Use keypad to
run keypad M1.15 or M3.2.1 monitor variable
Counter for bad Check external
frames (see Table interlockings (I/O)
3) increases
.
Counter OK
Other fault conditions

No communication
Check fieldbus Check Master’s Check termination
parameters parameters Check cabling Other bus devices
resistors

Check selected Check configura- Check that both Check cable for Check other
If the problem persists contact your local distributor.

protocol tions (Slave add- ends of the fieldbus cuts necessary devices
line have termina- (e.g. router)
ress, baudrate etc.) tion resistors
Check other field- Check correct place-
bus parameters in (chapter 4.4) ment of conductors
menu in terminals

Poor Check termination

communication Check cabling Check grounding Check connections
resistors

Figure 4. Fault tracing diagram for Modbus RTU

Check that both Check distances Check grounding, Check stripping of
ends of the fieldbus between cables, see chapter 4. Re- cables and
line have termi- see chapter 4.4. member to make conductors, see
nation resistors grounding for each chapter 4.
(chapter 4.4) Check cable types, device!
Check parameters see chapter 3. Check terminals for

9330.emf
loose connections
The following fault tracing diagram will help you to locate and fix some of the most usual problems.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
Fault tracing
 Drive does not Check communi- Is the device in Is fieldbus selected Does Master give
Fault tracing

start from the bus cation status (par. READY state? as control place? RUN command?
5.7.3.2.1/5.8.3.2.2)

Counter does not Check the led on Check parameter Use keypad to
run keypad M1.15 OR P3.2.1 monitor variable
Counter for bad Check external
frames (see Table interlockings (I/O)
3) increases
.
Counter OK
No communication
Check fieldbus Check Master’s
parameters parameters Check cabling Other bus devices

Check selected Check cable for Check other

Check IP address, cuts necessary devices
protocol

24-hour support +358 (0)201 212 575 • Email: [email protected]

gateway etc. (e.g. router)
Check other field- Check correct place-
bus parameters in ment of conductors
menu in terminals

Poor
communication Check cabling Check connections

Figure 5. Fault tracing diagram for Modbus TCP

Check distances Check stripping of
between cables, cables and
see chapter 4.4. conductors, see
chapter 4.
Check cable types
and lenghts, see Check e.g WLAN
chapter 3. or other routers

9329.emf
vacon • 47

7
 vacon • 48 Quick setup

8. QUICK SETUP
Following these instructions, you can easily and fast set up your Modbus for use:

Choose control place.

A. Press LOC/REM button on keypad to select Remote Control Place
1
B. Select Fieldbus as remote control place: Main Menu > Quick Setup (M1) >
Rem. Ctrl. Place (P1.15) > FieldbusCTRL
Make these settings in the master software
A. Set Control Word to '0' by writing the data 0000h to the register 2001d.
B. Set Control Word to '1' by writing the data 0001h to the register 2001d.
C. AC drive status is RUN
2 D. Set Speed Reference value to '5000' (=50.00%) by writing the data 1388h to the
register 2003d.
E. Actual speed is 5000 (25.00 Hz if MinFreq is 0.00 Hz and MaxFreq is 50.00 Hz)
F. Set Control Word to '0' by writing the data 0000h to the register 2001d.
G. AC drive status is STOP.

Tel. +358 (0) 201 2121 • Fax +358 (0)201 212 205
8
Annex vacon • 49

9. ANNEX
Process Data IN (Master to Slave)
Use of Process Data In variables depends on the used application. The configuration of the data is
free.

Process Data OUT (Slave to Master)

Use of Process Data Out variables depends on the used application.
The Fieldbus Master can read the AC drive’s actual values using process data variables. Control
applications use process data as follows:

Table 50. Process Data OUT variables

Table 51.

Register Data Default ID Information Unit

2104 Process data OUT 1 1 Output Frequency 0.01 Hz
2105 Process data OUT 2 2 Motor Speed 1 rpm
2106 Process data OUT 3 3(45)2 Motor Current 0.1 A
2107 Process data OUT 4 4 Motor Torque 0.1 %
2108 Process data OUT 5 5 Motor Power 0.1 %
2109 Process data OUT 6 6 Motor Voltage 0.1 V
2110 Process data OUT 7 7 DC link voltage 1V
2111 Process data OUT 8 37 Active Fault Code -

NOTE 1! In Vacon 100, the Motor Current scale depends on the drive size. In Vacon 100 HVAC the
Motor Current scale is always 0.1 A.
NOTE 2! In Vacon 100 HVAC, the default ID is 45 meaning "Motor Current 1 Decimal". In Vacon 100,
the default ID is 3 for Motor Current. The ID 45 can be mapped by the user to this variable also in
Vacon 100.

24-hour support +358 (0)201 212 575 • Email: [email protected]

9
 www.danfoss.com

Document ID:

Vacon Ltd
Member of the Danfoss Group
Runsorintie 7 Rev. C
65380 Vaasa
Finland Sales code: DOC-INSMODBUS+DLUK