Supplementary device manual AS-i controllere with Ethernet

Supplementary device manual

AS-i controllere with Ethernet programming interface

A

AC1353 / AC1354

AC1355 / AC1356

AC1357 / AC1358

Firmware version RTS 2.x

Target from V15 onwards for CoDeSys

®

from version 2.3 onwards

1

2

As on: 05 May 2011

© All rights reserved by

ifm electronic gmbh

.

No part of this manual may be reproduced and used without

ifm electronic's

consent.

Contents

1

On this manual ......................................................................................................................... 1-1

1.1

What do the symbols and formats stand for? .................................................................. 1-1

1.1.1

Warning levels, signal words............................................................................... 1-1

1.1.2

Symbols and formats .......................................................................................... 1-1

1.2

What devices are described in this manual? ................................................................... 1-2

1.3

How is this manual structured?........................................................................................ 1-2

1.4

Overview: where is what? ................................................................................................ 1-3

2

Safety instructions................................................................................................................... 2-1

2.1

General ............................................................................................................................ 2-1

2.2

What previous knowledge is required?............................................................................ 2-1

2.3

Functions and features .................................................................................................... 2-1

3

System requirements............................................................................................................... 3-1

3.1

Information concerning the device................................................................................... 3-1

3.2

Information concerning the software................................................................................ 3-1

3.3

Required accessories ...................................................................................................... 3-1

4

Function .................................................................................................................................... 4-1

4.1

Overview .......................................................................................................................... 4-1

4.2

Data management ........................................................................................................... 4-2

4.3

Which operating modes are there for the PLC in the controllere?................................... 4-3

4.4

AS-Interface as well as project transmission and diagnosis via RS232.......................... 4-3

4.5

Project transmission and diagnosis via Ethernet interface .............................................. 4-4

4.5.1

Point-to-point connection .................................................................................... 4-4

Overview point-to-point connection .............................................................................4-4

Step 1: Connect the PC to the controllere ...................................................................4-5

Step 2: Set IP addresses and subnet mask ................................................................4-5

Step 3: Select the target system and write the project ................................................4-9

Step 4: Set the communication parameters ..............................................................4-11

Step 5: Transmit and start the project .......................................................................4-13

Step 6: Set-up, monitoring and diagnosis of the AS-i system....................................4-14

Step 7: Create the boot project and save the source code........................................4-15

Step 8: Transmit the source code from the controllere to the PC (service case).......4-16

4.5.2

Ethernet network connection............................................................................. 4-18

Overview Ethernet network connection .....................................................................4-18

Excursion: Global network variables / EXP files............................................... 4-19

Overview: Steps for implementing an Ethernet network connection..........................4-20

Step 1: Connect the devices via Ethernet .................................................................4-20

Step 2: Set IP addresses and subnet mask ..............................................................4-20

Step 3: Select the first target system and create a project ........................................4-21

3

4

Step 4: Set the communication parameters ..............................................................4-23

Step 5: Activate the network variable support ...........................................................4-25

Step 6: Integrate libraries ..........................................................................................4-26

Step 7: Complete and transmit the project (Global network variables).....................4-27

Excursion: variable list identifier (COB ID) ....................................................... 4-29

Continuation of step 7: ..................................................................................... 4-30

Step 8: Write projects for further controllere devices.................................................4-30

Step 9: Transmit projects ..........................................................................................4-32

Step 10: Test the global network variable transmission ............................................4-32

4.5.3

MODBUS/TCP server / client............................................................................ 4-33

Overview MODBUS/TCP server / client ....................................................................4-33

Valid Modbus addresses and their meaning .............................................................4-34

Modbus address for controllere PLC status ..............................................................4-36

Modbus address for Modbus timeout ........................................................................4-36

Modbus address for Modbus write timeout................................................................4-36

Modbus address for "delete Modbus write timeout register" .....................................4-36

Modbus addresses of the digital slave inputs and outputs ........................................4-37

IEC addresses in the PLC of the controllere for the digital slave

inputs and outputs............................................................................................ 4-38

Modbus addresses for the master flags ....................................................................4-40

IEC addresses in the PLC of the controllere for the master flags .................... 4-40

Modbus addresses for the analogue slave inputs and outputs..................................4-41

Status information of analogue slaves ............................................................. 4-45

IEC addresses in the PLC of the controllere for the analogue slave inputs

and outputs ...................................................................................................... 4-47

Modbus addresses for configuration data (CDI) of the slaves...................................4-53

IEC addresses in the PLC of the controllere for configuration data (CDI)

of the slaves..................................................................................................... 4-54

Modbus addresses for parameter data of the slaves.................................................4-55

IEC addresses in the PLC of the controllere for parameter data

of the slaves..................................................................................................... 4-55

Modbus addresses for the slave list LAS (list of active slaves) .................................4-56

IEC addresses in the PLC of the controllere for the slave list LAS

(list of active slaves)......................................................................................... 4-56

Modbus addresses for the slave list LDS (list of detected slaves).............................4-57

IEC addresses in the PLC of the controllere for the slave list LDS

(list of detected slaves) .................................................................................... 4-57

Modbus addresses for the slave list LPF (list of slaves with periphery faults) ...........4-58

IEC addresses in the PLC of the controllere for the slave list LPF

(list of slaves with periphery faults) .................................................................. 4-58

Modbus addresses for the slave list LPS (list of projected slaves) ............................4-59

IEC addresses in the PLC of the controllere for the slave list LPS

(list of projected slaves) ................................................................................... 4-59

Modbus addresses for the slave telegram error counters .........................................4-60

IEC addresses in the PLC of the controllere for the slave telegram

error counter .................................................................................................... 4-61

Modbus addresses for the configuration error counter ..............................................4-62

IEC addresses in the PLC of the controllere for the configuration

error counter .................................................................................................... 4-62

Modbus addresses for the AS-i cycle counter ...........................................................4-62

IEC addresses in the PLC of the controllere for the AS-i cycle counter ........... 4-62

Modbus addresses for the request data of the host command channel ....................4-63

Modbus addresses for the response data of the host command channel .................4-64

Modbus addresses for the fieldbus data from/to the PLC of the controllere ..............4-65

IEC addresses in the PLC of the controllere for the fieldbus data

from/to the PLC of the controllere .................................................................... 4-66

Modbus addresses for the extended data from/to the PLC of the controllere............4-67

IEC addresses in the PLC of the controllere for the extended data

from/to the PLC of the controllere .................................................................... 4-73

4.5.4

Data exchange HTML page – controllere ......................................................... 4-74

Overview HTML data exchange ................................................................................4-74

Setting up an own web page .....................................................................................4-75

Step 1: Connect the devices via Ethernet .................................................................4-75

Step 2: Set IP addresses and subnet mask ..............................................................4-75

Step 3: Open the HTML page in the browser ............................................................4-76

Step 4: Address the file server via FTP .....................................................................4-77

Step 5: Edit the web page .........................................................................................4-79

Functions available in the applet...................................................................... 4-79

Call the function cyclically ................................................................................ 4-80

Step 6: Loading and testing the modified web page..................................................4-81

5

Menu .......................................................................................................................................... 5-1

5.1

Menu "Ethernet Setup"“ ................................................................................................... 5-1

6

Operation .................................................................................................................................. 6-1

6.1

The Modbus command channel....................................................................................... 6-1

Request from host: ....................................................................................................... 6-1

Response from controllere: .......................................................................................... 6-1

6.1.1

Overview of the commands in the Modbus command channel .......................... 6-2

6.1.2

Command 0 (0#00): no execution of a command............................................... 6-4


Response from controllere: .......................................................................................... 6-4

6.1.3

Command 1 (0#01): Write parameters to a connected AS-i slave ..................... 6-5


Response from controllere in the normal case: ............................................................ 6-5

Response from controllere in the case of an error: ...................................................... 6-6

Possible error codes:.................................................................................................... 6-6

6.1.4

Command 3 (0#03): Adopt and save currently connected AS-i slaves

in the configuration.............................................................................................. 6-7



Response from controllere in the case of an error: ...................................................... 6-8

Possible error codes:.................................................................................................... 6-8

5

6

6.1.5

Command 4 0#04): List of the projected AS-i slaves (LPS) .............................. 6-9



Response from controllere in the case of an error: .................................................... 6-10

Possible error codes:.................................................................................................. 6-10

6.1.6

Command 5 (0#05): Set the operating mode of the AS-i master..................... 6-11

Request from host: ..................................................................................................... 6-11

Response from controllere in the normal case: .......................................................... 6-11



6.1.7

Command 6 (0#06): Readdress a connected AS-i slave................................. 6-12





6.1.8

Command 7 (0#07): Set the auto address mode of the AS-i master............... 6-14


Response from controllere: ........................................................................................ 6-14

6.1.9

Command 9 (0#09): Change the extended ID code 1 in the connected

AS-i slave .......................................................................................................... 6-15





6.1.10

Command 10...20 (0#0A...0#14): Force analogue data transmission

directly to / from 3 AS-i slaves in each case ..................................................... 6-17



6.1.11

Command 21 (0#15): Read the ID string of an AS-i slave with profile S-7.4... 6-21





6.1.12

Command 28 (0#1C): Deactivate the slave reset when changing to the

protected mode ................................................................................................. 6-24



6.1.13

Command 31 (0#1F): One-time execution of the "Extended Safety Monitor

Protocol" in the "Safety at work" monitor .......................................................... 6-25





6.1.14

Command 33 (0#21): Read the diagnosis string of an AS-i slave with

profile S-7.4....................................................................................................... 6-29



6.1.15

Command 34 (0#22): Read the parameter string of an AS-i slave with

profile S-7.4....................................................................................................... 6-31



6.1.16

Command 35 (0#23): Write parameter string of an AS-i slave with the

profile S-7.4....................................................................................................... 6-33



6.1.17

Command 36 (0#24): Acyclic standard read call to an AS-i slave with

CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)........................................................ 6-35



Response from controllerein the case of an error (error detected by AS-i master):... 6-37


Response from controllere in the case of an error (error detected by AS-i slave): .... 6-38

Possible CTT2 error codes:........................................................................................ 6-38

6.1.18

Command 37 (0#25): Acyclic standard write call for an AS-i slave with

CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)........................................................ 6-39



Response from controllere in the case of an error (error detected by AS-i master):.. 6-41




6.1.19

Command 38 (0#26): Acyclic manufacturer-specific read call to an

AS-i slave with CTT2 profile (S-7.5.5, S-.7.A.5 or S-B.A.5).............................. 6-43



Response from controllere in the case of an error (error detected by AS-i master):.. 6-45




6.1.20

Command 39 (0#27): Acyclic standard manufacturer-specific write call

to an AS-i slave with CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)...................... 6-47



Response from controllere in the case of an error (error detected by AS-i master):. 6-49




6.1.21

Command 50 (0#32): Read current configuration of AS-i slaves 0(A)...15(A). 6-51



6.1.22

Command 54 (0#36): Read current parameters of a connected AS-i slave..... 6-52



7

6.1.23

Command 55 (0#37): Read current AS-i slaves .............................................. 6-54



6.1.24

Command 56 (0#38): Read projected configuration of the AS-i slaves

1(A)...15(A)........................................................................................................ 6-56



6.1.25

Command 96 (0#60): Save data non-volatilely in the flash memory

of the controllere ............................................................................................... 6-57



6.1.26

Command 97 (0#61): Carry out various settings in the controllere ................. 6-58



6.1.27

Command 102 (0#66): Retrieve the status of the controllere display.............. 6-59



6.1.28

Command 105 (0#69): Read the device properties of the controllere............. 6-61



7

Terms, abbreviations ............................................................................................................... 7-1

8

Index .......................................................................................................................................... 8-1

8

On this manual

What do the symbols and formats stand for?

1 On this manual

In this chapter you will find an overview of the following points:

 What do the symbols and formats stand for?

 What devices are described in this manual?

 How is this manual structured?

1.1 What do the symbols and formats stand for?

The following symbols or pictograms shall illustrate our remarks in this manual:

1.1.1 Warning levels, signal words

DANGER

Death

or serious irreversible injuries are to be expected.

WARNING

Death

or serious irreversible injuries may result.

CAUTION

Slight

reversible injuries may result.

NOTICE

Property damage

is to be expected or possible.

NOTE

Important

note for the correct handling of this product or the manual.

1.1.2



Symbols and formats

… A state to be prevented to avoid a danger.

► … Instruction

> … Reaction from the device or software

 … Means: "see" abc Active cross-reference (link) to another part of the text or an external target on the internet

1-1

On this manual

What devices are described in this manual?

[…] [Designation] of key, signalling lamp, button, menu item ....

Several buttons or menu items to be selected successively are indicated as follows:

► [1st step] > [2nd step] > [3rd step]

Several buttons to be clicked simultaneously are indicated as follows:

► [Ctrl] + [Alt] + [Del]

DESIGNATION of a parameter (in block capitals) ABC

ABC

DESIGNATION

of file names (in Monospace font)

1.2 What devices are described in this manual?

This manual presents the AS-i controllere family from


 with AS-i version 2.1 master

 with a firmware from version RTS 2.2 onwards

 with the target from V15 onwards

 with the option Ethernet programming interface (Ethernet PG)

In this supplementary manual only the Ethernet programming interface is described. Higher-level or general information

 separate basic instructions of the device manual.

1.3 How is this manual structured?

This manual is a combination of different instruction types. It is for beginners and also a reference for advanced users.

How to use this manual:

 To find a certain subject straight away, please use the table of contents at the beginning of this manual.

 You can also find a requested term quickly with the index at the end of the manual.

 At the beginning of a chapter we will give you a brief overview of its contents.

Headers

Footers

You can find the title of the current chapter in bold in the header of each page.

Below is the current title of the second order.

You can find the chapter-related number of the page in the footer of each page.

Example: 12-7 means page 7 in chapter 12.

Abbreviations and technical terms

 page

7-1 , (chapter Terms, abbreviations

at the end of the manual.

We reserve the right to make alterations which can result in a change of contents of the manual. You can find the current version on

ifm's

website at:

 www.ifm.com

> Select country/language > [Service] > [Download] > [Bus system AS-Interface]

Nobody is perfect. Send us your suggestions for improvements to this manual and you will receive a little gift from us to thank you.

© All rights reserved by


. No part of this manual may be reproduced and used without ifm electronic's consent.

1-2

On this manual

Overview: where is what?

1.4 Overview: where is what?

metal housing IP 20 status LEDs of the fieldbus interface

(option) device to unlock the device from a rail

4 pushbuttons option: field bus interface

(here: Ethernet) status LEDs

(here: 2 masters) terminals for the voltage supply 24 V,

AS-interface(s) and protective wire figure: overview of controllere option:

Ethernet programming interface

6-pole RJ11 socket of RS-232 C as programming interface

1-3

On this manual

Overview: where is what?

1-4

Safety instructions

General

In this chapter you can find general safety instructions such as:

 Required previous knowledge

 Safety instructions for mounting and installation

 When are you allowed to use this device and when not?

2.1 General

 separate basic instructions of the device manual

No characteristics are warranted with the information, notes and examples provided in this manual.

The drawings, representations and examples imply no responsibility for the system and no applicationspecific particularities.

The manufacturer of the machine/equipment is responsible for the safety of the machine/equipment.

WARNING

Property damage or bodily injury when the notes in this manual are not adhered to!

ifm electronic

assumes no liability for this.

► The acting person must have read and understood the safety instructions and the corresponding chapters of this manual before performing any work on or with this device.

► The acting person must be authorised to work on the machine/equipment.

2.2 What previous knowledge is required?

These instructions are for persons with knowledge and previous knowledge of control technology and

PLC programming with IEC 61131-3 as well as the CoDeSys® software.

The manual is intended for persons authorised to mount, connect and set up the controllere according to the EMC and low voltage directives. The controllers must be installed and put into operation by a qualified electrician.

In case of malfunctions or uncertainties please contact the manufacturer at:

 back of the instructions.

2.3 Functions and features


2-1

Safety instructions

Functions and features

2-2

System requirements

Information concerning the device

3.1 Information concerning the device


This manual describes the AS-i controllere device family from ifm electronic gmbh with the option

Ethernet TCP/IP interface.

3.2 Information concerning the software


Basic functions


For configuration and programming you also need:

 the software "CoDeSys for Automation Alliance™" version 2.3 or higher

 CD article no. AC0340

 in case of direct connection of the controllere to a PC with Ethernet interface (LAN): a cross-over CAT5 Ethernet patch cable with an RJ45 connector on both sides:

2 m article no. EC2080

5 m article no. E30112

 in case of connection of the controllere to a PC with Ethernet interface (LAN) via a hub or switch: a common CAT5 Ethernet patch cable with an RJ45 connector on both sides

 in case of direct connection of the controllere to a PC with serial interface: programming cable article no. E70320

3-1

System requirements

Required accessories

3-2

Function

Overview

4 Function

Basic functions


Fieldbus interface (option)

 separate supplementary device manual

4.1 Overview

 The programming Ethernet interface of the controllere can be used for project and data transmission.

- from the PC to the controllere, as well as

- from the controllere to the PC.

 In the network one or several PCs as well as one or several controllere devices can communicate.

 controllere devices of this type further contain a MODBUS/TCP server which allows data exchange with a MODBUS/TCP client. information for all above-mentioned transmissions can be found in these instructions.

AC1353/54

AS-Interface

RS 232

Ethernet Cross-Over Cable

Ethernet Switch / Hub

AC1353/54

AC1353/54 AC1353/54

PLC

Modbus/TCP Master

Intranet

PDM

4-1

Function

Data management

The controllere consists of different devices:

text/graphics display

AS-i master 1 fieldbus interface

(optional)

AS-i master 2

(optional) central processing unit

Ethernet programming interface

(optional)

SRAM memory flash memory

RS-232C programming interface

This manual exclusively describes the following subject:

 With the optional Ethernet programming interface, (10/100 MBd, twisted pair), the device can, in addition to even faster programming and diagnosis, also be networked to other controllere devices.

4-2

Function

Which operating modes are there for the PLC in the controllere?

4.3 Which operating modes are there for the PLC in the controllere?

Operating mode Meaning

Run SPS program start

> The PLC program stored in the controllere is processed.

Stop

> LED [PLC RUN] lights

SPS program stop

> The PLC program stored in the controllere is stopped.

> LED [PLC RUN] flashes

Gateway Controllere as gateway

> The PLC program stored in the controllere is not processed.

> LED [PLC RUN] goes out

Behaviour at Modbus / fieldbus

At Modbus AS-i Slaves in the controllere application program can be written:

Mapping of the PLC address ranges

%IB4.512…%IB4.639

%IW4.320…%IW4.639

Only for devices with the option fieldbus connection:

The fieldbus has exclusive write access on the AS-i outputs.

Device with fieldbus: Modbus has no access here!

Device without fieldbus: Modbus has write access

on the AS-i outputs.

The timeouts for the analogue and digital AS-i outputs only run in the operation mode Gateway. For the other data areas which are be written via

Modbus there is no timeout monitoring.

Note

During changes to the PLC program or to the slaves the PLC program should be stopped to avoid malfunctions.

Note

In devices with Profibus and Ethernet programming interface Modbus is not be used as fieldbus but as interface for operation and configuration.

4.4 AS-Interface as well as project transmission and diagnosis via RS232

Also the controllere devices of type AC1353/54 contain one ore more AS-Interface masters. An RS232 programming interface is also available.

AS-Interface system


Project transmission and diagnosis via RS232 interface


4-3

Function

Project transmission and diagnosis via Ethernet interface

4.5 Project transmission and diagnosis via Ethernet interface

This section describes the project transmission and diagnosis (AS-i networks and projects) via a simple structure (PC - controllere with a point-to-point connection via Ethernet) as well as in an

Ethernet network.

4.5.1 Point-to-point connection

Connection between via

 page

4-18

4-33

4-74

controllere HTML page PC HTML data exchange

Overview point-to-point connection

A simple point-to-point connection is to be implemented (

 figure):

AC1353/54

PC

Ethernet •

Cross-Over Cable

For this, the following steps are required:

Step 1

► Connect the PC to the controllere by means of a cross-over cable ( page 4-5

)

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

► Set IP addresses and subnet mask in the controllere and the PC ( page

4-5 )

► Select the target system and write the project (

 page

4-9 )

► Set the communication parameters (

 page

4-11

)

► Transmit and start the project (

 page

4-13

)

► Set-up, monitoring and diagnosis of the AS-i system (

 page

4-14

)

► Create the boot project (

 page

4-15

)

Transmit and save the source code from the PC to the controllere

Step 8 ► Transmit the source code from the controllere to the PC

(service case,

 page

4-16

)

4-4

Function


Here is the detailed description of the steps:

Step 1: Connect the PC to the controllere

► Connect the LAN connection of the PC to the controllere.

► To do so, use a cross-over CAT5 Ethernet patch cable with an RJ45 connector on both sides, e.g.: 2 m

5 m article no. EC2080 article no. E30112

A cross-over cable only enables a point-to-point connection. It cannot be used to establish a connection to a network.

Step 2: Set IP addresses and subnet mask

1.

M E N

U

0

U S E

R

► Press [ MENU ]

2.

Quick Setup

PLC Setup

Slave Lists

O

K

1

▲ ▼

E S C

► Use [▼] to scroll to [System Setup]

3.

Slave Info

Slave Setup

System Setup

O K

1

▲▼

E S C

► Select [System Setup] with [OK]

4-5

Function


4. System Setup

Serial Port Baudrate

Ethernet Setup

O

K

33

▲ ▼

E S C

► Use [▼] to scroll to [Ethernet Setup]

5. System Setup

Serial Port Baudrate

Ethernet Setup

O

K

33

▲▼

E S C

► Select [Ethernet Setup] with [OK]

6. Ethernet Setup

IP Address

Subnet Mask

O

K

121

▲ ▼

E S C

To set the IP address, DHCP must be switched off.

► Use [▼] to scroll to [DHCP Setup]


Auto Negotiation

DHCP Setup

O K

121

▲▼

E S C

► Select [DHCP Setup] with [OK]


DHCP on

DHCP off

O

K

126

▲ ▼

E S C

> Display of the current DHCP selection

► Use [▼]/[▲] to scroll to [DHCP OFF]

4-6

Function



DHCP on

DHCP off

O K

126

▲ ▼

E S C

► Select [DHCP OFF] with [OK]

> "Wait!" is displayed


Auto Negotiation

DHCP Setup

O

K

121

▲▼

E S C

> Display of the menu [Ethernet Setup]

► Use [▲] to scroll to [IP-Adresse]


IP Address

Subnet Mask

O K

121

▲ ▼

E S C

► Select [IP Adress] with [OK]

12. ENET IP Address

192 . 168 . 10 . 17

↑



127

▲▼

E S C

> Display of the current IP address

The arrow indicates the editable address group

► Use [▲] or [▼] to scroll to the requested address

► Use [] to go to the next address group


After the last address group:

► Use [] to exit the editing mode

13. IP Address

192 . 168 . 10 . 24

O K

127

▲▼

E S C

> Display of new IP address

► Confirm the new IP address with [OK]


► (Use [ESC] to exit without making a change)

4-7

Function



IP Address

Subnet Mask

O K

121

▲ ▼

E S C


► Use [▼] to scroll to [Subnet Mask]


IP Address

Subnet Mask

O

K

121

▲▼

E S C

► Select [Subnet Mask] with [OK]

16. ENET SubNet-Mask

255 . 255 . 255 . 0

↑



123

▲▼

E S C

> Display of the current subnet mask


► Use [] to go to the next address group


After the last address group:

► Use [] to exit the editing mode

17. ENET SubNet-Mask

255 . 255 . 255 . 0

O

K

123

▲▼

E S C


► Confirm the new subnet mask with [OK]


► (Use [ESC] to exit without making a change)


IP Address

Subnet Mask

O K

121

▲▼

E S C

► Use [ESC] 4 times to return to the start screen

In the Windows operating system the setting of the PC addresses is carried out correspondingly. In our example the settings of the PC are 192.168.10.20 as IP address and 255.255.255.0 as subnet mask.

4-8

Function


NOTE

In a local network the participants can only communicate if their IP addresses are from the same

"family".

Example: subnet mask = 255.255.255.0

Then the IP addresses of the first 3 address groups (where "255" is) must be identical for all participants. The IP address may (and must) only be different in the last block (where "0" is)

(permitted values): 0…254).

Here: IP address in the controllere = 192.168.10.24, IP address in the PC = 192.168.10.20

Step 3: Select the target system and write the project

► Start CoDeSys (version 2.3.5.0 or higher) on the PC

► Create a new project with [File] > [New]:

> The following figure appears:

► Select the target system (e.g. "AC13…, V15" or higher):

► Confirm with [OK]


4-9

Function



> The following (or similar) figure appears:

► Create the first POU. To do so, adopt the entries from the figure (

 above).



► Complement your POU PLC_PRG by the entries as in the figure to the right:

4-10

Function


► Select [File] > [Save as...] to save the project in the requested directory as "DemoProj"

(

 right):

Step 4: Set the communication parameters

The cable alone does not enable the communication between the controllere and the PC. The same communication parameters must be set for both devices and the project.

Note: the set communication parameters of the project are saved together with the project and are therefore part of the project.

► Select [Online] > [Communication

Parameters...] to call the following dialogue:

4-11

Function



► Click [New…]

Enter the parameters in the following dialogue window as shown in the window below


► Select the entry [Tcp/Ip(Level 2)]



► Activate the address field by double-clicking

► Enter the corresponding IP address of the controllere (see step 2)

► Use [ENTER] to exit the editing mode


4-12

Function


Step 5: Transmit and start the project

► Click [Online] > [Login] to activate the connection from the PC to the controllere:

> The following message appears:

Reason: in the project which is saved on the PC details have not yet been defined.

► Adopt the setting [Upload from PLC]

(

 figure)

►

Confirm with [OK]

Now there are two possibilities to proceed: a) no program has yet been saved in the controllere

> The following message appears: b) a program has already been saved in the controllere

> The following message appears:

► In both cases you send your project to the controllere by confirming with [yes].

► Click [Online] > [Run] to start the project:

> The project in the controllere starts

The project can then be tested.

4-13

Function


Step 6: Set-up, monitoring and diagnosis of the AS-i system

First use the PLC configuration window:

► Click the tab [Resources] (below)

► Click the option [PLC configuration]


In step 5 you copied the configuration data from the controllere to your PC into your project. This is why the data shown in the figure above is already available.

Detailed description of the PLC configuration


In the controllere you can observe the processing of your project and debug the program if necessary.

> Here:

Display of the POU PLC_PRG with the example of the adder.

4-14

Function


Step 7: Create the boot project and save the source code

When the controllere is switched off the device forgets all setting parameters. In the controllere you can non-volatilely save a boot project which loads all current settings when the device is switched on.

At the latest when completing the project you must create a boot project to non-volatilely save the project in the controllere.

► Menu [Online] > [Create boot project]

> The boot project is saved in the controllere

The source code does not only contain the program code of the project but also all comments and symbolic parameter names saved in the project. This allows a service technician later to copy the current program with all information to his PC and to edit the project.

► Click the menu points [Project] > [Options] >

[Source download] to save the source code in the controllere

► Use [OK] to confirm the settings

> When (again) creating the boot project the source code is transmitted to the controllere



4-15

Function


Step 8: Transmit the source code from the controllere to the PC (service case)

Your project was transmitted as source code from the PC to the controllere and is available there ( step 7).

► Save your current project and close it.

Imagine you are a service technician who has to change the work flow of a machine. Probably your

PC has not saved the current status of your project because other colleagues operated the machine in the meantime. For this reason you copy the project from the machine (controllere) to your PC:

► Menu [File] > [Open…]:


► Click [PLC…] (open the project from the controller)

► Carry out the steps as in the following figures (details

 steps 3...6):

4-16

Function


► Convince yourself that the copied project which you have transmitted from the controllere corresponds to your original project.

4-17

Function


4.5.2 Ethernet network connection

Connection between

controllere HTML page

PC

via

controllere controllere controllere network connection controllere client MODBUS/TCP server / client

HTML data exchange

Overview Ethernet network connection

An Ethernet network connection is to be implemented (

 example below).

 page

4-4

here

4-33

4-74

controllere 1 controllere 2 controllere 3

Ethernet switch

PC

Between 3 controllere devices and 1 PC, information exchange shall take place. We implement this by means of the "global network variables" (

 illustration below). The examples only show the variables x1, x2 and x3 in the global network variable lists of the corresponding projects.

DemoProj 1

Global network variables x1 x2 x3

ExportProj1.exp

DemoProj 2

Global network variables x1,x2,x3

ExportProj2.exp

DemoProj 3

Global network variables x1 x2 x3

ExportProj3.exp

Ethernet switch

PC

4-18

Function


Excursion: Global network variables / EXP files

Global network variables are used for data exchange between controllers in the network. There is a difference between export and import variables:

 Export variables originate from the local project.

Their values can be locally influenced.

It shall also be possible to read and use the variables in one or more other projects. Therefore theses variables must be exported (made available) from the local project.

 Import variables do not originate from the local project but from another project.

Their values cannot be locally influenced.

The variables are read and used in the local project (and possibly also in several other projects).

For this, these variables must be imported into the corresponding local project.

For exporting or importing, the global network variables must be summarised in lists. An EXP file is assigned to each global variable list.

In this example each project has 3 lists of global network variables:

- 1 with export variables (with local data for reading in other controllers) and

- 2 with import variables (with data of the two other controllers for local reading).

Please note the following when creating a global list of variables:

By ticking [Export before compile] in the window [Properties] CoDeSys updates the corresponding

EXP file (e.g. ExportProj1.exp) when rebuilding the project.

By ticking [Import before compile] in the window [Properties], CoDeSys takes into account the corresponding EXP file (e.g. ExportProj1.exp) when rebuilding the project, and updates the list.

Example:

The project "DemoProj1" contains the global network variable list "Global_Variables_Export_Proj1".

► In the properties of this list you enter the file ExportProj1.exp.

► Activate [Export before compile].

> When rebuilding this project, ExportProj1.exp is updated.

The project "DemoProj2" contains the global network variable list "Global_Variables_Import_Proj1".

► In the properties of this list you enter the file ExportProj1.exp.

► Activate [Import before compile].

> When starting to rebuild this project, the list "Global_Variables_Import_Proj1" is updated by means of the file ExportProj1.exp and then used for the rebuild.

NOTE

If a project with variables to be exported is changed, all projects which import these global network variable lists must then be rebuilt to update the lists:

► Menu [Project] > [Rebuild all]



4-19

Function


Overview: Steps for implementing an Ethernet network connection

An Ethernet network connection is to be implemented (

 page

4-18

). For this the following steps are required:

Step 1

Step 2

Step 3

Step 4

► Connect the devices via Ethernet (

 page

4-20

)

► Set IP addresses and subnet mask (

 page

4-20

)

► Select the first target system and create a project (

 page

4-21

)

► Set the communication parameters (

 page

4-23

)

Step 5

Step 6

Step 7

► Activate the network variables support (

 page

4-25

)

► Integrate libraries (

 page

4-26

)

► Complete and transmit the project (global network variables) (

 page

4-27

)

Step 8

► Write projects for further controllere devices ( page 4-30

)

Step 9

Step 10

► Transmit projects (

 page

4-32

)

► Test the transmission of global network variables (

 page

4-32

)


Step 1: Connect the devices via Ethernet

► Set up the Ethernet network by connecting the PC and the controllere to the hub (or switch).

► To do so, use common CAT5 Ethernet patch cables with an RJ45 connector on both sides.


► Set appropriate IP addresses and subnet masks on all three controllere devices (procedure  page

4-5 ).

NOTE


"family".

Example: Subnet mask = 255.255.255.0

Then the IP addresses of the first 3 address groups (where "255" is) must be identical for all participants. The IP address may (and must) only be different in the last block (where "0" is) (permitted values): 0…254).

Ask the network administrator for the specifications!

In our example we assume the following values:

Subnet mask = 255.255.255.0

IP address of the controllere 1 = 192.168.10.21



IP address of the PC = 192.168.10.20

4-20

Function


Step 3: Select the first target system and create a project

Three projects are to be written: one for each controllere in the network. The projects differ only slightly, the main differences concern the global variables and the executable part. Below please find a more detailed description of the projects.

Let's start with the project for controllere 1:

► Start CoDeSys (version 2.3.5.0 or higher) on the PC

► Create a new project with [File] > [New]:


► Select the target system (e.g. "AC13…, V15" or higher):




4-21

Function



► Create the first POU. To do so, adopt the entries from the figure (

 above).



► Complement your POU PLC_PRG by the entries as in the figure to the right:

► Click [File] > [Save as...] to save the project in the requested directory.

Here:

File name = "DemoProj1" (for the first controllere in the network)

4-22

Function


Step 4: Set the communication parameters

The same communication parameters must be set for the PC, the controllere and the project.

► Select [Online] > [Communication

Parameters...] to call the following dialogue:


► Click [New…]

Enter the parameters in the following dialogue window as shown in the window below

4-23

Function



► Select the entry [Tcp/Ip(Level 2)]



► Enter the corresponding IP address of the controller (see step 2)


4-24

Function


Step 5: Activate the network variable support

► Click the tab [Resources] in CoDeSys

► Double-click [Target Settings]


► Double-click the tab [Network functionality]

► Activate the field [Support network variables]

► Names of supported network interfaces = UDP


> Data exchange via global network variables is now possible

4-25

Function


Step 6: Integrate libraries

► Menu [Window] > [Library Manager]

> Display of the libraries already loaded (here: only standard.lib)

► Menu [Insert] > [Additional Library... Ins] or:

► Key [Ins]

► Insert the following libraries:

> Now the library manager should look like this or similar (the order is not relevant):

 SysLibSockets.lib

 SysLibCallback.lib

 NetVarUdp_LIB_V23.lib

4-26

Function


Step 7: Complete and transmit the project

(Global network variables)

To demonstrate the data exchange via global network variables you now write a project for each of the three controllere devices. These projects are suitable for this purpose mainly due to the global variable lists which they contain.

The example shows the project for controllere 1.

► Click the tab [Resources] in CoDeSys

► Click [Global Variables]

 right figure

► Menu [Projekt] > [Object] > [Add…]

> Display of the window

"Properties":

► Enter the name of the global variable list as shown


► Enter the variable x1 in the window that appears (

 figure)

► Right-click on the resources element

[Global_Variables_Export_Proj1]

4-27

4-28

Function


► Click [Object Properties...] (

 figure)

> Display of the window

"Properties":

► Click [Add network]


► Enter the properties of the list similarly as shown, but:

 The exact path of the link to file depends on the PC.

 The entered minimum gap depends on the application.

 For export: activate [Export before compile] and [Write]!

Function


Excursion: variable list identifier (COB ID)

Here we operate with variable lists which are exported from one controllere device and imported to one or more controllere devices. This assignment of the variable lists is marked by a COB ID. This correlation is shown in the figure below.

Export list

COB ID 51

DemoProj 1

Import list

COB ID 52

Import list

COB-ID 53

Import list

COB-ID 51

DemoProj 2

Export list

COB-ID 52

Import list

COB-ID 53

Import list

COB-ID 51

DemoProj 3

Import list

COB-ID 52

Export list

COB-ID 53

Here it can be seen that the export variables of the DemoProj1 in controllere1 have been assigned the

COB ID=51 and that these variables can be found each in DemoProj2 and DemoProj3 in controllere 2 and controllere 3. We have used this schematic illustration for the definition of the COB IDs.

NOTE

When selecting the COB IDs observe the following:

 The export list and its corresponding import lists must be assigned to the same COB ID.

 Each COB ID may be assigned only to one export list.

4-29

Function


Continuation of step 7:

► In the window [Properties] of the global variable list:

Click [Settings...]


► As broadcast address enter the IP address of controllere1, but: replace the value in the last group by "255" (

 figure).


Step 8: Write projects for further controllere devices

► Create now corresponding projects with export files also for the two other controllere devices

("DemoProj2", "DemoProj3"). These files are required for the following steps. Data names and entries

 following table:

Name of the global variable list COB ID

File name of the link to file

Global variable

1 DemoProj1.pro \ExportProj1.exp x1:INT



> For all three controllere devices the export lists have been created.

For the project "DemoProj1" in controllere1 we have so far only created the "global network variables" which are to be exported.

Now we create two lists of "global network variables" which will be imported by "DemoProj1". Use the above-mentioned methods:

► Open the project "DemoProj1" in CoDeSys

► Click the tab [Resources]

► Tick (click) the entry [Global Variables]

► Menu [Project] > [Object] > [Add…]

► Define the list „Global_Variables_Import_Proj2”


► Enter the variable x2 in the window that appears (

 figure)

4-30

Function


► Enter the properties and settings of this list (

 figure below)

For import: activate [Import before compile] and [Read]!

► Click [Settings...]


► As broadcast address enter the IP address of controllere2, but: replace the value in the last group by "255".


The same operation is to be carried out for controllere3:

► Define the list "Global_Variables_Import_Proj3"

► Content of the variable list: "x3:INT"

► File name of the link to file = \ExportProj3.exp

► Correspondingly create the global import variable lists also for the two other projects.

So far we have "only" organised the data management. Now we will look at the executable parts of the projects.

4-31

Function


For each project we will write only one POU which increases the contents of the corresponding variables (x1, x2 or x3) by 1 in each PLC cycle. In our example we show the POU PLC_PRG for

DemoProj1.pro

(

 figure).

► Create this program for each of these three controllere devices (DemoProj1.pro,

DemoProj2.pro and DemoProj3.pro

).

Step 9: Transmit projects

► Transmit the projects created in steps 6 + 7 to the corresponding controllere.

► Start these projects there.

Step 10: Test the global network variable transmission

► Check the behaviour of the data transmission by looking at the corresponding global network variable lists.

E.g. if you open the variables "Global_Variables_Import_Proj2" of DemoProj1, you should find that the value of x2 increases.

► Check the other projects and make sure that the transmission of the global network variables functions.

4-32

Function


4.5.3 MODBUS/TCP server / client

Connection between via

controllere controllere controllere network connection

MODBUS/TCP server / client controllere client controllere HTML page

PC HTML data exchange

 page

4-4

4-18

here

4-74

Overview MODBUS/TCP server / client

The controllere and AC1353/AC1354 contain a MODBUS/TCP server which enables the data exchange with a MODBUS/TCP client. Schematic illustration

 figure

Modbus/TCP client

AC1353/54

Modbus/TCP server

AS-Interface master(s)

PLC in controllere

Ethernet with Modbus/TCP

The algorithm for the data exchange depends on what client is used. All clients require the addresses of the memory locations from which the data are taken from the server and in which the data are saved in the server. Here these addresses are indicated as Modbus addresses.

The client carries out the corresponding operation on these Modbus addresses to receive the desired result.

4-33

Function


Valid Modbus addresses and their meaning

Modbus address [words] dec. start hex. end dec.

Content

1024 400 1024 controllere PLC status ( page

4-36

)

2048 800 2048 Modbus timeout (

 page

4-36

)

2049 801 2049 Modbus write timeout (

 page

4-36

)

2050 802 2050 delete the write timeout register

(

 page

4-36

)

Data AS-i master 1

4096 1000 4127 digital slave inputs (

 page

4-37

)

4128 1020 4129 master flags (

 page

4-40

)

4130 1022 4284 analogue slave inputs (

 page

4-41

)

4285 10BD 4348 current configuration data

(

 page

4-53

)

4349 10FD 4364 current parameters (

page

4-55

)

4365 110D 4368

4369 1111 4372

4373 1115 4376

4377 1119 4380

4381 111D 4444

LAS (

 page

4-56

)

LDS (

 page

4-57

)

LPF (

 page

4-58

)

LPS (

 page

4-59

) projected configuration data

(

 page

4-53

)

4445 115D 4460 reflected parameters (

 page

4-55

)

4461 116D 4522 telegram error counter (

 page

4-60

)

4523 11AB 4523 configuration error counter (

 page

4-62

)

4524 11AC 4524 AS-i cycle counter (

 page

4-62

)

4525 11AD 4556 digital slave outputs (  page

4-37

)

4557 11CD 4558 reserved

4559 11CF 4713 analogue slave outputs (  page

4-41

)

4714 126A 4777 reserved

4778 12AA 4793

4794 12BA 4812

4813 12CD 4831 reserved host command channel request

(

 page

4-63

) host command channel response

(

 page

4-64

)

Data AS-i master 2

8192 2000 8223 digital slave inputs (

 page

4-37

)

8224 2020 8225 master flags (

 page

4-40

)

8226 2022 8380 analogue slave inputs (

 page

4-41

)

8381 20BD 8444 current configuration data

(

 page

4-53

)

8445 20FD 8460 current parameters (

page

4-55

)

8461 210D 8464 LAS (

 page

4-56

)

8465 2111 8468

LDS (

 page

4-57

)

Access r = read w = write

Size

[words]

64

16

IEC addresses from to

r/w 1 — — r/w 1 — — r/w 1 — —

—

—

—

2

%IB1.31

%IB11.31

%QB1.31

%QB11.31

— —

— —

— — r/w 19 — —

%IB2.31

%IB12.31

4-34

Function


Modbus address [words] dec. start hex. end dec.

Content

8469 2115 8472

8473 2119 8476

8477 211D 8540

LPF (

 page

4-58

)

LPS (

 page

4-59

) projected configuration data

(

 page

4-53

)

8541 215D 8556 reflected parameters (  page

4-55

)

8557 216D 8618 telegram error counter (

 page

4-60

)

8619 21AB 8619 configuration error counter (

 page

4-62

)

8620 21AC 8620 AS-i cycle counter (

 page

4-62

)

8621 21AD 8652 digital slave outputs (

 page

4-37

)

8653 21CD 8654 reserved

8655 21CF 8809 analogue slave outputs (

 page

4-41

)

8810 226A 8873 reserved

8874 22AA 8889

8890 22BA 8908 reserved host command channel request

(

 page

4-63

)

8909 22CD 8927 host command channel response

(

 page

4-64

)

General data

12288 3000 12351 inputs from fieldbus (

 page

4-65

)

12352 3040 12415 outputs to fieldbus (

 page

4-65

) extended data to the PLC in the controllere

(

 page

4-67

)

12672 3180 12927 extended data from the PLC in the controllere

(

 page

4-67

)

Access r = read w = write

Size

[words]

— 2

IEC addresses from to

%QB2.31

%QB12.31

— —

—

—

64

16

— —

— — r/w 19 — —

4-35

Function


Modbus address for controllere PLC status

Modbus address

1024

Data content (16 bits = 1 word)

status value = 1

 PLC is in the operating mode RUN status value = 2

 PLC is in the operating mode STOP status value = 8

 PLC is in the operating mode GATEWAY

Modbus address for Modbus timeout

Modbus address Data content (16 bits = 1 word)

2048 timeout value in [ms]

► The PLC of the controllere must be in the gateway mode.

► If value ≠ 0: the outputs are reset if no Modbus telegram (read or write request) has been received in the specified time [ms].

► If value = 0: this function is deactivated.

► The register is predefined by the corresponding setting on the ifm standard HTML page of the web server. The value set via the ifm standard HTML page is stored non-volatilely in the controllere.

Changes of this register via Modbus however are volatile. After rebooting the controllere the value defined by the HTML page is again activated.

Modbus address for Modbus write timeout

Modbus address

2049

Data content (16 bits = 1 word)

timeout value in [ms]

► The PLC of the controllere must be in the gateway mode.

► Function is identical to "Modbus timeout" ( page

4-36

), but for the Modbus write timeout only

Modbus write requests are taken into account to trigger the timeout time counter.

Modbus address for "delete Modbus write timeout register"

Modbus address Data content (16 bits = 1 word)

2050 user-defined

► Writing on this Modbus address results in a reset of the Modbus write timeout register, thus the timeout time counter is reset.

► This function allows to prevent the triggering of the Modbus write timeout without having to write on the outputs used.

► The value written in this register is ignored in the controllere.

4-36

Function


Modbus addresses of the digital slave inputs and outputs

Modbus addresses Bits of the Modbus address

Master 1 inputs

Master 1 outputs

Master 2 inputs


Slave data bits



15…12 11 10 9 8 7…4 3

D3 D2 D1 D0

2 1 0

D3 D2 D1 D0

4203

4104

4105

4106

4107

4108

4109

4110

4111

4112

4096

4097

4098

4099

4100

4101

4102

4120

4121

4122

4123

4124

4113

4114

4115

4116

4117

4118

4119

4125

4126

4127

4532

4533

4534

4535

4536

4537

4538

4539

4540

4541

4525

4526

4527

4528

4529

4530

4531

4549

4550

4551

4552

4553

4542

4543

4544

4545

4546

4547

4548

4554

4555

4556

8199

8200

8201

8202

8203

8204

8205

8206

8207

8208

8192

8193

8194

8195

8196

8197

8198

8216

8217

8218

8219

8220

8209

8210

8211

8212

8213

8214

8215

8221

8222

8223

8628

8629

8630

8631

8632

8633

8634

8635

8636

8637

8621

8622

8623

8624

8625

8626

8627

8645

8646

8647

8648

8649

8638

8639

8640

8641

8642

8643

8644

8650

8651

8652

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0 slave 2 (A) slave 4 (A) slave 6 (A) slave 8 (A) slave 10 (A) slave 12 (A) slave 14 (A) slave 16 (A) slave 18 (A) slave 20 (A) slave 22 (A) slave 24 (A) slave 26 (A) slave 28 (A) slave 30 (A) reserved slave 2 B slave 4 B slave 6 B slave 8 B slave 10 B slave 12 B slave 14 B slave 16 B slave 18 B slave 20 B slave 22 B slave 24 B slave 26 B slave 28 B slave 30 B reserved

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0 slave 1 (A) slave 3 (A) slave 5 (A) slave 7 (A) slave 9 (A) slave 11 (A) slave 13 (A) slave 15 (A) slave 17 (A) slave 19 (A) slave 21 (A) slave 23 (A) slave 25 (A) slave 27 (A) slave 29 (A) slave 31 (A) slave 1 B slave 3 B slave 5 B slave 7 B slave 9 B slave 11 B slave 13 B slave 15 B slave 17 B slave 19 B slave 21 B slave 23 B slave 25 B slave 27 B slave 29 B slave 31 B

4-37

Function


Master 1 inputs

%IB1.1

%IB1.2

%IB1.3

%IB1.4

%IB1.5

%IB1.6

%IB1.7

%IB1.8

%IB1.9

%IB1.10

%IB1.11

%IB1.12

%IB1.13

%IB1.14

%IB1.15

%IB1.16

%IB1.17

%IB1.18

%IB1.19

%IB1.20

%IB1.21

%IB1.22

%IB1.23

%IB1.24

%IB1.25

%IB1.26

%IB1.27

%IB1.28

%IB1.29

%IB1.30

IEC addresses in the PLC of the controllere for the digital slave inputs and outputs

Data area

I = input

Q = output

%QB1.1

%QB1.2

%QB1.3

%QB1.4

%QB1.5

%QB1.6

%QB1.7

%QB1.8

%QB1.9

%QB1.10

%QB1.11

%QB1.12

%QB1.13

%QB1.14

%QB1.15

%QB1.16

%QB1.17

%QB1.18

%QB1.19

%QB1.20

%QB1.21

%QB1.22

%QB1.23

%QB1.24

%QB1.25

%QB1.26

%QB1.27

%QB1.28

%QB1.29

%QB1.30

% I B 1. 7

% Q X 21. 2 .3

Identification Type of access

Slave address Data bit

B = byte

X = bit

1 = S/A slave on master 1

2 = S/A slave on master 2

11 = B slave on master 1

21 = B slave on master 2

…

31 = slave 31

S/A slave = single slave or A slave

IEC addresses

(PLC in controllere)


Master 2 inputs


1 = slave 1

2 = slave 2 if type of access = X:

0 = D0

1 = D1

2 = D2

3 = D3

Inputs / outputs to slave address

%IB2.1

%IB2.2

%IB2.3

%IB2.4

%IB2.5

%IB2.6

%IB2.7

%IB2.8

%IB2.9

%IB2.10

%IB2.11

%IB2.12

%IB2.13

%IB2.14

%IB2.15

%IB2.16

%IB2.17

%IB2.18

%IB2.19

%IB2.20

%IB2.21

%IB2.22

%IB2.23

%IB2.24

%IB2.25

%IB2.26

%IB2.27

%IB2.28

%IB2.29

%IB2.30

4-38

%IB11.11

%IB11.12

%IB11.13

%IB11.14

%IB11.15

%IB11.16

%IB11.17

%IB11.18

%IB11.19

%IB11.20

Master 1 inputs

%IB1.31

%IB11.1

%IB11.2

%IB11.3

%IB11.4

%IB11.5

%IB11.6

%IB11.7

%IB11.8

%IB11.9

%IB11.10

%IB11.21

%IB11.22

%IB11.23

%IB11.24

%IB11.25

%IB11.26

%IB11.27

%IB11.28

%IB11.29

%IB11.30

%IB11.31

Function


%QB11.21

%QB11.22

%QB11.23

%QB11.24

%QB11.25

%QB11.26

%QB11.27

%QB11.28

%QB11.29

%QB11.30

%QB11.31

%QB11.11

%QB11.12

%QB11.13

%QB11.14

%QB11.15

%QB11.16

%QB11.17

%QB11.18

%QB11.19

%QB11.20

IEC addresses



Master 2 inputs

%QB1.31

%QB11.1

%QB11.2

%QB11.3

%IB2.31

%IB21.1

%IB21.2

%IB21.3

%QB11.4

%QB11.5

%QB11.6

%QB11.7

%QB11.8

%QB11.9

%QB11.10

%IB21.4

%IB21.5

%IB21.6

%IB21.7

%IB21.8

%IB21.9

%IB21.10

%IB21.11

%IB21.12

%IB21.13

%IB21.14

%IB21.15

%IB21.16

%IB21.17

%IB21.18

%IB21.19

%IB21.20

%IB21.21

%IB21.22

%IB21.23

%IB21.24

%IB21.25

%IB21.26

%IB21.27

%IB21.28

%IB21.29

%IB21.30

%IB21.31


Inputs / outputs to slave address

4-39

Function


Modbus addresses for the master flags

Modbus address

IEC address


Bit

Master 1 Master 2

Bit = TRUE means:

4128

%IW31.240

8224

%IW32.240

4129

%IW31.241

8225

%IW32.241

0

"No Slave Reset"

When executing the function "Config all" (via the menu or command channel of the controllere) the slaves are NOT reset, as described in the AS-i specification.

1...15 reserved

0

1

"Config OK"

There is no configuration error. The configuration of all AS-i slaves in the network complies with the configuration data.

"LDS.0"

One slave with the AS-i address 0 was detected on the master.

2 reserved

3 reserved

4

5

"Configuration_Active"

The controllere is in the configuration mode

"Normal_Operation_Active"

The AS-i master is in normal operation: it communicates with at least one slave.

6

„AS-i_Power_Fail“

The AS-i voltage is too low.

7 reserved

„Periphery_OK“

8

None of the active AS-i slaves signals a periphery fault.

9

„Auto_Address_Enable“

The mode "automatic addressing of the slaves" on this master is activated.

10...15 reserved

Examples:

To retrieve the bit LDS.0 "slave 0 detected" for master 1, the address %IX31.241.1 is used; for master 2 the address

%IX32.241.1 is used.

IEC addresses in the PLC of the controllere for the master flags

Data area

% I W 31. 240

% I X 32. 241 .8

Identification Word selection

I = input

Type of access

W = word

X = bit

31 = master 1

32 = master 2

240 = master flags word 1

241 = master flags word 2

Data bit no.

if type of access = X:

0…15

4-40

4582

4583

4584

4585

4586

4577

4578

4579

4580

4581

4572

4573

4574

4575

4576

4587

4588

4589

4590

4567

4568

4569

4570

4571

4562

4563

4564

4565

4566

8249

8250

8251

8252

8253

8244

8245

8246

8247

8248

8239

8240

8241

8242

8243

8254

8255

8256

8257

8234

8235

8236

8237

8238

8229

8230

8231

8232

8233

4153

4154

4155

4156

4157

4148

4149

4150

4151

4152

4143

4144

4145

4146

4147

4158

4159

4160

4161

4138

4139

4140

4141

4142

4133

4134

4135

4136

4137

Function


Modbus addresses for the analogue slave inputs and outputs

Master 1 inputs

Modbus addresses


Master 2 inputs


Data content (16 bits = word)

Channel Description

4130

4131

4559

4560

8226

8227

8655

8656

0

1

1st channel S/A slave

2nd channel S/A slave

4132 4561 8228

8660

8661

8665

8666

8670

8671

8675

8676

8680

8681

8685

8686

0

1

0

1

0

1

0

1

0

1

0

1













Slave address

1

2

3

4

5

6

7

4-41

4612

4613

4614

4615

4616

4607

4608

4609

4610

4611

4617

4618

4619

4620

4621

4602

4603

4604

4605

4606

4597

4598

4599

4600

4601

4592

4593

4594

4595

4596

8279

8280

8281

8282

8283

8274

8275

8276

8277

8278

8284

8285

8286

8287

8288

8269

8270

8271

8272

8273

8264

8265

8266

8267

8268

8259

8260

8261

8262

8263

4183

4184

4185

4186

4187

4178

4179

4180

4181

4182

4188

4189

4190

4191

4192

4173

4174

4175

4176

4177

4168

4169

4170

4171

4172

4163

4164

4165

4166

4167

Function


Master 1 inputs

4162



Master 2 inputs

4591 8258




8690

8691

8695

8696

8700

8701

8705

8706

8710

8711

8715

8716

0

1

0

1

0

1

0

1

0

1

0

1













4193

4194

4-42

4622

4623

8289

8290

Slave address

8

9

10

11

12

13

4642

4643

4644

4645

4646

4637

4638

4639

4640

4641

4647

4648

4649

4650

4651

4632

4633

4634

4635

4636

4627

4628

4629

4630

4631

8309

8310

8311

8312

8313

8304

8305

8306

8307

8308

8314

8315

8316

8317

8318

8299

8300

8301

8302

8303

8294

8295

8296

8297

8298

4213

4214

4215

4216

4217

4208

4209

4210

4211

4212

4218

4219

4220

4221

4222

4203

4204

4205

4206

4207

4198

4199

4200

4201

4202

Function


Master 1 inputs

4195

4196

4197



Master 2 inputs

4624

4625

8291

8292

4626 8293



8720

8721


0

1



8725

8726

8730

8731

8735

8736

8740

8741

8745

8746

0

1

0

1

0

1

0

1

0

1











4223

4224

4225

4226

4227

4652

4653

4654

4655

4656

8319

8320

8321

8322

8323

8750

8751

0

1



Slave address

14

15

16

17

18

19

20

4-43

4258

4259

4260

4261

4-44

4248

4249

4250

4251

4252

4253

4254

4255

4256

4257

4243

4244

4245

4246

4247

4238

4239

4240

4241

4242

4682

4683

4684

4685

4686

4687

4688

4689

4690

4677

4678

4679

4680

4681

4672

4673

4674

4675

4676

4667

4668

4669

4670

4671

4662

4663

4664

4665

4666

Function


Master 1 inputs

4228

4229

4230

4231

4232



Master 2 inputs

4657

4658

4659

4660

4661

8324

8325

8326

8327

8328




8755

8756

0

1



4233

4234

4235

4236

4237

8760

8761

0

1



8349

8350

8351

8352

8353

8354

8355

8356

8357

8344

8345

8346

8347

8348

8339

8340

8341

8342

8343

8334

8335

8336

8337

8338

8329

8330

8331

8332

8333

8765

8766

8770

8771

8775

8776

8780

8781

8785

8786

0

1

0

1

0

1

0

1

0

1











Slave address

21

22

23

24

25

26

27

Function


Master 1 inputs

4262



Master 2 inputs

4691 8358




Slave address

4263

4264

4265

4266

4267

4692

4693

4694

4695

4696

8359

8360

8361

8362

8363

8790

8791

0

1



28

4268

4269

4270

4271

4272

4697

4698

4699

4700

4701

8364

8365

8366

8367

8368

8795

8796

0

1



29

4273

4274

4275

4276

4277

4702

4703

4704

4705

4706

8369

8370

8371

8372

8373

8800

8801

0

1



30

4278

4279

4280

4281

4282

4707

4708

4709

4710

4711

8374

8375

8376

8377

8378

8805

8806

0

1



31

4283 4712 8379

4284 4713 8380

Status information of analogue slaves

Word no.

0

1

15 14 13 12

Bit

11 10 9 8 7 6 5 analogue channel 0 from/for slave or: analogue data channel 0 from/for slave 1A analogue data channel 1 from/for slave 1 or: analogue data channel 1 from/for slave 1A

4 3 2 1 0

2

3 analogue data channel 2 from/for slave 1 or: analogue data channel 0 from/for slave 1B analogue data channel 3 from/for slave 1 or: analogue data channel 1 from/for slave 1B

4 TIB TOB TIA TOA TVB OVB TVA OVA O3 V3 O2 V2 O1 V1 O0 V0

4-45

Function


Word no.

5

15 14 13 12

Bit

11 10 9 8 7 6 5 analogue data channel 0 from/for slave 2 or: analogue data channel 0 from/for slave 2A

4 3 2 1 0

6

7

8 analogue data channel 1 from/for slave 2 or: analogue data channel 1 from/for slave 2A analogue data channel 2 from/for slave 2 or: analogue data channel 0 from/for slave 2B analogue data channel 3 from/for slave 2 or: analogue data channel 1 from/for slave 2B


… …

150

151

152

153 analogue data channel 0 from/for slave 31 or: analogue data channel 0 from/for slave 31A analogue data channel 1 from/for slave 31 or: analogue data channel 1 from/for slave 31A analogue data channel 2 from/for slave 31 or: analogue data channel 0 from/for slave 31B analogue data channel 3 from/for slave 31 or: analogue data channel 1 from/for slave 31B


Legend:

Vn

On

OVA

TVA

OVB

TVB

TIA

TIB

TOA

TOB validity bit "valid" for channel number n = 0...3

NOTE: set Vn = "1" for analogue output slaves! bit "overflow" for channel number n = 0…3 channel-independent bit "output data valid" from A slave

CTT1:

0 = more than 3.5 s have elapsed since the last update of the output values

1 = slave requests new output data within the next 3 s

CTT2…CTT5:

0 = slave receives no new output data

1 = slave receives new output data channel-independent bit "transmission valid" from A slave/single slave:

0 = error during transmission or: timeout

1 = transmission of analogue input/output data OK channel-independent bit "output data valid" from B slave:

CTT1:

0 = more than 3.5 s have elapsed since the last update of the output values

1 = slave requests new output data within the next 3 s

CTT2…CTT5:

0 = slave receives no new output data

1 = slave receives new output data

NOTE: only valid for analogue output slaves. Set OVB = 0 for input slaves! channel-independent bit "transmission valid" from B slave:

0 = error during transmission or: timeout

1 = transmission of analogue input/output data OK slave transmits analogue input data...

0 = in the analogue mode (15 bits, with sign)

1 = in the transparent mode (16 bits, without sign) slave receives analogue output data...

0 = in the analogue mode (15 bits, with sign)

1 = in the transparent mode (16 bits, without sign)

4-46

Function


IEC addresses in the PLC of the controllere for the analogue slave inputs and outputs

% I W 21. 6 .0

Data area Type of access

% Q W 22. 9 .3

Identification Slave address Data channel

I = input

Q = output

W = word

21 = master 1

22 = master 2

S/A slave = single slave or A slave

1 = slave 1

2 = slave 2

…

31 = slave 31

0 =

1 =

2 =

3 =



3rd channel single slave or:

1st channel B slave

4th channel single slave or:

2nd channel B slave

4 = status

A/B slaves have max. 2 analogue channels

Master 1 inputs

IEC addresses



Master 2 inputs




Slave address

%IW21.1.0 %QW21.1.0 %IW22.1.0 %QW22.1.0

%IW21.1.1 %QW21.1.1 %IW22.1.1 %QW22.1.1

%IW21.1.2 %QW21.1.2 %IW22.1.2 %QW22.1.2

%IW21.1.3 %QW21.1.3 %IW22.1.3 %QW22.1.3

%IW21.1.4 %QW21.1.4 %IW22.1.4 %QW22.1.4

%IW21.2.0 %QW21.2.0 %IW22.2.0 %QW22.2.0

%IW21.2.1 %QW21.2.1 %IW22.2.1 %QW22.2.1

%IW21.2.2 %QW21.2.2 %IW22.2.2 %QW22.2.2

%IW21.2.3 %QW21.2.3 %IW22.2.3 %QW22.2.3

%IW21.2.4 %QW21.2.4 %IW22.2.4 %QW22.2.4

%IW21.3.0 %QW21.3.0 %IW22.3.0 %QW22.3.0

%IW21.3.1 %QW21.3.1 %IW22.3.1 %QW22.3.1

%IW21.3.2 %QW21.3.2 %IW22.3.2 %QW22.3.2

%IW21.3.3 %QW21.3.3 %IW22.3.3 %QW22.3.3

%IW21.3.4 %QW21.3.4 %IW22.3.4 %QW22.3.4

%IW21.4.0 %QW21.4.0 %IW22.4.0 %QW22.4.0

%IW21.4.1 %QW21.4.1 %IW22.4.1 %QW22.4.1

%IW21.4.2 %QW21.4.2 %IW22.4.2 %QW22.4.2

%IW21.4.3 %QW21.4.3 %IW22.4.3 %QW22.4.3

%IW21.4.4 %QW21.4.4 %IW22.4.4 %QW22.4.4

%IW21.5.0 %QW21.5.0 %IW22.5.0 %QW22.5.0

0

1

2

3




1st channel B slave


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1



2

3

4 status

0 1st channel S/A slave

1

2

3


1st channel B slave


2nd channel B slave



1st channel B slave


2nd channel B slave

4 status


1

2

3

4

5

4-47

Function


Master 1 inputs

IEC addresses



Master 2 inputs


%IW21.5.1 %QW21.5.1 %IW22.5.1 %QW22.5.1

%IW21.5.2 %QW21.5.2 %IW22.5.2 %QW22.5.2

%IW21.5.3

%IW21.5.4 %QW21.5.4 %IW22.5.4 %QW22.5.4

%IW21.6.0 %QW21.6.0 %IW22.6.0 %QW22.6.0

%IW21.6.1

%IW21.6.2

%IW21.6.3

%IW21.8.2

%QW21.6.1

%QW21.6.2

%QW21.8.2

%IW22.6.1

%IW22.6.2

%IW22.8.2

%QW22.6.1

%QW22.6.2

%IW21.6.4 %QW21.6.4 %IW22.6.4 %QW22.6.4

%IW21.7.0 %QW21.7.0 %IW22.7.0 %QW22.7.0

%IW21.7.1

%IW21.7.2

%IW21.7.3

%IW21.7.4 %QW21.7.4 %IW22.7.4 %QW22.7.4

%IW21.8.0 %QW21.8.0 %IW22.8.0 %QW22.8.0

%IW21.8.1 %QW21.8.1 %IW22.8.1 %QW22.8.1

%IW21.8.3

%IW21.9.3

%IW21.9.4

%QW21.7.1

%QW21.7.2

%QW21.7.3

%QW21.8.3

%IW22.7.1

%IW22.7.2

%IW22.7.3

%IW22.8.3

%QW22.7.1

%QW22.7.2

%QW22.7.3

%QW22.8.2

%QW22.8.3

%IW21.8.4 %QW21.8.4 %IW22.8.4 %QW22.8.4

%IW21.9.0 %QW21.9.0 %IW22.9.0 %QW22.9.0

%IW21.9.1 %QW21.9.1 %IW22.9.1 %QW22.9.1

%IW21.9.2 %QW21.9.2 %IW22.9.2 %QW22.9.2

%IW21.10.0 %QW21.10.0 %IW22.10.0 %QW22.10.0

%IW21.10.1 %QW21.10.1 %IW22.10.1 %QW22.10.1

%IW21.10.2

%IW21.10.3

%IW21.10.4

%QW21.9.4

%QW21.10.4

%IW22.9.4

%IW22.10.4

%QW22.9.4

%QW22.10.4

%IW21.11.0 %QW21.11.0 %IW22.11.0 %QW22.11.0

%IW21.11.1 %QW21.11.1 %IW22.11.1 %QW22.11.1

%IW21.11.2

%QW21.5.3

%QW21.6.3

%QW21.9.3

%QW21.10.2

%QW21.10.3

%QW21.11.2

%IW22.5.3

%IW22.6.3

%IW22.9.3

%IW22.10.2

%IW22.10.3

%IW22.11.2

%QW22.5.3

%QW22.6.3

%QW22.9.3

%QW22.10.2

%QW22.10.3

%QW22.11.2


1

2




1st channel B slave

3


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1

2

3




1st channel B slave


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1



2

3

4 status


1

2

3


1st channel B slave


2nd channel B slave



1st channel B slave


2nd channel B slave

4 status


1

2



1st channel B slave

4-48

Slave address

6

7

8

9

10

11

Function


Master 1 inputs

IEC addresses



Master 2 inputs


%IW21.11.3 %QW21.11.3 %IW22.11.3 %QW22.11.3



%IW21.11.4 %QW21.11.4 %IW22.11.4 %QW22.11.4

%IW21.12.0 %QW21.12.0 %IW22.12.0 %QW22.12.0

%IW21.12.1

%IW21.12.2

%IW21.12.3

%IW21.12.4 %QW21.12.4 %IW22.12.4 %QW22.12.4

%IW21.13.0 %QW21.13.0 %IW22.13.0 %QW22.13.0

%IW21.13.1 %QW21.13.1 %IW22.13.1 %QW22.13.1

%IW21.13.2

%IW21.13.3

%IW21.15.2

%QW21.13.2

%QW21.13.3

%QW21.15.2

%IW22.13.2

%IW22.13.3

%IW22.15.2

%QW22.13.2

%QW22.13.3

%IW21.13.4 %QW21.13.4 %IW22.13.4 %QW22.13.4

%IW21.14.0 %QW21.14.0 %IW22.14.0 %QW22.14.0

%IW21.14.1 %QW21.14.1 %IW22.14.1 %QW22.14.1

%IW21.14.2

%IW21.14.3

%IW21.14.4 %QW21.14.4 %IW22.14.4 %QW22.14.4

%IW21.15.0 %QW21.15.0 %IW22.15.0 %QW22.15.0

%IW21.15.1 %QW21.15.1 %IW22.15.1 %QW22.15.1

%IW21.15.3

%IW21.17.2

%QW21.14.2

%QW21.14.3

%QW21.15.3

%QW21.16.2

%QW21.17.2

%IW22.14.2

%IW22.14.3

%IW22.15.3

%IW22.16.2

%IW22.17.2

%QW22.14.2

%QW22.14.3

%QW22.15.2

%QW22.15.3

%IW21.15.4 %QW21.15.4 %IW22.15.4 %QW22.15.4

%IW21.16.0 %QW21.16.0 %IW22.16.0 %QW22.16.0

%IW21.16.1 %QW21.16.1 %IW22.16.1 %QW22.16.1

%IW21.16.2

%IW21.16.3

%QW21.12.1

%QW21.12.2

%QW21.12.3

%QW21.16.3

%IW22.12.1

%IW22.12.2

%IW22.12.3

%IW22.16.3

%QW22.12.1

%QW22.12.2

%QW22.12.3

%QW22.16.2

%QW22.16.3

%IW21.16.4 %QW21.16.4 %IW22.16.4 %QW22.16.4

%IW21.17.0 %QW21.17.0 %IW22.17.0 %QW22.17.0

%IW21.17.1 %QW21.17.1 %IW22.17.1 %QW22.17.1

%QW22.17.2

%IW21.17.3 %QW21.17.3 %IW22.17.3 %QW22.17.3

%IW21.17.4 %QW21.17.4 %IW22.17.4 %QW22.17.4

%IW21.18.0 %QW21.18.0 %IW22.18.0 %QW22.18.0

3


2nd channel B slave

4 status

0

1

2

3




1st channel B slave


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1



2

3

4 status


1

2

3


1st channel B slave


2nd channel B slave



1st channel B slave


2nd channel B slave

4 status


1

2

3



1st channel B slave


2nd channel B slave

4 status


1

2

3



1st channel B slave


2nd channel B slave

4 status


Slave address

12

13

14

15

16

17

18

4-49

Function


Master 1 inputs

IEC addresses



Master 2 inputs


%IW21.18.1 %QW21.18.1 %IW22.18.1 %QW22.18.1



%IW21.18.2

%IW21.18.3

%IW21.18.4

%IW21.19.0

%IW21.19.1

%IW21.19.2

%IW21.19.3

%IW21.19.4

%IW21.20.0

%IW21.20.1

%IW21.20.2

%IW21.20.3

%IW21.20.4

%IW21.21.0

%IW21.21.1

%IW21.21.2

%IW21.21.3

%IW21.21.4

%IW21.22.0

%IW21.22.1

%IW21.22.2

%IW21.22.3

%IW21.22.4

%IW21.23.0 %QW21.23.0 %IW22.23.0 %QW22.23.0

%IW21.23.1 %QW21.23.1 %IW22.23.1 %QW22.23.1

%IW21.23.2

%IW21.23.3

%IW21.23.4

%QW21.22.4

%QW21.23.4

%IW22.22.4

%IW22.23.4

%QW22.22.4

%QW22.23.4

%IW21.24.0 %QW21.24.0 %IW22.24.0 %QW22.24.0

%IW21.24.1 %QW21.24.1 %IW22.24.1 %QW22.24.1

%IW21.24.2

%QW21.18.2

%QW21.18.3

%QW21.18.4

%QW21.19.0

%QW21.19.1

%QW21.19.2

%QW21.19.3

%QW21.19.4

%QW21.20.0

%QW21.20.1

%QW21.20.2

%QW21.20.3

%QW21.20.4

%QW21.21.0

%QW21.21.1

%QW21.21.2

%QW21.21.3

%QW21.21.4

%QW21.22.0

%QW21.22.1

%QW21.22.2

%QW21.22.3

%QW21.23.2

%QW21.23.3

%QW21.24.2

%IW22.18.2

%IW22.18.3

%IW22.18.4

%IW22.19.0

%IW22.19.1

%IW22.19.2

%IW22.19.3

%IW22.19.4

%IW22.20.0

%IW22.20.1

%IW22.20.2

%IW22.20.3

%IW22.20.4

%IW22.21.0

%IW22.21.1

%IW22.21.2

%IW22.21.3

%IW22.21.4

%IW22.22.0

%IW22.22.1

%IW22.22.2

%IW22.22.3

%IW22.23.2

%IW22.23.3

%IW22.24.2

%QW22.18.2

%QW22.18.3

%QW22.18.4

%QW22.19.0

%QW22.19.1

%QW22.19.2

%QW22.19.3

%QW22.19.4

%QW22.20.0

%QW22.20.1

%QW22.20.2

%QW22.20.3

%QW22.20.4

%QW22.21.0

%QW22.21.1

%QW22.21.2

%QW22.21.3

%QW22.21.4

%QW22.22.0

%QW22.22.1

%QW22.22.2

%QW22.22.3

%QW22.23.2

%QW22.23.3

%QW22.24.2

1

2



1st channel B slave

3


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1

2

3




1st channel B slave


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1



2

3

4 status


1

2

3


1st channel B slave


2nd channel B slave



1st channel B slave


2nd channel B slave

4 status


1

2



1st channel B slave

4-50

Slave address

19

20

21

22

23

24

Function


Master 1 inputs

IEC addresses



Master 2 inputs


%IW21.24.3 %QW21.24.3 %IW22.24.3 %QW22.24.3



%IW21.24.4 %QW21.24.4 %IW22.24.4 %QW22.24.4

%IW21.25.0 %QW21.25.0 %IW22.25.0 %QW22.25.0

%IW21.25.1

%IW21.25.2

%IW21.25.3

%IW21.25.4 %QW21.25.4 %IW22.25.4 %QW22.25.4

%IW21.26.0 %QW21.26.0 %IW22.26.0 %QW22.26.0

%IW21.26.1 %QW21.26.1 %IW22.26.1 %QW22.26.1

%IW21.26.2

%IW21.26.3

%IW21.28.2

%QW21.26.2

%QW21.26.3

%QW21.28.2

%IW22.26.2

%IW22.26.3

%IW22.28.2

%QW22.26.2

%QW22.26.3

%IW21.26.4 %QW21.26.4 %IW22.26.4 %QW22.26.4

%IW21.27.0 %QW21.27.0 %IW22.27.0 %QW22.27.0

%IW21.27.1 %QW21.27.1 %IW22.27.1 %QW22.27.1

%IW21.27.2

%IW21.27.3

%IW21.27.4 %QW21.27.4 %IW22.27.4 %QW22.27.4

%IW21.28.0 %QW21.28.0 %IW22.28.0 %QW22.28.0

%IW21.28.1 %QW21.28.1 %IW22.28.1 %QW22.28.1

%IW21.28.3

%IW21.30.2

%QW21.27.2

%QW21.27.3

%QW21.28.3

%QW21.29.2

%QW21.30.2

%IW22.27.2

%IW22.27.3

%IW22.28.3

%IW22.29.2

%IW22.30.2

%QW22.27.2

%QW22.27.3

%QW22.28.2

%QW22.28.3

%IW21.28.4 %QW21.28.4 %IW22.28.4 %QW22.28.4

%IW21.29.0 %QW21.29.0 %IW22.29.0 %QW22.29.0

%IW21.29.1 %QW21.29.1 %IW22.29.1 %QW22.29.1

%IW21.29.2

%IW21.29.3

IW21.29.4

%QW21.25.1

%QW21.25.2

%QW21.25.3

%QW21.29.3

IW21.29.4

%IW22.25.1

%IW22.25.2

%IW22.25.3

%IW22.29.3

IW22.29.4

%QW22.25.1

%QW22.25.2

%QW22.25.3

%QW22.29.2

%QW22.29.3

IW22.29.4

%IW21.30.0 %QW21.30.0 %IW22.30.0 %QW22.30.0

%IW21.30.1 %QW21.30.1 %IW22.30.1 %QW22.30.1

%QW22.30.2

%IW21.30.3 %QW21.30.3 %IW22.30.3 %QW22.30.3

%IW21.30.4 %QW21.30.4 %IW22.30.4 %QW22.30.4

%IW21.31.0 %QW21.31.0 %IW22.31.0 %QW22.31.0

3


2nd channel B slave

4 status

0

1

2

3




1st channel B slave


2nd channel B slave

4 status

0

1



2

3


1st channel B slave


2nd channel B slave

4 status

0

1



2

3

4 status


1

2

3


1st channel B slave


2nd channel B slave



1st channel B slave


2nd channel B slave

4 status


1

2

3



1st channel B slave


2nd channel B slave

4 status


1

2

3



1st channel B slave


2nd channel B slave

4 status


Slave address

25

26

27

28

29

30

31

4-51

Function


Master 1 inputs

IEC addresses



Master 2 inputs


%IW21.31.1 %QW21.31.1 %IW22.31.1 %QW22.31.1



%IW21.31.2

%IW21.31.3

%IW21.31.4

%QW21.31.2

%QW21.31.3

%QW21.31.4

%IW22.31.2

%IW22.31.3

%IW22.31.4

%QW22.31.2

%QW22.31.3

%QW22.31.4

1

2



1st channel B slave

3


2nd channel B slave

4 status

Slave address

4-52

Function


Modbus addresses for configuration data (CDI) of the slaves

CDI = Configuration Data Image

Modbus addresses Bits / data content


15…12

XID2 current projected current projected

4285 4381 8381 8477

11…8

XID1

7…4

ID

0

3…0

IO configuration data of slave

4286 4382 8382 8478

4287 4383 8383 8479

4288 4384 8384 8480

4289 4385 8385 8481

4290 4386 8386 8482

4291 4387 8387 8483

4292 4388 8388 8484

4293 4389 8389 8485

4294 4390 8390 8486

4295 4391 8391 8487

4296 4392 8392 8488

4297 4393 8393 8489

4298 4394 8394 8490

4299 4395 8395 8491

4300 4396 8396 8492

4301 4397 8397 8493

4302 4398 8398 8494

4303 4399 8399 8495

4304 4400 8400 8496

4305 4401 8401 8497

4306 4402 8402 8498

4307 4403 8403 8499

4308 4404 8404 8500

4309 4405 8405 8501

4310 4406 8406 8502

4311 4407 8407 8503

4312 4408 8408 8504

4313 4409 8409 8505

4314 4410 8410 8506

4315 4411 8411 8507

4316 4412 8412 8508

4317 4413 8413 8509

4318 4414 8414 8510

4319 4415 8415 8511

4320 4416 8416 8512

4321 4417 8417 8513

4322 4418 8418 8514

IEC addresses


Master 1 Master 2 current projected current projected

%IW31.0 %IW31.96 %IW32.0 %IW32.96

%IW31.1 %IW31.97 %IW32.1 %IW32.97

%IW31.2 %IW31.98 %IW32.2 %IW32.98

%IW31.3 %IW31.99 %IW32.3 %IW32.99

%IW31.4 %IW31.100 %IW32.4 %IW32.100

%IW31.5 %IW31.101 %IW32.5 %IW32.101

%IW31.6 %IW31.102 %IW32.6 %IW32.102

%IW31.7 %IW31.103 %IW32.7 %IW32.103

%IW31.8 %IW31.104 %IW32.8 %IW32.104

%IW31.9 %IW31.105 %IW32.9 %IW32.105

%IW31.10 %IW31.106 %IW32.10 %IW32.106

%IW31.11 %IW31.107 %IW32.11 %IW32.107

%IW31.12 %IW31.108 %IW32.12 %IW32.108

%IW31.13 %IW31.109 %IW32.13 %IW32.109

%IW31.14 %IW31.110 %IW32.14 %IW32.110

%IW31.15 %IW31.111 %IW32.15 %IW32.111

%IW31.16 %IW31.112 %IW32.16 %IW32.112

%IW31.17 %IW31.113 %IW32.17 %IW32.113

%IW31.18 %IW31.114 %IW32.18 %IW32.114

%IW31.19 %IW31.115 %IW32.19 %IW32.115

%IW31.20 %IW31.116 %IW32.20 %IW32.116

%IW31.21 %IW31.117 %IW32.21 %IW32.117

%IW31.22 %IW31.118 %IW32.22 %IW32.118

%IW31.23 %IW31.119 %IW32.23 %IW32.119

%IW31.24 %IW31.120 %IW32.24 %IW32.120

%IW31.25 %IW31.121 %IW32.25 %IW32.121

%IW31.26 %IW31.122 %IW32.26 %IW32.122

%IW31.27 %IW31.123 %IW32.27 %IW32.123

%IW31.28 %IW31.124 %IW32.28 %IW32.124

%IW31.29 %IW31.125 %IW32.29 %IW32.125

%IW31.30 %IW31.126 %IW32.30 %IW32.126

%IW31.31 %IW31.127 %IW32.31 %IW32.127

%IW31.32 %IW31.128 %IW32.32 %IW32.128

%IW31.33 %IW31.129 %IW32.33 %IW32.129

%IW31.34 %IW31.130 %IW32.34 %IW32.130

%IW31.35 %IW31.131 %IW32.35 %IW32.131

%IW31.36 %IW31.132 %IW32.36 %IW32.132

%IW31.37 %IW31.133 %IW32.37 %IW32.133

4-53

Function


Modbus addresses Bits / data content

IEC addresses



15…12

XID2 current projected current projected

4323 4419 8419 8515

4324 4420 8420 8516

4325 4421 8421 8517

4326 4422 8422 8518

4327 4423 8423 8519

4328 4424 8424 8520

11…8

XID1

7…4

ID

3…0

IO configuration data of slave

Master 1 Master 2 current projected current projected

%IW31.38 %IW31.134 %IW32.38 %IW32.134

%IW31.39 %IW31.135 %IW32.39 %IW32.135

%IW31.40 %IW31.136 %IW32.40 %IW32.136

%IW31.41 %IW31.137 %IW32.41 %IW32.137

%IW31.42 %IW31.138 %IW32.42 %IW32.138

%IW31.43 %IW31.139 %IW32.43 %IW32.139

%IW31.44 %IW31.140 %IW32.44 %IW32.140

4329 4425 8425 8521

4330 4426 8426 8522

4331 4427 8427 8523

4332 4428 8428 8524

4333 4429 8429 8525

4334 4430 8430 8526

4335 4431 8431 8527

%IW31.45 %IW31.141 %IW32.45 %IW32.141

%IW31.46 %IW31.142 %IW32.46 %IW32.142

%IW31.47 %IW31.143 %IW32.47 %IW32.143

%IW31.48 %IW31.144 %IW32.48 %IW32.144

%IW31.49 %IW31.145 %IW32.49 %IW32.145

%IW31.50 %IW31.146 %IW32.50 %IW32.146

%IW31.51 %IW31.147 %IW32.51 %IW32.147

4336 4432 8432 8528

4337 4433 8433 8529

4338 4434 8434 8530

4339 4435 8435 8531

4340 4436 8436 8532

4341 4437 8437 8533

%IW31.52 %IW31.148 %IW32.52 %IW32.148

%IW31.53 %IW31.149 %IW32.53 %IW32.149

%IW31.54 %IW31.150 %IW32.54 %IW32.150

%IW31.55 %IW31.151 %IW32.55 %IW32.151

%IW31.56 %IW31.152 %IW32.56 %IW32.152

4342 4438 8438 8534

4343 4439 8439 8535

%IW31.57 %IW31.153 %IW32.57 %IW32.153

%IW31.58 %IW31.154 %IW32.58 %IW32.154

4344 4440 8440 8536

4345 4441 8441 8537

4346 4442 8442 8538

4347 4443 8443 8539

4348 4444 8444 8540

%IW31.59 %IW31.155 %IW32.59 %IW32.155

%IW31.60 %IW31.156 %IW32.60 %IW32.156

%IW31.61 %IW31.157 %IW32.61 %IW32.157

%IW31.62 %IW31.158 %IW32.62 %IW32.158

%IW31.63 %IW31.159 %IW32.63 %IW32.159

*) For the AS-i address 0B there is no configuration data. The value of this field is always zero.

IEC addresses in the PLC of the controllere for configuration data (CDI) of the slaves

CDI = Configuration Data Image


% I W 31. 8

Identification IEC address index

I = input W = word

31 = master 1

32 = master 2

0…63

96…159 current configuration projected configuration

––

not used

4-54

Function


Modbus addresses for parameter data of the slaves

Modbus addresses Bits

Master 1 current reflected


15…12 11…8 7…4 3…0 parameter data of slave

IEC addresses




4351 4447 8447 8543

%IW31.66 %IW31.162 %IW32.66 %IW32.162

4352 4448 8448 8544 %IW31.67 %IW31.163 %IW32.67 %IW32.163

4353 4449 8449 8545

%IW31.68 %IW31.164 %IW32.68 %IW32.164

4354 4450 8450 8546 %IW31.69 %IW31.165 %IW32.69 %IW32.165

4355 4451 8451 8547

%IW31.70 %IW31.166 %IW32.70 %IW32.166

4356 4452 8452 8548 1B %IW31.71 %IW31.167 %IW32.71 %IW32.167

IEC addresses in the PLC of the controllere for parameter data of the slaves

% I W 31. 64



I = input W = word

31 = master 1

32 = master 2

64….79

160…175 current parameters reflected parameters

––

not used

4-55

Function


Modbus addresses for the slave list LAS (list of active slaves)


IEC addresses


Master 1 Master 2 15 14 13 12 11 10

Bits

AS-i slave addresses

9 8 7 6 5 4 3 2 1 0

4365

%IW31.80

4366

%IW31.81

4367

%IW31.82

8461

%IW32.80

8462

%IW32.81

8463

%IW32.82

15(A) 14(A) 13(A) 12(A) 11(A) 10(A) 9(A) 8(A) 7(A) 6(A) 5(A) 4(A) 3(A) 2(A) 1(A) 0*)

31(A) 30(A) 29(A) 28(A) 27(A) 26(A) 25(A) 24(A) 23(A) 22(A) 21(A) 20(A) 19(A) 18(A) 17(A) 16(A)

15B 14B 13B 12B 11B 10B 9B 8B 7B 6B 5B 4B 3B 2B 1B —

4368

%IW31.83

8464

%IW32.83

31B 30B 29B 28B 27B 26B 25B 24B 23B 22B 21B 20B 19B 18B 17B 16B

*) LAS has no slave 0, so these values are set to 0 by default!

IEC addresses in the PLC of the controllere for the slave list LAS (list of active slaves)


% I W 31. 80

Identification Slave selection ––

I = input W = word

31 = master 1

32 = master 2

80 = LAS of the slaves 1(A)…15(A)

81 = LAS of the slaves 16(A)…31(A)

82 = LAS of the slaves 1B…15B

83 = LAS of the slaves 16B…31B not used

4-56

Function


Modbus addresses for the slave list LDS (list of detected slaves)


IEC addresses


Master 1 Master 2 15 14 13 12 11 10

Bits


9 8 7 6

4369

%IW31.84

4370

%IW31.85

4371

%IW31.86

4372

%IW31.87

5 4 3 2 1 0

8465

%IW32.84

8466

%IW32.85

8467

%IW32.86

8468

%IW32.87

15(A) 14(A) 13(A) 12(A) 11(A) 10(A) 9(A) 8(A) 7(A) 6(A) 5(A) 4(A) 3(A) 2(A) 1(A) 0




IEC addresses in the PLC of the controllere for the slave list LDS

(list of detected slaves)

% I W 31. 84


Identification Slave selection

I = input W = word

31 = master 1

32 = master 2

84 = LDS of the slaves 1(A)…15(A)

85 = LDS of the slaves 16(A)…31(A)

86 = LDS of the slaves 1B…15B

87 = LDS of the slaves 16B…31B

––

not used

4-57

Function


Modbus addresses for the slave list LPF (list of slaves with periphery faults)


IEC addresses


Master 1 Master 2 15 14 13 12 11 10

Bits


9 8 7 6 5 4 3 2 1 0

4373

%IW31.88

4374

%IW31.89

4375

%IW31.90

8469

%IW32.88

8470

%IW32.89

8471

%IW32.90




4376

%IW31.91

8472

%IW32.91


*) LPF has no slave 0, so these values are set to 0 by default!

IEC addresses in the PLC of the controllere for the slave list LPF

(list of slaves with periphery faults)

% I W 31. 88



I = input W = word

31 = master 1

32 = master 2

88 = LPF of the slaves 1(A)…15(A)

89 = LPF of the slaves 16(A)…31(A)

90 = LPF of the slaves 1B…15B

91 = LPF of the slaves 16B…31B

––

not used

4-58

Function


Modbus addresses for the slave list LPS (list of projected slaves)


IEC addresses


Master 1 Master 2 15 14 13 12 11 10

Bits


9 8 7 6 5 4 3 2 1 0

4377

%IW3192

4378

%IW31.93

4379

%IW31.94

8473

%IW32.92

8474

%IW32.93

8475

%IW32.94




4380

%IW31.95

8476

%IW32.95


*) LPS has no slave 0, so these values are set to 0 by default!

IEC addresses in the PLC of the controllere for the slave list LPS

(list of projected slaves)

% I W 31. 92



I = input W = word

31 = master 1

32 = master 2

92 = LPS of the slaves 1(A)…15(A)

93 = LPS of the slaves 16(A)…31(A)

94 = LPS of the slaves 1B…15B

95 = LPS of the slaves 16B…31B

––

not used

4-59

Function


Modbus addresses for the slave telegram error counters


Master 1

4494

4495

4496

4497

4498

4499

4500

4501

4484

4485

4486

4487

4488

4489

4490

4491

4492

4493

4473

4474

4475

4476

4477

4478

4479

4480

4481

4482

4483

4467

4468

4469

4470

4471

4472

4461

4462

4463

4464

4465

4466

Master 2

8590

8591

8592

8593

8594

8595

8596

8597

8580

8581

8582

8583

8584

8585

8586

8587

8588

8589

8569

8570

8571

8572

8573

8574

8575

8576

8577

8578

8579

8563

8564

8565

8566

8567

8568

8557

8558

8559

8560

8561

8562

Telegram error counter of slave

(16 bits = 1 word)

3 B

4 B

5 B

6 B

7 B

8 B

9 B

10 B

24 (A)

25 (A)

26 (A)

27 (A)

28 (A)

29 (A)

30 (A)

31 (A)

1 B

2 B

13 (A)

14 (A)

15 (A)

16 (A)

17 (A)

18 (A)

19 (A)

20 (A)

21 (A)

22 (A)

23 (A)

7 (A)

8 (A)

9 (A)

10 (A)

11 (A)

12 (A)

1 (A)

2 (A)

3 (A)

4 (A)

5 (A)

6 (A)

4-60

IEC addresses



%IW31.176 %IW32.176

%IW31.177 %IW32.177

%IW31.178 %IW32.178

%IW31.179 %IW32.179

%IW31.180 %IW32.180

%IW31.181 %IW32.181

%IW31.182 %IW32.182

%IW31.183 %IW32.183

%IW31.184 %IW32.184

%IW31.185 %IW32.185

%IW31.186 %IW32.186

%IW31.187 %IW32.187

%IW31.188 %IW32.188

%IW31.189 %IW32.189

%IW31.190 %IW32.190

%IW31.191 %IW32.191

%IW31.192 %IW32.192

%IW31.193 %IW32.193

%IW31.194 %IW32.194

%IW31.195 %IW32.195

%IW31.196 %IW32.196

%IW31.197 %IW32.197

%IW31.198 %IW32.198

%IW31.199 %IW32.199

%IW31.200 %IW32.200

%IW31.201 %IW32.201

%IW31.202 %IW32.202

%IW31.203 %IW32.203

%IW31.204 %IW32.204

%IW31.205 %IW32.205

%IW31.206 %IW32.206

%IW31.207 %IW32.207

%IW31.208 %IW32.208

%IW31.209 %IW32.209

%IW31.210 %IW32.210

%IW31.211 %IW32.211

%IW31.212 %IW32.212

%IW31.213 %IW32.213

%IW31.214 %IW32.214

%IW31.215 %IW32.215

%IW31.216 %IW32.216

Function



Master 1

4512

4513

4514

4515

4516

4517

4518

4519

4520

4521

4522

4502

4503

4504

4505

4506

4507

4508

4509

4510

4511

Master 2

8608

8609

8610

8611

8612

8613

8614

8615

8616

8617

8618

8598

8599

8600

8601

8602

8603

8604

8605

8606

8607

Telegram error counter of slave

(16 bits = 1 word)

26 B

27 B

28 B

29 B

30 B

31 B

21 B

22 B

23 B

24 B

25 B

16 B

17 B

18 B

19 B

20 B

11 B

12 B

13 B

14 B

15 B

IEC addresses



%IW31.217 %IW32.217

%IW31.218 %IW32.218

%IW31.219 %IW32.219

%IW31.220 %IW32.220

%IW31.221 %IW32.221

%IW31.222 %IW32.222

%IW31.223 %IW32.223

%IW31.224 %IW32.224

%IW31.225 %IW32.225

%IW31.226 %IW32.226

%IW31.227 %IW32.227

%IW31.228 %IW32.228

%IW31.229 %IW32.229

%IW31.230 %IW32.230

%IW31.231 %IW32.231

%IW31.2xx %IW32.2xx

%IW31.233 %IW32.233

%IW31.234 %IW32.234

%W31.235 %W32.235

%IW31.236 %IW32.236

%IW31.237 %IW32.237

IEC addresses in the PLC of the controllere for the slave telegram error counter

% I W 31. 176



I = input W = word

31 = master 1

32 = master 2

––

176…237 = error counter of the slaves 1(A)…31B not used

4-61

Function


Modbus addresses for the configuration error counter


Master 1

4523

Master 2

8619

Configuration error counter of AS-i master

(16 bits = 1 word)

configuration error counter of AS-i master

IEC addresses



%IW31.238 %IW32.238

IEC addresses in the PLC of the controllere for the configuration error counter

% I W 31. 238



I = input W = word

31 = master 1

32 = master 2

238 = configuration error counter

––

not used

Modbus addresses for the AS-i cycle counter


Master 1

4524

Master 2

8620

AS-i cycle counter of AS-i master

(16 bits = 1 word)

AS-i cycle counter of AS-i master

IEC addresses in the PLC of the controllere for the AS-i cycle counter


% I W 31. 239


I = input W = word

31 = master 1

32 = master 2

239 = AS-i cycle counter

IEC addresses



%IW31.239 %IW32.239

––

not used

4-62

Function


Modbus addresses for the request data of the host command channel

Modbus addresses Bit

Master 1 Master 2 15 14 13 12 11 10 9 8 7 6 5

echo byte of the request

4 3

request / status

2

4794 8890

4795 8891

4796 8892

4797 8893

4798 8894

4799 8895

4800 8896

4801 8897

4802 8898

4803 8899

4804 8900

4805 8901

4806 8902

4807 8903

4808 8904

4809 8905

4810 8906

4811 8907

4812 8908 reserved

1 0

4-63

Function


Modbus addresses for the response data of the host command channel

Modbus addresses Bit

Master 1 Master 2 15 14 13 12 11 10 9 8 7 6 5

4813 8909

4814 8910

4815 8911

4816 8912

4817 8913

4818 8914

4819 8915

4820 8916

4821 8917

4822 8918

4823 8919

4824 8920

4825 8921

4826 8922

4827 8923

4828 8924

4829 8925

4830 8926

4831 8927 echo byte of the response reserved

4 3

status

2 1 0

4-64

Function


Modbus addresses for the fieldbus data from/to the PLC of the controllere


Data to the

PLC

Data from the PLC

Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


12318

12319

12320

12321

12322

12323

12324

12325

12326

12327

12328

12308

12309

12310

12311

12312

12313

12314

12315

12316

12317

12298

12299

12300

12301

12302

12303

12304

12305

12306

12307

12288

12289

12290

12291

12292

12293

12294

12295

12296

12297

%QW0.30

%QW0.31

%QW0.32

%QW0.33

%QW0.34

%QW0.35

%QW0.36

%QW0.37

%QW0.38

%QW0.39

%QW0.40

%QW0.20

%QW0.21

%QW0.22

%QW0.23

%QW0.24

%QW0.25

%QW0.26

%QW0.27

%QW0.28

%QW0.29

%QW0.10

%QW0.11

%QW0.12

%QW0.13

%QW0.14

%QW0.15

%QW0.16

%QW0.17

%QW0.18

%QW0.19

%QW0.0

%QW0.1

%QW0.2

%QW0.3

%QW0.4

%QW0.5

%QW0.6

%QW0.7

%QW0.8

%QW0.9

4-65

Function



Data content

(16 bits = 1 word)

Data to the

PLC

12338

12339

12340

12341

12342

12343

12344

12345

12346

12347

12348

12349

12350

12351

12329

12330

12331

12332

12333

12334

12335

12336

12337


IEC addresses in the PLC of the controllere for the fieldbus data from/to the PLC of the controllere


% I W 0. 10

% Q W 0. 20


I = input

Q = output

W = word 0 (fixed value) 0…63 = word x of the data field

––

not used

IEC addresses


Data to the

PLC


%QW0.50

%QW0.51

%QW0.52

%QW0.53

%QW0.54

%QW0.55

%QW0.56

%QW0.57

%QW0.58

%QW0.59

%QW0.60

%QW0.61

%QW0.62

%QW0.63

%QW0.41

%QW0.42

%QW0.43

%QW0.44

%QW0.45

%QW0.46

%QW0.47

%QW0.48

%QW0.49

4-66

Function


Modbus addresses for the extended data from/to the PLC of the controllere


Data to the

PLC


Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


12446

12447

12448

12449

12450

12451

12452

12453

12454

12455

12456

12436

12437

12438

12439

12440

12441

12442

12443

12444

12445

12426

12427

12428

12429

12430

12431

12432

12433

12434

12435

12416

12417

12418

12419

12420

12421

12422

12423

12424

12425

%QW4.30

%QW4.31

%QW4.32

%QW4.33

%QW4.34

%QW4.35

%QW4.36

%QW4.37

%QW4.38

%QW4.39

%QW4.40

%QW4.20

%QW4.21

%QW4.22

%QW4.23

%QW4.24

%QW4.25

%QW4.26

%QW4.27

%QW4.28

%QW4.29

%QW4.10

%QW4.11

%QW4.12

%QW4.13

%QW4.14

%QW4.15

%QW4.16

%QW4.17

%QW4.18

%QW4.19

%QW4.0

%QW4.1

%QW4.2

%QW4.3

%QW4.4

%QW4.5

%QW4.6

%QW4.7

%QW4.8

%QW4.9

4-67

Function



Data to the

PLC

12466

12467

12468

12469

12470

12471

12472

12473

12474

12475

12476

12477

12457

12458

12459

12460

12461

12462

12463

12464

12465

12478

12479

12480

12481

12482

12483

12484

12485

12486

12487

12488

12489

12490

12491

12492

12493

12494

12495

12496

12497

12498


4-68

Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.50

%QW4.51

%QW4.52

%QW4.53

%QW4.54

%QW4.55

%QW4.56

%QW4.57

%QW4.58

%QW4.59

%QW4.60

%QW4.61

%QW4.41

%QW4.42

%QW4.43

%QW4.44

%QW4.45

%QW4.46

%QW4.47

%QW4.48

%QW4.49

%QW4.62

%QW4.63

%QW4.64

%QW4.65

%QW4.66

%QW4.67

%QW4.68

%QW4.69

%QW4.70

%QW4.71

%QW4.72

%QW4.73

%QW4.74

%QW4.75

%QW4.76

%QW4.77

%QW4.78

%QW4.79

%QW4.80

%QW4.81

%QW4.82

Function



Data to the

PLC

12508

12509

12510

12511

12512

12513

12514

12515

12516

12517

12518

12519

12499

12500

12501

12502

12503

12504

12505

12506

12507

12520

12521

12522

12523

12524

12525

12526

12527

12528

12529

12530

12531

12532

12533

12534

12535

12536

12537

12538

12539

12540


Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.83

%QW4.84

%QW4.85

%QW4.86

%QW4.87

%QW4.88

%QW4.89

%QW4.90

%QW4.91

%QW4.92

%QW4.93

%QW4.94

%QW4.95

%QW4.96

%QW4.97

%QW4.98

%QW4.99

%QW4.100

%QW4.101

%QW4.102

%QW4.103

%QW4.104

%QW4.105

%QW4.106

%QW4.107

%QW4.108

%QW4.109

%QW4.110

%QW4.111

%QW4.112

%QW4.113

%QW4.114

%QW4.115

%QW4.116

%QW4.117

%QW4.118

%QW4.119

%QW4.120

%QW4.121

%QW4.122

%QW4.123

%QW4.124

4-69

Function



Data to the

PLC

12550

12551

12552

12553

12554

12555

12556

12557

12558

12559

12560

12561

12541

12542

12543

12544

12545

12546

12547

12548

12549

12562

12563

12564

12565

12566

12567

12568

12569

12570

12571

12572

12573

12574

12575

12576

12577

12578

12579

12580

12581

12582


4-70

Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.125

%QW4.126

%QW4.127

%QW4.128

%QW4.129

%QW4.130

%QW4.131

%QW4.132

%QW4.133

%QW4.134

%QW4.135

%QW4.136

%QW4.137

%QW4.138

%QW4.139

%QW4.140

%QW4.141

%QW4.142

%QW4.143

%QW4.144

%QW4.145

%QW4.146

%QW4.147

%QW4.148

%QW4.149

%QW4.150

%QW4.151

%QW4.152

%QW4.153

%QW4.154

%QW4.155

%QW4.156

%QW4.157

%QW4.158

%QW4.159

%QW4.160

%QW4.161

%QW4.162

%QW4.163

%QW4.164

%QW4.165

%QW4.166

Function



Data to the

PLC

12592

12593

12594

12595

12596

12597

12598

12599

12600

12601

12602

12603

12583

12584

12585

12586

12587

12588

12589

12590

12591

12604

12605

12606

12607

12608

12609

12610

12611

12612

12613

12614

12615

12616

12617

12618

12619

12620

12621

12622

12623

12624


Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.167

%QW4.168

%QW4.169

%QW4.170

%QW4.171

%QW4.172

%QW4.173

%QW4.174

%QW4.175

%QW4.176

%QW4.177

%QW4.178

%QW4.179

%QW4.180

%QW4.181

%QW4.182

%QW4.183

%QW4.184

%QW4.185

%QW4.186

%QW4.187

%QW4.188

%QW4.189

%QW4.190

%QW4.191

%QW4.192

%QW4.193

%QW4.194

%QW4.195

%QW4.196

%QW4.197

%QW4.198

%QW4.199

%QW4.200

%QW4.201

%QW4.202

%QW4.203

%QW4.204

%QW4.205

%QW4.206

%QW4.207

%QW4.208

4-71

Function



Data to the

PLC

12634

12635

12636

12637

12638

12639

12640

12641

12642

12643

12644

12645

12625

12626

12627

12628

12629

12630

12631

12632

12633

12646

12647

12648

12649

12650

12651

12652

12653

12654

12655

12656

12657

12658

12659

12660

12661

12662

12663

12664

12665

12666


4-72

Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.209

%QW4.210

%QW4.211

%QW4.212

%QW4.213

%QW4.214

%QW4.215

%QW4.216

%QW4.217

%QW4.218

%QW4.219

%QW4.220

%QW4.221

%QW4.222

%QW4.223

%QW4.224

%QW4.225

%QW4.226

%QW4.227

%QW4.228

%QW4.229

%QW4.230

%QW4.231

%QW4.232

%QW4.233

%QW4.234

%QW4.235

%QW4.236

%QW4.237

%QW4.238

%QW4.239

%QW4.240

%QW4.241

%QW4.242

%QW4.243

%QW4.244

%QW4.245

%QW4.246

%QW4.247

%QW4.248

%QW4.249

%QW4.250

Function



Data to the

PLC

12667

12668

12669

12670

12671


Data content

(16 bits = 1 word)

IEC addresses


Data to the

PLC


%QW4.251

%QW4.252

%QW4.253

%QW4.254

%QW4.255

IEC addresses in the PLC of the controllere for the extended data from/to the PLC of the controllere

% Q W 4. 27

Identification IEC address index Data area

I = input

Q = output

Type of access

W = word 4 (fixed value) 0…255 = word x of the data field

––

not used

4-73

4-74

Function


4.5.4 Data exchange HTML page – controllere

Connection between

controllere

via

controllere controllere network connection controllere client MODBUS/TCP server / client controllere HTML page PC HTML data exchange

 page

4-4

4-18

4-33

here

Overview HTML data exchange

With an integrated web server HTML pages of the controllere can be represented on a PC via an

Ethernet network by means of a standard browser. By integrating a Java applet in the HTML page data can dynamically be exchanged with the controllere. To do so, the applet uses the Modbus/TCP protocol.

HTML page switch

Ethernet

AC1353/54

Modbus/TCP server web server

AS-i master

file server

AS-Interface digital

I/O slaves

analogue

I/O slaves

Function


Setting up an own web page

An own web page is to be realised on the controllere. For this the following steps are required:

Step 1

Step 2

► Connect the devices via Ethernet (

 page

4-75

)

► Set IP addresses and subnet mask (

 page

4-75

)

Step 3

Step 4

Step 5

Step 6

► Open the HTML page in the browser (

 page

4-76

)

► Address the file server via FTP (

 page

4-77

)

► Edit the web page (

 page

4-79

)

► Load and test the modified web page (

 page

4-81

)


Step 1: Connect the devices via Ethernet

► Set up the Ethernet network by connecting the PC and the controllere to the hub (or switch).

► To do so, use common CAT5 Ethernet patch cables with an RJ45 connector on both sides.


► Set appropriate IP addresses and subnet masks on the controllere and your PC

(methode

 page

4-5 ).

NOTE


"family".

Example: Subnet mask = 255.255.255.0

Then the IP addresses of the first 3 address groups (where "255" is) must be identical for all participants. The IP address may (and must) only be different in the last block (where "0" is)

(permitted values): 0…254).

Ask the network administrator for the specifications!

In our example we assume the following values:

Subnet mask = 255.255.255.0

IP address of the controllere = 192.168.10.11

IP address of the PC = 192.168.10.20

Set up the Ethernet network by connecting the PC and the controllere to the switch.

4-75

Function


Step 3: Open the HTML page in the browser

On delivery, a start page is stored in the web server of the controllere. This page is displayed when you access the IP address of the controllere with the HTTP protocol in a browser.

An example of calling the start page of the controllere with the IP address 192.168.10.11 is shown in the following figure.

► Enter "http://" and then the IP address of the controllere in the address bar.


In this window:

A click on ...

Software update

enables ...

Update of the Ethernet driver software

...in this window:

Modbus Settings of the Modbus/TCP server

User Site

4-76

Calling the HTML page

In the following we will describe the adaptation of the contents:

Function


NOTE

To allow the web page to be updated it must be possible to run Java applets in the browser (e.g. by

Java 2 Runtime Environment 5.0).

Step 4: Address the file server via FTP

As shown in the following example the file server in the controllere can be called via the browser /

Explorer.

► Enter "ftp://" followed by the requested IP address of the controllere as search address:

4-77

Function


If RAM disk in the controllere <10.120:


► User name = ftpuser

Do not enter a password

► Click [Login]

To all controllere devices the following applies:

> The browser opens a kind of Windows Explorer

► Open the directory pub under the requested IP address of the controllere

Then open the subdirectory WWW


The file user.html contains the source code of the page accessed as example in step 3.

In the following you can adapt this page to your application.

4-78

Function


Step 5: Edit the web page

► Right-click the file name user.html

► Select [Edit the source code]

In the following we describe the device-specific particularities of the HTML program code. Please find a description of the HTML orders in the appropriate technical literature.

> The following figure appears (detail):

<html>

<head>

</head>

<body onLoad="LoadFct()">

<applet archive="CeMasterApplet.jar" code="CeMasterApplet" name="CeM" width="0" height="0"><param name="DEBUG" value="0"><param name="UNITID" value="1"></applet>

<script LANGUAGE=javascript> function LoadFct()

{ setTimeout("Timer()", 500);

} etc.

In the HTML file an HTML tag <applet> must be indicated.

Detail from the above example:

<applet archive=“CeMasterApplet.jar“ code=“CeMasterApplet“ name=“CeM“ width=“0“ height=“0“> <param name=“DEBUG“ value=“0“>

<param name=“UNITID“ value=“1“>

</applet>

Here, the applet which is saved and available in the Java archive CeMasterApplet.jar is integrated in a web page. name=“CeM“ param name=“UNITID“

The object created by the applet is assigned the name "CeM"

The parameter UNITID is passed to the applet value="1"

UNITID is assigned the value 1

With this applet the user can read or write all registers of the Modbus register model (

 page

4-34

) to display data on a web page or to enter values via the web page in the Modbus registers of the controllere.

Functions available in the applet

 public int getUnitID()

With this function the UnitID of the Java applets can be read. The applet tries to address the controllere with this UnitID. If the UnitID of the applet and the controllere do not match, a

Modbus connection is not set up.

 public void setUnitID(int id) setUnitID

is used to change the UnitID of the applet.

 public int readInputRegister(int ref) readInputRegister reads the register "ref" of the Modbus register model of the controllere. In

4-79

Function

Project transmission and diagnosis via Ethernet interface case of a fault the value "-1" is returned. The content of the Modbus register is returned in the value range 0…65535.

 public void writeSingleRegister(int ref, int value) writeSingleRegister

is used to write a register of a Modbus register model. With the parameter "value" the value to be written is transmitted. If the value is greater than 65535, the bits which are more significant are ignored. With the parameter "ref" the Modbus register to be written is identified.

 public int readDigitalInputSlave(int slave) readDigitalInputSlave

reads the data of a digital input slave. This is a comfort function which makes it unnecessary for the user to extract the slave data from the register value. The 4-bit value of the corresponding input slave is directly delivered. The parameter “slave" must contain a slave address in the range of 0...62. The slave addresses 32...62 are used for B slaves.

 public int writeDigitalOutputSlave(int slave, int value) writeDigitalOutputSlave

enables to write the outputs of a digital output slave. With the parameter "slave" a slave address in the range of 0...62 is transmitted. The addresses 32...62 are used to address B slaves. In the parameter "value" the value to be written is transmitted.

 public void setDebugMode(int level)

With the setDebugMode the output of debug messages of the Java applet to the Java console can be controlled. For the parameter "level" the values 0...9 are possible. Outputs are activated by setting a bit in the parameter "level".

 public int getDebugMode()

The function getDebugMode delivers the currently set debug level value.

Call the function cyclically

Function calls in the script are normally only processed when a page is loaded. To obtain a cyclic update of the data the function "Timer" recalls itself always at the end with a defined delay (here: 250 ms): function LoadFct()

{ setTimeout("Timer()", 500); // Initial call of Timer()

} function Timer() // List of all textboxes whose values shall be updated regularly

{

... // Update of the data setTimeout("Timer()", 250);

}

//Restarts Timer() in 250 ms

4-80

Function


Step 6: Loading and testing the modified web page

There are two possibilities to open an application-specific web page:

 The page shall be accessible via the link [User-Site] from the supplied start page:

 A file user.html must be saved in the directory /pub/www.

 The web page shall replace the supplied start page:

 It must be saved as file index.html in the directoy /pub/www.

The page cannot be saved from the editor directly in the controllere. Therefore:

► First save the new page on the hard disk of the PC.

► Carry out the following steps to copy the user web page to the controllere:

 Login to the controllere by means of ftp  Step 4, page

4-77

).

 Change to the directory pub.

 If it does not yet exist: create directory www

Change to the directory www

Copy the file user.html or index.html from the PC to this directory.

 If

changed:

Power the controllere off and on again

NOTE

After switching on the controllere it is checked whether a file user.html or index.html exists. If yes, a link to this file is created.

If none of these both files exists, a link to a default page is created.

4-81

Function


4-82

Menu

Menu "Ethernet Setup"“

5 Menu

NOTE

In this manual the menu texts are all indicated in English.

Basic functions


5.1 Menu "Ethernet Setup"“

Quick setting of the Ethernet programming interface, reading of the parameter data (password level 1 required).

Menu tree Explanation

System Setup

Setup


► Menu selection with [▲] or [▼] and [OK]

► (Cancel with [ESC])

System Setup

Setup

IP

> Display of the current IP address

► Setting of the IP addess block by block with [▲] or [▼]

(only possible when DHCP = OFF)



System Setup

Setup

Subnet

System Setup

Ethernet

Address


► Setting of the subnet mask block by block [▲] or [▼]

(only possible when DHCP = OFF)



> Display of the current gateway address

► Setting of the gateway addess block by block with [▲] or

[▼]



System Setup

Setup

Baud

> Display of the current baud rate of the Ethernet interface

► Selection of the requested baud rate with [▲] or [▼]:

 100MBd duplex (default setting)

 100MBd

 10MBd

 10MBd



5-1

Menu

Menu "Ethernet Setup"“

Menu tree

System Setup

Setup

Negotiation

System Setup

System Setup

Setup

Setup

Setup

Explanation

> Display: automatic negotiation of the network connection parameters

► Selection: Use [▲] or [▼] to switch the function on or off.



> Display: assignment of the IP address by the host

► Selection: Use [▲] or [▼] to switch the function on or off.



> Display: manufacturer's identifier of the Ethernet interface

► Back with [ESC]

5-2

Operation

The Modbus command channel

6 Operation

6.1 The Modbus command channel

In the Modbus address space a command channel with a length of 19 words is defined for each AS-i master. A Modbus TCP client operates as host system.


Start End dec. hex. dec.

Contents

4794 12BA 4812 master 1 command channel request

4813 12CD 4831 master 1 command channel response

8890 22BA 8908 master 2 command channel request

8909 22CD 8927 master 2 command channel response

Access r=read w=write

r/w r r/w r

Size

[words]

19

19

19

19

The commands are always triggered by the host by means of a corresponding entry in his output data area. The controllere responds then in the input data area of the host system.

Request from host:

Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID command request reserved for string transfers command number

19 0#00

Response from controllere:

Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

reflected user ID reserved for string transfers command status reflected command number

19 0#00

NOTE

If a command is to be executed, the value 0#65 must be entered in the command request. Changing the command number does not start the execution. If a command is to be executed several times, the user ID must be changed accordingly, e.g. by counting up. Before starting a command it should be verified in the command status whether the previous command has been completed.

6-1

Operation


The command status indicates the status of the command channel:

0#65

0#6A

0#6B

0#6C

0#6D command request by the host command is being processed command aborted due to an error abort after timeout during command processing command completed, but response data not yet consistent

0#6F

6.1.1

Command number

Decimal Hexadecimal

0

1

0#00

0#01

4

5

6

7

9 command completed, response buffer is valid

Overview of the commands in the Modbus command channel

0#04

0#05

0#06

0#07

0#09

Description

no execution of a command write parameters to a connected AS-i slave change the list of the projected AS-i slaves (LPS) set the operating mode of the AS-i master readdress a connected AS-i slave set the auto addressing mode of the AS-i master change the extended ID code 1 in the connected AS-i slave

 page

6-4

6-5

6-7

6-9

6-11

6-12

6-14

6-15

6-17

6-24

21

33

34

35

0#15

0#21

0#22

0#23 read the ID string of an AS-i slave with profile S-7.4 read the diagnosis string of an AS-i slave with profile S-7.4 read the parameter string of an AS-i slave with profile S-7.4 write the parameter string of an AS-i slave with profile S-7.4 acyclic standard read call to an AS-i slave with CTT2 profile

36 0#24

– available from master profile M4 onwards - acyclic standard write call to an AS-i slave with CTT2 profile

37 0#25

- available from master profile M4 onwards - acyclic manufacturer-specific read call to an AS-i slave with

38 0#26

- available from master profile M4 onwards -

6-25

6-21

6-29

6-31

6-33

6-35

6-39

6-43

6-2

Operation


Command number


Description

acyclic manufacturer-specific read call to an AS-i slave with

CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)

- available from master profile M4 onwards -

 page

6-47

6-51

54

55

56

57

58

59

0#36

0#37

0#38

0#39

0#3A

0#3B read current parameters of a connected AS-i slave read current AS-i slaves lists read projected configuration of the AS-i slaves 1(A)...15(A) read projected configuration of the AS-i slaves 16(A)...31(A) read projected configuration of the AS-i slaves (0)1B...15B read projected configuration of the AS-i slaves 16B...31B

6-52

6-54

6-56

6-57

6-58

6-59

6-61

Syntax and examples (values in hexadecimal representation) on the following pages.

6-3

Operation


6.1.2 Command 0 (0#00): no execution of a command


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00

3…19 ignored command request = 0#65 command number = 0#00 ignored

Example:

1 0#0365 user ID changes to 0#03, command request with 0#65

2 0#0000 0#00 = command number 0


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID reserved

3…19 ignored command status = 0#6F reflected command number = 0#00 ignored

Example:

1 0#036F user ID changes to 0#03, command status is "completed" = 0#6F (no error)

2 0#0300 0#00 = reflected command number 0

6-4

Operation


6.1.3 Command 1 (0#01):

Write parameters to a connected AS-i slave


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command request = 0#65 command number = 0#01

3 ignored A/B AS-i slave address parameter value to be written

5…19 ignored

Legend:

A/B

Bit for addressing A or B slaves

Length: 1 bit

Permitted values: 0/1

Meaning:

0 = standard slave or A slave

1 = B slave (addition of 20 h

or 32 d

to the slave address)

Example:


2

3

4

0#0001

0#0024

0#0003

0#01 = command number 1 slave address 4B parameter value to be written

Response from controllere in the normal case:

Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID command status = 0#6F

0#00 reflected command number = 0#01 read back

4…17 ignored

18…19 reserved

Example:



3 0#0003 parameter value read back; might differ from the value to be written

6-5

Operation


Response from controllere in the case of an error:

Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID ignored

3 0#00 command status = 0#6B reflected command number = 0#01

Possible error codes:

0#01 NOK no slave response or master is in the offline mode when calling the command

0#0A

0#0B

0#14

NA

ID

IC slave is not in LAS parameter or address invalid master is not in the normal mode

Example:

1 0#096B user ID changes to 0#09,

0#6B = error during command execution


3 0#000A error code 0#0A

 slave is not in LAS

6-6

Operation


6.1.4 Command 3 (0#03):

Adopt and save currently connected AS-i slaves in the configuration


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID ignored command request = 0#65 command number = 0#03

3…19 ignored

Example:

1 0#0C65 user ID changes to 0#0C, command request with 0#65



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00 command status = 0#6F reflected command number = 0#03

3…19 ignored

Example:


6-7

Operation



Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command status = 0#6B reflected command number = 0#03

3 0#00

4…19 ignored


0#14 IC master is not in the normal mode

Example:


3 0#0014 error code 0#14

 master is not in the normal mode

6-8

Operation


6.1.5 Command 4 0#04):

List of the projected AS-i slaves (LPS)


Word no.

3

4

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


15(A) 14(A) 13(A) 12(A) 11(A) 10(A) 9(A) 8(A) 7(A) 6(A) 5(A) 4(A) 3(A) 2(A) 1(A) res


5

6

15B 14B 13B 12B 11B 10B 9B 8B 7B 6B 5B 4B 3B 2B 1B res


7…17 ignored

18…19 reserved

Example:

4

5

6


2

3

0#0004

0#003E

0#04 = command number 4 slaves 1 to 5 are to be projected

0#8000

0#0002

0#0001 slave 31(A) is to be projected slave 1B is to be projected slave 16B is to be projected


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


Example:



6-9

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00

3 ignored command status = 0#6B reflected command number = 0#04


0#14 IC master is not in the configuration mode

Example:




3 0#0014 error code 0#14

 master not in the configuration mode

6-10

Operation


6.1.6 Command 5 (0#05):

Set the operating mode of the AS-i master


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3 ignored

4…17 ignored

18…19 reserved

Example:



3 0#0001

0#00 = activate the protected operation

0#01 = activate the configuration mode


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


0#00 reflected command number = 0#05

Example:




Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00



0#03 SD0 slave with address 0 connected

Example:




3 0#0003 error code 0#03

 slave with address 0 connected

6-11

Operation


6.1.7 Command 6 (0#06):

Readdress a connected AS-i slave


Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 ignored command request = 0#65 command number = 0#06

A/B old slave address

5…17 ignored

18…19 reserved

Legend:

A/B


Length: 1 bit


Meaning:



or 32 d


Example:


2

3

4

0#0006

0#0029

0#000B

0#06 = command number 6 old slave address 9B new slave address 11A


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



Example:



6-12

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00




0#02

0#03

SND

SD0 no slave with the old address found slave with address 0 is connected

0#04

0#05

0#06

0#07

SD2

DE

RE

SE no slave with the new address found error when deleting the old address error when reading the IO configuration error when writing the new address or the extended ID code 1

0#08

0#09

0#0B

0#14

AT

ET

ID

IC new address could only temporarily be saved extended ID code 1 could only be saved temporarily parameter or address invalid master is not in the normal mode

Example:




3 0#0003 error code 0#03

 slave with address 0 connected

6-13

Operation


6.1.8 Command 7 (0#07):

Set the auto address mode of the AS-i master


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3 ignored

4…17 ignored

18…19 reserved

Example:



3 0#0001

0#00 = automatic addressing is deactivated

0#01 = automatic addressing is possible


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



Example:



6-14

Operation


6.1.9 Command 9 (0#09):

Change the extended ID code 1 in the connected AS-i slave


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


4 ignored new "extended ID code 1"

5…17 ignored

18…19 reserved

Legend:

A/B


Length: 1 bit


Meaning:



or 32 d


Example:

1 0#0F65 user ID changes to 0#0F, command request with 0#65

2

3

4

0#0009

0#0011

0#0008

0#09 = command number 9

0#11 = slave address 17(A) new "extended ID code 1" = 8


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



Example:

1 0#0F6F user ID changes to 0#0F, command status is "completed" = 0#6F (no error)


6-15

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00




0#02 SND no with the address found

0#03

0#07

0#09

SD0

SE

ET

0#0B IA slave with address 0 is connected error when writing the extended ID code 1 extended ID code 1 could only be saved temporarily address is invalid or: 2 slaves with address 0 detected

Example:

1 0#0F6B user ID changes to 0#0F,



3 0#0007 error code 0#07  slave does not support the extended ID code

6-16

Operation


6.1.10 Command 10...20 (0#0A...0#14):

Force analogue data transmission directly to / from 3 AS-i slaves in each case


Word no.

3

4

1

2

5

6

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command request = 0#65 command number = 0#0A…0#14 output data AS-i slave 1(A), channel 0 output data AS-i slave 1(A), channel 1 output data AS-i slave 1, channel 2 or output data AS-i slave 1B, channel 0 output data AS-i slave 1, channel 3 or output data AS-i slave 1B, channel 1

8

9

10

11

13

14

15

16 output data AS-i slave 2(A), channel 0 output data AS-i slave 2(A), channel 1 output data AS-i slave 2, channel 2 or output data AS-i slave 2B, channel 0 output data AS-i slave 2, channel 3 or output data AS-i slave 2B, channel 1 output data AS-i slave 3(A), channel 0 output data AS-i slave 3(A), channel 1 output data AS-i slave 3, channel 2 or output data AS-i slave 3B), channel 0 output data AS-i slave 3, channel 3 or output data AS-i slave 3B, channel 1

18…19 reserved

Legend:

V0…V3

O0...O3

Valid:

0 = data invalid

1 = data valid

Output data must be valid (V=1) to be enabled in the AS-i slave!

Overflow

0 = data is in the valid range

1 = data is in the invalid range

(especially in case of input modules when the measuring range is not reached or exceeded)

6-17

Operation


Example:


2

3

0#000A

0#0169

0#0A = command number 10 output data AS-i slave 1, channel 0

4

5

6

0#0202

0#0395

0#1033 output data AS-i slave 1, channel 1 output data AS-i slave 1, channel 2 output data AS-i slave 1, channel 3 overflow and valid bits for AS-i slave 1:

7 0#0055 55 h

= 0101 0101 b

O3 = 0, V3 = 1, O2 = 0, V2 = 1, O1 = 0, V1 = 1, O0 = 0, V0 = 1

8

9

10

11

0#2009

0#2202

0#0195

0#1022 output data AS-i slave 2, channel 0 output data AS-i slave 2, channel 1 output data AS-i slave 2, channel 2 output data AS-i slave 2, channel 3

12 0#0055 overflow and valid bits for AS-i slave 2:

55 h

= 0101 0101 b

O3 = 0, V3 = 1, O2 = 0, V2 = 1, O1 = 0, V1 = 1, O0 = 0, V0 = 1

13

14

0#3339

0#1102 output data AS-i slave 3, channel 0 output data AS-i slave 3, channel 1

15 0#1953 output data AS-i slave 3, channel 2



55 h

= 0101 0101 b

O3 = 0, V3 = 1, O2 = 0, V2 = 1, O1 = 0, V1 = 1, O0 = 0, V0 = 1

6-18

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1 user ID command status = 0#6F

2 0#00 reflected command number = 0#0A…0#14

3

4 input data or reflected output data AS-i slave 1(A), channel 0 input data or reflected output data AS-i slave 1(A), channel 1

5 input data or reflected output data AS-i slave 1, channel 2 or input data or reflected output data AS-i slave 1B, channel 0

6 input data or reflected output data AS-i slave 1, channel 3 or input data or reflected output data AS-i slave 1B, channel 1

TIB TOB TIA TOA TVB OVB TVA OVA O3 V3 O2 V2 O1 V1 O0 V0 7

8

9 input data or reflected output data AS-i slave 2(A), channel 0 input data or reflected output data AS-i slave 2(A), channel 1

10

11 input data or reflected output data AS-i slave 2, channel 2 or input data or reflected output data AS-i slave 2B, channel 0 input data or reflected output data AS-i slave 2, channel 3 or input data or reflected output data AS-i slave 2B, channel 1

12

13

14

TIB TOB TIA TOA TVB OVB TVA OVA O3 V3 O2 V2 O1 V1 O0 V0 input data or reflected output data AS-i slave 3(A), channel 0 input data or reflected output data AS-i slave 3(A), channel 1

15

16 input data or reflected output data AS-i slave 3, channel 2 or input data or reflected output data AS-i slave 3B, channel 0 input data or reflected output data AS-i slave 3, channel 3 or input data or reflected output data AS-i slave 3B, channel 1

TIB TOB TIA TOA TVB OVB TVA OVA O3 V3 O2 V2 O1 V1 O0 V0

17

Legend:

OVA

OVB

TVA

Channel-independent data valid flag of the A slave / standard slave:

1 = within max. 3 seconds the slave requests new data (CTT1) or: the slave has received new output values (CTT2...5)

0 = the last valid data transmission took place more than 3.5 s ago (TT1) or: the slave has not received new output values (CTT2...5)

Channel-independent data valid flag of the B slave (from master profile M4 onwards):

1 = slave has received new output values

0 = the slave has not received new output values

Note: valid only for reflected output data

Channel-independent transmission valid flag of the A slave / standard slave:

1 = analogue data transfer is running

0 = transmission error or timeout occurred

TVB

Channel-independent transmission valid flag of the B slave (from master profile M4 onwards):

1 = analogue data transfer is running

0 = transmission error or timeout occurred

Note: since this flag evaluates the data transmission cycle which was last connected, the response is delayed by up to 140 ms.

From master profile M4 onwards:

TIA 1 = slave sends input data as bit pattern (16-bit length, without sign)

TIB

TOA

TOB

0 = slave sends input data as value (15-bit length, with sign)

1 = slave receives output data as bit pattern (16-bit length, without sign)

0 = slave receives output data as value (15-bit length, with sign)

6-19

Operation


Command number


Slaves

14 0#0E 13 14 15

16 0#10 19 20 21

17 0#11 22 23 24

18 0#12 25 26 27

19 0#13 28 29 30

20 0#14 31 – –

Example:


4

5

2 0#000A 0#0A = reflected command number 10

3 0#3169 slave 1 is a 4-channel input slave: input data AS-i slave 1, channel 0

0#2202

0#1395 input data AS-i slave 1, channel 1 input data AS-i slave 1, channel 2

6 0#0033 input data AS-i slave 1, channel 3 overflow and valid bits for AS-i slave 1:

7 0#0255 0255 h

= 0000 0010 0101 0101 b

TVA = 1, OVA = 0, O3 = 0, V3 = 1, O2 = 0, V2 = 1, O1 = 0, V1 = 1, O0 = 0, V0 = 1

8 0#2229 slave 2 is a 2-channel input slave: input data AS-i slave 2, channel 0

9 0#2332 input data AS-i slave 2, channel 1

10

11

0#7FFF

0#7FFF no valid value for channel 2 no valid value for channel 3


0205 h

= 0000 0010 0000 0101 b

TVA = 1, OVA = 0, O3 = 0, V3 = 0, O2 = 0, V2 = 0, O1 = 0, V1 = 1, O0 = 0, V0 = 1

13 0#3339 slave 3 is a 4-channel input slave: output data AS-i slave 3, channel 0


15

16

0#1953

0#1234 output data AS-i slave 3, channel 2 output data AS-i slave 3, channel 3


0255 h

= 0000 0010 0101 0101 b

TVA = 1, OVA = 0, O3 = 0, V3 = 1, O2 = 0, V2 = 1, O1 = 0, V1 = 1, O0 = 0, V0 = 1

6-20

Operation


6.1.11 Command 21 (0#15):

Read the ID string of an AS-i slave with profile S-7.4


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 0 0 0 user ID

AS-i slave address command request = 0#65 command number = 21 (0#15)

3…19 ignored

Example:


2 0#0315 slave address = 3,


3

4

1

2

5

6


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

TG S

AS-i slave address

I/O 2D DT-Start DT-Count

F number of parameters to be read

EDT Write reserved device-specific information command status = 0#6F reflected command number = 0#15

Mux field

EDT Read

E type reserved diag reserved number of parameters to be written manufacturer identification

18 reserved number of bytes received

19 reserved

Legend:

S

TG

F

Mux field

Sequence bit

Length: 1 bit


Meaning:

0 = data transmission completed.

1 = data transmission not yet completed, at least one more packet follows.

Toggle

Length: 1 bit


Meaning:

1 = value changes for each execution of the command

Error bit

Length: 1 bit


Meaning:

0 = execution was error free

1 = an error occurred during execution, e.g. slave does not have the profile S-7.4

Number of multiplexed data words

Length: 3 bit

Permitted values: 0...3

Meaning:

number = Mux field + 1

6-21

Operation


E type

I/O

Number of parameters to be read

Number of parameters to be written

2D

DT-Start

DT-Count

EDT Read

EDT Write

Diag

Characterises the slave concerning functionality and data structure

Length: 5 bits


Meaning:

0 = reserved

1 = transmitted values are measured values

2 = transmitted values are 16 digital bit values

3 = normal operation in 4-bit mode (4E/4A)

4...31 = reserved

Direction of data for the devices with E type <> 3

Length: 1 bit


Meaning:

0 = input

1 = output

Number of bytes which can be read as parameter string

Length: 8 bits


Meaning:

0 = no parameter string readable

1...219 = number of bytes

Number of bytes which can be written as parameter string

Length: 8 bits

Permitted values: 0…219

Meaning:

0 = no parameter string readable

1…219 = number of bytes

Double data transfer possible (

 redundancy)

Length: 1 bit


Meaning: 0 = simple data transfer

Start triple (information for the driver in the master)

Number of data triples (information for the driver in the master)

Reserved for later profiles

Reserved for later profiles

Slave supports the 7.4 diagnosis string

Length: 1 bit


Meaning:

0 = diagnosis string is not supported

1 = diagnosis string is supported

Manufacturer identification

Device-specific information

Defined manufacturer number assigned by AS-International

As an option more bytes for the manufacturer-specific device description

Example:


2

0#0615 or

0#8615

06 h

= 00000110 b

 slave address = 3

0#15 = reflected command number 21 the most significant bit changes after each execution

3

4

0#2D01

0#0203

… …

17 0#0008

1st word of the ID string of slave 3

2nd word of the ID string of slave 3

… in this case the device sends an ID string of 8-byte length

6-22

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00



0#0C

0#0D

0#0E

0#0F faulty S-7.4 protocol sequence

S-7.4 protocol aborted (timeout) invalid AS-i slave address for the S-7.4 protocol (e.g. B slaves)

AS-i slave has completed the S-7.4 string

0#10

0#11

0#12

0#13

AS-i S-7.4 no longer connected (no longer in LAS) to this AS-i slave another S-7.4 transfer is already active previous segmented S-7.4 transfer not yet completed invalid S-7.4 data length

0#14 invalid command

Example:




3 0#0014 error code 0#14

 master is not in the normal mode

6-23

Operation


6.1.12 Command 28 (0#1C):

Deactivate the slave reset when changing to the protected mode


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command request = 0#65 command number = 28 (0#1C)

3 ignored with / without offline phase

4…19 ignored

Example:


2 0#001C 0#1C = command number 28

3 0#0001

0#00 = offline phase when changing to the protected mode

0#01 = no offline phase when changing to the protected mode


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



Example:


2 0#001C 0#1C = reflected command number 28

6-24

Operation


6.1.13 Command 31 (0#1F):

One-time execution of the "Extended Safety Monitor Protocol" in the "Safety at work" monitor


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command request = 0#65 command number = 31 (0#1F)

(1...31

10

)

4…17

18 field number (0#00 / 0#01) see sub command data length = 0#00

Example:


2 0#001F 0#1F = command number 31 sub command

3 0#001E 0#00 = one-time execution of the "Extended safety monitor protocol" in the "Safety at work" monitor with the address 30 (0#1E)


Word no.

3

4

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 sub command = 0#00

LEDs OSSD 2 LEDs OSSD 1

5 OSSD2 not green

6 1 st

colour output circuit 1

7 2 nd


8 3 rd


9 4 th


10 5 th


11 6 th


12 1 st


13 2 nd


14 3 rd


15 4 th


16 5 th


17 6 th


18 field number = 0/1

0 0 command status = 0#6F reflected command number = 0#1F

0 data call 1

AS-i slave address

OSSD1 not green

1 st

module address output circuit 1

2 nd


3 rd


4 th


5 th


6 th


1 st


2 nd


3 rd


4 th


5 th


6 th


0#00 data call 0

6-25

Operation


Description of the different fields:

Word no. 4:

LEDs OSSD 1 LEDs OSSD 2

15 14 13 12 11 10 9 8

0 0

0 0

0

0

0

1

0

0

0

0

0

0

Meaning

0 green: contacts of the output circuits closed

1 yellow: startup / restart disable active

data call 1

7 6 5 4

0

0

0

0

0

0

0

1

1

1

0

1

0

0

0

data call 0

3 2 1

0

0

0

0

1

1

Meaning

0

protective operation; everything OK

(output circuits which are not available, not configured or dependent are indicated as OK)

1 protective operation, output circuit 1 off

0 protective operation, output circuit 2 off

1 protective operation, both output circuits off

0 1 1 0 0 1 1 0 not reserved / not defined

Word no. 5:

OSSD2 not green OSSD1 not green

15..12 11 10...8 7…4 3 2...0

Meaning

reserved 0 0 reserved 0 0 no modules - responses of the data calls in the words 6..17 are not relevant reserved 0 1...6 reserved 0 1...6 number of modules which are not green reserved 0 7 reserved 0 7 more than 6 modules are not green

Word no. 6...17:

1st to 6th module address output circuit 1/2:

Indicates the index of the module of the configuration. The module address which was defined in the program ASIMON is indicated.

6-26

Operation


1st to 6th colour output circuit 1/2:

3 2 1 0 Meaning

0 1 0 0 continuous

0 1 0 1 flashing

Example („Safety at work“ monitor has not switched):


2 0#001F 0#1F = reflected command number 31

3 0#001E

0#00 = reflected sub command 0;

0#1E = AS-i slave address 30

4

5

6…17

18

0#0000

0#0000

0#xxxx

0#0100 green: contacts of the output circuits closed both output circuits green not relevant because 5th word = 0#0000 field number = 1

Example ("Safety at work" monitor has switched):



3 0#001E

0#00 = reflected sub command 0

0#1E = AS-i slave address 30

0#0xxx = output circuit 2 green

4 0#0211 0#x2xx = output circuit 1 red

0#xx11 = protective operation, output circuit 1 off (in both data calls)

5 0#0003 result from 4th word = OSSD2 green; OSSD1 not green

0#03 = delivers 3 modules which are not green

6 0#0421 module 33 (0#21) red, continuous (0#04)

7

8

0#0422

0#0423 module 34 (0#22) red, continuous (0#04) module 35 (0#23) red, continuous (0#04)

9…11 0#xxxx not relevant because low byte from 5th word = 0#03

 3 modules relevant

12…17 0#xxxx not relevant because high byte from 5th word = 0#00: green

 no module relevant

18 0#0100 field number = 1

6-27

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00

3 0#00 command status = 0#6B reflected command number = 0#1F


0#00…

0#02

0#0A…

0#-C general errors during command processing internal protocol error

0#11

0#16

0#20

0#EE no slave with the profile S-7.F.F on the slave address the protocol mode of the monitor at the address was changed it was not possible to process the command within the specified time fatal error during command execution

Example:

1 0#076B user ID changes to 0#07, error during command execution


3 0#0011 error code 0#11  no slave with the profile S-7.F.F

6-28

Operation


6.1.14 Command 33 (0#21):

Read the diagnosis string of an AS-i slave with profile S-7.4


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 reserved = 0 user ID


3…17 ignored

18 field number (0#00 / 0#01) number of bytes to be read

Example:


2 0#0321 slave address = 3(A),



Word no.

1

2

3

4…16

17

18

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG S user ID

AS-i slave address diagnosis string 1

F command status = 0#6F reflected command number = 0#21 diagnosis string 0 diagnosis string 29

0#00 diagnosis string 2...27 diagnosis string 28 number of bytes received

Legend:

S

TG

F

Sequence bit

Length: 1 bit


Meaning:

0 = data transmission completed


Toggle

Length: 1 bit


Meaning: value changes for each execution of the command

Error bit

Length: 1 bit


Meaning:


1 = an error occurred during execution, e.g.: slave has not the profile S-7.4

NOTE

The control bytes defined in profile 7.4 with follow byte and valid byte are filtered out by the system.

6-29

Operation


Example:

3

4


2

0#0621 or

0#8621

S = 0: last sequence,

06 h

= 00000110 b

 slave address = 3(A),

0#21= reflected command number 33

5

0#2D01

0#0203

0#1122 the most significant bit changes after each execution

1st word of the diagnosis data of slave 3(A)

2nd word of the diagnosis data of slave 3(A)

3rd word of the diagnosis data of slave 3(A)

6 0#3344

… …

18 0#0008

4th word of the diagnosis data of slave 3(A)

…

8 bytes diagnosis data

6-30

Operation


6.1.15 Command 34 (0#22):

Read the parameter string of an AS-i slave with profile S-7.4


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 reserved = 0 user ID


3…17 ignored

18 field number (0#00 / 0#01) number of bytes to be read

Example:


2 0#0322 slave address = 3,



Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG S user ID

AS-i slave address parameter string 1

F command status = 0#6F reflected command number = 0#22 parameter string 0

17

18

Legend: parameter string 29

0#00 parameter string 28 number of bytes received

S

TG

F

Sequence bit

Length: 1 bit


Meaning:



Toggle

Length: 1 bit



Error bit

Length: 1 bit


Meaning:



NOTE

The control bytes defined in profile 7.4 with follow byte and valid byte are filtered out by the system.

6-31

Operation


Example:


2

0#0622 or

0#8622

06 h

= 00000110 b



3

4

0#1234

0#5678

… …

18 0#0004

1st word of the parameter string of slave 3(A)

2nd word of the parameter string of slave 3(A)

…

4-byte parameter string was read

6-32

Operation


6.1.16 Command 35 (0#23):

Write parameter string of an AS-i slave with the profile S-7.4


Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

R S R user ID

AS-i slave address parameter string 1 command request = 0#65 command number = 35 (0#23) parameter string 0

17

18 parameter string 29 field number (0#00 / 0#01) parameter string 28 number of bytes to be sent

(rest is ignored)

Legend:

R

S

Reserved; in request = "0"

Sequence bit

Length: 1 bit


Meaning:



Example:


2 0#0323 slave address = 3(A),


3

4

0#1AF4

0#5BB8

1st word of the parameter string for slave 3(A)

2nd word of the parameter string for slave 3(A)

… …

18 0#0004

…

4-byte parameter string to be sent

6-33

Operation



Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG S user ID

AS-i slave address F

3...18 0#00 command status = 0#6F reflected command number = 0#23

0#00

Legend:

S

TG

F

Sequence bit

Length: 1 bit


Meaning:



Toggle

Length: 1 bit



Error bit

Length: 1 bit


Meaning:



NOTE

The number of the bytes to be sent must be divisible by 2 since the system always transmits only multiples of 2 bytes in the S7.4 protocol.

The control bytes defined in profile 7.4 with follow bit and valid bit are automatically added by the system. Therefore, without segmentation, this command is limited to 20 bytes of parameter data.

Larger data volumes must be divided into segments.

Example:


2

0#0623 or

0#8623 x6 h

= xx000110 b



6-34

Operation


6.1.17 Command 36 (0#24):

Acyclic standard read call to an AS-i slave with CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)

– available from master profile M4 onwards –


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2

3

0 0 A/B user ID

AS-i slave address number of bytes to be read command request = 0#65 command number = 36 (0#24)

Index

4…17 ignored

18…19 reserved

Legend:

A/B

Index

Number of bytes to be read


Length: 1 bit


Meaning:

0 = A slave


or 32 d


Pointer to the page to be read

Length: 1 byte


Meaning:

 data sheet of the addressed CTT2 slaves


Length: 1 byte


Meaning:


Example:


2 0#0324

0#03 = slave address 3(A),


3 0#0409 in index 9, 4 parameter bytes are to be read

6-35

Operation



Word no.

1

2

3

4…16

17

18

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG L32 user ID reserved parameter byte 0

F=0 command status = 0#6F reflected command number = 0#24 parameter byte 1 parameter byte 28 parameter byte 30 or number of bytes read parameter bytes 2...27 parameter byte 29 parameter byte 31

Legend:

L32

TG

F

Number of parameter bytes = 32

Length: 1 bit


Meaning:

0 = number of bytes to be sent <32

1 = number of bytes to be sent =32

Toggle

Length: 1 bit



Error bit

Length: 1 bit


Meaning:


1 = an error occurred during execution

NOTE

The high byte in the 18th word contains the number of the parameter bytes read as long as the number is <32 (L32 = 0).

If the length is 32 (= maximum possible length), the bit L32 is set and the high byte in the 18th word contains the 32nd parameter byte.

Example:


2

0#0024 or

0#8024

0#00 / 0#80

 L32 =  net length <


3

4

5…17

18

0#1234

0#5678

0#0000

0#0400

1st and 2nd parameter byte from index 9 in slave 3(A)

3rd and 4th parameter byte from index 9 in slave 3(A) invalid / not used


6-36

Operation


Response from controllerein the case of an error (error detected by AS-i master):

Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 TG user ID reserved


Legend:

TG

Toggle

Length: 1 bit




0#16

0#17 timeout during command processing wrong slave profile or slave not in LAS or master not in the normal mode

0#E0...

0#EF

0#F0

0#F1

0#F2 error detected by AS-i slave; see error code CTT2 (see below) invalid CTT2 command invalid CTT2 response

7.5 data length longer than 30 bytes

Example:



2

0#0024 or

0#8024 reflected command number = 0#24 the most significant bit changes after each execution

3 0#0016 error code 0#16  timeout during command processing

6-37

Operation


Response from controllere in the case of an error (error detected by AS-i slave):

Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG 0 user ID reserved

CTT2 error code

F=1 command status = 0#6B reflected command number = 0#24 error code = 0#E1

Legend: :

TG

F

Toggle

Length: 1 bit


Meaning: 1 = value changes for each execution of the command

Error bit

Length: 1 bit


Meaning:



Possible CTT2 error codes:

0#03

0#04

0#05 command not implemented used; it was not possible to complete the command in the specified time command was not acknowledged

Example:



2

0#0124 or

0#8124

0#x1 = error during command execution


6-38

Operation


6.1.18 Command 37 (0#25):

Acyclic standard write call for an AS-i slave with CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)



3

4

1

2

Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 0 A/B user ID

AS-i slave address number of bytes to be sent parameter byte 0 command request = 0#65 command number = 37 (0#25) index parameter byte 1

5…17

18 parameter byte 28 parameter bytes 2...27 parameter byte 29

19 reserved

Legend:

A/B

Index

number of bytes to be sent


Length: 1 bit


Meaning:

0 = A slave


or 32 d



Length: 1 byte


Meaning:


Number of bytes to be sent

Length: 1 byte


Meaning:


Example:


2 0#0325



3

4

0#0207

0#1AF4 in index 7, 2 parameter bytes are to be written both parameter bytes for slave 3(A)

6-39

Operation



Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG 0 user ID reserved F=0 command status = 0#6F reflected command number = 0#25

Legend:

TG

F

Toggle

Length: 1 bit



Error bit

Length: 1 bit


Meaning:



Example:


2

0#0025 or

0#8025


6-40

Operation


Response from controllere in the case of an error (error detected by AS-i master):

Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1




0#16


0#E...

0#EF

0#F0

0#F1



Example:



2

0#0025 or

0#8025


3 0#0016 error code 0#16

 timeout during command processing

6-41

Operation



Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


CTT2 error code



0#03

0#04


Example:



2

0#0125 or

0#8125



6-42

Operation


6.1.19 Command 38 (0#26):

Acyclic manufacturer-specific read call to an AS-i slave with CTT2 profile (S-

7.5.5, S-.7.A.5 or S-B.A.5)



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2

3 reserved = 0

A/B user ID

AS-i slave address number of bytes to be read command request = 0#65 command number = 38 (0#26)

Index

4…17 ignored

18…19 reserved

Legend:

A/B

Index



Length: 1 bit


Meaning:

0 = A slave


or 32 d



Length: 1 byte


Meaning:



Length: 1 byte


Meaning:


Example:


2 0#0326



3 0#0409 in index 9, 4 parameter bytes are to be read

6-43

Operation



Word no.

1

2

3

4…16

17

18

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG L32 user ID reserved parameter byte 0

F=0 command status = 0#6F reflected command number = 0#26 parameter byte 1 parameter byte 28 parameter byte 30 or number of bytes read parameter bytes 2...27 parameter byte 29 parameter byte 31

Legend:

L32

TG

F

Number of parameter bytes = 32

Length: 1 bit


Meaning:

0 = number of bytes to be sent <32

1 = number of bytes to be sent =32

Toggle

Length: 1 bit



Error bit

Length: 1 bit


Meaning:



NOTE

The high byte in the 18th word contains the number of the parameter bytes read as long as the number is <32 (L32 = 0).

If the length is 32 (= maximum possible length), the bit L32 is set and the high byte in the 18th word contains the 32nd parameter byte.

Example:


2

0#0026 or

0#8026

0#0x / 0#8x

 L32 =  number of parameter bytes <32


3

4

5…17

18

0#1234

0#5678

0#0000

0#0400

1st and 2nd parameter byte from index 9 in slave 4

3rd and 4th parameter byte of index 9 in slave 4 invalid / not used


6-44

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1




0#16


0#E0...

0#EF

0#F0

0#F1



Example:



2

0#0026 or

0#8026


3 0#0016 error code 0#16


6-45

Operation



Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


CTT2 error code



0#03

0#04


Example:



2

0#0126 or

0#8126

0#x1 = error during command execution reflected command number = 0#26 the most significant bit changes after each execution

6-46

Operation


6.1.20 Command 39 (0#27):

Acyclic standard manufacturer-specific write call to an AS-i slave with CTT2 profile (S-7.5.5, S-7.A.5 or S-B.A.5)



3

4

1

2

Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 0 A/B user ID

AS-i slave address number of bytes to be sent parameter byte 0 command request = 0#65 command number = 39 (0#27) index parameter byte 1

5…17

18 parameter byte 28 parameter bytes 2…27 parameter byte 29

19 reserved

Legend:

A/B

Index



Length: 1 bit


Meaning:

0 = A slave


or 32 d



Length: 1 byte


Meaning:



Length: 1 byte


Meaning:


Example:


2 0#0327



3

4

0#0207

0#1AF4 in index 7, 2 parameter bytes are to be written both parameter bytes for slave 3(A)

6-47

Operation



Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

TG 0 user ID reserved F=0 command status = 0#6F reflected command number = 0#27

Legend:

TG

F

Toggle

Length: 1 bit


Meaning: value changes for each command execution

Error bit

Length: 1 bit


Meaning:



Example:


2

0#0027 or

0#8027


6-48

Operation



Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1




0#16


0#E0...

0#EF

0#F0

0#F1

0#F2 error detected by AS-i slave; note error code CTT2 (see below) invalid CTT2 command invalid CTT2 response


Example:



2

0#0027 or

0#8027


3 0#0016 error code 0#16


6-49

Operation



Word no.

1

2

3

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


CTT2 error code



0#03

0#04


Example:



2

0#0127 or

0#8127


0#27 = reflected command number the most significant bit changes after each execution

6-50

Operation


6.1.21 Command 50 (0#32):

Read current configuration of AS-i slaves 0(A)...15(A)


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command request = 0#65 command number = 50 (0#32)

3…17 ignored

18…19 reserved

Example:


2 0#0032 0#32 = command number 50


Word no.

3

4

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command status = 0#6F reflected command number = 0#32 slave0, ID2 slave1(A), ID2 slave0, ID1 slave 1 (A), ID1 slave0, ID code slave 0, IO conf. slave 1(A), ID code slave 1(A), IO conf.

18 slave15(A), ID2 slave15(A), ID1 slave15(A), ID code slave15(A), IO conf.

Example:



4 0#EF03 current configuration of slave 1(A)

ID2 =E, ID1=F, ID=0 and IO=3

… … …

18 0#EF37 current configuration of slave 15(A):


Command 51 (0#33): read current configuration AS-i slaves 16(A)....31(A)

Command 52 (0#34): read current configuration of AS-i slaves (0)1B...15B

Command 53 (0#35): read current configuration of AS-i slaves 16B...31B

 Command 50 (0#32)

6-51

Operation


11

12

13

14

7

8

9

10

15

16

17

18

6.1.22 Command 54 (0#36):

Read current parameters of a connected AS-i slave


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3…17 ignored

18…19 reserved

Example:


2 0#0036 0#36 = command number 54


Word no.

3

4

1

2

5

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command status = 0#6F reflected command number = 0#36 param. slave4(A) param. slave8(A) param. slave3(A) param. slave7(A) param. slave2(A) param. slave6(A) param. slave1(A) param. slave5(A) param. slave12(A) param. slave11(A) param. slave10(A) param. slave9(A)

6 param. slave16(A) param. slave15(A) param. slave14(A) param. slave13(A) param. slave20(A) param. slave19(A) param. slave18(A) param. slave17(A) param. slave24(A) param. slave23(A) param. slave22(A) param. slave21(A) param. slave28(A) param. slave27(A) param. slave26(A) param. slave25(A) param. slave1B param. slave31(A) param. slave30(A) param. slave29(A) param. slave5B param. slave9B param. slave13B param. slave17B param. slave4B param. slave8B param. slave12B param. slave16B param. slave3B param. slave7B param. slave11B param. slave15B param. slave2B param. slave6B param. slave10B param. slave14B param. slave21B param. slave25B param. slave29B not used param. slave20B param. slave24B param. slave28B not used param. slave19B param. slave23B param. slave27B param. slave31B param. slave18B param. slave22B param. slave26B param. slave30B

6-52

Operation


Example:


2

3

0#0036

0#4321

0#36 = reflected command number 54 parameters of slave 1 [value = 1] to slave 4 [value = 4]

4 0#8765 parameters of slave 5 [value = 5] to slave 8 [value = 8]

… … … slave 29(A) [value = 3],

9 0#6543 slave 30(A) [value = 4], slave 31(A) [value = 5], slave 1B [value = 6]

… …

17 0#FE98

18 0#0098

… parameters of slave 26B [value = 8] to slave 29B [value = F] parameters of slave 30B [value = 8] and slave 31B [value = 9 ]

6-53

Operation


6.1.23 Command 55 (0#37):

Read current AS-i slaves


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3…17 ignored

18…19 reserved

Example:


2 0#0037 0#37 = command number 55


Word no.

Bit

–– 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID


3

4

5

6

15A 14A 13A 12A 11A 10A 9A 8A 7A 6A 5A 4A 3A 2A 1A –

LAS

31A 30A 29A 28A 27A 26A 25A 24A 23A 22A 21A 20A 19A 18A 17A 16A

15B 14B 13B 12B 11B 10B 9B 8B 7B 6B 5B 4B 3B 2B 1B –

7

8

9

10


15A 14A 13A 12A 11A 10A 9A 8A 7A 6A 5A 4A 3A 2A 1A 0

LDS



11

12

13

14



LPF



15

16

17

18



LPS




6-54

Operation


Example:



LAS slaves 1(A) to 15(A):

3 0#0102 0102 h

= 0000 0001 0000 0010 b slaves 1 and 8 are active

LAS slaves 16(A) to 31(A):

4 0#8001 8001 h

= 1000 0000 0000 0001 b slaves 16(A) and 31(A) are active

LAS slaves 1B to 15B:

5 0#0102 0102 h

= 0000 0001 0000 0010 b slaves 1B and 8B are active

LAS slaves 16B to 31B:

6 0#8001 8001 h

= 1000 0000 0000 0001 b slaves 16B and 31B are active

7 0#0102

LDS slaves 0 to 15(A):

0102 h

= 0000 0001 0000 0010 b slaves 1(A) and 8(A) are detected

LDS slaves 16(A) to 31(A):

8 0#8001 8001 h

= 1000 0000 0000 0001 b slaves 16(A) and 31(A) are detected

LDS slaves 1B to 15B:

9 0#0102 0102 h

= 0000 0001 0000 0010 b slaves 1B and 8B are detected

10 0#8001

LDS slaves 16B to 31B:

8001 h

= 1000 0000 0000 0001 b slaves 16B and 31B are detected

11 0#0100

LPF slaves 0 to 15(A):

0100 h

= 0000 0001 0000 0000 b peripheral fault on slave 8(A) signalled

12 0#0001

LPF slaves 16(A) to 31(A): peripheral fault on slave 16(A) signalled

13 0#0002

LPF slaves 1B to 15B: peripheral fault on slave 1B signalled

14 0#8000

LPF slaves 16B to 31B:

8000 h

= 1000 0000 0000 0000 b peripheral fault on slave 31B signalled

15 0#0102

LPS slaves 1(A) to 15(A):

0102 h

= 0000 0001 0000 0010 b slaves 1(A) and 8(A) are projected

16 0#8001

LPS slaves 16(A) to 31(A):

8001 h

= 1000 0000 0000 0001 b slaves 16(A) and 31(A) are projected

17 0#0102

LPS slaves 1B to 15B:

0102 h

= 0000 0001 0000 0010 b slaves 1B and 8B are projected

18 0#8001

LPS slaves 16B to 31B:

8001 h

= 1000 0000 0000 0001 b slaves 16B and 31B are projected

6-55

Operation


6.1.24 Command 56 (0#38):

Read projected configuration of the AS-i slaves 1(A)...15(A)


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3…17 ignored

18…19 reserved

Example:


2 0#0038 0#38 = command number 56


Word no.

3

4

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 command status = 0#6F reflected command number = 0#38 slave0, ID2 slave1(A), ID2 slave0, ID1 slave 1 (A), ID1 slave 0, ID code slave 0, IO conf. slave 1(A), ID code slave 1(A), IO conf.

18 slave15(A), ID2 slave15(A), ID1 slave15(A), ID code slave15(A), IO conf.

Example:



3 0#FFFF here not used since slave 0 cannot be projected

4 0#EF03 projected configuration for slave 1(A):


… … …

18 0#EF37 projected configuration for slave 15(A):


Command 57 (0#39): read projected configuration of the AS-i slaves 16(A)...31(A)

Command 58 (0#3A): read projected configuration of the AS-i slaves (0)1B...15B

Command 59 (0#3B): read projected configuration of the AS-i slaves 16B...31B

 Command 56 (0#38)

6-56

Operation


6.1.25 Command 96 (0#60):

Save data non-volatilely in the flash memory of the controllere


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3 0#00

4…19 ignored

Example:


2 0#0060 0#60 = command number 96 area number

3 0#0002 0#02 = non-volatilely save the configuration of AS-i master 1

0#03 = non-volatilely save the configuration of AS-i master 2


Word no.

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

1

2 user ID

0#00

3 0#00 command status = 0#6F reflected command number = 0#60

Example:



3 0#0002 reflected area number

0#02 = non-volatilely save the configuration of AS-i master 1

6-57

Operation


6.1.26 Command 97 (0#61):

Carry out various settings in the controllere


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00

3 0#00 command request = 0#65 command number = 97 (0#61)

Example:


2 0#0061 0#61 = command number 97 command number:

0#10 = changes the operating mode of the PLC (corresponding parameters

 word 4)

3 0#0010 further command numbers:

0#12 = reset all slave error counters

0#13 = reset the configuration error counter

0#14 = reset AS-i cycle error counter parameters, here for command number 0#10:

4 0#0002

0#0000 = activates the gateway mode

0#0001 = stops the PLC

0#0002 = sets the operation mode of the PLC to RUN


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00

3...18 0#00 command status = 0#6F reflected command number = 0#61

0#00

Example:



6-58

Operation


6.1.27 Command 102 (0#66):

Retrieve the status of the controllere display


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3 0#00

4…n parameter(s) (according to command number)

Example:


2 0#0066 0#66 = command number 102 command number, here:

0#01 = enquires the display status

3 0#0001 further command numbers:

0#02 = change to menu screen 0

0#03 = change to user menu screen 0#A1


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3 0#00 reflected command number here: 0#01

7

8

5

6 activated menu area process error occurred currently displayed menu screen activated system language

9…18 reserved

Legend:

0#0001

Buttons pressed

Active menu area

Process

0#0008

0#00A0

0#00A1

0#00AE

0#00AF

0#0000 left button pressed right button is pressed system menu is active user menu is active process error display is active (E10...E30) system error display is active (acknowledgement required) no process error

6-59

Operation

The Modbus command channel error occurred

Currently displayed menu screen

Activated system language

0#xxxx

0#0000

0#0001 number of the current menu screen display of menus in English display of menus in the second system language (e.g. German)

Example:


4

5

2

3

0#0066

0#0001

0#0008

0#00A0

0#66 = reflected command number 102

0#01 = reflected command number right button is pressed system menu is active

7

8

0#001B

0#0000 menu screen 27 "Quick Setup" is displayed display of menus in English

6-60

Operation


6.1.28 Command 105 (0#69):

Read the device properties of the controllere


Word no.

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID


3…17 ignored

18…19 reserved

Example:


2 0#0069 0#69 = command number 105


Word no.

4

5

1

2

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

user ID

0#00 reserved command status = 0#6F reflected command number = 0#69

0#00

0#00 fieldbus type flash memory type

7

8

9

10

11

12

RTS firmware version number

RTS firmware release number

AS-i master 1 firmware version number

AS-i master 1 firmware release number

AS-i master 2 firmware version number

AS-i master 2 firmware release number

14 Linux ramdisk version

15…18 0#00

Legend:

2M

DP

EN

0

1

0

1

0

1 device with 1 AS-i master device with 2 AS-i master fieldbus interface Profibus DP(V1) not available fieldbus interface Profibus DP is available device without Ethernet programming interface device with Ethernet programming interface

6-61

Operation


PLC mode

0#01

0#02

0#04

PLC is in the RUN mode

PLC is in the STOP mode

PLC stops at the breakpoint fieldbus type

0#0B

0#0C ifm Profibus DP no fieldbus module detected

Example:



40 h

= 0100 0000 b

2M = 0

 with one AS-i master,

3 0#4008 DP = 1

 Profibus DP controllere

EN = 0

 without Ethernet programming interface,

PLC mode 0#08 = gateway; signal preprocessing is not used

5 0#0002 flash memory type

7 0#0002

1st part of the RTS firmware number 02.218B:

RTS firmware version number = 02

8 0#218B

2nd part of the RTS firmware number 02.218B:

RTS firmware release number = 218B

9 0#0000

1st part of the firmware number 0.238A for AS-i master 1:

AS-i master 1 firmware version number = 0

10 0#238A

2nd part of the firmware number 0.238A for AS-i master 1:

AS-i master 1 firmware release number = 238A

11 0#0000

1st part of the firmware number 0.238A for AS-i master 2:

AS-i master 2 firmware version number = 0

12 0#238A

2nd part of the firmware number 0.238A for AS-i master 2:

AS-i master 2 firmware release number = 238A

13 0#0196

Linux kernel version:

406 d

= 0#0196

14 0#0A6E

Linux ramdisk version:

10.110

d

= 0#0A.0#6E

6-62

Terms, abbreviations

A/B slave

Address

Slave with an A or B being appended to its address number and which may therefore be present twice on the

master.

This is the "name" of the bus participant. All participants need a unique defined address so that the signals can be exchanged without problem.

Bus system for the first binary field level.

Auto-negotiation Auto-negotiation designates a procedure which allows network cards or host bus adapters to independently detect the correct transmission speed and the duplex mode of the network interface to which they are connected, and to configure themselves accordingly.

Baud Baud, abbrev.: Bd = unit for the data transmission speed. Do not confuse baud with "bits per second" (bps, bits/s). Baud indicates the number of changes of state (steps, cycles) per second over a transmission length. But it is not defined how many bits per step are transmitted. The name baud can be traced back to the French inventor J. M. Baudot whose code was used for telex machines.

1 MBd = 1024 x 1024 Bd = 1 048 576 Bd

Bus Serial data transmission of several participants on the same cable.

COB ID

CoDeSys

® controllere

Cycle time

DeviceNet

CAN is a priority controlled fieldbus system for larger data volumes. It is available in different variants, e.g. CANopen, CAN in Automation (CiA) or

DeviceNet.

CAN can be used e.g. as a supplier for AS-i over larger distances.

Corresponding

gateways are available.

COB = Communication Object

ID = Identifier

Each communication object has a unique COB ID in the network. The COB ID consists of 32-bit values; the first two bits have each an object-specific meaning.

CoDeSys for Automation Alliance associates companies of the automation industry whose hardware devices are all programmed with the widely used IEC

61131-3 development tool CoDeSys®.

CoDeSys

®

is a registered trademark of 3S – Smart Software Solutions GmbH,

Germany

 http://www.3s-software.com

Master in the AS-i bus system of the generation E

This is the time for a cycle. The following process happens:

 PLC cycle: the PLC program performs one complete run.

 AS-i cycle: all AS-i slaves are updated (5...10 ms).

Fieldbus system for larger data volumes based on

CAN technology, requires special cables, complex connection technology. Can be used e.g. as a supplier for AS-i over longer distances. Corresponding


7-1


= configuration by the

host

DHCP is a protocol which offers the dynamic configuration of IP addresses and thus coherent information. The protocol supports the further use of IP-addresses which are only available in a limited number by a centralised management of the address assignment.

At first power on of a participant in a network the participant logs on a server using this service. The server assigns a local free

IP address to the participant.

Ethernet

Fieldbus

Firmware

According to the EC directive (89/336 EEC) concerning electromagnetic compatibility (in short EMC directive) requirements are made for electrical and electronic apparatus, equipment, systems or components to operate satisfactorily in the existing electromagnetic environment. The devices must not interfere with their environment and must not be adversely influenced by external electromagnetic interference.

Ethernet is a widely used, manufacturer-independent technology which enables data transmission in the network at a speed of 10 or 100 million bits per second

(Mbps). Ethernet belongs to the family of so-called "optimum data transmission" on a non exclusive transmission medium. The concept was developed in 1972 and specified as IEEE 802.3 in 1985.

Functional earth is a reference potential which is not connected to protective earth or only connected when special measures are taken. The functional earth serves as equalisation of potential for an ungrounded installation (e.g.

SELV).

A

bus for industrial applications: mechanically extremely robust and excellent data protection

Basic program in the device, virtually the operating system

The firmware establishes the connection between the hardware of the device and the user software.

GSD

Host

IP address

Gateways enable connection of completely different systems. Gateways are used when two incompatible network types are to be connected by converting the protocol of one system to the protocol of the other system.

Here: connection between AS-i and higher-level fieldbus systems such as

Profibus-DP, DeviceNet, Interbus-S or other interfaces, e.g. RS-485. The device includes an AS-i master which is directly coupled to the

host interface

(e.g.

Profibus-DP slave).

Device master file

Describes the interface to the device to be connected to the fieldbus. File

 www.ifm.com

> Select country/language > [Service] > [Download] > [Bus system AS-Interface]

The controller in the hierarchy above the AS-i master, e.g. a PLC or a processor.

Name to differentiate the devices / participants connected to a system.

IP = Internet Protocol

The IP address is a number which is necessary to clearly identify an internet participant. For the sake of clarity the number is written in 4 decimal values, e.g.

127.215.205.156.

7-2


Jitter

LAS

LDS

By jitter is understood a slight fluctuation in accuracy in the transmission cycle when transmitting digital signals.

In general jitter is an abrupt and undesired change of the signal characteristics in transmission technology.

List of Active Slaves

In this slave list the controllere enters the slaves detected as active for this AS-i master.

List of Detected Slaves

In this slave list the controllere enters the slaves detected as present for this

AS-i master.

LFS

LPS

Light emitting diode, also called luminescent diode, an electronic element of high coloured luminosity at small volume with negligible power loss.

List of Failed Slaves

In this slave list the controllere enters the slaves with a configuration error on this

AS-i master.

List of Projected Slaves

In this slave list the controllere enters the slaves projected for this AS-i master.

MAC ID

Master

Master-slave communication

MBd

MAC = Manufacturer‘s Address Code

ID = Identifier

Every network card has a MAC address, a clearly defined worldwide unique numerical code, more or less a kind of serial number. Such a MAC address is a sequence of 6 hexadecimal numbers, e.g. "00-0C-0E-D0-02-3F".

Handles the complete organisation on the bus. The master decides on the bus access time and polls the

slaves cyclically.

AS-i strictly operates to the master-slave principle. The master polls all slaves one after the other in always the same order. Only one master per network line is allowed (

cyclical polling).

Baud

Modbus

The Modbus protocol is a communication protocol based on a

master/slave architecture and was generated by Modicon* in 1979 for communication with its

PLCs. In industry Modbus is the de-facto standard.

Modbus/TCP is based on

Ethernet-TCP/IP. Modbus/TCP ports the protocol defined for the serial interface to TCP. The

IP address clearly defines every device in a network. Therefore the slave address was used to identify one of several logical units (unit IDs) in a physical device. To do so, extended IP addressing is used.

Example: 192.168.83.28.1 means unit ID 1 on IP address 192.168.83.28.

*) Modicon passed from AEG to the group Schneider in 1994.

Operating system Basic program in the device, establishes the connection between the hardware of the device and the user software.

=

= output signal of a switching device, here: output signal of an AS-i safety monitor

7-3


Password In the menu [System Setup] in the menu item [Password] the operation can be restricted or enabled. When delivered, the device is in the user mode. By entering an invalid password (e.g. 1000) all menu items which can change settings are blocked.


Pictograms

Polling

Profibus

Profibus DP

Profibus PA

Profibus-FMS

Functional extra low voltage with safe separation, grounded variant of SELV.

Extra low voltage with safe separation (grounded variant of SELV). The specification as PELV system to IEC364-4-41 (initially DIN VDE 0100-410:1997-

01) covers a measure to protect against direct and indirect contact with dangerous voltages by a "safe separation" between primary and secondary side in the device (e.g. power supply to PELV specification).

For this reason no separate PE conductor is required in a PELV system. It is allowed to ground circuits and / or bodies in a PELV system.

Image symbols which convey information by a simplified graphic representation.

 page

1-1 chapter: What do the symbols and formats stand for?

to poll = to count votes

The controller master fetches the data from every participant in the system successively:

1. Master calls participant 1

2. Participant 1 replies with its current data (actual values)

3. Master transmits more data (preset values) to participant 1 if needed

4. Participant 1 acknowledges receipt of the data etc., the same procedure for all other participants.

Cyclical polling: AS-i master cyclically polls the data of all

slaves in the bus

(see above). The data is updated in the

master after max. 5 ms. If A/B slaves are used, the

cycle time can be 10 ms.

Fieldbus system for larger data volumes, it requires special cables, complex connection technology. It is available in different variants as Profibus FMS, DP or

PA. The Profibus DP can be used as a supplier for AS-i over longer distances.

Corresponding


 http://www.profibus.com/

Profibus DP (Decentralised Periphery) to trigger sensors and actuators by a central controller in production technology. In particular the numerous standard diagnostic options are important. More applications are the connection of

"distributed intelligence", i.e. networking of several controllers among each

(similar to

Profibus FMS). Data rates up to 12 Mbits/s on twisted two-wire cables and/or fibre optics are possible.

Profibus PA (Process-Automation) is used to control field devices by means of a process control system in process technology. This Profibus variant is suitable for hazardous areas (zones 0 and 1). Only a small current flows on the bus cables in an intrinsically safe circuit so that even in case of a problem no sparks are produced. The disadvantage of this variant is the slower data transmission rate.

Profibus FMS (Fieldbus Message Specification) to network controllers – no longer standardised as from 2007

7-4


Remanent Remanent data is protected against data loss in case of power failure.

The operating system for example automatically copies the remanent data to a flash memory as soon as the voltage supply falls below a critical value. If the voltage supply is available again, the

operating system loads the remanent data back to the RAM memory.

The data in the RAM memory of a controller, however, is volatile and normally lost in case of power failure.

Run time systems are basic versions of applications. These minimum versions are supplied with certain products to meet the prerequisites for the execution of the actual product or to be able to look at or use results generated by this product on other processors: making available all routines required to execute a program in a programming language, e.g. interactions with the

operating system, memory requirements, error routines, inputs and outputs.

Run time system RTS

Single slave

Slave

Target

Unit ID

Watchdog

Active parts integrated in SELV circuits must not be connected to ground or protective conductors of other circuits. They must be safely separated from live parts of higher voltage.

SELV circuit = secondary circuit (output voltage) which is rated and protected so that its voltages do not exceed a safe value in case of correct operation (of the power supply) or in case of a single fault (of the power supply).

SELV circuits are separated from the input voltage (mains voltage) by double or enhanced insulation. The voltage value must not exceed 60 V DC (or 42.4 V

AC).

Slave whose address number may only occur once on the master.

Passive participant on the bus, only replies on request of the

master. Slaves have a clearly defined and unique

address in the bus. A distinction is made between:

 single slaves whose address numbers may only occur once on the master and

 A / B slaves with an A or B being appended to its address number which may therefore be present twice on the master.

The target indicates the target system where the PLC program is to run. The target contains the files (drivers) required for programming and parameter setting.

UDP is a minimal connectionless network protocol belonging to the transport layer of the internet protocol family. The task of UDP is to ensure that data which is transmitted via the internet is passed to the right application.

Modbus

In general the term watchdog is used for a component of a system which watches the function of other components. If a possible malfunction is detected, this is either signalled or suitable program branchings are activated. The signal or branchings serve as a trigger for other co-operating system components to solve the problem.

7-5


7-6

Index

8 Index

nn-n The indication of the page where you can find some information about the keyword is written in normal characters.

ii-i

The indication of the page where the keyword is detailed is written in italics.

A/B slave ............................................................. 7-1

Abbreviations....................................................... 7-1

Address ............................................................... 7-1

AS-i...................................................................... 7-1

Auto-negotiation .................................................. 7-1

Baud .................................................................... 7-1

Bus ...................................................................... 7-1

CAN..................................................................... 7-1

COB ID ....................................................... 4-29, 7-1

Command channel .............................................. 6-1 controllere............................................................ 7-1

Cycle time............................................................ 7-1

DeviceNet ............................................................ 7-1

DHCP .................................................................. 7-2

EMC .................................................................... 7-2

Ethernet........................................................ 4-1, 7-2

Ethernet Setup.................................................... 5-1

FE........................................................................ 7-2

Fieldbus............................................................... 7-2

Firmware ...................................................... 1-2, 7-2

Functional earth................................................... 7-2

Gateway .............................................................. 7-2

GSD..................................................................... 7-2

Host ..................................................................... 7-2

HTML data exchange ........................................ 4-74

ID ........................................................................ 7-2

IP address ........................................................... 7-2

Jitter..................................................................... 7-3

LAS...................................................................... 7-3

LDS ..................................................................... 7-3

LED ..................................................................... 7-3

LFS...................................................................... 7-3

LPS...................................................................... 7-3

MAC ID................................................................ 7-3

Main menu........................................................... 5-1

Master ................................................................. 7-3

Master-slave principle ......................................... 7-3

MBd..................................................................... 7-1

Menu ................................................................... 5-1

Menu tree ............................................................ 5-1

Modbus................................................................ 7-3

Modbus command channel ................................. 6-1

MODBUS/TCP .................................................. 4-33

Network connection........................................... 4-18

Orientation........................................................... 1-2

Pictograms ...................................................... 1-1

OSSD .................................................................. 7-3

Overview of the commands ................................. 6-2

Password............................................................. 7-4

PELV ................................................................... 7-4

Pictograms ................................................... 1-1, 7-4

Point-to-point connection..................................... 4-4

Polling.................................................................. 7-4

Profibus ............................................................... 7-4

Programming interface

Ethernet........................................................... 4-2

Remanent............................................................ 7-5

Run time system.................................................. 7-5

Safety instructions such as general rules ............ 2-1

SELV ................................................................... 7-5

Single slave ......................................................... 7-5

Slave ................................................................... 7-5

Symbols............................................................... 1-1

Target.................................................................. 7-5

Terms .................................................................. 7-1

UDP..................................................................... 7-5

Watchdog ............................................................ 7-5

8-1

Supplementary device manual AS-i controllere with Ethernet

Supplementary device manual

AS-i controllere with Ethernet programming interface

1.1 What do the symbols and formats stand for?

DANGER

NOTICE

1.2 What devices are described in this manual?

1.3 How is this manual structured?

1.4 Overview: where is what?

2.1 General

2.2 What previous knowledge is required?

2.3 Functions and features

3.1 Information concerning the device

3.2 Information concerning the software

4.1 Overview

4.3 Which operating modes are there for the PLC in the controllere?

4.4 AS-Interface as well as project transmission and diagnosis via RS232

4.5 Project transmission and diagnosis via Ethernet interface

5.1 Menu "Ethernet Setup"“

6.1 The Modbus command channel

Related manuals

Table of contents

Supplementary device manual AS-i controllere with Ethernet