Vacon nxs User manual

vacon nx

ac drives

optc2/c8

modbus/n2 option board

user manual

INDEX Document code: DPD00899A

Date 19.01.2012

1. GENERAL ........................................................................................................................... 3

2.

RS-485 OPTION BOARD TECHNICAL DATA ........................................................................ 4

2.1 General ......................................................................................................................................... 4

3.

RS-485 FIELDBUS BOARD LAYOUT AND CONNECTIONS ................................................... 5

3.1 RS-485 OPTC2 option board ......................................................................................................... 5

3.2 RS-485 OPTC8 option board ......................................................................................................... 6

3.3 Grounding ..................................................................................................................................... 7

3.3.1 Grounding by clamping the cable to the converter frame .................................................7

3.3.2 Grounding only one point on the net ..................................................................................9

3.3.3 Grounding jumper X1 ....................................................................................................... 10

3.4 Bus terminal resistors................................................................................................................ 11

3.5 Bus Biasing ................................................................................................................................. 12

3.6 LED indications ........................................................................................................................... 13

4.

INSTALLATION OF VACON NX RS-485 BOARD ................................................................. 14

5.

COMMISSIONING .............................................................................................................. 16

5.1 Fieldbus board parameters ........................................................................................................ 16

6.

MODBUS ........................................................................................................................... 19

6.1 Modbus RTU protocol, introduction ............................................................................................ 19

6.1.1 Supported functions ......................................................................................................... 21

6.1.2 Exception responses ........................................................................................................ 23

6.2 Modbus interface ........................................................................................................................ 25

6.2.1 Modbus registers ............................................................................................................. 25

6.2.2 Process data .................................................................................................................... 25

6.2.3 Process data in ................................................................................................................ 26

6.2.4 Process data out .............................................................................................................. 27

6.2.5 Parameters ...................................................................................................................... 30

6.2.6 Actual values .................................................................................................................... 30

6.2.7 Example messages .......................................................................................................... 31

6.3 Start-up test ............................................................................................................................... 33

7.

METASYS N2 ..................................................................................................................... 34

7.1 Metasys N2 Protocol Introduction .............................................................................................. 34

7.2 Metasys N2 interface .................................................................................................................. 34

7.2.1 Analogue Input (AI) .......................................................................................................... 34

7.2.2 Binary Input (BI) ............................................................................................................... 34

7.2.3 Analogue Output (AO)....................................................................................................... 35

7.2.4 Binary Output (BO) ........................................................................................................... 35

7.2.5 Internal Integer (ADI) ....................................................................................................... 35

7.3 N2 POINT MAP ............................................................................................................................ 36

7.3.1 Analogue Inputs (AI) ......................................................................................................... 36

7.3.2 Binary Inputs (BI) ............................................................................................................. 37

7.3.3 Analogue Outputs (AO) ..................................................................................................... 37

7.3.4 Binary Outputs (BO) ......................................................................................................... 38

7.3.5 Internal Integers (ADI) ..................................................................................................... 38

8.

FAULT TRACKING ............................................................................................................. 39

APPENDIX 1 ............................................................................................................................................ 40

general vacon • 3

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

1

1. GENERAL

Instead of sending and receiving information to and from frequency converters through I/O, you can

connect them to a fieldbus.

Vacon NX frequency converters can be connected to the RS-485 bus using a fieldbus board. The con-

verter can then be controlled, monitored and programmed from the host system.

If you purchase your RS-485 Option Board separately, please note that it shall be installed in

slot E on

the control board of the frequency converter.

WARNING!

Internal components and circuit boards are at high potential when the frequency

converter is connected to the power source. This voltage is extremely dangerous

and may cause death or severe injury if you come into contact with it.

4 • vacon technical data

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

2

2. RS-485 OPTION BOARD TECHNICAL DATA

2.1 General

Connections

Interface

OPTC2

: Pluggable connector (5.08mm)

OPTC8

: 9-pin DSUB connector (female)

Data transfer

method

RS-485, half-duplex

Transfer cable Twisted pair (1 pair and shield)

Electrical isolation 500 VDC

Communications

Modbus RTU

Metasys N2

As described in document “Modicon Modbus Protocol

Reference Guide”

Find it for example at: http://public.modicon.com/

As described in Metasys N2 System Protocol Specifica-

tion

Baud rate 300, 600, 1200, 2400, 4800, 9600, 19200 and 38400 kbaud

Addresses 1 to 247

Environment

Ambient operating

temperature

–10°C…55°C

Storing tempera-

ture

–40°C…60°C

Humidity <95%, no condensation allowed

Altitude Max. 1000 m

Vibration 0.5 G at 9…200 Hz

Safety

Fulfils EN50178 standard

Table 1. RS-485 technical data

layout and connections vacon • 5

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

3

3. RS-485 FIELDBUS BOARD LAYOUT AND CONNECTIONS

Vacon RS-485 Fieldbus Board is connected to the fieldbus through either a 5-pin pluggable bus con-

nector (board OPTC2) or a 9-pin female sub-D-connector (board OPTC8).

The communication with the control board of the frequency converter takes place through the stan-

dard Vacon Interface Board Connector.

3.1 RS-485 OPTC2 option board

Figure 1. Vacon RS-485 option board OPTC2

Signal

Connector

Description

NC* 1* No connection

VP 2 Supply voltage – plus (5V)

RxD/TxD –N 3 Receive/Transmit data – A

RxD/TxD –P 4 Receive/Transmit data – B

DGND 5 Data ground (reference potential for VP)

*You can use this pin (1) to bypass the cable shield to the next slave

Table 2. OPTC2 bus connector signals

X4

X1

Bus connector

Jumpers Interface board connector

Grounding plate

1

2

3

4

5

6 • vacon layout and connections

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

3

3.2 RS-485 OPTC8 option board

Figure 2. Vacon RS-485 option board OPTC8

Signal

Connector

Description

Shield 1 Cable shield

RxD/TxD-N 3 Receive/ A

DGND 5 Data ground (reference potential for VP)

VP 6 Supply voltage – plus (5V)

RxD/TxD-P 8 Receive/ Transmit data/ B

Table 3. OPTC8 bus connector signals

X4

X1

Bus connector

Jumpers Interface board connector

Grounding plate

12345

9 8 7 6

layout and connections vacon • 7

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

3

3.3 Grounding

3.3.1

Grounding by clamping the cable to the converter frame

This manner of grounding is the most effective and especially recommended when the distances be-

tween the devices are relatively short or if the device is the last device on

the net.

Note: Normally, the option board has already been installed in slot D or slot E of the control board. It

is not necessary to detach the whole board for the grounding of the bus cable shield. Just detach the

terminal block.

1 Strip about 5 cm of the cable and cut off the grey cable shield.

Remember to do this for both bus cables (except for the last device). See pictures below.

2 Leave no more than 1 cm of the cable outside the terminal block and strip the data cables at

about 0.5 cm to fit in the terminals. See pictures below.

Note: Do this for both bus cables.

Figure 3.

Figure 4.

3 Insert the data cables of both cables into terminals #3 (Line B) and #4 (Line A).

4 Strip the cable at such a distance from the terminal that you can fix it to the frame with the

grounding clamp. See

1 2 3 4 5

B

A

Cut here

Strip this part

8 • vacon layout and connections

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

3

Figure 5.

layout and connections vacon • 9

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

3

3.3.2

Grounding only one point on the net

In this manner of grounding, the shield is connected to ground only at the last device on the net in the

same way as described in chapter 3.3.1. Other devices of the net just pass the shield.

We recommend you to use an Abico connector to fit the shields into the terminal.

1 Strip about 5 cm of the cable and cut off the grey cable shield. Remember to do this for both

bus cables (except for the last device).

2 Leave no more than 1 cm of the cable outside the terminal block and strip the data cables at

about 0.5 cm to fit in the terminals. See Figure 6.

Note: Do this for both bus cables.

Figure 6.

3 Fix both the cables on the frame with the clamp. See Figure 7.

Figure 7.

1 2 3 4 5

B

A

Shield

10 • vacon layout and connections

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

3

3.3.3

Grounding jumper X1

The Grounding jumper X1 on the OPTC8 is used for grounding selection. If position ON is selected it

means that the D-sub connector PIN1 is connected directly to ground. Selection of position OFF

means that PIN1 is connected to ground via an RC-filter. Jumper X1 has no effect on OPTC2.

Figure 8. Grounding jumper X1

X4

X1

ON

OFF

12345

9 8 7 6

layout and connections vacon • 11

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

3

3.4 Bus terminal resistors

If Vacon is the last device of the fieldbus line the bus termination must be set. Use jumper X4 (ON po-

sition) or external termination resistors (e.g. in DSUB-9 connector). See Figure 9.

Figure 9. Using jumper X4 to set the bus termination.

X4

X1

12345

9 8 7 6

ON

OFF

12 • vacon layout and connections

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

3

3.5 Bus Biasing

Bus biasing is required to ensure faultless communication between devices at RS-485 bus. Bus bias-

ing makes sure that the bus state is at proper potential when no device is transmitting. Without bias-

ing, faulty messages can be detected when the bus is in idle state. RS-485 bus state should be

neather +0,200..+7V or –0,200..-7V. Illegal bus state is <200mV..-200mV.

Number of nodes Bias resistance

2-5 1.8 kohm

5-10 2.7 kohm

11-20 12 kohm

21-30 18 kohm

31-40 27 kohm

Table 4. Bias resistor size vs number of node

Fail safe

biasing in OPTC2 option board

Connect resistor biasing resistors between pins #2 and #4 as well as pins #3 and #5 as shown in pic-

ture.

Matters related to this are discussed in the application note

Failsafe Biasing of Differential Buses

(an-

847.pdf) published by National Semiconductor (www.national.com).

DATA-

DATA+

5

1

2

3

4

5

A

B

layout and connections vacon • 13

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

3

3.6 LED indications

The two LED indications next to the connector show the present statuses of the RS-485 board (yellow)

and the Fieldbus Module (green).

Figure 10. LED indications on the RS-485 board

RS-485 board status LED (BS) YELLOW

LED is:

Meaning:

OFF Option board not activated

ON Option board in initialisation state waiting for activation

command from the frequency converter

Blinking fast

(once/sec)

Option board is activated and in RUN state

•

Option board is ready for external communication

Blinking

slow

(once/5 secs)

Option board is activated and in FAULT state

• Internal fault of option board

Fieldbus status LED (FS) GREEN

LED is:

Meaning:

OFF Fieldbus module is waiting for parameters from the fre-

quency converter

•

No external communication

ON Fieldbus module is activated

• Parameters received and module activated

•

Module is waiting for messages from the bus

Blinking fast

(once/sec)

Module is activated and receiving messages from the bus

Blinking

slow

(once/5 secs)

Module is in FAULT state

• No messages from Master within the watchdog time

•

Bus broken, cable loose or Master off line

X4

X1

1

2

3

4

5

Yellow

Green

14 • vacon installation

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

4

4. INSTALLATION OF VACON NX RS-485 BOARD

A

Vacon NX frequency converter

B

Remove the cable cover.

C

Open the cover of the control unit.

installation vacon • 15

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

4

D

Install RS-485 option board in slot E on the control board of the frequency con-

verter. Make sure that the grounding plate (see below) fits tightly in the clamp.

E

Make a sufficiently wide opening for

your cable by cutting the grid as wide as

necessary.

F

Close the cover of the control unit and

the cable cover.

X4

X1

1

2

3

4

5

16 • vacon modbus

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

5

5. COMMISSIONING

READ FIRST CHAPTER 8 'COMMISSIONING' IN VACON NX USER'S MANUAL (Document nr. ud00701,

please visit http://www.vacon.com/925.html).

Note! You must select Fieldbus as the active control place, if you wish to control the frequency con-

verter through fieldbus. See Vacon NX User’s Manual, Chapter 7.3.3.1.

5.1 Fieldbus board parameters

The Vacon RS-485 board is commissioned with the control keypad by giving values to appropriate pa-

rameters in menu

M7 (for locating the expander board menu see Vacon NX User's Manual, Chapter

7).

Expander board menu (M7)

The

Expander board menu

makes it possible for the user 1) to see what expander boards are con-

nected to the control board and 2) to reach and edit the parameters associated with the expander

board.

Enter the following menu level

(G#) with the

Menu button right

. At this level, you can browse through

slots A to E with the

Browser buttons

to see what expander boards are connected. On the lowermost

line of the display you also see the number of parameter groups associated with the board.

If you still press the

Menu button right

once you will reach the parameter group level where there are

two groups: Editable parameters and Monitored values. A further press on the

Menu button right

takes you to either of these groups.

RS-485 parameters

To commission the RS-485 board, enter the level P7.5.1.# from the

Parameters

group (G7.5.1). Give

desired values to all RS-485 parameters (see Figure 11 and Table 5).

Figure 11. Changing the RS-485 board commissioning parameter values

Expander Board

G1



G5

READY

I/Oterm

NXOPTC5

READY

I/Oterm

G1



G2

Slave address

READY

I/Oterm

126

enter

CHANGE VALUE

CONFIRM CHANGE

Parameters

READY

I/Oterm

P1



P4

Slave address

READY

I/Oterm

126

commissioning vacon • 17

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

5

#

Name

Default

Range

Description

1 COMMUNICATION

PROTOCOL

1

1 – Modbus RTU

2 – N2

Protocol

2

SLAVE ADDRESS

1

1…247

3 BAUD RATE

6

1 – 300 baud

2 – 600 baud

3 – 1200 baud

4 – 2400 baud

5 – 4800 baud

6 – 9600 baud

7 – 19200 baud

8 – 38400 baud

Communication speed

When N2 protocol is used

Baudrate

must be set to 9600.

4 PARITY TYPE

0

0 – None

1 – Even

2 – Odd

Describes what kind of parity checking

is used.

When N2-protocol is used

Pari

ty

type

must be set to 0 = None

5 COMMUNICATION

TIMEOUT

20

0—OFF

1—300 s

See chapter Communication timeout

below

6 OPERATE MODE 1 1 – Normal Reserved for later use

Table 5. RS-485 parameters

The parameters of every device must be set before connecting to the bus. Especially the parameters

Communication Protocol

,

Slave Address

and

Baud Rate

must be the same as in the master configura-

tion.

Communication timeout

The RS-485 board initiates a communication error if communication is broken for as long as defined

by the

Communication Timeout

.

Communication Timeout

is disabled when given the value 0.

Communication status

To see the present status of the RS-485 fieldbus, enter the

Comm.Status

page from

Monitor

menu

(G7.5.2). See Figure 12 and Table 6 below.

Figure 12. Communication status

Monitor

READY

I/Oterm

V1



V1

READY

I/Oterm

0.841

Comm. status

Error messages

Good messages

18 • vacon modbus

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

5

Good messages

0…999 Number of messages received without

communication errors

Error messages

0…64 Number of messages received with

CRC or parity errors

Table 6. RS-485 message indications

modbus vacon • 19

24-hour support +358 (0)40 8371 150 • Email: va[email protected]

6

6. MODBUS

6.1 Modbus RTU protocol, introduction

The MODBUS protocol is an industrial communications and distributed control system to integrate

PLCs, computers, terminals, and other monitoring, sensing, and control devices. MODBUS is a Mas-

ter-Slave communications protocol. The Master controls all serial activity by selectively polling one or

more slave devices. The protocol provides for one master device and up to 247 slave devices on a

common line. Each device is assigned an address to distinguish it from all other connected devices.

The MODBUS protocol uses the master-slave technique, in which only one device (the master) can

initiate a transaction. The other devices (the slaves) respond by supplying the request data to the

master, or by taking the action requested in the query. The master can address individual slaves or

initiate a broadcast message to all slaves. Slaves return a message (‘response’) to queries that are

addressed to them individually. Responses are not returned to broadcast queries from the master.

A transaction comprises a single query and single response frame or a single broadcast frame. The

transaction frames are defined below.

Master's

message

Slave

response

START

ADDRESS ADDRESS

FUNCTION FUNCTION

DATA

CRC

END

Figure 13. The basic structure of a Modbus frame

Valid slave device addresses are in the range of 0 ... 247 decimal. The individual slave devices are as-

signed addresses in the range of 1 ... 247. A master addresses a slave by placing the slave address in

the address field of the message. When the slave sends its response, it places its own address in this

address field of the response to let the master know which slave is responding.

The function code field of a message frame contains two characters (ASCII) or eight bits (RTU). Valid

codes are in the range of 1 ... 255 decimal. When a message is sent from a master to a slave device

the function code field tells the slave what kind of action to perform. Examples are to read the ON /

OFF states of a group of discrete coils or inputs; to read the data contents of a group of registers; to

20 • vacon modbus

Tel.+358 (0)201 2121 • Fax +358 (0)201 212 205

6

read the diagnostic status of the slave; to write to designated coils or registers; or to allow loading,

recording, or verifying the program within the slave.

When the slave responds to the master, it uses the function code field to indicate either a normal (er-

ror-free) response or that some kind of error occurred (called an exception response). For a normal

response, the slave simply echoes the original function code. For an exception response, the slave

returns a code that is equivalent to the original function code with its most significant bit set to a logic

1.

The data field is constructed using sets of two hexadecimal digits, in the range of 00 to FF hexadeci-

mal. These can be made from a pair of ASCII characters, or from one RTU character, according to the

network's serial transmission mode.

The data field of messages sent from a master to slave devices contains additional information which

the slave must use to take the action defined by the function code. This can include items like discrete

and register addresses, the quantity of items to be handled, and the count of actual data bytes in the

field.

If no error occurs, the data field of a response from a slave to a master contains the data requested. If

an error occurs, the field contains an exception code that the master application can use to determine

the next action to be taken.

Two kinds of checksum are used for standard Modbus networks. The error checking field contents

depend upon the transmission method that is being used.

Page is loading ...

Vacon nxs User manual

Related papers

Other documents