ASM410_e.pdf

7/28/2019 ASM410_e.pdf

1/42

ASM 410 Interface ModuleASM 410

MOBYI Identification System

Release 12.98Technical Description

7/28/2019 ASM410_e.pdf

2/42

7/28/2019 ASM410_e.pdf

3/42

ASM 410 Technical Description 6GT2097-3AC00-0DA2

- 1 -6GT2002-0BA00

RD: 12/98

Subject to change without notice!ASM 410

(4) J31069D0125U001A07618

Table of Contents

Page

1. ASM 410: A Brief Description 2

2. The ASM 410 3

2.1 Mechanical Design 3

2.2 Block Diagram 5

2.3 Pin Assignments 6

2.4 Cable Connections of the ASM 410 7

3. Programming 9

3.1 Representation of the ASM 410 in the Process Image 9

3.2 Timing Diagram of Control Signals 123.3 Programming Example 15

3.4 Programming of Cold Start and Restart Procedures 16

3.5 Application of SLG ON/OFF" and Presence" 16

3.6 Using the ASM 410 as Decentralized Periphery 20

3.6.1 Use in the ET 100U 20

3.6.2 Use in the ET 200 22

3.6.3 Use with SIMATIC S7 via ET 200U 23

3.7 Processing Mobile Data Carriers 24

3.8 Dialog Operation 26

3.8.1 How is the MOBYI Dialog Set Up? 26

3.8.2 How Does the User Work with the MOBYI Dialog? 28

4. The ECC Driver 30

5. Error Evaluation 32

6. Transmission Times 34

7. Commissioning 35

8. Technical Specifications of the ASM 410 37

9. Warnings 38

7/28/2019 ASM410_e.pdf

4/42

ASM 410 Technical Description6GT2097-3AC00-0DA2

- 2 - 6GT2002-0BA00

RD: 12/98

Subject to change without notice! ASM 410

(4) J31069D0125U001A07618

1. ASM 410: A Brief Description

The ASM 410 interface module offers the MOBY-I user a lowcost interface for the SIMATIC S590U,

S595U and S5100U programmable controllers.

Main characteristics:

. Can be used in: S5-100U with CPU 102 and CPU 103

CPU 100 V.02 and higher (6ES5100-8MA-02)

S5-95U

S5-90U

Restricted use in ET 100U

. Designed as an analog module with 8 input bytes and 8 output bytes

. Simple programming via process image inputs and process image outputs ( PII/PIQ).

No function block required.

. Fully compatible with all MOBY-I components: Unrestricted use with all MDS mobile data

carriers, SLG read/write devices and the STG service and test unit

. Up to 2 SLG read/write devices can be driven from one ASM 410 in time multiplex mode

. One 5byte data block is processed with each command;

for larger amounts of data, several commands must be processed consecutively.

. Interferencefree design by galvanic isolation of MOBY-I interface to S5 bus

. Status and error indications clearly displayed on the front panel of the module

7/28/2019 ASM410_e.pdf

5/42


- 3 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

2. The ASM 410

2.1 Mechanical Design

The ASM 410 is the same size as all other standard modules of the SIMATIC S5100U series. It can be

plugged directly onto the bus modules (6ES5 7008MA11 or 6ES5 7008MA21).

A2A3A1

B1B2B3

MOBY - I6GT2002-0BA00

1 2 3 4 5 6

5

16

9

STG

1 2 3

LEDs

Betriebsart

8

9

6

res.

02

46 8 A

C

E

A

B

Connector to serial S5 bus

10-way connector to bus module (24 V supply,interface to SLG read/write device)

Status and error LEDs (See table 1.)

9way subminiature D connector for connecting theSTG service and test unit with cable 6GT20910B...

Coding plug (not shown; on reverse side ofmodule).Fixed in position H" to denote analog module.

Anschaltmodul

Mode selection switch (See table 2.)

ANWaktivFehler

1.SLG2.SLGPower

(screw lock)

01234567

normalECC

Test+ECCINIT normINIT ECCres.res.

Testbetr.

1.SLG

2.SLG

F

Label insertThe English equivalent is on the reserve.

TEST

bzw.

Ventilation slits of the adapter capsuleIt is important to ensure that the slitsare not covered during operation.Forced ventilation is not required.

See chapter 2.2

No.

A3

A2

A1

B1

B2

B3

Green

Yellow

Red

Green

Green

Green

Description

Rapid, irregular flashing indicates that a dialog with the SLG or the mobile data carrier

module is defective.

B1 = 1st SLG

B2 = 2nd SLG

B3 = Power ON:

Note:

Colour

Table 1

Error: The last command was terminated with an error, or the hardware of the

is in use

is in use

This LED is always on as long as the 24 V supply to the module is

(MDS) is currently in progress. This LED is on when presence detection isenabled.

Mobile data carrier within range of SLG. The SLG that has detected the MDS isidentified by the LEDs B1 and B2. (The LED is only on when presence detection isin operation; see chapter 3.1.)

present. Use the STG service and test unit to test the module.

Only one of the two LEDs (B1 or B2) shouldbe on at a time. Check the cabling to the SLG ifboth LEDs are on at the same time.(See chapter 4.2.)

7/28/2019 ASM410_e.pdf

6/42


- 4 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Mode selection switch:

Positions 0 to 7: Setting the mode of operation:

The ASM 410 uses the serial S5 bus. The STG interface is inactive.

Positions 8 to F: Test mode using the STG service and test unit:

Telegrams from the S5 are ignored.

Note: The functionality of the serial S5 bus is not affected by switching to test

mode since it has its own microprocessor and can operate independently of

all MOBY-I activities.

Attention: Remember to perform a new start or RESET after changing the mode selec

tion switch.

Mode of Operation

Table 2

Switch Text Descriptionon Label InsertPosition

0

1

2

3

4

5

6

7

Normal

ECC driver

Test operation

Test + ECC

INIT normal

INIT ECC

Reserved

8

9

F

1st or 2nd SLG

Reserved

Test (only for MOBYI operation)

An STG service and test device can be connected via the9way subminiature D connector so that all MOBY-Ihardware can be tested.

Initialisation of the MDS with the ECCdriver;- Otherwise the same as position 4

Initialisation of the MDS. An INIT command is sent to theMDS at the start of a write command via the processimage. This deletes the contents of the MDS.

The ECC driver is enabled (see chap. 4);- otherwise the same as position 2

All types of MDS can be processed in test mode. The ASM410 tightens up its error controls while communicatingwith the MDS. Weak points and malfunctions can thus be

detected during commissioning.

Read from and write to all types of MDS; the ECC driveris enabled (see chap. 4).

Normal operation; read from and write to all types ofMDS; ECC driver is inactive.

7/28/2019 ASM410_e.pdf

7/42


- 5 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

2.2 Block Diagram

Galvanicisolation

power supply

5 V DC

24 V DC

STG

MOBY-I

MOBY-I processorSI

Clear

Clock

Latch

Ident

S0

GND

+9 V

+24 V

-

-+

Clamp or crimpconnector for SLG

(depends on bus module)SLG

Ext. powersupply

SYAS processor+ shift register

TxDTxD

RxDRxD

EPROM, RAM

S5

Multiplexer

TxD RxD

Interface to1st SLG

Interface to2nd SLG

+ TxD

- TxD

+ RxD

- RxD

RS 422

GND

+24 V

The ASM 410 is equipped with 2 microprocessors (SYAS and MOBY-I processor) which are galvani

cally isolated by 2 optocouplers. As a result, no external interferences can influence the S5. The SYAS

processor (synchronous / asynchronous processor) services the synchronous interface to the S5. It

stores incoming data from the PIQ (process image output) which it then sends to the MOBY-I proces

sor after a short delay via the asynchronous interface. Error detection and telegram repetition via the

3964R procedure make it impossible to disrupt this interprocessor interface. The following rules of

communication apply to both processes:

The SYAS processor always sends the MOBYI processor a telegram when any bit in the PIQ ischanged by the application programmer.

The MOBYI processor sends the SYAS processor a telegram for changes in presence, acknowledge-ment of a command, finished message of a command and return of power. These telegrams appear inthe PII for the user.

Caution:

Telegrams between the SYAS and MOBY-I processors can be lost if the handshake

described in chapter 3.2 is not used.

Power supply:

The SYAS processor receives its power from the +9 V supply of the S5 CPU. This means that the SYAS

CPU services the S5 bus as soon as the S5 CPU is switched on regardless of the 24 V supply. The

MOBY-I processor (and all MOBY-I components) receive their power from the external 24 V supply.During commissioning it is therefore possible to test all MOBY-I components with the STG service and

test unit without having to switch on the S5 CPU (see chapter 7).

7/28/2019 ASM410_e.pdf

8/42


- 6 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

2.3 Pin Assignments

Pin Assignments to STG: RS 422 Interface

Pin Assignment to STG

Pin Function

123456789

Not used+ Transmit+ ReceiveNot used- Receive- TransmitGround (0 V)

Not usedHsg. Cable shield

9way subminiature D connector

+24 V

Terminal Assignments on the Bus Module:

BUS MODULE

(Left Side)

1 3 5 7 9

2 4 6 8 10

1 3 5 7 9

2 4 6 8 10

Bus module with

screw or crimpconnection

Terminal

1

2

3

4

5

6

7

8

9

10

Function

0 V: Ground for ASM 410 and all SLGs and STG

+ TxD

- TxD

+ RxD

- RxD

+ TxD

- TxD

+ RxD

- RxD

Transmit to 1st SLG

Receive from 1st SLG

Transmit to 2nd SLG

Receive from 2nd SLG

Data cablesto 1st SLG

Data cablesto 2nd SLG

(Right Side)

+24 V external power supply for MOBY-I (ASM 410, STG and SLG)

7/28/2019 ASM410_e.pdf

9/42


- 7 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

2.4 Cable Connections of the ASM 410

Number of ASM 410s and Addressing:

PLCs Max. Number ofASM 410s per Station

Addressing Remarks

S5100U 8 *

S595U 4/8 * 8 modules can be used with the S595Ustarting with release status 4/94.

S590U 2 * Limitation to 2 modules due to the powerpack of the SIMATIC S590U

ET 100U 2 Any Cf. chap. 3.6.1

ET 200U 4 Any Cf. chap. 3.6.2

* Slotoriented addressing

0 1 2 3 4 5 6 7S5100U 64

71

72

79

80

87

88

95

96

103

104

111

112

119

120

127

8Slotnumber

Addressallocation for ASM 410

to to to to to to to to

Free slots foradditional digital modules

95U 90U

Overview of Cabling Options:

Service and test unitSTG 4F

Read/write deviceSLG

Read/write deviceSLG

Mobile data carrierMDS

SIEMENS SIEMENS

Mobile data carrierMDS

Bus module of S5100U withASM 410 interface module

7/28/2019 ASM410_e.pdf

10/42


- 8 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Cabling of One or Two SLGs:

B U S MODULE

1

2

3

4

5

6

7

8

9

10Terminal stripon bus module

+24 V

0 V

From external

power supply

Cable shield

1st SLG

Mounting rail

Shield

2nd SLG

Cable incl. SLG connector and open end with coreend ferrule 6GT2091-0D...2

2 MOBY length code

1 The maximum cable length depends on which SLG is connected and thetolerance of the external 24 V supply. (See chapter 2 of MOBY catalogue.)

- RxD

+ TxD

- TxD

+24 V

0 V

+ RxD

- RxD

+ TxD

- TxD

+24 V

0 V

+ RxD

Colour coding3 of cablesupplied by Siemens

3 Colour codinggn = green = Pin 4 in SLG connectorye = yellow = Pin 5 in SLG connectorwh = white = Pin 6 in SLG connectorbr = brown = Pin 1 in SLG connectorpk = pink = Pin 2 in SLG connectorgr = grey = Pin 3 in SLG connector

Max. cable length = 1000 m1

ye

wh

br

pk

gr

gn

ye

wh

br

pk

gr

gn

7/28/2019 ASM410_e.pdf

11/42


- 9 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3. Programming

The ASM 410 is programmed directly by the user. Commands are started and data fetched in STEP5 by

setting and scanning just a few control bits in the process image (PIQ/PII). You can program in an FB ora PB or directly in OB1. A special function block is not required.

3.1 Representation of the ASM 410 in the Process Image

*** The ASM 410 is designed as an analog input/output module and takes up 8 bytes of the

process image. The length of a telegram is therefore 8 bytes.

*** 5 bytes of data on the mobile data carrier are always processed for each command.

*** The user sends a telegram to the PIQ and receives a status (or the results) in the PII each

time a new cycle starts.

The following is transmitted to the ASM from the PIQ:

-- Start of command: read, write, initialise or reset

-- MDS address

-- User data for a write command

The following is returned to the application program from the PII:

-- Command status

-- Error byte for precise error decoding

-- Data read from the MDS

Note:

Multiplexer Operation with 2 SLGs:

Although up to 2 SLG read/write devices can be connected to one ASM 410, only one SLG can be active

at a time. You cannot switch to the other SLG until the active SLG has indicated that it is finished.

If the user issues another command while one is still active, it will be ignored.

Exception:A reset command can be executed at any time. The command currently being processed

will be aborted. If that command is a write command, the reset command will be completed

with an appropriate message.

Caution:

Time-Controlled Program Processing with OB13

The OB13 is called in the SIMATIC during the normal cycle completely asynchronously. This cancause inconsistencies in the PIQ/PII for the MOBY modules. Adhere to the following rules whenprogramming the ASM 410:

a) Do not process an OB13. (System data word SD 97 of the SIMATIC must have the value0". See SIMATIC manual.)

b) If you have to work with OB13, you must disable alarm processing with the AS" command

while MOBY is being processed. After MOBY processing is completed, you must enablealarm processing again with the AF" command. (See example in chapter 3.3.)

7/28/2019 ASM410_e.pdf

12/42


- 10 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

1

2

34

5

6

7

8

01234567

1st

2nd

3rd

4th

5th

byte / INIT

byte

byte

byte

byte01

= SLG no. 1= SLG no. 2

Control byte

Address MSB

Address LSB

User data:5 bytes for a

00 = ACKNOWLEDGE

01 = Read10 = Write/INIT11 = Resetwrite command

PIQ:

Res. Res. Expanded

SLG ON/OFF(presence detection)

Command:

Bit:Byte:

Start addresson MDS

commandRESET4for FB

01

= Normal operation= Dialog

Dialog mode6:

5

1

2

3

4

5

6

7

8

01234567

1st byte / error

Error

Ready

Battery

MDS detected

01

= SLG no. 1= SLG no. 2

Status byte

Address MSB

Address LSB

User data:5 bytes for a

00 = Nothing

01 = Read10 = Write/INIT11 = Resetread command

PII:

(1 = presence)

Bit:Byte:

active

Start addresson MDS

low

ECC correction:1 = ECC correctionwas performed.

2nd

3rd

4th

5th

byte

byte

byte

byte

3

2

1

1 No command was processed since powering up the system or the MOBY CPU has been restarted (failure of 24 V supply).

2 The ERROR bit signals the occurrence of an error. The READY bit is also set. Exact error code in byte 4 of the PII. Bytes 5 to 8 do

not contain valid data.

3 Battery low: This bit can be set by the ASM after each command. It indicates that the battery voltage in the MDS is low. When

Battery low"=1, the MDS will still operate for a certain period of time. To avoid loss of data on the MDS, replace the MDS or the

MDS battery as soon as possible.

4 It is mandatory that this bit be set if you are using the MDS 507/407E. It has the following effect on the PII:

Expanded RESET = 0 ! Bit 4 in the PII indicates that the RAM backup battery is empty. Bit 4 in the PII is set after each

command for MDS models equipped with EEPROM.

Expanded RESET = 1 ! Bit 4 in the PII indicates that the RAM backup battery is empty or a dialogue battery is empty.

The expanded RESET bit may only be set during the RESET command. This bit must be reset during read/write accesses.

5 The SLG ON/OFF bit must be set to 0 before switching the MOBY operating mode.

6 When the dialog bit is set, dialog mode is switched on with the RESET command. The selection mode switch of the ASM 410 must

be set to 0.

Since the VMDS is cleared on the ASM, this bit should be set to 0 again when the RESET command is being used in dialog mode.

Cf. chap. 3.8.

7/28/2019 ASM410_e.pdf

13/42


- 11 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Special Commands

PIQ: During initialisation. (Switch setting 4 or 5. See chapter 2.1.)

1

2

3

4

5

6

7

8

01234567

Control byte

00 = ACKNOWLEDGE

10 = INIT

Command:

Byte

2

Bit:

1= Expanded RESET

00

00

INIT data

00

MSB

LSB

End address +1:

00 00 40 62 bytes00 00 80 128 bytes00 08 00 2 Kbytes00 20 00 8 Kbytes00 80 00 32 Kbytes00 02 F0 MOBY E00 00 C0 MOBY F: MDS F4xx00 00 10 MOBY F: MDS F2xx

MSB LSB MDS Type

The meaning of the PII is identical to the PIQ described above.

PIQ: Expanded RESET (switch setting 0 to 7)

S Switching on the MDS 507/407E operating mode

S Switch on/off MOBIV operating mode

The PIQ (bit 4 of byte 1) is used to parameterize the MDS 507/407E when the ASM 410 is used. tABTAST is

transferred during the reset command with byte 4 in the PIQ.

1

2

3

4

5

67

8

01234567

Control byte

00 = ACKNOWLEDGE

Command:

Byte:

2

Bit:

1= Expanded RESET(See bytes 4 and 5 in PIQ).

1st byte, tABTAST

11 = RESET1

Time value: 00 to 3F

Time factor: 00 = 0.01 sec11 = 0.1 sec10 = 1 sec11 = 10 sec

MOBY

01234567Bit:

01234567Bit:

00 = MOBY I/E91 = MOBY F: MDS F1xx92 = MOBY F: MDS F4xx93 = MOBY F: MDS F2xx81 = Switch MOBYV operating mode on/off

1 The tABTAST parameter is only transferred during the reset command when the MDS 55507/407E" bit is set at the same

time.See the MDS 507/407E description for a detailed description of the handling of tABTAST.

2 It is strongly recommended that this bit be set when using the MDS 507/407E. It has the following effect on the PII:

Expanded RESET = 0 ! Bit 4 of the PII indicates that a RAM backup battery is empty. Bit 4 of the PII is set

after each command for MDS models equipped with EEPROM.

Expanded RESET = 1 ! Bit 4 of the PII indicates that a RAM backup battery is empty or a dialogue battery is empty.

1

2

3

4

5

67

8

01234

XX00

00

00

00

00

01 = Perform FFT

01 = Read00 = ACK

1 = Special command

00

Perform FFT scan (only MOBYF)PIQ:

7/28/2019 ASM410_e.pdf

14/42


- 12 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.2 Timing Diagram of the Control Signals

The control of MOBY-I commands to the ASM 410 is handled by a handshake procedure using the

control signals read/write and ready.

dcba

Read / write:

Ready:

a) Activation of a read or write command is initiated by the user setting bit 0 or 1 in the PIQ.

Note : Ready must be set before start of command.

b) The ASM 410 acknowledges the receipt of a new command while the command itself is executed

at the same time. The acknowledgement with ready = 0 does not have to follow in the next cycle;

several cycles may elapse between a and b.

c) User reset of the read/write control bits:

---> Issue acknowledge command.

This action is necessary so that the next command can be processed by the ASM 410. If no

acknowledge command" is issued, all subsequent commands except the reset command

will be ignored.

d) Completion of command by the ASM 410:

The error bit must be interrogated. User data in the PII is valid up to the start of the next command.

With the next cycle, a new MOBY-I command can be initiated in the PIQ.

Extra care...

... must be taken with the programming when the handshake is interrupted by presence mes

sages, RESET commands and SLG switchovers. The user program can hang up if the pro

gramming is wrong.

Frequent causes:

S The user changes the PII as desired (i.e., in every cycle), and the cycle time in the SIMATIC

is less than 20 msec.

S Frequent occurrence of presence massages. The MDS is located on the boundary of the

SLG, and the cycle time in the SIMATIC is relatively long (i.e., > 100 msec).

S Read/write commands or RESET commands are sent to the MDS when an MDS is present

(e.g., when the MDS is in the border area).

S After a RESET command, the user program does not perform a complete handshake with

acknowledge" and wait for finished message".

By following some simple rules, this problem can be avoided.

1. TIMEOUT monitoring in the user program:

The user sends a RESET command to the ASM when the user program does not receive a

reaction after a suitable amount of time based on the application.

2. Cycle time monitoring in the user program:The PIQ for the ASM is only processed after more than 30 msec have passed since the last

PIQ was processed.

7/28/2019 ASM410_e.pdf

15/42


- 13 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

The following timing diagram shows the exact representation of the data in the PII/PIQ.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

Read

Write

Address

QB 2+3

Write data

QB 4 to 8

Ready

Error

Address

IB 2+3

Read data

IB 4 to 8

Duration of one cycle

Cycle change: Output telegram from ASM 410+ Input telegram from ASM 410

1 2 4 6 8 2 9

10 1010

= Valid data

3 5 7 3

7/28/2019 ASM410_e.pdf

16/42


- 14 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

After a new command is acknowledged by the ASM 410 with READY = 0, the usermust issue an acknowledge command". The acknowledge command" must beissued to the ASM after the command active signal (in PII: ready = 0) is received.The acknowledge command" guarantees that the ASM 410 reports back the resultin the PIQ as soon as this is available.

Start of read command. With the cycle change, the rising READ edge andthe MDS address of QB2 and QB3 are passed to the ASM 410. The address andREADY bit = 0 do not appear in the input telegram of the ASM 410 until the nextcycle change.

The ASM 410 is communicating with the MDS.

After a restart (power on) the ASM 410 comes up with READY.

A RESET must be programmed in the cold start and restart OB.

ASM

Read is completed. The data which was read is located in bytes 4 to 8 of the

The last results remain in the PII until the start of the next command.

Start of a write command; address and data to be written is passed to theASM 410.

Data being written to MDS.

Write command complete: Ready = 1

Command was terminated with an error . The error code is located in byte 4 of

1

2

3

4

5

6

7

8

9

10

No Initiatedby Description

ACKNOWLEDGE command phase :

READY = 1

User

User

User

ASM

ASM

ASM

ASM

ASM

input telegram.

the input telegram.

7/28/2019 ASM410_e.pdf

17/42


- 15 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.3 Programming Example

The ASM 410 which is installed in slot 0 of the S5100U is to activate a read command whenever the

START" flag is set by the user. The handshake procedure described in chapter 3.2 is used in the pro

gram.

The command parameters (address in MDS) are contained in OB21/OB22 (see chapter 3.4).

In the example below, the same addresses are read from each data carrier.

UN I 64.0I 64.1

I 64.7Q 64.0Q 64.1

Q 64.0Q 64.0

I 64.6ERROR

UN

BEB

UNRRBEB

OOBEB

USBEB

Reset command from cold start or restart not yet executed.. or 24 V of ASM failed.... > Wait for ASM to perform reset

If READY inactive, then command being processed.. issue an acknowledge command to the ASM 410

> Wait for ready bit to be set in input

Has a command just been sent to the ASM 410, or not.. yet acknowledged by ASM with ready = 0 ?> Yes: then wait for ready = 0 (this resets bits 0 and 1)

Command executed; completed with errors ?.. If yes, set error flag. Error code in IB 67.. > and abort the operation

********** C O M M A N D E X E C U T E D C O R R E C T L Y *************

UNTIL START OF NEXT MOBY COMMAND, MOBY DATA READARE AVAILABLE IN PII STARTING AT IB 67.

L

L

IW 67

IW 69..

.

. Userrelated processing of data

USBE

STARTQ 64.0

NOTE: After a cold start or restart, this area of the PIQcontains zeros

If START is set, start same command again

U I 64.0I 64.1I 64.7

UUUUN

Q 64.0Q 64.1

If PII indicates that.. reset command has been executed,.. then send an acknowledge in.. PIQ to ASM 410

PB 10:

BEB

UUUUNUBEB

I 64.0I 64.1I 64.7Q 64.0Q 64.1

If programming (with OB13) of the SIMATIC is timecontrolled, the MOBY call must be programmed

as follows:

.

.

.

AS ; Disable alarms and time control

JU PB 10 ; Process MOBY

AF ; Enable alarms

.

.

.

7/28/2019 ASM410_e.pdf

18/42


- 16 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.4 Programming of Cold Start and Restart Procedures

A RESET command for the ASM 410 must be programmed in the cold start and restart OBs

(OB 21/OB 22). This is to ensure that the ASM 410 sends the ready signal. After the reset com

mand, the PLC is synchronised with the ASM 410. In addition, a standard telegram can be issued in

OB 21/22. This is particularly useful if the same data block is always processed on the MDS.

Example: Read (or write) address 30 to 34 (dec.) on the MDS

LT

LT

L

T

BE

KH0000QB65

KB30QB66

KB3

QB64

Start address on the MDS is 30

Issue RESET command for synchronisation

(is sent to the ASM during first cycle change)

OB21 / OB22:

3.5 Application of SLG On/Off" and Presence"

The ASM 410 permits one of two SLGs to be activated via the SLG on/off" control bit without having toprocess a command (see bit 5 of byte 1 in PIQ/PII).

SLG on/off = 1:

The SLG samples its surroundings to see whether a mobile data carrier is present. If one is detected, the

presence bit is set in the status byte of the PII after the next cycle change.

After the MDS has left the magnetic field, the presence bit is also reset in the PII while the SLG samples

the field for the next MDS.

A hysteresis function ensures that the presence bit is not constantly flipped should the mobile data car

rier stop exactly on the boundary of the SLG's magnetic field. This hysteresis function is handled by the

processor on the ASM.

Read/write commands can be sent completely transparently to the ASM 410 for presence monitoring.

Similarly, the presence bit" retains its validity after the start of a command.

SLG on/off = 0:

The user can enable and disable presence monitoring in the PIQ at all times.

If an SLG is deactivated (SLG on/off = 0), a presence bit in the PII will not be returned (i.e., no presence

bit is returned even if the ASM is currently processing a command with the MDS).

This enables projects to be implemented where the stipulated distance between SLGs can be reduced

as desired. The only requirement is that those SLGs situated close to one another be addressed in multiplexer mode. This may be necessary in dynamic operation where large amounts of data have to be

transferred. Stopping the conveyor belt can be avoided by splitting up the data and distributing it

among several SLGs.

Note: Of the two SLGs that can be connected, only one can be activated with SLG on/off" at a

time. When the user changes the SLG no." in the PIQ, the new SLG is activated automati

cally. Errors cannot be evaluated by the user when using SLG on/off=1". If the ASM de

tects an error (e.g., as a result of field interference), no presence bit is reported in the PII.

The error message is not sent until a read/write command is sent to the ASM.

7/28/2019 ASM410_e.pdf

19/42


- 17 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Function Diagram:

MDS

SLG

B

a

b

L

Hysteresis field for

Transmission window:

Exchange of data betweenMDS and SLG

presence monitoring

h

bc

L, B: Dimensions of the transmission window of anSLG read/write device at operational distance toMDS (see manual)L = Field length; B = Field width

h: Hysteresis: Area in which the data carrier remains detectedafter it has been detected (cf. below)

a) The point at which the data carrier is detected by the SLG.

Its presence is reported in the PII.

Starting now, the queued MOBY command is now executed on the MDS. The presence bit re

mains set.

b) The MOBY command must be completed by this point as the data carrier is leaving the

transmission window.

The presence bit remains set.

c) The presence bit is reset in the PII. The MDS has passed out of range of the SLG.

Length of the Hysteresis Field (at operational distance Sa): h

The length of the hysteresis field depends on the SLG and MDS model. The following applies:

0.1 mm < h < 15 mm

7/28/2019 ASM410_e.pdf

20/42


- 18 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Example of an SLG On/Off Application:

All pallets on a transfer line are to be counted by a MOBY station. In addition, a 6digit identification num

ber is to be read from each pallet. This task is to be performed by an SLG without proximity switches.

Error if

command = readREADY =0;Presence = 0

be read completelyMDS could not

Reset pallet counterIssue MOBY command

Control byte : RESET commandSLG ON/OFF=1

Startreadcommand

If command = read,then forward data

(not for reset)

Wait forend of command

READY=1

Step palletcounter

Waitforpresence = 1

SendACK command

to ASM

Waitfor

READY=0

Diagram:

*

Wait forpresence = 0

Status 4

Status 1

Status 2

Status 3

Overall start

* A new read command can be started immediately after the data carrier just read has passed out

of range of the SLG.

Programming of Cold Start and Restart:

OB21/OB22

L KH0023 Reset command; SLG on/off = 1T QB64

L KB0T QB65

L KB0 Start address on MDS = 0T QB66BE

7/28/2019 ASM410_e.pdf

21/42


- 19 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Programming in a Function Block with STEP 5:

FB10SEGMENT 1 Wait for Ready from ASM 410

U I 64.0 The system waits for a newU I 64.1 .. data carrier following a

U I 64.7 .. cold start or restartS STATUS4UN STATUS1JC =NXTUN Q 64.1UN I 64.7UN I 64.5S ERROR BEBUN I 64.7BEB > MDS could not be read completelyU I 64.6 Check for errorsS ERROR BEBR STATUS1 Switch to next statusS STATUS2U I 64.1 Command was not a read command BEB > Data not processed L IB67 )

: )L IB68 ) Process the 6digit number read : )

L IB69 ): )

BEBNXT:***

SEGMENT 2 Wait till MDS has left the SLG window

UN STATUS2JC =NXTU I 64.5BEBR STATUS2S STATUS3 Switch to next statusR Q 64.1S Q 64.0 Set Start bit for read BEA

NXT:***

FB10SEGMENT 3 Wait for command acknowledgement from ASM 410

UN STATUS3JC=NXTU I 64.7BEBR STATUS3 Switch to next status if acknowledged S STATUS4R Q 64.0BEA

NXT:***

SEGMENT 4 Wait for new data carrier

UN STATUS4

JC =NXTUN I 64.5 Wait for presence = 1BEB

Queued read command executed automaticallyif new MDS detected

R STATUS4S STATUS1 Switch to program status 1L PALCNT Step pallet counterL KB1+FT PALCNT

NXT:BE

Note: The user can place the program variables anywhere in the flag area.

7/28/2019 ASM410_e.pdf

22/42


- 20 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.6 Using the ASM 410 as Decentralized Periphery

3.6.1 Use in the ET 100U

CPU

ET 100U

ET 100U

Max. of 32 ET 100Us

Max. cable length3000 m

Max. of 2 ASM 410s per ET 100U

SIMATIC

DI DQ DQ

Central controller: S5115US5135US5150US5155U

The ASM 410 is used in the ET 100 as an analog module. If the module is being parameterised with COM

ET 100 software, it must be specified with 4AXfor the corresponding slot. The ASM 410 occupies 8 input

and 8 output bytes (i.e., 16 bytes). Since up to 32 bytes can be used by each ET 100 in the process

image of the central controller, a maximum of 2 modules can be used with each ET 100. If other modules

(in addition to the ASM 410) are to be used in an ET 100, only one MOBY-I module can be installed.

The ASM 410 in the ET 100 can be addressed from every address area of the PLC (P, Q, IM3 and IM4).

General notes:

The ASM 410 interface module cannot replace the ASM 400 module (the S5 modules used for MOBY-I)

used during operation with the ET 100U.

MOBY operation with the ET 100 is not recommended for applications in which large amounts of data

have to be processed, or very fast controller response times are involved.

Bear these points in mind when designing your system.

Special programming notes:

A characteristic of the ETAS308 interface module in the central controller is that it transfers data to

and from the peripherals (ET 100Us) regardless of the cycle change of the S5. The incorrect programming sequence then causes the 8byte command telegrams to be forwarded to the ASM 410

with incorrect data.

7/28/2019 ASM410_e.pdf

23/42


- 21 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Note: Bytes 2 to 8 must sent first in the command telegram (e.g., PIQ) and then the start of a com

mand in byte 1 (control byte) with the transfer command. Individual bits in the control byte

cannot be set and reset.

If the MOBY interface module receives an incomplete command (as described above), it will be ignored

until the read or write bit is recognised in the control byte.

Data is transferred from ET 100U to S5 independently of the shift cycle in an ET 100U. This may, however,

cause incomplete response telegrams to be received by the central controller.

Only after an additional delay corresponding to the total data transmission time" of the system, can the

user be sure that all data are available in the PII in the central controller.

Note: When the READY bit is set in the PII in response to a read command, the user must start a

timer with a time equal to/greater than the total data transmission time" of the system. Only

when this timer has expired can the user be certain that the data is available in the PII for

further processing.

Calculating the total transmission time of the system:

(See pages 3-24 ff of chapter 3 of the ET 100U Manual.)

As per formula on page 3-35:

t trans max A max B max= t + t + t C + t C

Transmission distance I/O bus

Time for I/O bus transmissioncan be assumed tobe a constant of 8 msec.(i.e., transmission of 8 byteson the I/O bus)

Applicable to the ASM 410:

t trans max A max B max= t + t + 8 msec

Calculation as shownin manual of ET 100U

Therefore: the wait time required by the system in an average configuration is between 10 and 70

msec. This corresponds to between 1 to 5 cycles of the controller.

Diagram of the Read Sequence:

Start readcommand

Wait forReady = 0

Sendack. cmd.to ASM

Wait forReady = 1

Start timerwith trans

mission time

Wait until

timer expires

Processread data

7/28/2019 ASM410_e.pdf

24/42


- 22 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Programming Example :

Three (3) bytes are to be written to the data carrier starting at address 5. The data to be written is inFY 10 to FY 12. The ASM 410 is located in the Parea at address 80.A new data carrier is to be written each time a rising edge occurs on the start switch".

ON I 80.0ON I 80.1ON I 80.7JC =M002L KB0 Issue acknowledge after resetT QB64 ..command

M002: UN START )R EFSTART ) > Edge flag for STARTUN I 80.0 )UN I 80.1 )BEB )U I 80.7 )JC =NXT1 )L KB0 ) identical to example in chap. 3.3T QB80 * )BEA )

NXT1:O Q 80.0 )

O Q 80.1 )BEB )U I 80.6 )S ERROR )BEB

If read command, then start timer here with systemtransmission time before read data become valid

UN STARTBEB > No new command startU EFSTARTBEB > No new rising edge from StartS EFSTART **** START COMMAND ****L KB0 Specify address MSBT QB81L KB5 Specify address LSB...T QB82L FW10T QB83L FW13 ...and write data...

T QB85L FY14 ...in PIQT QB87L KH0002 Start write command T QB80 **BE

* Output of ACKNOWLEDGE command" may not be performed with 2 RESET output bit" commands as in the example in chapter 3.

** The command start must be the last action (unconditional) when issuing the command.

3.6.2 Use in the ET 200

The ASM 410 may be used in the ET 200 under the following conditions:

- ET 200s equipped with an ASM 410 must be operated in slow mode". See the ET 200 Manual forsetting of slow mode".

- The ASM 410 is parameterised with the COM ET 200" software.:

S ET 200U in acc. w. Siemens standard: The ASM 410 module must be parameterised with 095 or

223. The 223 parameterisation is somewhat slower. The 8 bytes of the process image are always

consistent.

S ET 200U in acc. w. DP standard: The ASM 410 module must be parameterised with 4AX or 243.

- Up to four ASM 410s can be driven from one ET 200. If DI/DQ or other I/O devices are also driven by

the ET 200, the maximum number of ASM 410s is reduced.

- The response to a read command is available immediately if the ready bit is set. Using a timer to wait

for the read data (see ET 100U) is not necessary here.

Otherwise, the conditions described in chapter 3.6.1 apply.

7/28/2019 ASM410_e.pdf

25/42


- 23 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.6.3 Use with SIMATIC S7 via ET 200U

Configuration:

PROFIBUS

S7300/400 ET 200U

24 V

ASM 410

SLG 1

SLG 2

PROFIBUSDP

Programming Example:

DB 100 is used for indirect addressing as the global data block. System functions SFC 14 and SFC 15

must be programmed for the data transmission to and from the ASM 410. These functions must be called

cyclically.

The write data are stored starting at DBB 22.

The read data are available starting at DBB 33.

SLG switchover is handled here via I 0.7.

Input 0.1 is programmed as the start command.

AUF DB 100

CALL DPWR_DAT //Write SFC 15 to DP slave

LADDR :=W#16#80 //Addresse 128

RECORD :=P#DB100.DBX 20.0 BYTE 8 //Length 8 bytes

RET_VAL:=DB100.DBW10 //SFC 15 error message

CALL DPRD_DAT //Read SFC 14 from DP slave

LADDR :=W#16#80 //Addresse 128RET_VAL:=DB100.DBW11 //SFC 14 error message

RECORD :=P#DB100.DBX 30.0 BYTE 8 //Length 8 bytes

U DBX 30.0 //RESET was performed

U DBX 30.1 //in startup OB 100

U DBX 30.7

R DBX 20.0 //Then send acknowledge

R DBX 20.1

UN DBX 30.0 //If no RESET performed, then

UN DBX 30.1 //wait here

BEB

UN DBX 30.7 //If finished inactive, then

R DBX 20.0 //send acknowledge

R DBX 20.1

BEB

O DBX 20.0 //If command was started and

O DBX 20.1 //finished not yet returned,

BEB //then wait here

U DBX 30.6 //Error occurred?

S A 8.0 //Set output 8.0

BEB //and stop program

U E 0.1 //Start read command

= DBX 20.0 //with input 0.0

U E 0.7 //Input 0.7 causes switch

= DBX 20.2 //to SLG 2

BE

7/28/2019 ASM410_e.pdf

26/42


- 24 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.7 Processing Mobile Data Carriers

Mobile data carriers with different memory capacities are available. The versions currently available are:

- 62 (42)* bytes RAM (e.g., MDS 115)

- 128 (112)* bytes EEPROM (e.g., MDS 213E)

- 2 (1.7)* Kbytes RAM (e.g., MDS 302)- 8 (7)* Kbytes EEPROM (e.g., MDS 413E and 438E)

- 32 (28)* Kbytes RAM (e.g., MDS 505, 506 and 515)

752 (658)* bytes EEPROM (MOBY E)

40 bits fixed code (MOBY F MDS 1xx)

32 bytes EEPROM (MOBY F MDS 2xx)

256 bytes EEPROM (MOBY F MDS 4xx)

* Net capacity in ECC mode

7/28/2019 ASM410_e.pdf

27/42


- 25 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Addressing of the data carriers is linear from address 0000 to the end address. The ASM determines the

amount of memory on the MDS automatically. The user receives an error message if an address beyond

the end of the MDS is specified.

Addressing KH KY KFNormal with ECC Normal with ECC Normal with ECC

62-Byte Data Carrier with RAM

Start address 0000 0000 00,00 0,0 + 0 + 0

End address 003D 0029 00,61 0,41 + 61 + 41

128-Byte Data Carrier with EEPROM

Start address 0000 0000 00,00 00,00 + 0 + 0

End address 007F 006F 00,127 0,111 + 127 + 1112-Kbyte Data Carrier with RAM

Start address 0000 0000 00,00 00,00 + 0 + 0

End address 07FC 06F1 07,252 06,241 + 2044 + 1777

8-Kbyte Data Carrier with EEPROM

Start address 0000 0000 00,00 00,00 + 0 + 0

End address 1FFC 1BF1 31,252 27,241 + 8188 + 7153

32-Kbyte Data Carrier with RAM

Start address 0000 0000 00,00 00,00 + 0 + 0

End address 7FFC 6FF1 127,252 111,241 + 32764 + 28657

752-Byte Data Carrier with EEPROM (MOBY E)

Start address 0000 0000 0,0 0,0 + 0 + 0

End address 02EF 0291 2,239 2,145 + 751 + 657

Read out ID no. (can only be read in one piece)

Start address 1FF0 31,240 8176

Length 0004 0,4 4

MOBY F MDS F1xx (5 Bytes)

Start address 0000 0,0 + 0

End address 0004 0,4 + 4 MOBY F MDS F2xx (32 Bytes)


End address 001F 0,31 + 31

Read out ID no. (can only be read in one piece)


Length 0004 0,4 + 4

MOBY F MDS F4xx (256 Bytes)


End address 00FF 0,255 + 255

Read out ID no. (can only be read in one piece)Start address 0000 0,0 + 0

Length 0004 0,4 + 4

7/28/2019 ASM410_e.pdf

28/42


- 26 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.8 Dialog Operation

The dialog function of MOBY I can be used to transfer data from one interface to another.

To switch on dialog mode on the ASM 410, the user must set bit 3 (i.e., a control byte of the PIQ) and then

perform a RESET. Cf. chap. 3.1. The mode selection switch on the ASM 410 must be positioned to 0.

Note:When dialog mode is on, the module can only be reset by turning it off.

When dialog mode is switched on, the VMDS is cleared.

If the RESET command is repeated, the VMDS is not cleared if bit 3 of the control byte is set to 0.

3.8.1 How is the MOBYI Dialog Set Up?

The following figure shows dialog communication with MOBYI.

SLG_N SLG_D

MOBY-I interfacein normal operation(e.g., ASM 400 in SIMATIC S5)

Read or writethe VMDS with FB 250

Station_N

MOBY-I interfacein dialog operation(e.g., ASM 410 in SIMATIC S5)

Station_D

VMDSRead/write/initialize theVMDSwithFB 41 or via PIQ(Cf. chap. 3.1.)

Station_N reads/writes the VMDSthrough the clearance in air.

7/28/2019 ASM410_e.pdf

29/42


- 27 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Station_N Normal ASM from MOBY I (i.e., ASM 400, ASM 410, ASM 420, ASM 440,ASM 450, ASM 470 and SIM4x). The user operates station_N in the usualway (i.e., as if the user wanted to exchange data with an MDS).

SLG_N An SLG (i.e., SLG 41, SLG 42, SLG 43 and SLG 44) which is connected tostation_N.

Station_D Dialog ASM from MOBY I (i.e., ASM 400, ASM 410, ASM 450 and ASM 470).While being turned on, station_D is parameterized with a user command asdialog ASM. During parameterization, a 16Kbyte memory area is definedon station_D. This memory area is called VMDS(i.e., virtual MDS). It is used as communications memory. Processing ofstation_D by the user is the same as with the program on station_N.Station_D uses the same tools as station_N (e.g., FB 47).

SLG_D An SLG (i.e., SLG 41, SLG 42, SLG 43 and SLG 44) which is connected tostation_D.

VMDS Virtual mobile data carrier. The VMDS is a 16Kbyte memory area onstation_D. The VMDS is specified and cleared when station_D is turned onand parameterized.

Designation Explanation

7/28/2019 ASM410_e.pdf

30/42


- 28 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

3.8.2 How Does the User Work with the MOBYI Dialog?

ExampleThe user program on station_D issues a write command containing the data to be transferred. The com

mand is executed immediately. The data are now available in the VMDS. This concludes the job of

station_D. The user program on station_N issues a read command. At this time, SLG_N and SLG_D

may not yet be facing each other in the transmission window. As soon as SLG_D enters the transmis

sion window of SLG_N, the desired data are read. The data are read from the VMDS and transferred to

the user on station_N. The green ANW LED on each ASM indicates the presence of a dialog SLG/ASM.

Communication time during dialogThe same times apply to the configuration of the communication time as described in the MOBY catalog.

tk = 16 msec + 0.8 msec * nbyte

Transmission window during dialog

The transmission window of SLG_D to SLG_N has a polarization direction (i.e., SLG_D and SLG_N mustbe positioned at certain angles to each other). The following figure shows the transmission window

during dialog.

Sa

Sg

View of side

View of top

L

B

SLG_D

SLG_N

Direction of movement fromSLG_D to SLG_N

Sa = Working distanceSg= Limit distance

L = Length of the transmission windowB = Width of the transmission window

Positioning of SLG_D

Transmission window

Enlargement of the transmission window when SLG_D andSLG_N use minimum working distance

7/28/2019 ASM410_e.pdf

31/42


- 29 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Field data during dialog operationThe following table lists the field data during dialog operation. Dimensions are shown in millimeters.

Length of the 60 230 600 3000transmissionwindow (L)

Width of the trans- 30 80 280 1300mission window (B)

Working 0 to 15 0 to 70 20 to 250 200 to 1000distance (Sa)

Limit distance (Sg) 30 130 450 2500

Distance from > 200 > 800 > 2000 > 10000SLG to SLG (D)

All Specificationsin mm

SLG 41-

SLG 41

SLG 42-

SLG 42

SLG 44-

SLG 44

SLG 43-

SLG 43

Dialog with ECC

ECC mode must always be off during dialog operation.

New start of an ASM 410 as station_D

When dialog operation is turned on, the ASM 410 checks to determine whether the SLG is correctly

connected and powered. If not, the red LED permanently indicates a triple flashing pattern. Process

image PII does not give the user an error message.

7/28/2019 ASM410_e.pdf

32/42


- 30 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

4. The ECC Driver

The ECC driver (Error Correction Code) is an option in the ASM 410 firmware. It is set during commis

sioning with the mode selection switch:

Mode selection switch in position 1, 3 or 5 ! ECC driver is on.

Use:

The ECC driver provides additional assurance of accurate data on the MDS. Manufacturers of MDS

models equipped with EEPROMs guarantee up to 10,000 write operations only. If the ECC driver is

used, you can continue to use the MDS until the actual end of its life and still be assured of accurate

data.

The ECC driver can also be used for the MDS models equipped with RAMs in situations in which

extremely high levels of interference are likely to disrupt communications.

Call:

When installing the system, all the programmer has to do is make sure the mode selection switch is set

correctly.

1 ! Read and write MDS with ECC

3 ! Read and write with stricter error checking (with ECC)

5 ! Initialise MDS with ECC

All other parameters, such as

- setup of MDS data structure

- start address- programming and interrogation via PIQ/PII

do not need to be modified.

Function:

The ECC driver divides MDS memory into 16byte blocks (14 bytes of user data and 2 bytes of ECC

information). At least one block is read or written each time the MDS is accessed. This slows down

access to the MDS data (see table in catalogue). If an ECC MDS is read without the ECC driver

(e.g., with switch = 0 or with the STG), the ECC bytes between the user data can be recognised. If

an ECC MDS is written without the ECC driver, the data structure of the MDS is destroyed. The MDS(i.e., the destroyed data block) can no longer be read by the ECC driver.

Data Correction:

If at some time the MDS loses a bit of data (e.g., as can happen when EEPROM MDSs are overwrit

ten very frequently ), the ECC driver is able to reconstruct the lost data bit. The user is assured of

correct data. The user can examine and evaluate the correction via a status bit ( bit 3 of byte 0) in

the PII (e.g., to determine whether prompt replacement of the worn out" MDS is required).

7/28/2019 ASM410_e.pdf

33/42


- 31 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

Example:

Data structure of a 62byte MDS. This table is for clarification purposes only and can be ignored by

the programmer/user).

MDS Address fromUser's View Point

Address on MDS Meaning

0

1617

293031

3233

454647

48

61

1415

27

2829

41

ECCECC

ECCECC

1

131415

ECCECC

01

13

14 bytes of user data



An incomplete block at the end of MDSmemory cannot be used for user data.

1st block

2nd block

3rd block

Please note:

- More time is needed to access MDS data (less data can be processed in dynamic mode).

- The net capacity of the MDS is reduced (see chapter 3.7).

- The results of a data correction may be delayed by up to one second.

- A normal" MDS must be initialised before being commissioned with an active ECC driver

(e.g., with an STG).

7/28/2019 ASM410_e.pdf

34/42


- 32 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

5. Error Evaluation

An error detected by the interface module is indicated as follows :

- - Red LED: Flashing pattern corresponds to the error number.

The flashing pattern will continue until the 24 V supply of the ASM 410 is turned off.

- - Error bit set in bit 6 of the status byte of the PII

The SLG number addressed is also stored in the bit 2 of byte 1 of the PII.

The exact error code is always located in byte 4 of the PII.

The error bit and error code remain stored in the PII until a new command is started (or the PLC is turned

off).A reset command is not required after an error occurs. Instead, you can start a new read or write com

mand immediately after error evaluation.

ASM errors: Meaning, causes and remedies

General:

0 0 0

Error indication

01234567

PII, Byte 4 FlashingPattern ofRed LED

Description

______ Once No communication between ASM and SIMATIC has taken place yet.-> Perform reset via the PIQ.

00000011

(03)

3times Error in the connection to the SLG. The SLG does not answer.-> Cable between ASM and SLG is wired incorrectly, or cable break.-> 24 V supply voltage is not connected or is not turned on.-> Hardware defective: ASM 410 or SLG

00000100(04)

4 times Error in the memory of the MDSThe MDS has never been writeaccessed, or its memory was lost during a batteryfailure (only with a RAMMDS).-> Replace MDS (if the battery bit is set).-> Initialise MDS with STG.-> Initialise MDS via SIMATIC.

(Mode selection switch in position 4 or 5)

00000101(05)

5 times Unknown commandThe user has issued a command to the MDS which it cannot interpret.-> Access to address greater than address area of the MDS

-> The ASM 410 was started in switch position 4 or 5 (i.e., initialisation)with a read command. Only write accesses are permitted duringinitialisation.

Meaning for MOBY-F-> Read/write area is protected by password.-> FFT command with presence monitoring-> Operating mode is not suitable for the command (e.g., MOBY-I with

FFT command).-> Switch position 4 (INIT) with read/write command

00000110(06)

6 times Field interference on the SLGThe SLG is receiving interference from the environment.-> External field of interference; the interference field can be

determined with the inductive field indicator" of the STG.-> The distance between two SLGs is too small and does not meet

the configuration guidelines.-> The connection cable to the SLG is receiving interference, is too

long or does not meet specifications.

7/28/2019 ASM410_e.pdf

35/42


- 33 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

PII, Byte 4 FlashingPattern ofRed LED

Description

00000111(07)

7 times Too many sending errorsDespite several attempts, the MDS was unable to receive the command or the writedata from the ASM correctly.-> The MDS is right on the border of the transmission window.-> Data transmission to the MDS is being disturbed by external

interferences.

00001000(08)

8 times CRC sending error-> Monitoring has detected an error during sending. This can only

happen when the mode selection switch is in position 2 or 3.-> Cause: Same as error 00000110

-> MDS reports a great number of CRC errors.-> MDS is in the boundary area of the SLG.-> Hardware of MDS and/or SLG is defective.

00001001(09)

9 times Only during initialisation (mode selection switch in position 4 or 5):CRC error for receipt of acknowledgement by MDS-> Cause: Same as error 00000110

Meaning for MOBYF-> Wrong MDS type for expanded RESET command (MOBY parameter)

00001010(0A)

10 times Only during initialisation (mode selection switch in position 4 or 5):MDS cannot execute INIT command.-> MDS is defective.

00001011(0B)

11 times Only during initialisation (mode selection switch in position 4 or 5):Timeout during initialisation-> MDS is right on the border of the transmission window.-> MDS is using too much power (defective).

00001100(0C)

12 times Memory of MDS cannot be writeaccessed.-> Memory of MDS is defective.-> EEPROMMDS was writeaccessed too often (i.e., is worn out").

00001101(0D)

13 times Address errorAddress area of MDS was exceeded.-> Start address in bytes 2 and 3 of PIQ was specified incorrectly.-> MDS is not the right model.

00001110(0E)

14 times ECC error (selection mode switch in position 1, 3 or 5):MDS cannot read the data.-> MDS data have been lost (MDS defective).-> MDS was not initialised with ECC driver.-> Initialise MDS.-> MDS EEPROM is defective. Data have been lost.

-> Replace MDS.-> MDS was moved out of the field while being writeaccessed.

-> MDS is not positioned correctly.

00001111(0F)

15 times MOBY-F: Driver error-> Internal error-> FFT command with MDS F1xx in the field

00011011(1B)

27 times MOBY-F: Checksum error-> CRC check in data telegram is not correct.-> Data distorted-> Interface defective

7/28/2019 ASM410_e.pdf

36/42


- 34 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

6. Transmission Times

The following time diagram shows a MOBY command sequence from command start" to command

ready".

S5 SYAS MOBY

User program incl.ASM 410programming andscanningtheASM 410

Start MOBY command in user program

S5 cycle change: One S5 cycle change requiresan additional 2 msec for each ASM 410 regardlessof what task is being executed at the time.

Transfer command from SYAS processorto MOBY CPU: 20 msec

MOBY processor executes MOBY command:Time: Example:

16 msec + n x 0.8 msecn = number of bytes to be transferred to MDS = 5

-> t = 20 msec

Acknowledgement telegram (does not affectexecution of MOBY command) from MOBY CPUReady = 0

Transfer result to SYAS CPU: 20 msecReady = 1

Send ACKNOWLEDGE command to ASM 410(does not delay execution of MOBY command)

During next cycle change, SYAS CPU sendsresult to S5 and thus PII.

Result is now available to user.

There are two primary factors which determine transmission speed.

a) The serial transmission via the SYAS processor

- Transfer command to MOBY 20 msec

- Transfer acknowledgement telegram to PII 20 msec

- Transfer ACKNOWLEDGE command to MOBY 20 msec

- Transfer result to PII 20 msec

Total 80 msec

b) The cycle time on the PLC

Four (4) to six (6) PLC cycles are required to process each command. At a cycle time of

10 msec, this means an average time delay of 50 msec.

When a RAMMDS is used, the time required for communication with the MDS is approxi

mately 20 msec. This time is not included when transmission time is calculated.

The following rule of thumb applies if larger data blocks are to be processed on the MDS.

t (100 bytes)> 2.6 seconds (Depending on the cycle time of the PLC)

7/28/2019 ASM410_e.pdf

37/42


- 35 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

7. Commissioning

a) Insert the module in one of the free slots (0 to 7) and secure in place.

Note: Turn the coding pin" on the bus module to position 6" before installing the module.

Otherwise, the module cannot be inserted.

b) Connect the external power supply and the SLG to the screw or crimp terminal on the bus mo

dule.

-> Make sure wiring of 0 V and 24 V, and cable shield are correct.

c) Turn on the24 V supply voltage.

LED B3 on the front panel must go on. Now use the STG to check that the MOBY components are

functioning properly and the wiring is correct (mode selection switch in position 8; the PLC can

remain off).

d) Set the desired command type on mode selection switch (positions 0 to 5).

(Operation with the S5 will now be tested.)

e) Program a reset command in the cold start and restart OB (chapter 3.4).

f) After the PLC is turned on, you can monitor the process image of the ASM on the PG with

FORCE VAR".

In this example, the ASM 410 has address 64.

0000 0011

00

00

00

00

00

00

00

QB64

QB65

QB66

QB67

QB68

QB69

QB70

QB71

PIQ:

After the reset command, the PII looks like this:

1000 0011

00

00

00

00

00

00

00

IB64

IB65

IB66

IB67

IB68

IB69

IB70

IB71

PII:

7/28/2019 ASM410_e.pdf

38/42


- 36 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

h) Now start the issued command by setting bit 0 (or bit 1) in the control byte.

0000 0001

00

05

00

00

00

00

00

PIQ: Start reading (from SLG no. 1)QB64QB65

QB66

QB67

QB68

QB69

QB70

QB71

No change

You will receive a reset ready bit" in the PII.

0000 0001

00

05

00

00

00

00

00

PII: IB64IB65

IB66

IB67

IB68

IB69

IB70

IB71

Ready bit = 0; read command echo: bit 0 = 1

The address is returned as echo.

LEDs B1" and A2" must light up on the ASM 410: SLG no. 1 is active.

Error: If an error occurs in this or one of the following steps and the ready bit" and

the error bit" are set in the status byte of the PII, continue error evaluation as

described in chapter 5.

i) Acknowledge execution of the command in the PIQ with ACKNOWLEDGE command".

0000 0000

00

05

00

00

00

00

00

PIQ:

7/28/2019 ASM410_e.pdf

39/42


- 37 -6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

8. Technical Specifications of the ASM 410

Weight 0.25 kg

Storage temperature -25 C to +70 C

Ambient temperature

SIMATIC installed horizontally 0 C to + 60 CSIMATIC installed vertically 0 C to + 40 C

Relative humidity at 25 C (without condensation) 15% to 95%

Operational voltage range 24 V (max. of 10% residual ripple)20 V to 30 V

Current consumption

+9 V from S5: Average 20 to 60 mA(20 mA = long cycle time)(60 mA = short cycle time)

Maximum 110 mA (S5 in STOP)

+24 V external: All SLGs off 90 mASLG 40 in operation 180 mASLG 41 in operation 180 mASLG 42 in operation 270 mASLG 43 in operation 340 mASLG 44 in operation 170 mA

Power consumption

Average (without SLG) 2.5 W

Cooling Convection cooling

Transfer rate to S5 125 KbaudIn 5bit blocks; with a 90 msectime gap between two blocks

Transfer rate betweenSYAS and MOBY processors 9600 baud

Transfer rate to mobile data carrierDependent on - MDS model

- ECC operation (See chapter 2 ofcatalogue.)

Average (16 + n x 0.8) msec

Programming Direct via process image PIQ/PIINo function block required5 bytes are processed per command.

Isolation group C in accordance with VDE 0110

Protection rating IP20 in accordance with IEC529

Mechanical stress IEC 68-2-27

Dimensions (W x H x D) 45 x 135 x 100 mm

7/28/2019 ASM410_e.pdf

40/42


- 38 - 6GT2002-0BA00

RD: 12/98


(4) J31069D0125U001A07618

9. Warnings

7/28/2019 ASM410_e.pdf

41/42

7/28/2019 ASM410_e.pdf

42/42

Documents

ASM410_e.pdf