FIELD BUS

SAE-STAHL GMBHIm Gewerbegebiet Pesch 14

D-50767 KölnTel.: +49-221-59808-200

Fax: +49-221-59808-60http://www.sae-stahl.de

E-mail:[email protected]

Protocol Driver Manual Fieldbus / MMI-COMProVicom, Exicom Visualisation

MT-300 MT-310

ET-8

Protocol Driver Manual Fieldbus /MMI-COM:

ProVicom, Exicom Visualisation

Art.-no.: 200630100800

Version: 1.10

Edition: 09.10.01

of 41 SAE-STAHL GMBH / VS_FBGB.DOC / 09.10.01

Publisher and copyright by:

SAE-STAHL GMBH KölnIm Gewerbegebiet Pesch 14D-50767 Köln

Phone (exchange)+49/(0)221/ 5 98 08 - 200(Hotline) - 59

Fax - 260

• All rights reserved.• This document may not be reproduced in whole or in part except with the written consent

of the publisher obtained.• The right to technical changes is reserved. This Manual was carefully produced. Nevertheless, SAE-STAHL GMBH do not warrant thatthe information contained therein to be free from errors. IBM is a registered trademark of IBM-Corp. MS DOS is a registered trademark of MICROSOFT Corporation WINDOWS 95 is a registered trademark of MICROSOFT Corporation S5/ S7 are registered trademarks of Siemens AG Cologne, dated 09.10.01

Protocol Driver Manual Fieldbus / MMI-COM Contents

SAE-STAHL GMBH / VS_FBGB.DOC / 09.10.01 of 41

Table of Contents

1. General Notes ............................................................................... 5

1.1. Documentation Manuals ..........................................................................................51.1.1. Device Manual .....................................................................................................51.1.2. Engineering Manual .............................................................................................51.1.3. Protocol Driver Manuals.......................................................................................51.1.4. Target Groups......................................................................................................51.2. Safety Alert Symbols................................................................................................6

2. Safety Notes.................................................................................. 7

2.1. General Provisions...................................................................................................72.2. Use for Intended Purpose ........................................................................................72.3. Repairs.....................................................................................................................8

3. Communication ............................................................................ 9

3.1. Communication via L2-DP/ Profibus-DP ..................................................................93.2. Communication via Interbus-S MMI........................................................................10

4. Installation on the PLC............................................................... 11

4.1. Installation via L2-Bus / Profibus-DP......................................................................114.1.1. PIN assignment of the interface for L2-DP (Socket X14)...................................114.1.2. Adjustment of the serial interface.......................................................................114.1.3. Adjustment of the slave address........................................................................114.1.4. Busparameterizing/ Type file .............................................................................124.1.5. Diagnostic LEDs on SK-FB................................................................................164.1.6. Communication error messages ........................................................................174.1.7. Error detection Profibus connection S7 .............................................................184.1.8. Communication cycle times ...............................................................................194.2. Installation MT-310 on Simatic S7 via L2DP/ Profibus-DP.....................................204.2.1. PIN assignment of the interface for L2-DP/ Profibus-DP (Field bus) .................204.2.2. Integration of the GSD file .................................................................................204.2.3. Parameterizing of the master system.................................................................204.2.4. Integration of the program..................................................................................214.2.5. Diagnosis LEDs of the L2DP/ Profibus-DP interface .........................................224.2.6. Parameterizing in SPSPlusWIN.........................................................................224.3. Installation via Interbus-S.......................................................................................244.3.1. Bus connection ..................................................................................................24

Contents Protocol Driver Manual Fieldbus / MMI-COM


4.3.2. Connection to Interbus-S via S5/S7...................................................................284.3.3. Communication error messages ........................................................................294.3.4. Inputs/ Outputs ..................................................................................................30

5. Addressing.................................................................................. 31

5.1. Address Specification ............................................................................................315.2. Setting Station Parameters ....................................................................................32

6. Function References .................................................................. 33

6.1. Key functions .........................................................................................................336.2. LED Bit Area ..........................................................................................................366.2.1. LEDs (ProVicom only)........................................................................................386.3. Fault Message and Operating Message Areas ......................................................396.4. Other Communication Areas..................................................................................396.5. Elementary Data Types and Formats.....................................................................406.5.1. Communication between PLC and Terminal......................................................406.5.2. Table Showing Types of Variables ....................................................................416.5.3. Assignments of variable types to the PLC format ..............................................41

Protocol Driver Manual Fieldbus / MMI-COM General Notes


1. General Notes

1.1. Documentation Manuals

The documentation is presented in 3 manuals: 1.1.1. Device Manual The Device Manual contains• a product overview with technical specifications and the features of the devices and the

firmware, and the designation of the accessories. • the setting up and installation instructions, • and the description of the start-up. 1.1.2. Engineering Manual The Engineering Manual contains• a description of the SPSPlus WIN project tool, and• the design of the devices 1.1.3. Protocol Driver Manuals The Protocol Driver Manuals contain descriptions of all features of the protocol drivers used,e.g., addressing the process links and specific design notes. 1.1.4. Target Groups

Target group Required manual Required chapters Overview Device manual Product overview Protocol driver manual Function overview Design engineer /programmer

all all

Operator Device manual Operation Installer Device manual Setting-up and installation

instructions Service Device manual all Protocol driver manual Configuration In compiling the manuals we have made every attempt to provide complete and correctinformation for the design and use of the products described. If despite this you should findthat an important document is missing or if you find a mistake or other discrepancy in any ofthe Manuals, please inform us so that we can take necessary remedial action.

General Notes Protocol Driver Manual Fieldbus / MMI-COM


1.2. Safety Alert Symbols

Safety alert symbols in this Manual use the words

Caution

to indicate a potentially dangerous situation which, if not avoided, could result in fatal injuryand damage to property. Notes using the symbol

indicate important information to which we want to draw your particular attention. Text in square brackets [] indicates input strings

Input only the chain, not the square brackets.

Protocol Driver Manual Fieldbus / MMI-COM Safety Notes


2. Safety Notes

2.1. General Provisions

This Manual contains information for the proper use and application of the productsdescribed herein. The Manual has been written for operators with technical qualification andapplicable know-how in the area of automation equipment and data transfer technology. Operators with technical qualification are persons, • who as designers are familiar with safety concepts in automation engineering and data

transfer technology, • or who as operators have been trained in handling devices and the system, respectively,

and who are familiar with the contents of this Manual, • or who have been trained as installers or service technicians of appropriate systems in

accordance with applicable safety standards. Detailed knowledge and the technically correct application of the installation procedures /safety notes / functions described in this Manual are a precondition for its safe operation. As the components and devices described in this Manual can be used in most diverseareas and systems, it is absolutely required that their functions and the appropriate safetynotes be integrated in the safety concept of the system of which they are a part. If you have any questions, the support staff of SAE-STAHL will be pleased to assist you. 2.2. Use for Intended Purpose

The components / the device may only be used for the purpose for which it is designed (asdescribed in the product information or the technical specification). The applicable safetystandards have been implemented in the development, production, testing anddocumentation of the product. Normally the product is not associated with dangeroussituations which may result in injury or damage provided the handling instructions andsafety notes are observed.

Caution: • When the casing is removed or the control cubicle door opened, parts that may

be live with dangerous voltage become accessible. • The product is only safe if it is transported, stored, installed and operated

properly.

• Only certified personnel who have read and understood this Manual may work onthe product (see below).

Safety Notes Protocol Driver Manual Fieldbus / MMI-COM


2.3. Repairs

• SAE-STAHL products may only be repaired by SAE-STAHL customer service staff orother certified persons / firms.

• Only original modules and parts of SAE-STAHL may be used. • The customer is only allowed to replace modules if this is expressly allowed in this

Manual. The work must be carried out by trained personnel. • Standard parts, such as fuses, must be of the specified rating.

Protocol Driver Manual Fieldbus / MMI-COM Communication


3. CommunicationFor simple and fast data exchange in the instrumentation a fieldbus system isrecommended. The connection of automation devices and operation panels is very simple.The communication protocol consists of several layers:

Physical LayerFieldbus

Link LayerFieldbus

ApplicationPLC-Mode

Write/Read

Order processing

n Bit In n Bit Out

Picture: Layers of the communication protocol

Fieldbus types as Profibus-DP, Interbus-S, CAN- Bus etc. in principle only offer a parallelinterface. The size of the parallel interface can be parameterized to 10 or 16 Bytes,because inputs and outputs of PLCs are limited. For Interbus-S, a protocol for such aninterface exists which is used. For Simatic S5 and S7 comfortable handling modules areavailable. For other connections, the protocol descriptions are in this manual resp. availableat SAE-STAHL.

Application LayerThe application layer is according to the profile MMI-COM of the Interbus-S Club andencloses all functions of the PLC-Mode. The PLC-Mode devices operate as clients, theconnected host/ PLC as server.

3.1. Communication via L2-DP/ Profibus-DP

Link LayerThe "Link Layer" is based on the Siemens DPS2-Bibliothek (library) with ASIC SPC3,Desribed in "SPC3 Siemens PROFIBUS Controller“ and according to DIN 19245 Teil 3(design).

Physical LayerThe physical bus connection is according to DIN E 19245 Teil 1 via a two wire line.

Communication Protocol Driver Manual Fieldbus / MMI-COM


3.2. Communication via Interbus-S MMI

Link LayerThe data transfer is made via the process data channel according to DIN 1958 (design) andthe guidelines of the InterBus-S-Club.

Physical LayerThe physical bus connection is via the InterBus-S Remotebus interface on the 2-lines ring.

Protocol Driver Manual Fieldbus / MMI-COM Installation on the PLC


4. Installation on the PLC

4.1. Installation via L2-Bus / Profibus-DP

For successful installation, the following steps are necessary:

1. Adjustment of the serial interface2. Adjustment of the slave address3. Busparameterizing/ Type file

4.1.1. PIN assignment of the interface for L2-DP (Socket X14)

X14View PIN Signal Comment

123456789

--RxD/TxD-PRTSM5V2P5V2-RxD/TxD-N-

Data BRequest to SendData groundPower plus 5V

Data A

The bus connection of the terminals to the SINEC-L2-Bus is made via a SINEC-L2 busconnection plug in consideration of the instructions valid for the SINEC-L2-Bus

4.1.2. Adjustment of the serial interface(only Exicom)See Device Manual, "Mounting Instructions and Installation / Installation of the fieldbusbridge"

4.1.3. Adjustment of the slave addressAt first, please adjust the slave address via the switch S2. On ProVicom, the latter is placedon the back side, on SK-FB-1-TTL-L2DP on the upper (smaller) circuit board,

S2 L2-DP slaveaddress

1 2 3 4 5 6 7 80 0 0 0 0 0 0 0 0, invalid1 0 0 0 0 0 0 0 1, invalid0 1 0 0 0 0 0 0 2, invalid1 1 0 0 0 0 0 0 30 0 1 0 0 0 0 0 4...1 1 1 1 1 1 1 1 255

Installation on the PLC Protocol Driver Manual Fieldbus / MMI-COM


4.1.4. Busparameterizing/ Type fileOn the disk with the handling module HB L2-DP there are the current type and GSD files.

the GSD file is needed for operation with• Siemens Master CP5412 (PC board)• CP342-5 (Master unit for S7)• Bosch Master

Use the type file in the directory Typ4.x for• COMET200 from version 4.x and board IM308B

Use the type file in the directory Typ5.x• Windows COM from Version 1.0 and installation unit IM308C, AG95U as L2DP master• and S7-COM

In the future, for projecting with the COM Profibus V3.0 and S7-COM, the GSD file will beused.

Proceed as follows:• Copy the type files from the disk to the corresponding directories of the projecting

program• For the slave parameterizing, choose " B+B " and• select SAE-MT-XX-L2DP edition 2

configure slave Variant 1 : 10 Byte Input 25 10 Byte Output 41configure slave Variant 2 : 16 Byte Input 31 16 Byte Output 47

4.1.4.1. Installation of the handling blocks for Simatic S5For the operation of the SAE-STAHL terminals on the L2DP bus two variants are available: Variant 1. 10 byte process data (only ProVicom) Variant 2. 16 byte process data

For ProVicom, selection is made in the configuration menu:

PD-Channel size

10 Byte16 Byte

<CUP/CDN> - Select .<ESC> - Exit <CR> - OK



For each variant one STEP 5 file is necessary.

File Function1 L2DP01ST.S5D 10 Byte2 SAEMMIST.S5D 16 Byte

Operation Variant 1 - 10 Bytes

In the L2DP01ST.S5D file there are the following data blocks:

FB10 MT80L2DP function block for the processing of the byte variant.The FB10 should be called in each cycle.If several terminals are active on the bus then the FB10 must be called for eachterminal.

DB100 H-DB data block as memory area of the variables.The data words 0 - DW10 are required by the function block MT80L2DP andmust not be changed.Each terminal needs its own data block, which should consist of 20 data words

Parameters of function block

Name Type Format CommentADR D KY Address KY = YYY,XXX

X : = address 0 - 246Y : 0 = input/ output address area 1 = peripherals

H_DB D KY Data block of255 words

KY = YYY,XXXX: = DB number 4 -> 255Y: 0 = data block addressing 1 = DX block addressing

T T Timer Arbitrary timer for supervising the communicationBUS E BI activation bit

L2DP bus= 0 stop function block processing data are set to 0000= 1 activation of function block communication to the terminal is set up

BUSY A BY CommunicationError

BIT 0 = 1 No connection to masterBIT 7 = 1 invalid connection to master




In the file SAEMMIST.S5D are following blocks:

FB11 MMI01 function block for the MMI communicationThe FB11 is to be called in each cycle for every terminal in the bus

DB110 H-DB data block for communication handlingThe data words 0- DW 10 are required by the function block MT80L2DP and must not be changed.Each terminal needs its own data block, which should consist of 20 data words.


FB 11 Name :MMI01Name Typ

eFormat Comment

ADR D KY Address KY = YYY,XXXX : = address 0 - 246Y : 0 = input/ output address area 1 = peripherals

H_DB D KY Data block of255 words

KY = YYY,XXXX: = DB numberY: 0 = data block addressing

T T Timer Arbitrary timer for supervising the communicationBUSY A BY Error BIT 0 = 1 No connection to master

BIT 7 = 1 invalid connection to masterMODE D KY Reserve

Each terminal in the L2 bus needs 16 bytes input and 16 bytes output. Input andoutput area must start at the same address.



4.1.4.2. Coupling of the SAE-STAHL terminals to SIMATIC S7 via L2DPProcedure1. Integration of the GSD file2. Parameterizing of the master system3. Integration of the program

Integration of the GSD file:On the disk, directory GSD, there is the file SAE_0730.GSD.To integrate this file into the Step7 system you must proceed as follows:

1. Copy the file SAE_0730.GSD into the directory STEP7/ S7DATA/GSD2. In the menu Configure hardware / EXTRAS choose

"Actualise GSD file"

Parameterizing of the master systemFor integrating the terminals choose in the configuration of the master system in thehardware catalogue PROFIBUS-DP -> Other field devices -> Others SAE-MT-L2DP

Each terminal in the L2 bus needs 16 bytes input and 16 bytes output. Input andoutput area must start at the same address

Integration of the programOn the disk in the directory SAE_S7L2 there are the two programs S7-300 and S7-400.The program in directory S7-300 operates with L IW and T QW instructions. Therefore theaddressing is restricted to the process image of the inputs and outputs.

The program in directory S7-400 operates with L PIW and L PQW instructions. Thereforethe whole DP address area can be addressed.

If the DP slave is not in the bus an I/O Access Error is generated. OB122 must beprogrammed so that the CPU does not go into STOP.

The FB11 in directory S7-400 can also run with S7-300.

After opening the project the FB11 must be copied into the user project. The FB11 is to becalled in each cycle for every terminal in the bus.

Example :

CALL FB 11 , DB3 Call of FB11 with an arbitrary instance dataADR :=70 parameterizing addressT :=T1 arbitrary timerMODE :=W#16#0 ReserveBUSY :=MB10 0 = no communication 1 = communication OK



4.1.5. Diagnostic LEDs on SK-FB

LED Name Colour Description1 RUN green FB main function

• blinking - OK2 BUS red BUS status

• Off - OK• On - bus failure

3 TxD green Output to Exicom• flashing - OK

4 RxD green Input from Exicom• flashing - OK



4.1.6. Communication error messages

Message MT-300-L2DPNo communication STOP on The L2-Bus did not synchronise

− L2 cable− L2-DP slave address− parameters of masterFor the function in runningmode, the Response Monitoringmust be activated.

No communication STOP offCOM off

The L2-Bus has synchronised,MMI protocol error− parameters of handling block− PLC in Stop

Bad address Text or configuration contains abad address

Exicom message SK-FB-1No communication BUS-LED on Bus failure

− L2 cable− L2-DP slave address− parameters of master

No communication BUS-LED offTxD and RxDare flashing

MMI protocol error− parameters of handling block− AG in Stop

No communication BUS-LED offTxD and RxDoff or only RxDis flashing

Communication error betweenSK-FB and Exicom− Check baudrate parameters




4.1.7. Error detection Profibus connection S7The first three questions refer only to the Exicom terminals, after that are also the ProVicomterminals are included.

Can you transfer the configuration / system via the SK-FB-L2DP?Check the wiring of the SK-FB with the SK-RS422 card.

Are the SK-FB-L2DP card and the terminal adjusted to the same Baudrate?Under normal conditions card and terminals should be adjusted to the parameters 57600baud / 8 data bit / 1 stop element / even parity. You can check the adjustments with theterminal via the system menu. With the SK-FB-L2DP J1 + J2 must be put (see also DeviceManual).

Does the LED 1 (run) of the SK-FB-L2DP light up statically ?Then please remove the programming cable at the SK-FB-L2DP card. The LED 1 (run)should now flash.

Exicom: Does the red bus LED 2 (bus error) at the SK-FB-L2DP light up ?ProVicom: Is the LED " Data Exchange " off?Check the connection of bus and the adjustment of the DP master system. Is the adjusteduser number set to the SK-FB-L2DP / on the terminal in the hardware configuration?

With ProVicom: Remove the programming cable from the plug X2. The LED " DataExchange " should now be statically on.

Can you read the function keys in the direct input word resp. set the LED in the directoutput word?When creating the hardware configuration you assign a start address of the input/outputarea for the user (total 16 byte). These input/output areas must begin with the sameaddress.In the bytes 13 and 14 of the input area you see an image of the function keys.In the bytes 13 and 14 of the output area you can head for the LED's of the function keys.

If an address area > 128 is selected then the program for the S7-400 must be used.

At the call, is the start address of the input/output area specificated?The " addr: =... " specification with the call of the FB11 refers to the start addressinput/output area for the respective terminal. These input/output areas must begin with thesame address and are not to be compared with the adjusted user number (Slave address).

Is the instance data block used in the configuration of the terminal?Within the configuration of the terminal the instance data block (is specified for the call ofthe FB 11 ) may never be addressed. It may also not be used by other program sections ofthe PLC.

Does the PLC possibly go into " STOP " (if OB122/OB86 is not programmed)?Check the length of the created data blocks. All data blocks used in the terminal must bedeclared in the PLC.



4.1.8. Communication cycle timesThese cycle times have been detected on a test system with two SAE-STAHL terminals andone ET-200 with a data transfer rate of 1,5 Mbaud on the respective master system

Transfer times 95UFunction keys F1...F16 20 msChange of the PLC cycletime with each terminal

2 ms



4.2. Installation MT-310 on Simatic S7 via L2DP/ Profibus-DP

Procedure:1. Integration of the GSD file2. Parameterizing of the master system3. Integration of the program

4.2.1. PIN assignment of the interface for L2-DP/ Profibus-DP (Field bus)

X14View PIN Signal Comment

123456789

--RxD/TxD-PRTSM5V2P5V2-RxD/TxD-N-

Data BRequest to SendData groundPower plus 5V

Data A

The bus connection of the terminals to the SINEC-L2-Bus is made via a SINEC-L2 busconnection plug in consideration of the instructions valid for the SINEC-L2-Bus

4.2.2. Integration of the GSD fileOn the disk, directory GSD, there is the file Hil_7501.gsd. In order to integrate this file intothe Step7 system you must proceed as follows:

1. Copy the file Hil5701.gsd into the STEP7/ S7DATA/GSD directory.2. In the "Configure hardware" / "EXTRAS" menu choose "Actualise GSD file" .

4.2.3. Parameterizing of the master systemStart Step7 and open first the hardware configuration and then the hardware catalogue.Now the modules you need you find under Field devices/general/com-dps.

Choose the desired net masterbus by mouse click and insert the slave by double click onCom-dps. In the opening window, you can already declare the desired slave number youwant to assign to the terminal.

Confirm this with ok. In the opening overview you can now integrate the needed modules.Insert on position 0 module 16 byte input and on position 1 module 16 byte output bydouble click.

Never insert the con modules (consistent).

The software automatically assigns the addresses. These you can change any timewithin the allowed scope. Input and output addresses must be identical.



4.2.4. Integration of the programOn the disk in the directory MT310_L2DP there is the program S7-400.

If the DP slave is not in the bus a periphery error will be generated. OB122 must beprogrammed so that the CPU does not go into STOP.

After opening the project the FB11 must be copied into the user project.

The FB11 is to be called in each cycle for every terminal in the bus. If several terminals inthe bus are active then the FB will have to be called for every terminal one time.

Example:

Call FB11, DB3 Call of FB11 with an arbitrary instance dataparameterizing address

ADR:= 70 Input or output addressT:= T1 arbitrary timerMode:= W#16#0 ReserveBusy:= MB10 0 = no communication

1 = communication OK



4.2.5. Diagnosis LEDs of the L2DP/ Profibus-DP interfacePositions:

Green - RDY Yellow - STA

Orange - RUN Red - ERR

LED State MeaningGreen - RDY On CIF ready

Flashes cyclically Bootstrap loader activeFlashes discontinuous Hardware or system errorOff Hardware defect

Orange - RUN On Communication runningFlashes cyclically Communication stoppedFlashes discontinuous Missing or incorrect CommunicationOff No Communication

Red - ERR On PROFIBUS errorOff No error

Yellow - STA On DP/FMS master: sends data or tokenDP Slave: data exchange with master

Off No token

4.2.6. Parameterizing in SPSPlusWINIf you create a new project you will have to select S7 Sinec Profibus-DP driver on COM3 inthe "Port and driver" window.

The last setting is the station number or node number of the slave.



Select the item "Port" in the project explorer and open the station in the right window with adouble click.

The window in the following picture opens and you can enter the station parameters. Afterdownload with the system files the terminal is ready for communication.



4.3. Installation via Interbus-S

4.3.1. Bus connection9-pin D-SUB-plug type connectors should be connected to the cable, which may have alength of max. 400 m. The pin configuration is as follows:

Remote bus IN X14SUB-D plug(incoming)

Remote bus OUT X15SUB-D socked(continuing)

Enclosure Screen Screen Enclosure12367

DODIGroundDO/DI/

DODIGround+5VDO/DI/RBST

1235679

Signals marked with "*" are "0"-active.

The 3-pair twisted cable with the description LIYCY 3 x 2 x 0,14 with a max. cable capacityof 120 pF/m is recommended as data transmission cable for the INTERBUS-S.

Literature: refer to Phoenix Installation Notes

Typical connection cable:

BR brownGE yellowGN greenGR greyRS pinkWS white

Enclosure Enclosure

Cable requirements:twisted pair andscreened



Bus cable incoming Bus cable continuingX14 = Remote INX15 = Remote OUT

The shield is principally laid on both sides of the 9-pin SUB-D housing. Metallic or metallizedplug housings must be used. In order to prevent the flow of equipotential currents throughthe shield of the bus cable, the plug type connector for the incoming cable (X14) is earthedvia a capacitor.

4.3.1.1. Installation of the handling blocks for Simatic S5For the operation of the SAE-STAHL terminals on the Interbus two variants are available: Variant 1. 10 byte process data Variant 2. 16 byte process data

For each variant one STEP 5 file is necessary..

File Function1 IBS01ST.S5D 10 Byte2 SAEMMIST.S5D 16 Byte

MT MT




In the IBS01ST.S5D file there are the following data blocks:

FB10 MT80L2DP function block for the processing of the byte variant.The FB10 should be called in each cycle.If several terminals are active on the bus them the FB10 must be called for eachterminal.

DB100 H-DB data block as memory area of the variables.The data words 0 - DW10 are required by the function block MT80L2DP andmust not be changed.Each terminal needs its own data block, which should consist of 20 data words.


FB 10 Name : MT80IBSName Type Format CommentADR D KY Address KY = YYY,XXX


H_DB D KY Handling datablock of255 words

KY = YYY,XXXX: = DB number 4 -> 255Y: 0 = data block addressing 1 = DX block addressing

T T Timer Arbitrary timer for supervising the communicationBUS E BI activation bit

Interbus-S= 0 stop function block processing data are set to 0000= 1 activation of function block communication to the terminal is set up

BUSY A BY CommunicationError

BIT 0 = 1 No connection to masterBIT 7 = 1 invalid connection to master




In the file SAEMMIST.S5D are following blocks:

FB11 MMI01 function block for the MMI communicationThe FB11 is to be called in each cycle for every terminal in the bus

DB110 H-DB data block as memory area of the variables.The data words 0 - DW10 are required by the function block and must not bechanged .Each terminal needs its own data block, which should consist of 20 data words.


FB 11 Name :MMI01Name Type Format CommentADR D KY Address KY = YYY,XXX


H_DB D KY Handling datablock of255 words

KY = YYY,XXXX: = DB numberY: 0 = data block addressing

T T Timer Arbitrary timer for supervising the communicationBUSY A BY Communication

errorBIT 0 = 1 No connection to masterBIT 7 = 1 invalid connection to master

MODE D KY Reserve



4.3.2. Connection to Interbus-S via S5/S7Procedure1. Reading the stations2. Parameterizing of the stations3. Linking the program

Reading the stationsStarting program and reading the stationsAfter reading the stations the terminal is displayed with ID:47.

Parameterizing of the stationsNow you can select the process data at the station with right mouse click.

Each terminal which is linked in the INTERBUS-S, needs 16 byte of inputs and 16 byte ofoutputs and is given automatically. The respective input and output section must begin withthe same address and is declared in the allocation field.



Linking the programOn the diskette the Step7 project SAE_S7L2 is in the directory SAE_S7L2. From openingthe project the FB11 must be copied into the user project.The FB11 should be called in each PLC cycle. If several terminals are active in the bus thenFB11 must be called once for each terminal.

Example:

CALL FB 11 , DB3 calling FB11 with any instance data blockADR :=34 the parameterizing addressT :=T1 any timerMODE :=W#16#0 reserveBUSY :=MB10 0 = no communication 1 = communication OK

4.3.3. Communication error messages

Message MT-300No communication STOP on The bus did not synchronise

− cable− parameters of IBS master

No communication STOP offCOM off

The bus has synchronised, MMIprotocol error− parameters of handling block− PLC in Stop




4.3.4. Inputs/ OutputsPLC output data (10 Byte PD channel)

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10indirect Process Data Channel direct PD

channelRepro-ductionByte 1

Reserve

Control wordS-Bit = x, I-Bit = 1

Data field LED 9...LED 16

LED 1...LED 8

see Byte1

Outputs1...4*

with S-Bit (Standard) = 0 for addressing DB/DWS-Bit = 1 for Index addressing

PLC output data (16 Byte PD channel)

Byte1

Byte2

Byte3

Byte4

Byte5

Byte6

Byte7

Byte8

Byte9

Byte10

Byte11

Byte12

Byte13

Byte14

Byte15

Byte16

indirect Process Data Channel direct PDchannel

Consistenceword*

Controlword

Data field LED9..16

LED1...8

Byte1

Out-puts1...4*


PLC input data (10 Byte PD channel))

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10indirect Process Data Channel direct PD

channelRepro-ductionByte 1

Reserve

Control wordS-Bit = x, I-Bit = 1

Data field F9...F16 F1...F8 see Byte1

Inputs1...8*


PLC input data (16 Byte PD channel)

Byte1

Byte2

Byte3

Byte4

Byte5

Byte6

Byte7

Byte8

Byte9

Byte10

Byte11

Byte12

Byte13

Byte14

Byte15

Byte16

indirect Process Data Channel direct PDchannel

Consistenceword*

Controlword

Data field F9...F16

F1...F8

Byte1

Inputs1...8*


* Only devices with inputs/ outputs

Protocol Driver Manual Fieldbus / MMI-COM Addressing


5. Addressing

5.1. Address Specification

The addresses are specified by data block (DB2...DB255) and data words (DW0...DW255).

Value rangeDB 2...255DW 0...255

In this case, the protocol driver S5 Sinec Profibus-DP serves as an example.

» Enter the name of the data block in DB.

» Enter the name of the data word in DW.

» Select the required file format in Format.

For details, please consult chapter 6.6 of the Design Engineer’s Manual.

Addressing Protocol Driver Manual Fieldbus / MMI-COM


5.2. Setting Station Parameters

The settings of the various address areas, e.g., for Fault message field, Keyboard field,LED-Bit field, etc. can be made in the following screen.

For details, please consult chapter 9.2 "Station Parameters" of the Engineering Manual.

Protocol Driver Manual Fieldbus / MMI-COM Function References


6. Function References

The address areas specified below must be observed at any rate, even if theassigned function is not covered by the device.

6.1. Key functions

Function keys and cursor keys are transferred form the base address set by you. (Seechapter 5.2. Setting the Station Parameters).

Address "Keyboard field"+00 Bit

15Bit14

Bit13

Bit12

Bit11

Bit10

Bit9

Bit8

Bit7

Bit6

Bit5

Bit4

Bit3

Bit2

Bit1

Bit0

Meaning

x x x x x x x x x x x x x x x 1 Cursor upx x x x x x x x x x x x x x 1 x Cursor downx x x x x x x x x x x x x 1 x x Cursor leftx x x x x x x x x x x x 1 x x x Cursor rightx x x x x x x x x x x 1 x x x x Clear or Escape keyx x x x x x x x x x 1 x x x x x Enter keyx x x 1 x x x x x x x x x x x x Info keyx x 1 x x x x x x x x x x x x x Trigger bitx 1 x x x x x x x x x x x x x x Histogram full 1)

1 x x x x x x x x x x x x x x x Pass bit;Device pass control1)

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

+01 x x x x x x x x x x x x x x 1 F1. . . . . . . . . . . . . . . .x x x x 1 x x x 1 x x x x x x x F12

+02 x x x x x x x x x x x x x x x 1 Shift-F1. . . . . . . . . . . . . . . .x x x x 1 x x x 1 x x x x x x x Shift-F12

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

+03 x x x x x x x x x x x x x x x 1 Alt-F1. . . . . . . . . . . . . . . .x x x x 1 x x x 1 x x x x x x x Alt-F12

+04 x x x x x x x x x x x x x x x 1 Ctrl-F1. . . . . . . . . . . . . . . .x x x x 1 x x x 1 x x x x x x x Ctrl-F12

F= Function key

1) Function currently not implemented.

Function References Protocol Driver Manual Fieldbus / MMI-COM


+05 Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Meaning15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 (only ProVicom)x x x x x x x x x x x x x x x 1 S1x x x x x x x x x x x x x x 1 x S2x x x x x x x x x x x x x 1 x x S3x x x x x x x x x x x x 1 x x x S4x x x x x x x x x x x 1 x x x x S5x x x x x x x x x x 1 x x x x x S6x x x x x x x x x 1 x x x x x x S7x x x x x x x x 1 x x x x x x x S8x x x x x x x 1 x x x x x x x x S9x x x x x x 1 x x x x x x x x x S10

S = Soft key

• Press any of the above keys → Sets the key bit• Release → Resets the bit• It is not possible to press several function keys at the same time; in this case all bits

settings will be zero.• Key transfer has priority.• Each key press also sets the trigger bit.• Besides, an event bit is set in case of histogram overflow. 1)

• Moreover, a PASS bit is transmitted cyclically. The pass bit is used by control to monitorthe communication. This bit can be reset by the PLC on positive-going edge. If the stateis still Zero after some time (e.g., time-out = 15 sec), control knows that thecommunication is under fault condition. 1)

Example:The "Keyboard range" is located, for example, at DB31 DW2. This causes function keys F1to F8 "Keyboard range“ +1 to be placed in DB31 DW3. Now if the operator pressed the F1key, the devise sets bit 1 or bit 7 in case of F7, in DB31 DW3. At the same time the functionsaved under F1 is enabled.




For simpler handling the keypad bits can be transferred in the flag area. The following S5instructions are specified for all function keys and the use of flags 10.0 to 19.7 :

:A DB 31::L DR 0 Cursor keys:T MB 10 After flag byte 10:L DL 0 Pass bit 1)

:T MB 11 After flag 11.7::L DR 1 Function keys F1-F8:T MB 12 After flag byte 12::L DR 2 Shift F1-F8:T MB 13 After flag byte 13::L DR 3 Alt F1-F8:T MB 14 After flag byte 14:

The assignment in the flag area is then as follows :

M10.0 - Cursor up ...M10.5 - Enter keyM11.6 - Histogram full 1)

M11.7 - Pass bit 1)

...M12.0 - F1 ...M12.7 - F8 ...M13.0 - Shift F1 ...M13.7 - Shift F8 ...M14.0 - Alt F1 ...M14.7 - Alt F8




6.2. LED Bit Area

The LED functions are transferred from the base address set by you. (See chapter 5.2.Setting the Station Parameters).

"LED bit range"+00 Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Meaning

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 (only ProVicom)x x x x x x x x x x x x x x x 1 LED F1 on greenx x x x x x x x x x x x x x 1 x LED F2 on greenx x x x x x x x x x x x x 1 x x LED F3 on greenx x x x x x x x x x x x 1 x x x LED F4 on greenx x x x x x x x x x x 1 x x x x LED F5 on greenx x x x x x x x x x 1 x x x x x LED F6 on greenx x x x x x x x x 1 x x x x x x LED F7 on greenx x x x x x x x 1 x x x x x x x LED F8 on greenx x x x x x x 1 x x x x x x x x LED F1 on yellowx x x x x x 1 x x x x x x x x x LED F2 on yellowx x x x x 1 x x x x x x x x x x LED F3 on yellowx x x x 1 x x x x x x x x x x x LED F4 on yellowx x x 1 x x x x x x x x x x x x LED F5 on yellowx x 1 x x x x x x x x x x x x x LED F6 on yellowx 1 x x x x x x x x x x x x x x LED F7 on yellow1 x x x x x x x x x x x x x x x LED F8 on yellow

+01 Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Meaning15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 (only ProVicom)x x x x x x x x x x x x x x x 1 LED F1 flashing greenx x x x x x x x x x x x x x 1 x LED F2 flashing greenx x x x x x x x x x x x x 1 x x LED F3 flashing greenx x x x x x x x x x x x 1 x x x LED F4 flashing greenx x x x x x x x x x x 1 x x x x LED F5 flashing greenx x x x x x x x x x 1 x x x x x LED F6 flashing greenx x x x x x x x x 1 x x x x x x LED F7 flashing greenx x x x x x x x 1 x x x x x x x LED F8 flashing greenx x x x x x x 1 x x x x x x x x LED F1 flashing yellowx x x x x x 1 x x x x x x x x x LED F2 flashing yellowx x x x x 1 x x x x x x x x x x LED F3 flashing yellowx x x x 1 x x x x x x x x x x x LED F4 flashing yellowx x x 1 x x x x x x x x x x x x LED F5 flashing yellowx x 1 x x x x x x x x x x x x x LED F6 flashing yellowx 1 x x x x x x x x x x x x x x LED F7 flashing yellow1 x x x x x x x x x x x x x x x LED F8 flashing yellow



+02 Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Meaning15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 (only ProVicom)x x x x x x x x x x x x x x x 1 LED F1 flashing fast

greenx x x x x x x x x x x x x x 1 x LED F2 flashing fast

greenx x x x x x x x x x x x x 1 x x LED F3 flashing fast

greenx x x x x x x x x x x x 1 x x x LED F4 flashing fast

greenx x x x x x x x x x x 1 x x x x LED F5 flashing fast

greenx x x x x x x x x x 1 x x x x x LED F6 flashing fast

greenx x x x x x x x x 1 x x x x x x LED F7 flashing fast

greenx x x x x x x x 1 x x x x x x x LED F8 flashing fast

greenx x x x x x x 1 x x x x x x x x LED F1 flashing fast

yellowx x x x x x 1 x x x x x x x x x LED F2 flashing fast

yellowx x x x x 1 x x x x x x x x x x LED F3 flashing fast

yellowx x x x 1 x x x x x x x x x x x LED F4 flashing fast

yellowx x x 1 x x x x x x x x x x x x LED F5 flashing fast

yellowx x 1 x x x x x x x x x x x x x LED F6 flashing fast

yellowx 1 x x x x x x x x x x x x x x LED F7 flashing fast

yellow1 x x x x x x x x x x x x x x x LED F8 flashing fast

yellow



6.2.1. LEDs (ProVicom only)Switching on and flashing of LEDs is enabled by setting the appropriate bit. The LEDremains switched on for as long as the appropriate bit remains static. If several bits are setfor one and the same LED, priorities are assigned. "Fast flashing" has highest priority,"Switching" lowest priority.

Example : PLC address LED bit area DB31 DW10

:L MB 20 LED 1-8 on green:T DR 10::L MB 22 LED 1-8 flashing green:T DR 11::L MB 24 LED 1-8 fast flashing green:T DR 12:

In this example, the base address "LED-Bit range" is located at DB31 DW10. Now, to switchon the LED of function keys F1...F8, the appropriate bits in "LED-Bit range" " +0, viz., DB31DW10, are set. For flashing: DB31 DW11, for fast flashing: DB31 DW12. If in the PLC bit 0in DB31 DW10 is set, LED 1 lights.LED setting is simpler by flags and transfer of the flags in the data area. In this example,flags 20.0 to 24.7 are used. The assignment in the flag area is as follows :

M20.0- LED 1 on green...M22.0- LED 1 flashing green...M24.0- LED 1 fast flashing green



6.3. Fault Message and Operating Message Areas

The messages are transferred form the base address set by you. (See chapter 5.2. Settingthe Station Parameters).

Fault message report resp. Operating message range 1-32 words+00 Bit

15Bit14

Bit13

Bit12

Bit11

Bit10

Bit9

Bit8

Bit7

Bit6

Bit5

Bit4

Bit3

Bit2

Bit1

Bit0

Meaning

x x x x x x x x x x x x x x x 1 Fault 0. . . . . . . . . . . . . . . . ...1 x x x x x x x x x x x x x x x Fault 15

+01 x x x x x x x x x x x x x x x 1 Fault 16. . . . . . . . . . . . . . . . ...1 x x x x x x x x x x x x x x x Fault 31

...+255 x x x x x x x x x x x x x x x 1 Fault 4080

. . . . . . . . . . . . . . . . ...1 x x x x x x x x x x x x x x x Fault 4095

It is not necessary to define the message area to DW 255. If only a few faults occur, asmaller area can be chosen.

6.4. Other Communication Areas

Curves range Bit area for curve transmission

Curves- acknowledgerange

Bit area for confirming curve transmissions

Demand bit range Bit area to require curve values

Demand bitacknowledge range

Bit area for confirming curve requirements

Triggerbit range Bit area for setpoint triggering

Ready bit Address for ready bit

For more details, please read chapter 9.2. "Setting Station Parameters" of the EngineeringManual.



6.5. Elementary Data Types and Formats

6.5.1. Communication between PLC and TerminalThe communication between the PLC and the SAE-STAHL terminal comprises theexchangeof variable data. Data is stored in the PLC in certain formats. If variables are transferredfrom the PLC to the terminal in a certain format, the terminal device must identify the datatype in which the data is to be presented. When variables are read from the terminal in thePLC, they must be stored in a defined format in the PLC. Hence the data must beconverted in the format in which they are presented in the PLC.

PLC

Format

S5 S7

• KF INT• KB BYTE• KH WORD• KM BOOL• KD DINT• KD DWORD• KC STRING• KT0 10ms• KT1 100ms• KT2 1sec• KT3 10sec• KZ BCD3• KG REAL

Terminal

Data type

• Integer• Unsigned Integer• Long Integer• Unsigned Long Integ.• Float

The setting of formats and data types is made by means of the SPSPlus WIN engineeringsoftware. For more details, see the SPSPlus WIN Engineering Manual.



6.5.2. Table Showing Types of Variables

Type: Description: Max. digits: Value range:Integer 16-bit signed

integer5+ sign -32768 ... 32767

Unsigned Integer 16-bit unsignedinteger

5 0 ... 65535

Long Integer 32-bit signedinteger

10+ sign -2147483648 ...2147483647

Long UnsignedInteger

32-bit unsignedinteger

10 0 ... 4294967295

Float Floating pointnumber

For details of creating variables, see chapter 6 "Variables" in the SPSPlus WIN EngineeringManual.

6.5.3. Assignments of variable types to the PLC formatAny assignment is possible however only specific combinations are reasonable.A listing of the PLC formats and of the possible variable types follows.

S5 format S7 format possible variable typesKF INT Integer, Unsigned IntegerKB BYTE Integer, Unsigned Integer (only Low-Byte)KH WORD Integer, Unsigned IntegerKM BOOL for digital variablesKD DINT Long Integer, Long Unsigned IntegerKD DWORD Long Integer, Long Unsigned IntegerKC STRING for stringsKT0 10ms Float (2 decimal positions)

display 0.00 - 9.99 secondsKT1 100ms Float (1 decimal position)

display 00.0 - 99.9 secondsKT2 1sek Inetger, Float

display 0 - 999 secondsKT3 10sek Integer, Float

display 10 - 9990 secondsKZ BCD3 Integer, FloatKG REAL Float

FIELD BUS

Documents

Transcript of FIELD BUS