al2-mbu - contrive wireless products advanced manual... · 2018. 12. 20. · al2-mbu advanced...

AL2-MBU Advanced Manual

REVISION 003.08

December 2008

AL2-MBU Advanced Manual - 1

REVISION LIST

001.08 January 2008 Preliminary version

002.08 June 2008 First official release

003.08 December 2008 New feature: Force Multiple Coils Specific Registers for AlphaXL timeout THE INFORMATION CONTAINED IN THIS DOCUMENT ARE SUBJECT TO CHANGE WITHOUT NOTICE.

PRODUCT NAMES, CORPORATE NAMES, OR TITLES USED WITHIN THIS DOCUMENT MAY BE TRADEMARKS OR REGISTERED TRADEMARKS OF OTHER COMPANIES, AND ARE MENTIONED ONLY IN AN EXPLANATORY MANNER TO THE READERS‟ BENEFIT, AND WITHOUT INTENTION TO INFRINGE. WHILE EVERY EFFORT HAS BEEN MADE TO MAKE SURE THE INFORMATION IN THIS DOCUMENT IS CORRECT, CONTRIVE CAN NOT BE LIABLE FOR ANY DAMAGES WHATSOEVER FOR LOSS RELATING TO THIS DOCUMENT. MODBUS® IS A REGISTERED TRADEMARK OF SCHNEIDER ELECTRIC. © COPYRIGHT 2008 CONTRIVE SRL ITALY.ALL RIGHT RESERVED.


1. INTRODUCTION TO MODBUS .................................................................................. 4

2. MODBUS REGISTER MAP ........................................................................................ 5

2.1 AL2 Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 AL2 External Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.3 AL2 L ink Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.4 AL2 Communicat ion Bit devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.5 AL2 System Bi t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.6 AL2 Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.7 AL2 External Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.8 AL2 L ink Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.9 AL2 Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.10 AL2 Communicat ion W ord devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3. MODBUS SERIAL TRANSMISSION MODE ................................................................. 13

3.1 Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.2 Par it y. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3 AlphaXL communicat ion t imeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4. MODBUS ADDRESSES ................................................................................................ 14

5. MODBUS FUNCTIONS ................................................................................................. 14

5.1 Read Coi l Status - 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1.1 Example ........................................................................................................................................ 15

5.2 Read Input Status - 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.2.1 Example ........................................................................................................................................ 16

5.3 Read Hold ing Register - 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.3.1 Example ........................................................................................................................................ 17

5.4 Read Input Registers - 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.4.1 Example ........................................................................................................................................ 18

5.5 Force Single Coi l - 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.5.1 Example ........................................................................................................................................ 19

5.6 Force Multp le Coi ls - 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.6.1 Example ........................................................................................................................................ 20

5.7 Preset Single Register - 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.7.1 Example ........................................................................................................................................ 21

5.8 Device Ident i f icat ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.8.1 Categories of objects .................................................................................................................... 22 5.8.2 Identification request .................................................................................................................... 22


6. MODBUS ERROR CHECKING ..................................................................................... 23

7. MODBUS EXCEPTIONS ............................................................................................... 23

8. HARDWARE ................................................................................................................. 24

8.1 Terminal Des ignat ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.1 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.2 Format Sett ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8.3 Address Sett ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8.4 Baud Rate and Par ity Sett ings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9. PHYSICAL INTERFACE ............................................................................................... 26

9.1 Isolated Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.2 Non Isolated Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6. EXAMPLES WITHOUT COMM MEMORY .................................................................... 29

6.1 Contro l through ASi channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6.2 Contro l through External Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6.3 Contro l through External Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7. EXAMPLES WITH COMM MEMORY ............................................................................ 32

7.1 Set outputs f rom local and remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7.2 Read/Write local var iables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7.3 Read Analog Input / W rite Analog Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


1. INTRODUCTION TO MODBUS The Modbus protocol provides an industry standard method that Modbus devices use for parsing messages. This protocol was developed by Modicon Inc. for industrial automation systems and programmable controllers. Modbus devices communicate using a master-slave technique in which only one device (the master) can initiate transactions (called queries). The other devices (slaves) respond by supplying the requested data to the master, or by taking the action requested in the query. A slave is any peripheral device (PLC, I/O transducer, valve, network drive, or other devices) which processes information and sends its output to the master using Modbus. Masters can address individual slaves, or can initiate a broadcast message to all slaves. Slaves return a response to all queries addressed to them individually, but do not respond to broadcast queries. A master's query consists of a slave address (or broadcast address), a function code defining the requested action, any required data, and an error checking field. A slave's response consists of fields confirming the action taken, any data to be returned, and an error checking field. Note that the query and response both include a device address, plus a function code, plus applicable data, and an error checking field. If no error occurs, the AL2-MBU will answer within the specified AlphaXL COM TIMEOUT with the requested data (the maximum answer time: factory default = 6,6 seconds including Tw, TP and data transfer). If an error occurs in the query received, or if the slave is unable to perform the action requested, the slave will return an exception message as its response (see Modbus Exceptions). The error check field of the message frame allows the master to confirm that the contents of the message are valid. Additionally, parity checking is also applied to each transmitted character in its data frame control.


2. MODBUS REGISTER MAP

Modbus functions operate on map registers to monitor, configure, and control I/O. Modbus registers are organized into reference types identified by the leading number of the reference address. The leading character is generally implied by the function code and omitted from the address specifier for a given function. The leading character also identifies the I/O data type.

2.1 AL2 Outputs

Up to 9 channels can be read and/or set from remote, depending on the controller type. When the output channel is linked to a program Function Block it could be overwritten by the controller at further cycle.

MO

DB

US

CO

ILS

0 0001 O 01

AL2

OU

TS

Supported Modbus Funct ions:

01 Read Single Coi l

05 Force Single Coi l 15 Force Mult iple Coi ls

0 0002 O 02

0 0003 O 03

0 0004 O 04

0 0005 O 05

0 0006 O 06

0 0007 O 07

0 0008 O 08

0 0009 O 09

2.2 AL2 External Outputs

Up to 4 channels can be read and/or set from remote when the boards AL2-4EYT or AL2-4EYR have been installed into the expansion slot. When the expansion output board is not installed these could be used like virtual channels.

MO

DB

US

CO

ILS

0 0010 EO 01

AL2

EX

T

OU

TS


01 Read Single Coi l 05 Force Single Coi l

0 0011 EO 02

0 0012 EO 03

0 0013 EO 04

2.3 AL2 Link Outputs

Up to 4 channels can be read and/or set from remote when the board AL2-ASI-BD has been installed into the expansion slot. When the expansion output board is not installed these could be used like virtual channels.

MO

DB

US

CO

ILS

0 0014 AO 01

AL2

LIN

K

OU

TS



0 0015 AO 02

0 0016 AO 03

0 0017 AO 04


2.4 AL2 Communication Bit devices

50 or 100 Communication Bits could be optionally assigned to Communication Memory. CB are associated to any bit of FB used within the program and can be read or set from remote.

MO

DB

US

CO

ILS

0 0018 CB 1

AL2

CO

MM

UN

ICA

TIO

N B

ITS



05 Force Single Coi l

0 0019 CB 2

0 0020 CB 3

0 0021 CB 4

0 0022 CB 5

0 0023 CB 6

0 0024 CB 7

0 0025 CB 8

0 0026 CB 9

0 0027 CB 10

0 0028 CB 11

0 0029 CB 12

0 0030 CB 13

0 0031 CB 14

0 0032 CB 15

0 0033 CB 16

0 0034 CB 17

0 0035 CB 18

0 0036 CB 19

0 0037 CB 20

0 0038 CB 21

0 0039 CB 22

0 0040 CB 23

0 0041 CB 24

0 0042 CB 25

0 0043 CB 26

0 0044 CB 27

0 0045 CB 28

0 0046 CB 29

0 0047 CB 30

0 0048 CB 31

0 0049 CB 32

0 0050 CB 33

0 0051 CB 34

0 0052 CB 35

0 0053 CB 36

0 0054 CB 37

0 0055 CB 38

0 0056 CB 39

0 0057 CB 40


MO

DB

US

CO

ILS

0 0058 CB 41

AL2

CO

MM

UN

ICA

TIO

N B

ITS



0 0059 CB 42

0 0060 CB 43

0 0061 CB 44

0 0062 CB 45

0 0063 CB 46

0 0064 CB 47

0 0065 CB 48

0 0066 CB 49

0 0067 CB 50

0 0068 CB 51

0 0069 CB 52

0 0070 CB 53

0 0071 CB 54

0 0072 CB 55

0 0073 CB 56

0 0074 CB 57

0 0075 CB 58

0 0076 CB 59

0 0077 CB 60

0 0078 CB 61

0 0079 CB 62

0 0080 CB 63

0 0081 CB 64

0 0082 CB 65

0 0083 CB 66

0 0084 CB 67

0 0085 CB 68

0 0086 CB 69

0 0087 CB 70

0 0088 CB 71

0 0089 CB 72

0 0090 CB 73

0 0091 CB 74

0 0092 CB 75

0 0093 CB 76

0 0094 CB 77

0 0095 CB 78

0 0096 CB 79

0 0097 CB 80

0 0098 CB 81

0 0099 CB 82

0 0100 CB 83

0 0101 CB 84

0 0102 CB 85


MO

DB

US

CO

ILS

0 0103 CB 86

AL2

CO

MM

UN

ICA

TIO

N B

ITS



05 Force Single Coi l

0 0104 CB 87

0 0104 CB 88

0 0106 CB 89

0 0107 CB 90

0 0108 CB 91

0 0109 CB 92

0 0110 CB 93

0 0111 CB 94

0 0112 CB 95

0 0113 CB 96

0 0114 CB 97

0 0115 CB 98

0 0116 CB 99

0 0117 CB 100

2.5 AL2 System Bit

Predefined system informations. Ref.: Programming Manual § 2.1.3

MO

DB

US

CO

ILS

0 0118 M 01

AL2

SY

ST

EM

BIT

S



0 0119 M 02

0 0120 M 03

0 0121 M 04

0 0122 M 05

0 0123 M 06

0 0124 M 07

0 0125 M 08

0 0126 M 09

0 0127 M 10

0 0128 M 11

0 0129 M 12

0 0130 M 13

0 0131 M 14

0 0132 M 15

0 0133 M 16

0 0134 M 17

0 0135 M 18

0 0136 M 19

0 0137 M 20

0 0138 M 21

0 0139 M 22

0 0140 M 23

0 0141 M 24


2.6 AL2 Inputs

Up to 15 channels can be read from remote, depending on the controller type.

MO

DB

US

CO

ILS

1 0142 I 01

AL2

INP

UT

S


02 Read Input Status

05 Force Single Coi l §

1 0143 I 02

1 0144 I 03

1 0145 I 04

1 0146 I 05

1 0147 I 06

1 0148 I 07

1 0149 I 08

1 0150 I 09

1 0151 I 10

1 0152 I 11

1 0153 I 12

1 0154 I 13

1 0155 I 14

1 0156 I 15

2.7 AL2 External Inputs

Up to 4 channels can be read from remote when the boards AL2-4EX or AL2-4EXR have been installed into the expansion slot. When the expansion output board is not installed these could be used like virtual channels.

MO

DB

US

CO

ILS

1 0157 EI 01

AL2

EX

T

INP

UT

S Supported Modbus Funct ions:



1 0158 EI 02

1 0159 EI 03

1 0160 EI 04

2.8 AL2 Link Inputs

Up to 4 channels can be read from remote when the board AL2-ASI-BD has been installed into the expansion slot. When the expansion output board is not installed these could be set like virtual coils.

MO

DB

US

CO

ILS

0 0161 E 01

AL2

LIN

K

INP

UT

S




0 0162 E 02

0 0163 E 03

0 0164 E 04

§ Could also be set from remote like any coil, but it will be overwritten by controller at further

cycle (could make a pulse).


2.9 AL2 Analog Inputs

Up to 8 channels can be read from remote, depending on the controller type.

MO

DB

US

WO

RD

S

3 0001 AI 01

AL2

AN

ALO

G I

NP

UT

S


04 Read Input Register

3 0002 AI 02

3 0003 AI 03

3 0004 AI 04

3 0005 AI 05

3 0006 AI 06

3 0007 AI 07

3 0008 AI 08

2.10 AL2 Communication Word devices

50 or 100 Communication Words could be optionally assigned to Communication Memory. CW are associated to any word value of FB used within the program and can be read or set from remote.

MO

DB

US

WO

RD

S

4 0001 CW 1

AL2

CO

MM

UN

ICA

TIO

N W

OR

DS


03 Read Hold ing Register 06 Preset Single Register

4 0002 CW 2

4 0003 CW 3

4 0004 CW 4

4 0005 CW 5

4 0006 CW 6

4 0007 CW 7

4 0008 CW 8

4 0009 CW 9

4 0010 CW 10

4 0011 CW 11

4 0012 CW 12

4 0013 CW 13

4 0014 CW 14

4 0015 CW 15

4 0016 CW 16

4 0017 CW 17

4 0018 CW 18

4 0019 CW 19

4 0020 CW 20

4 0021 CW 21

4 0022 CW 22

4 0023 CW 23

4 0024 CW 24

4 0025 CW 25

4 0026 CW 26

4 0027 CW 27

4 0028 CW 28


MO

DB

US

WO

RD

S

4 0029 CW 29

AL2

CO

MM

UN

ICA

TIO

N W

OR

DS


03 Read Hold ing Register 06 Preset Single Register

4 0030 CW 30

4 0031 CW 31

4 0032 CW 32

4 0033 CW 33

4 0034 CW 34

4 0035 CW 35

4 0036 CW 36

4 0037 CW 37

4 0038 CW 38

4 0039 CW 39

4 0040 CW 40

4 0041 CW 41

4 0042 CW 42

4 0043 CW 43

4 0044 CW 44

4 0045 CW 45

4 0046 CW 46

4 0047 CW 47

4 0048 CW 48

4 0049 CW 49

4 0050 CW 50

4 0051 CW 51

4 0052 CW 52

4 0053 CW 53

4 0054 CW 54

4 0055 CW 55

4 0056 CW 56

4 0057 CW 57

4 0058 CW 58

4 0059 CW 59

4 0060 CW 60

4 0061 CW 61

4 0062 CW 62

4 0063 CW 63

4 0064 CW 64

4 0065 CW 65

4 0066 CW 66

4 0067 CW 67

4 0068 CW 68

4 0069 CW 69

4 0470 CW 70

4 0171 CW 71

4 0172 CW 72

4 0173 CW 73


MO

DB

US

WO

RD

S

4 0074 CW 74

AL2

CO

MM

UN

ICA

TIO

N W

OR

DS


03 Read Hold ing Register

06 Preset Single Register

4 0075 CW 75

4 0076 CW 76

4 0077 CW 77

4 0078 CW 78

4 0079 CW 79

4 0080 CW 80

4 0081 CW 81

4 0082 CW 82

4 0083 CW 83

4 0084 CW 84

4 0085 CW 85

4 0086 CW 86

4 0087 CW 87

4 0088 CW 88

4 0089 CW 89

4 0090 CW 90

4 0091 CW 91

4 0092 CW 92

4 0093 CW 93

4 0094 CW 94

4 0095 CW 95

4 0096 CW 96

4 0097 CW 97

4 0098 CW 98

4 0099 CW 99

4 0100 CW 100

The register addresses which are not allocated to any AL2 parameter or data set are invalid. A valid answer is given if at least one of read register or coil is valid, the returned value of those parameters will be 0 (zero). An error is given when all the addressed parameters are not valid. If there is an attempt to write non allocated registers or outside the parameter addresses, the AL2-MBU gateway will return an exception code to the controller.


3. MODBUS SERIAL TRANSMISSION MODE Standard Modbus networks employ one of two types of transmission modes:

ASCII Mode RTU Mode

(hardware selectable on the AL2-MBU board).

The transmission mode defines the bit contents of the message bytes transmitted along the network, and how the message information is to be packed into the message stream and decoded. Some configuration can be modified via the Modbus registers.

3.1 Baud Rate

Default communication baud rate is 9600. New parameters are applied at next power-on.

MO

DB

US

WO

RD

4 0101 0 : 1200

BAUD RATE (kbit/s)




1 : 2400

2 : 4800

3 : 9600

4 : 19200

5 : 38400

6 : 57600

7 : 115200

3.2 Parity

Default communication parity is NONE. New parameters are applied at next power-on.

MO

DB

US

WO

RD

4 0102 0 : NONE PARITY




1 : ODD

2 : EVEN

3.3 AlphaXL communication timeout

Although communication timeout communicating with AlphaXL are the maximum declared on the original literature (Communication Manual § 7.4), the controller may take more time to serve the process: a slave device failure could be returned in such cases. It‟s possible to increase the timeout up to 9 seconds both for Tw and TP. New parameters are applied at next power-on.

MO

DB

US

WO

RD

4 0103 Tw 1…90

TIMEOUT




DEFAULT 35 (3 ,5s)

4 0134 TP 1…90

DEFAULT 1 (100ms)


4. MODBUS ADDRESSES The master device addresses a specific slave device by placing the 8-bit slave address in the address field of the message (RTU Mode). The address field of the message frame contains two characters (in ASCII mode), or 8 binary bits (in RTU Mode). Valid addresses are from 1-247, to be set using rotary switches on the AL2-MBU board. When the slave responds, it places its own address in this field of its response to let the master know which slave is responding. Address 0 is reserved for the broadcast address, which all slave devices on a network recognize. Some functions do not support the broadcast address. A slave device does not issue a response to a broadcast message.

All data addresses in Modbus messages are referenced to 0, with the first occurrence of a data item addressed as item number zero. Further, a function code field already specifies which register group it operates on (i.e. 0x, 1x, 3x, or 4x reference addresses). For example, holding register 40001 is addressed as register 0000 in the data address field of the message. The function code that operates on this register specifies a "holding register" operation and the "4xxxx" reference group is implied. Thus, holding register 40108 is actually addressed as register 006BH (107 decimal).

5. MODBUS FUNCTIONS The following table highlights the subset of standard Modbus functions supported by the AL2-MBU gateway (the reference register addresses that the function operates on are also indicated):

CODE FUNCTION REFERENCE

01 (01H) Read Coi l Status 0xxxx

02 (02H) Read Input Status 1xxxx

03 (03H) Read Holding Registers 4xxxx

04 (04H) Read Input Registers 3xxxx

05 (05H) Force Single Coi l 0xxxx

15 (0FH) Force Mult iple Coi ls 0xxxx

06 (06H) Preset Single Register 4xxxx

43 (2BH) Read Device Ident i f icat ion MEI:01

When the slave device responds to the master, it uses the function code field to indicate either a normal (error-free) response, or that some kind of error has occurred (an exception response). The number of registers/coils returned in a single answer is limited to 64. A valid answer is given if at least one of read coil or register is valid, in such case the value returned for the invalid ones will be 0 (zero). An error is given when the whole addresses are not valid.


5.1 Read Coil Status - 01

This command will read the ON/OFF status of discrete outputs or coils (0x reference addresses) in the slave. Broadcast transmission is not supported. The Read Coil Status query specifies the starting coil (output channel) and quantity of coils to be read. The Read Coil Status in the response message is packed as one coil or channel per bit of the data field. The output status is indicated as 1 for ON (conducting current), and 0 for OFF (not conducting). The LSB of the first data byte corresponds to the status of the coil addressed in the query. The other coils follow sequentially, moving toward the high order end of the byte. Unused bits of the data byte will be set to zero toward the unused high order end of the byte. The number of coils returned in a single answer is limited to 60 (8 bytes).

5.1.1 Example

This example reads the output channel status of coils 0-3 (physical coils 1-4)at slave 247.

QUERY FIELD VALUE (HEX)

Slave address 247 F7

Funct ion code 1 01

Start ing Address (H) 0

00

Start ing Address (L) 00

Number of Points (H) 4

00

Number of Points (L) 04

CRC / LRC - -

Note that the leading character of the 0x reference address is implied by the function code and omitted from the address specified. The starting address 0 (00H) is corresponding to coil 1 (0 0001 – O01).

RESPONSE FIELD VALUE (HEX)


Funct ion code 1 01

Byte count 1 01

Data coi ls 10 0A

CRC / LRC - -

To summarize, the status of coils 3-0 is shown as the byte value 0A hex, or 00001010 binary. Coil 3 is the fifth bit from the left of this byte, and coil 0 is the LSB. The four remaining bits (toward the high-order end) are zero. Reading left to right, the output status of physical coils 4...1 is ON-OFF-ON-OFF.

BINARY 0 0 0 0 1 0 1 0

HEX 0 A

COILS - - - - 4 3 2 1


5.2 Read Input Status - 02

This command will read the ON/OFF status of discrete inputs (1x reference addresses) in the slave. Broadcast transmission is not supported. The Read Input Status query specifies the starting input and quantity of points to be read. The Read Input Status in the response message is packed as one input per bit of the data field. The input status is indicated as 1 for ON (closed, powered), and 0 for OFF (open, not powered). The LSB of the first data byte corresponds to the status of the input addressed in the query. The other inputs follow sequentially, moving toward the high order end of the byte. Unused bits of the data byte will be set to zero toward the unused high order end of the byte. The number of inputs returned in a single answer is limited to 60 (8 bytes).

5.2.1 Example

This example reads the status of input channels 142-145 (physical inputs 1-4) at slave 247.



Funct ion code 1 01

Start ing Address (H) 142

00

Start ing Address (L) 8E

Number of Points (H) 4

00

Number of Points (L) 04

CRC / LRC - -

Note that the leading character of the 1x reference address is implied by the function code and omitted from the address specified. The starting address 142 (8EH) is corresponding to coil 1 (0 0142 – I1).



Funct ion code 1 01

Byte count 1 01

Data coi ls 10 0A

CRC / LRC - -

To summarize, the status of inputs 142-145 is shown as the byte value 0A hex, or 00001010 binary. Input 145 is the fifth bit from the left of this byte, and input 142 is the LSB. The four remaining bits (toward the high-order end) are zero. Reading left to right, the output status of physical inputs 4…1 is ON-OFF-ON-OFF.

BINARY 0 0 0 0 1 0 1 0

HEX 0 A

INPUTS - - - - 4 3 2 1


5.3 Read Holding Register - 03

Reads the binary contents of holding registers (4x reference addresses) in the slave device. Broadcast transmission is not supported. The Read Holding Registers query specifies the starting register and quantity of registers to be read. Note that registers are addressed starting at 0 (registers 1-100 addressed as 0-99). The Read Holding Registers response message is packed as two bytes per register, with the binary contents right-justified in each byte. For each register, the first byte contains the high order bits and the second byte the low order bits. The number of registers returned in a single answer is limited to 60.

5.3.1 Example

This example reads holding registers 40006…40008 (Communication Words 6-8) at slave 247.



Funct ion code 3 03

Start ing Address (H) 0 00

Start ing Address (L) 5 05

Number of Points (H) 0 00

Number of Points (L) 3 03

CRC / LRC - -

Note that the leading character of the 4x reference address is implied by the function code and omitted from the address specified. The starting address 5 (05H) is corresponding to register 6 (4 0006 – CW6).



Funct ion code 3 03

Byte count 6 06

Data High (Register 40006) 211

00

Data Low (Register 40006) D3


A0

Data Low (Register 40007) 14


04


CRC / LRC - -

To summarize our example: the contents of register 40006 (2 bytes) is the Communication Word 6 = 15000 (00D3H); the contents of register 40007 (2 bytes) is the Communication Word 7 = 40980 (A014H); the contents of register 40008 (2 bytes) is the Communication Word 8 = 1024 (0400H).


5.4 Read Input Registers - 04

This command will read the binary contents of input registers (3x reference addresses) in the slave device. Broadcast transmission is not supported. The Read Input Registers query specifies the starting register and quantity of registers to be read. The Read Input Registers response message is packed as two bytes per register, with the binary contents right-justified in each byte. For each register, the first byte contains the high order bits and the second byte the low order bits. The number of registers returned in a single answer is limited to 60.

5.4.1 Example

This example reads input registers 30003 & 30004 (Analog Inputs 3 & 4) at slave 247.



Funct ion code 4 04



Number of Points (H) 0 00

Number of Points (L) 2 02

CRC / LRC - -

Note that the leading character of the 3x reference address is implied by the function code and omitted from the address specified. The starting address 2 (02H) is corresponding to register 3 (3 0003 – AI03).



Funct ion code 4 04

Byte count 4 04


00

Data Low (Register 30003) D3


00


CRC / LRC - -

To summarize our example: the contents of register 30004 (2 bytes) is the Analog Input 3 = 211 (00D3H); the contents of register 30004 (2 bytes) is the Analog Input 4 = 136 (0088H);


5.5 Force Single Coil - 05

Forces a single coil/output (0x reference address) to either ON or OFF. With broadcast transmission (address 0), it forces the same coil in all networked slaves. The Force Single Coil query specifies the coil reference address to be forced, and the state to force it to. The ON/OFF state is indicated via a constant in the query data field. A value of FF00H forces the coil to be turned ON (i.e. the corresponding relay is turned ON or closed), and 0000H forces the coil to be turned OFF (i.e. the output relay is turned OFF or opened). All other values are invalid and will not affect the coil.

5.5.1 Example

This example forces discrete output 3 ON (physical output 4) at slave 247.



Funct ion code 5 05



Force Data (H) 255 FF

Force Data (L) 0 00

CRC / LRC - -

Note that the leading character of the 0x reference address is implied by the function code and omitted from the address specified. The starting address 3 (03H) is corresponding to coil 4 (0 0004 – O04). The Force Single Coil response message is simply an echo (copy) of the query as shown above, but returned after executing the force coil command. No response is returned to broadcast queries from a master device.

The function will override the controller‟s settings. The forced state will remain valid until the controller‟s logic next solves the coil. The coil will remain forced if it is not programmed in the controller‟s logic.


5.6 Force Multiple Coils - 15

Forces each coil/output (0x reference address) in a sequence of coils/outputs to either ON or OFF. With broadcast transmission (address 0), it forces the same coils in all networked slaves. The Force Multiple Coils query specifies the coil reference address to be forced, and the state to force it to. The ON/OFF state is indicated in the Force Data fields. A value of FF00H forces the coil to be turned ON (i.e. the corresponding relay is turned ON or closed), and 0000H forces the coil to be turned OFF (i.e. the output relay is turned OFF or opened). All other values are invalid and will not affect the coil.

5.6.1 Example

This example forces ON all discrete outputs from 0 to 9 at slave 247.



Funct ion code 15 0F



Quant ity of Coi ls (H) 0 00

Quant ity of Coi ls (L) 9 09

Byte count 2 02

Force Data (H) 255 FF

Force Data (L) 1 01

CRC / LRC - -

Note that the leading character of the 0x reference address is implied by the function code and omitted from the address specified. The starting address 0 (00H) is corresponding to coil 0 (0 0001 – O01).



Funct ion code 15 0F



Quant ity of Coi ls (H) 0 00

Quant ity of Coi ls (L) 9 09

CRC / LRC - -

No response is returned to broadcast queries from a master device. The function will override the controller‟s settings. The forced state will remain valid until the controller‟s logic next solves the coil. The coil will remain forced if it is not programmed in the controller‟s logic.


5.7 Preset Single Register - 06

Presets a single holding register (4x reference addresses) to a specific value. When broadcast, the function presets the same register reference in all attached slaves. The Preset Single Register query specifies the register reference address to be preset, and the preset value.

5.7.1 Example

This example writes the value 16384 into Register 1 (Communication Word 1) at slave 247.



Funct ion code 6 06



Preset Data (H) 16384

40

Preset Data (L) 00

CRC / LRC - -

Note that the leading character of the 4x reference address is implied by the function code and omitted from the address specified. The starting address 0 (00H) is corresponding to register 1 (4 0001 – CW1). The Preset Single Register response message is simply an echo (copy) of the query as shown above, but is returned after the register contents have been preset. No response is returned to broadcast queries from a master device.

The function will override the controller‟s settings. The forced state will remain valid until the controller‟s logic next solves the register. The register will remain unchanged if it is not written by controller‟s logic.


5.8 Device Identification

This function code allows reading the identification and additional information relative to the physical and functional description of a remote device. The Read Device Identification interface is modeled as an address space composed of a set of addressable data elements. The data elements are called objects and an object Id identifies them.

5.8.1 Categories of objects

The interface consists of 3 categories of objects : Basic Device Identification.

Objects of this category are mandatory: VendorName, Product code and revision number

Regular Device Identification. In addition to Basic data objects, the device provides additional and optional identification and description data objects. All of the objects of this category are defined in the standard but their implementation is optional

Extended Device Identification. In addition to regular data objects, the device provides additional and optional identification and description private data. All of these data are device dependent.

5.8.2 Identification request

A Modbus Encapsulated Interface (MEI) assigned number 14 identifies the Read identification request. Four access types are defined :

01 : request to get the basic device identification (stream access)

02 : request to get the regular device identification (stream access)

03 : request to get the extended device identification (stream access)

04 : request to get one specific identification object (individual access)

Example of a Read Device Identification request for "Basic device dentification" of AL2-MBU. In this example all information are sent in one response PDU (only Basic Device Idetification, MEI=01 supported).

REQUEST RESPONSE

Field Name Value Field Name Value

Funct ion 2B Funct ion 2B

MEI Type 0E MEI Type 0E

Read Dev Id Code 01 Read Dev Id Code 01

Object Id 00 Conformity Level 01

More Fol lows 00

Next ObjectId 00

Number of Objects 03

Object Id 00

Object Length 0E

MAUFACTURER Object Va lue “CONTRIVE ITALY”

Object Id 01

Object Length 07

DEVICE TYPE Object Va lue “AL2-MBU”

Object Id 03

Object Length 08

FIRMWARE VERSION Object Va lue “20081203”


6. MODBUS ERROR CHECKING Modbus networks employ two methods of error checking:

parity checking of the data character frame Even, odd, or no parity

frame checking within the message frame Cyclical Redundancy Check in RTU Mode, Longitudinal Redundancy Check in ASCII Mode

7. MODBUS EXCEPTIONS In a normal response, the slave echoes the function code of the original query in the function field of the response. All function codes have their most-significant bit (msb) set to 0 (their values are below 80H). In an exception response, the slave sets the MSB of the function code to 1 in the returned response (i.e. exactly 80H higher than normal) and returns the exception code in the data field. This is used by the master's application to recognize an exception response and to direct an examination of the data field for the applicable exception code.

CODE EXCEPTION DESCRIPTION

01 I l legal

Funct ion

The funct ion code received in the query is not

al lowed or inval id.

02 I l legal

Data Address

The data address received in the query is not an

al lowable address for the slave or is inval id.

03 I l legal Data Value

A value contained in the query data f ie ld is not an al lowable value for the slave or is inval id.

04 Slave Device

Fai lure

An unrecoverable error occurred whi le the slave

was at tempting to perform the requested act ion.

The master's application program must handle the exception response. It may choose to post subsequent retries of the original message, it may try sending a diagnostic query, or it may simply notify the operator of the exception error.


8. HARDWARE

The AL2-MBU Modbus Gateway module is an optional device for Mitsubishi 2 controllers which enables the connection to a Modbus system.

The 2 controller is considered as a slave on the Modbus network. Before attempting to use AL2-MBU, the following original MITSUBISHI manuals should be carefully read and understood:

• Hardware Manual • Programming Manual • Software Manual • Communication Manual

For any information on 2 controller and its derivate products, please refer to the literature provided by MITSUBISHI and available for download at: www.mitsubishi-automation.com

8.1 Terminal Designations

A Data negative (Conductor 1 in twisted pair).

B Data positive (Conductor 2 in twisted pair).

- Ground (Conductor 3 in a three-wire system) and negative power supply

+ Positive power supply

Data line B is positive with respect to data line A when ALl2-MBU is transmitting „1‟.

8.1 Power Supply

The logic side of the gateway is powered from the 2 controller side. An external power supply must be provided for the bus side. Although it‟s possible to supply the bus side using the same 24V used for the controller, it‟s strongly suggested to provide an independent power supply. This independent supply must be externally protected. Each AL2-MBU will draw 2,5mA from the bus in idle mode, rising to a max of 150mA while in transmission mode.

8.2 Format Setting

The AL2-MBU supports both the RTU and ASCII protocol. Leave the jumper open to operate RTU mode, close the jumper for ASCII mode. A valid selection is applied on power up. This cannot be modified during operation.


8.3 Address Setting

The address is set using two rotary encoding switches. The left switch is used to set the most significant character and the right switch is used to set the least significant character. Addresses can be set between 1 and 247 in hexadecimal format ranging 00 to FF. Address 0 is reserved for the broadcast address, which all slave devices on a network recognize. The figure below shows the address setting "14". Any address change will take place immediately, also when the unit is running.

8.4 Baud Rate and Parity Settings

In addition to the described setting options, some configuration can be modified via the Modbus registers. Default communication baud rate is 9600, edit Modbus Register 40101 to modify. Default parity option is NONE, edit Modbus Rgister 40102 to modify. The new parameters are applied at next power-on.

AL2-MBU operates with factory default settings for 2 controller: OTHER COM, 8 bits data length, No parity, 1 stop bit, STATION NUMBER = 0. Parameters can be modified through local keyboard or VLS software.


9. PHYSICAL INTERFACE Modbus is a serial, asynchronous protocol. The Modbus protocol does not specify the physical interface. Typical physical interfaces are RS-232 and RS-485. AL2-MBU gateway provides a galvanically-isolated ANSI EIA/TIA-485-A interface, designed for bidirectional data communication on balanced, multipoint bus transmission lines and is slew-limited to reduce reflections with improperly terminated lines. It's a fractional (1/8) power transceiver, allowing up to 256 similar transceivers on the bus. Building mixed network with classic full power transceiver, a line repeater must be provided for each group of 32 units. The receiver inputs have a true fail-safe feature that ensures a reliable operation when the inputs are open or shorted. Current limiting and thermal shutdown features protect against output short circuits and bus contention situations that might cause excessive power dissipation. Use shielded twisted-pair wire to connect each slave to the Modbus network, daisy-chain style. The polarity of the twisted pair is critically important. Close the jumper for the built-in bus termination if the AL2-MBU is installed at the end of the bus, otherwise the bus termination jumper must be left open. Bus termination prevents signal reflections from the bus cable ends. Multiple controllers can be networked together using AL2-MBU. A maximum of 247 controllers can be connected together. Max wiring distance should not exceed 1200 m (4000 ft.) at 19,200 baud. THE SHIELD SHOULD BE GROUNDED IN ONE PLACE ONLY Grounding the shield at multiple points will create a “ground loop” that may disrupt communications or cause damage to the controller circuitry.


9.1 Isolated Network

Figure below illustrates a typical configuration where three slave units are shown. The communication wires are daisy-chained from one controller RS-485 port to the next. Power for bus side of AL2-MBU is supplied by a power supply unit. Of course it‟s possible to provide different power supplies for each AL2-MBU gateway or group of AL2-MBU gateways but the negative must be linked to reference ground.

Termination must be activated at the last AL2-MBU of the network. Termination must be provided also at the first unit of the network (usually the master).

Negative power supply must be used like RS-485 reference ground, three-wire connection is highly recommended as it improves noise immunity.


9.2 Non Isolated Network

Figure below illustrates a typical configuration where three slave units are shown. The communication wires are daisy-chained from one controller RS-485 port to the next.

Power for bus side of AL2-MBU is supplied from the same power supply of 2 controller.

Termination must be activated at the last AL2-MBU of the network. Termination must be provided also at the first unit of the network (usually the master).

Negative power supply must be used like RS-485 reference ground, three-wire connection is highly recommended as it improves noise immunity.


6. EXAMPLES WITHOUT COMM MEMORY It‟s possible to control some I/Os from remote through Modbus within a FB program without Communication Memory allocation.

6.1 Control through ASi channels

In the figure below ASi channels are user within a program and can be read / set from remote.

This can be done also when AL2-ASI-BD is not installed into 2, allowing a remote control through “virtual” channels (without assigning communication memory).

MODBUS 2 SIGNAL MODE

0.0002 O02 Motor (d irect) READ / SET

0.0003 O03 Heather (d irect) READ / SET

0.0005 O05 Clutch (d irect) READ / SET

0.0014 A01 Pos it ion sensor (through LinkIN) READ

0.0015 A02 Counter clear push button ( latched) READ

1.0142 I01 Pos it ion sensor (d irect) READ

1.0147 I06 Counter clear push button READ / SET

1.0161 E01 Heather Output enable READ / SET §

1.0162 E02 Counter pulse generator READ / SET §

1.0163 E03 Reset Clear counter la tch READ / SET §


6.2 Control through External Outputs

In the figure below the status of an External Outputs is read from remote.

This can be done also when AL2-4EYx is not installed into 2, allowing a remote control through “virtual” channels (without assigning communication memory).


1.0142 I01 Alarm test pushbutton READ

1.0147 I06 Door l imit switch (direct) READ

1.0149 I08 Acknowledge push button READ / SET §

0.0001 O01 Visual a larm (direct) SET

0.0002 O01 Audib le a larm (d irect) SET

0.0010 EO01 Door l imit switch ( latched) READ

§ The function will override the controller‟s settings.

The forced state will remain valid until the controller‟s logic next solves the register. The register will remain unchanged if it is not written by controller‟s logic.


6.3 Control through External Inputs

In the figure below the status of an External Outputs is read from remote.

This can be done also when AL2-4EX is not installed into 2, allowing a remote control through “virtual” channels (without assigning communication memory).


0.0004 O04 Motor (d irect) READ / SET

1.0157 EI01 Run Motor READ / SET §

1.0158 EI02 Stop Motor READ / SET §

0.0006 O06 Heather (d irect) READ / SET


7. EXAMPLES WITH COMM MEMORY Some digital and analog variables used within a program can be assigned to Communication Memory, to be set and read from remote through Modbus interface. Ref.: α2 SIMPLE APPLICATION CONTROLLER – COMMUNICATION MANUAL § 6 Ref.: α2 SIMPLE APPLICATION CONTROLLER – SOFTWARE MANUAL § 12

7.1 Set outputs from local and remote

A simple remote control of outputs leaving local control can be achieved using SET/RESET FB. Set and Reset inputs can be left unconnected if the control is achieved only from remote. The output could be set retentive (after power-off).


1.0142 I01 Set output 2 READ / SET §

1.0146 I05 Reset both outputs READ / SET §

0.0018 CB1 B01 - Output on (resetable) READ / SET

0.0019 CB2 B02 - Output on (resetable) READ / SET

0.0002 O02 Output 2 (di rect) READ / SET





To assign CB (Communication Bits) select Dedicated Communication… from Option menu:

Depending on Communication Memory settings, 50 or 100 Bit Devices will be allocated.

Select Bit Device tag.

Leave Station = 0.

Select from the left column the FB Bit Devices to be shared with Modbus

Choose the CBNo from Communication Bit Device table

Click the Set button

Repeat until all association are completed

B01 - Set Reset Output 2 CB1 avai lab le from Modbus at coi l 0.0018

B02 - Set Reset Output 4 CB2 avai lab le from Modbus at coi l 0.0019

WARNING When the controller is running, most of digital variables are written directly by the program thus remote setting could be overwritten.


7.2 Read/Write local variables

Complete interactivity can be achieved assigning local variables to Communication Memory. In the example above a position switch will enable the PWM generator that can be set from remote. Selected motor speed value is reported on the local display. A tacho sensor will read the real motor speed, the value is reported on the local display and can be read from remote. Output 5 will turn on exceeding speed limits, that can be set from remote.


1.0143 I02 Pos it ion switch READ / SET §

1.0147 I06 Tacho sensor READ / SET §

0.0018 CB1 B05 - Speed Control Output READ / SET

4.0001 CW1 B04 - Speed sett ing READ / SET

4.0002 CW2 B05 - Pulse period READ / SET

4.0003 CW3 B05 - Pulse current period READ / SET






To assign CB (Communication Bits) select Dedicated Communication… from Option menu:

Depending on Communication Memory settings, 50 or 100 Bit Devices will be allocated.

Select Bit Device tag.

Leave Station = 0.

Select from the left column the FB Bit Devices to be shared with Modbus

Choose the CBNo from Communication Bit Device table



B05 – Speed Detect Output CB1 avai lab le from Modbus at coi l 0.0018



To assign CW (Communication Words) select Dedicated Communication… from Option menu:

Depending on Communication Memory settings 50 or 100 Word Devices will be allocated. Select Word Device tag.

Leave Station = 0.

Select from the left column the FB Word to be shared with Modbus

Choose the CWNo from Communication Word Device table



B04 – Speed CW1 avai lab le from Modbus at co i l 4.0001

B05 – Pulse Period CW2 avai lab le from Modbus at co i l 4.0002

B05 – Pulse CurPeriod CW3 avai lab le from Modbus at co i l 4.0003



7.3 Read Analog Input / Write Analog Outputs

Analog inputs can be read directly. Assign variables to Communication Memory to read modified values or set analog outputs (AL2-2DA installed:


3.0001 AI01 0…10V Setpoint READ

3.0003 AI03 0…10V Temperature READ

4.0001 CW1 B05 - Scaled Setpoint READ / SET

4.0002 CW2 B10 - Scaled Temperature READ / SET

4.0003 CW3 B07 – Value for Analog Output B03 READ / SET

4.0004 CW4 B08 – Value for Analog Output B09 READ / SET

Two dummy Function blocks can be used to transfer value to ANALOG OUTPUTS:

B07 ONE SHOT range –32768 … 32767 B08 ADD range –32768 … 32767 input must be forced to ground

Analog outputs can accept values in the range 0÷4000 (max 4040) to be converted to 0..10 (max 10.1) V 0÷2000 (max 2020) to be converted to 4..20 (max 20.16) mA


To assign CW (Communication Words) select Dedicated Communication… from Option menu:

Depending on Communication Memory settings 50 or 100 Word Devices will be allocated. Select Word Device tag.

Leave Station = 0.

Select from the left column the FB Word to be shared with Modbus

Choose the CWNo from Communication Word Device table



B05 – GainAnalogVal CW1 avai lab le from Modbus at co i l 4.0001

B10 – GainAnalogVal CW2 avai lab le from Modbus at co i l 4.0002

B07 – SetOneShot CW3 avai lab le from Modbus at co i l 4.0003

B08 – Sum CW4 avai lab le from Modbus at co i l 4.0004


al2-mbu - contrive wireless products advanced manual... · 2018. 12. 20. · al2-mbu advanced...

Documents