moby i asm 420 interface module - siemens...aaaa11 aaa = address of asm on sinec l1 bus (asm is...

s

MOBY IASM 420 Interface Module

Technical Description Release 07/99

ASM 420 Technical Description 6GT2 097--3AF00--0DA2

--- 1 ---RD: 07/99

6GT2002---0CA00 ASM 420 / V.24 Subject to change without notice!6GT2002---0CB00 ASM 420 / RS4226GT2002---0CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

Contents

1 General Features 2

2 ASM 420 Hardware 32.1 Technical Data 42.2 Pin Assignment 52.2.1 Assignment of Basic Connector X1 52.2.2 ASM 420 Connector System 62.3 Setting the Mode of Operation 72.4 Hardware Configuration 102.4.1 System Configuration 102.4.2 Power Supply 122.4.3 TTY Cabling 132.4.4 RS 422 Cabling 142.4.5 V.24 Cabling 142.4.6 STG Cabling 152.4.7 SINEC L1 Cabling 152.4.8 SINUMERIK Cabling 182.4.9 DI/DO Cabling 20

3 Programming the ASM 420 Module 213.1 Software and Driver 213.2 Telegram Layout 223.2.1 Standard Telegrams 223.2.1.1 System Commands 233.2.1.2 Process All MDS Types (Normal Operation) 253.2.1.3 ECC Special Driver Active (All MDS Types) 263.2.2 SINUMERIK Telegrams 283.3 Protocols 353.3.1 3964R Protocol 353.3.2 Lauf Protocol 363.3.3 SINEC L1 383.4 Telegram Examples 39

4 Cold Start and Restart 42

5 DI/DOs and Proximity Detection 435.1 Proximity Detection with 2 DIs 455.2 Field Scanning as Proximity Detection 475.3 Proximity Detection with Field Scanning and 1 DI 49

6 SLG and MDS Configuration and Installation Guidelines 50

7 Error Diagnosis and Error Messages 51

8 Warnings 59

ASM 420 Technical Description6GT2 097--3AF00--0DA2

--- 2 ---RD: 07/99

6GT2002---0CA00 ASM 420 / V.24Subject to change without notice!6GT2002---0CB00 ASM 420 / RS4226GT2002---0CC00 ASM 420 / TTYJ31069-D0100-U001-A1-7618

1 General Features

The ASM 420 interface module is a general-pupose module with a serial interface that allows MOBY-Icomponents to be used with any computer or PC.

. AnSLG41, SLG42, SLG 43and SLG44 read/write device canbe operated on an ASM420.

. The module is a single-height Eurocard and can be inserted in any standard rack.

. The ASM 420 can be addressed using the following protocols.--- 3964R--- Lauf--- SINEC L1

. A special telegram format for SINUMERIK is provided by the 3964R protocol. Up to fourASM 420 modules can be operated on a single SINUMERIK serial interface.

. Up to16ASM420modules, eachwith a digital input andoutput, can be operated on a serialinterface (with RS 422 and TTY user interfaces only).

. Three versions of the ASM 420 module are available:ASM 420 / RS 422 ---> 6GT2002---0CB00ASM 420 / V.24 ---> 6GT2002---0CA00ASM 420 / TTY ---> 6GT2002---0CC00

. Three LEDs allow the operational status of the ASM 420 to be monitored.

. The module can be switched to dialog mode via expanded parameterization with theRESET command.

. Starting with version release 7, the ASM 420 can be operated with an SLG 65 of MOBY-V.Parameterization is performed with the RESET command. Cf. chapter 3.2.1.1.


--- 3 ---RD: 07/99


2 ASM 420 Hardware

CPU

EPROM

Basic connector (X1)

Fuse(T 315 mA)

Switch bank (S1)for setting mode of operation

3 LEDs:Red LED: indicates a fault (see chap. 7)Yellow LED: indicates that the SLG device is activeGreen LED: indicates that an MDS is present

9-way subminiature D connector (screw locking)(X2) for connecting the SLG read/write device(The SLG can also be connected via the basicconnector if desired).

Pin Function

123456789

Free+ transmit+ receiveFree--- receive--- transmitGround (0 V)+ 24 VoltFree

Housing Cable shield

Pin Assignment on ASM

MOBY

Erroraktiv

ANW

Pin Function

6

1

4

5

2

+ Send+ Receive

--- Receive--- Send

Ground (0 V)+ 24 Volt

3

Cable shield

Pin Assignment on SLG


--- 4 ---RD: 07/99


2.1 Technical Data

Environmental conditions:--- Operating temperature: 0 ˚C to +55 ˚C--- Storage temperature: ---40 ˚C to +70 ˚C

Protection rating in acc.w. IEC 529: IP 00

Serial interface (to computer/PC):--- Transmission rate: 2400 to 9600 Baud (38.4 kBaud)--- Protocol: 3964R

SINEC L1LaufSINUMERIK protocol

--- Cable lengths: TTY 1000 m (shielded)RS 422 1000 m (shielded)V.24 30 m (shielded)

Serial interface (to SLG):--- Transmission rate (gross): 19200 Baud--- Protocol: Asynchronous; 8 data bits; even parity

MOBY-I: MDS protocol--- Cable lengths: SLG dependent; max. of 1000 m

(see cable configurations inMOBY catalogue)

Power supply: 20 to 30 V DC

Current consumption:--- Max. off-load current: 200 mA

(no SLG; DOs off-load)--- Max. current consumption of the SLG: 300 mA

Dimensions:--- L x W x H 160 x 100 x 20 (mm)

Weight: 0.2 kg

DI/DO; Select; Request; Error; ANW:--- Digital inputs: 3

Non-floatingLogical “0”: 0 V to 8 VLogical “1”: 15 V to 24 V(Ri = 10 kOhm)Delay: < 10 msec

--- Digital outputs: 5non-floating(internal power supply)Short-circuit proofImax = 200 mA (per DO; or for 2 DO’s)

--- Max. cable lengths: 100 m


--- 5 ---RD: 07/99


2.2 Pin Assignment

2.2.1 Assignment of Basic Connector X1

Z4Z6Z8Z10Z12Z14Z16Z18Z20Z22Z24Z26Z28Z30X32

b2b4b6b8b10b12b14b16b18b20b22b24b26b28b30b32

Power supply

Serial interface to user

Optional control and signal line

Optional SLG connection

Protective ground (shield)

Z2

V.24 RS 422 TTY

--- ---RxD--- ---

R+D+D---

+EM+SE--- ---*

V.24 RS 422 TTY

TxD---

GND

E+R---E---

---EM---SE--- ---

b2

b4

b6

b8

b10

b12

b14

b18

b16

b20

b22

b24

b26

b28

b30

b32

z4

z2

z6

z8

z10

z12

z14

z16

z18

z20

z22

z24

z26

z28

z30

z32

DI0

DO0

SLG receive +

SLG transmit +

0 V

DI1

DO1

Select module (Select)

SLG receive ---

SLG transmit ---

2 digital inputs andoutputs each for con-trolling data carrier

0 V

Interface (type dependent)

24 V

Interface (type dependent)

( )Protective ground

ASM has user data oracknowledgement (Request)

Error code (same asred LED) (same as green LED)

2 digital inputs andoutputs each for con-trolling data carrier

( )Protective ground

Presence (ANW) 2)

R+ (Terminating resistor) TxD (Transmit data)

E+ (Receive) RxD (Receive data)

D+ (Transmit) +EM (Receive)

R--- (Terminating resistor) ---EM (Receive)

D--- (Transmit) +SE (Transmit)

E--- (Receive) ---SE (Transmit)

* Pin b8 must not be connected in TTY mode.

2) The presence of an MDS is indicated on this pin with 0 V level.


--- 6 ---RD: 07/99


2.2.2 ASM 420 Connector System

Connector: The connector used with the ASM 420 is a 48-way male connector conforming toDIN 41612, design F, whose soldering pins are bent at 90˚. Only rows z andb are assignedand soldered permanently to the ASM 420.

Socket: Female connectors conforming to DIN 41612, design F must be used as mating compo-nents for the ASM 420 connector. All 48-way, ”-type female connectors conforming toDIN 41612, design F” are suitable.

Various types of female connectors are available. Examples:

--- With soldered connection

--- With a screw connection

--- As wire wrap model

Example: SFL 0,5 / F 32 / 2 B:

10.5 23.6 14.8

Female connector with screw con-nection 0.5 mm2; rows z and bassigned.

z b d

Design:

--- 3 rows of connectors

--- Number of contacts: 32 (2 rows, each with 16 contacts)

--- Contact principle: insulation displacement connector with double-sided contact spring

--- Snap-in hooks and elements to ensure secure contact between male and female connectors


--- 7 ---RD: 07/99


2.3 Setting the Mode of Operation

Switch bank S1:

4 532ON 1 7 86

Setting the procedureto the user

Control of MDS

ON

OFF

=̂

=̂

“1”

“0”

Control of MDS:

Theoperatingmodes shownbelow simplify operation andmonitoring of the datacarrier by the user (seechapter 5 for more detailed information).

Switch7 8

Function

0 0 No control of data carrierProximity detection is disabled

The DIs/DOs can be programmed as required using the system command.

0 1 Proximity detection via ASM firmwareDIs can be used as required and interrogated by the DI/DO command.

1 0 Proximity detection using DI0 and DI1, wherebyDI0 = 1 MDS entersDI1 = 1 MDS leaves

1 1 Proximity detection using DI1, wherebyDI1 = 1 MDS leavesDI0 is not used and can be interrogated by the status command.*

* The RESET command can be used to set a time factor for field scanning when MDS 507 is used. Cf. chapter 3.2.1.1. Thissetting is not available when SINUMERIK is used.

When operating mode ”D0” or ”90” is used (see page 24), switches 7 and 8must be placed in this position. The NEXT command may not be used.


--- 8 ---RD: 07/99


Setting the protocol

Switch

1 2 3 4 5 6

b b 1

b b 0 01 1

b b a a 1 0

Function

3964R: ASM = Slave

3964R: ASM = MasterStandard 3964R protocol for all interfacesThe system processes standard telegrams from the ASM.b b = baud rate (see below)

SINUMERIK 850/880 protocol (no response telegram)Connection of ASM to SINUMERIK3964R protocol (cf. chapter 3.3.1); ASM = SlaveInterfaces: RS 422 or TTY;Maximum of 4 ASMs on one interfaceIf only one ASM is being used with SINUMERIK, an ASM with a V.24 in-terface may also be connected.

Switch: 3 4 ASM address (=a a)0011

0101

0123

(always present)

b b = Baud rate (see below)

b b 0 1 0 0b b 0 0 0 0b b 0 1 0 1b b 0 0 0 1

These switch settings are not used at this time.

(The ASM does not function with these switch positions.)

Baud rate (= bb)

(Applies to Lauf, 3964R and SINUMERIK protocols)

0 0 x x x x0 1 x x x x1 0 x x x x

9600 Baud4800 Baud2400 Baud

0 00

Caution: When SINUMERIK is used, some type of presencedetection must be switched on with switches 7 and 8.

1 1 x x x x 38400 Baud (not approved for TTY interface)


--- 9 ---RD: 07/99


Switch

1 2 3 4 5 6

Function

SINEC address

1 1 1 11 1 1 01 1 0 11 1 0 0

1 11 01 0 1 01 0 0 11 0 0 0

1 1 101 10 010 1010 0 0

0 0 1 10 0 1 00 0 0 10 0 0 0 1

23456789

10111213141516

4 3 2 1

a a a a 1 1

aaa = address of ASM on SINEC L1 bus(ASM is always a slave.)The address is set as follows:

SINEC L1

SINEC addresses 17to 31 cannot be seton the ASM and aretherefore notavailable.

The system processes standard telegrams from the ASM;RS 422 and TTY only.

b b 1 1 0 1

The system processes standard telegrams from the ASM;all interfaces can be used.

Lauf protocol

b b = Baud rate

0 1 1 0 0 1

3964R protocol; ASM = slaveBaud rate = 4800 Baud

STG interface

The telegram format, which is used internally by MOBY, is irrel-evant as far as the user is concerned.ASM 420 user interface: RS 422

Switch:


--- 10 ---RD: 07/99


2.4 Hardware Configuration

2.4.1 System Configuration

SIEMENS

Computer/PC

RequestSelectSerial

interface*DIDO

SIEMENS

SLGread/writedevice

The SLG read/write device can be connec-terd to either the X1 basic connector or the9-way subminiature D connector X2.

One select linefor eachASM 420

One request linefor eachASM 420

Serial

interface

PLC, PCor

computer

Please note:

The Select and Requestlines may be omitted ifonly one ASM 420 isbeing driven from aserial interface. The ex-ternal wiring of unnec-essary signals can alsobe omitted.

* Daisy-chain mode isonly possible with theRS 422 and TTY inter-faces.

SLGread/writedevice

Max. length of the selectand request line:100 m (cf. chap. 2.4.9)

4 or 8 ASM 420 can beconnected in standardMOBY housings. Max. of 16 ASM 420

in daisy-chain mode


--- 11 ---RD: 07/99


ASM 420 interface modules can operate in daisy-chain modewhen usedwith RS 422 or TTY user inter-faces. This allows up to 16 interface modules to be driven from one serial interface.

To achieve this, the ASM 420 must use either the 3964R or Lauf protocols (not SINUMERIK). The com-puter/PC must have one digital input (DI) and one digital output (DO) for each ASM 420.

Mode of operation:

Programming the ASM:The computer/PC selects the requiredmodule using “Select” and then transmits the job telegramto the module.

Command processing:The ASM then processes the command, the length of time for which varies from command tocommand. Command processing can take any length of time (if no MDS is in the window).

Transmission of result to user:The ASM indicates that it has a telegram to send by setting the “Request” bit. This is picked upbythe computer/PC, which selects the module using “Select”. The selected ASM then sends theresponse telegram.

Job telegramto ASM

Responsetelegramfrom ASM

t2t5t4t2t1t3

Data

Request

Select

t1 > 30 msec : Delay between Select and start of data transmission (debouncing time of the Select signal)t2 > 0 : Delay between end of data transmission and deselection of the ASM 420t3 = command dependent : Execution of user command by ASM 420t4 > 0 : Time from “Request active” and selection of the ASM 420t5 = 10 to 30 msec : Time between selection of the module and transmission of the response telegramt6 < 30 msec : Deselect time: The ASMcan still send a response telegram to the user during this time (debouncing

time of the Select signal during deselection)

*

Select scan by ASM

**

Responsetelegram from

ASM

t6

Data

Request

Select

t2

Select timing when theresult of a command isavailable immediately af-ter the job telegram

Important: * When the response telegram is involved, the ASM only scans “Select” at the beginningof a transmission. If “Select” is deactivated during the telegram transmission, the ASMalways sends the complete telegram to the computer. This ensures that no garbled tele-grams are sent by the ASM.

** “Select” must be activated for the entire duration of a job telegram.


--- 12 ---RD: 07/99


2.4.2 Power Supply

The cable between the ASM 420 and the SLG read/write device consists of 6 cores plus shield. 4 ofthese cores are assigned to the serial data interface and 2 to the power supply for the SLG read/writedevice. Themaximum length of the data cables can, depending on the physical interface, be up to1000m. The maximum permitted cable length is usually shorter if the 24 V supply for the SLG read/write de-vice is used by the ASM 420. Themaximum cable length also depends on the voltage drop. The follow-ing table gives an overview of permitted cable lengths.

Con-ductordiame-ter inmm

ResistanceΩ/km *)

SLG 40 / SLG 41(I=90 mA)

SLG 42 (I=180 mA)

Max. cable length for

UV = 30 V

0.3

0.5

0.8

1.0

1.4

550

185

70

50

24

120

360

950

1000

1000

240

720

1000

1000

1000

UV = 24 V UV = 30 V

40 100

120 300

310 790

440 1000

920 1000

SLG 43 (I=250 mA)

UV = 24 V UV = 30 V

30 70

85 210

230 570

320 800

660 1000

UV = 24 V

Max. cable length for Max. cable length for

SLG 44 (I=80 mA)

UV = 24 V UV = 30 V

90 200

250 650

700 1000

1000 1000

1000 1000

Max. cable length for

Con-ductorcrosssectionin mm2

0.07

0.2

0.5

0.8

1.5

*) The values for resistance are average values and refer to the feed and return conductors. A singleconductor has half the quoted resistance.

If cable lengths longer than those in the table are required, the 24V supply for theSLG read/write devicemust not be used by the ASM 420. Instead, a 24 V supply must be fed directly to the SLG.

Highlighted field:The standard shielded LiYCY 6 x 0.5 cable recommended by SIEMENS. This cable is available fromSIEMENS under the order number 6GT2090--0A...1).

24 V supply to ASM 420:Themaximum length of the power supply cable for theASM420 is restricted to 20m. If a longer cableis used, or several ASMsare supplied from a single cable, the voltagedrop on the supply cable to theASM 420 and SLG read/write devicemust be considered individually. If necessary, the cross sectionof the supply cable must be increased.


--- 13 ---RD: 07/99


2.4.3 TTY Cabling

TxD

RxD

Max.length1000 m

+

+

TxD

RxD

ASM 420 (passive) Computer (active)

b4z4b6z6

X1

---SE+SE---EM+EM

X21---9

SLG

b30/z30

The ASMmodule does not contain power sources for the active part of the TTY interface. Should, how-ever, it becomenecessary for the ASM to power the interface, the active part of the ASMshould bewiredas follows.

TxD

RxD

Max.length1000 m

TxD

RxD

RR

R

R

ASM 420 (active)

b4z4b6z6

b32

z2

X1

Computer (passive)

X21---9

SLG

b30/z30

The resistors R should each have a value of 470 Ohms if a current loop of 20 to 30 mA is present(P = 0.5 W).


--- 14 ---RD: 07/99


2.4.4 RS 422 Cabling

TxD

RxD

*)

Max.length1000 m

ASM 420 Computer

X21---9

SLG

b4

z4b6

b8z6z8

X1

*)E---

D---

D+

E+

b30/z30

+5V

**

**

*) The cable can be terminated on the receiver side by setting jumpersz4 -b4 and z8 - z6. Thiswill increase the system’s immunityto interference. When daisy chain mode is used (cf. chap. 2.4.1), the jumpers may only be wired on the last ASM 420.

**) The terminal resistors shown in the drawing must be present on the computer side (R = 220 to 1000 Ohm). If lines are short,these resistors can be wired on the ASM side. Jumpers z6 - z8 and b4 - z4 are then omitted. 2 jumpers are added:b4 - b6 and z6 - b8.

2.4.5 V.24 Cabling

TxD

RxD

TxD

RxD

Example of standard cabling

ASM 420 Computer

Max.length30 m

b32

b6z4

X21---9

SLG

X1

b30/z30

V.24 control lines (e.g., DSR, DTR, RTS andCTS) are not supported by the ASM. The acknowledgmentof data is handled at the protocol level.


--- 15 ---RD: 07/99


2.4.6 STG Cabling

TxD

RxD

1

9

+

ASM 420 STG 4

Max. length fotest cable100 m

E---

D---

D+E+

X1

z2

z8

b8

b6z4b320V

X21---9

SLG

24 V

b30/z30

z6

b4

The SLG can be operated directly with the STG 4 via a cable, or the complete distance can be tested viathe ASM 420, as shown above.

2.4.7 SINEC L1 Cabling

The ASM 420 can only be operated on SINEC L1 via RS 422 or TTY.A maximum of 16 ASM 420modules can be connected to one SINEC L1 bus. The SINEC L1 address isdetermined by switches on switch bank S1 of the module.

Additional information on configuring andprogramming theSINECL1bus canbe found in theSINECL1bus system manual, order no. 6ES5998---7LA11.

Bus topology: ASM 420 / RS 422 on SINEC L1

Control computer

CP530

RS 485

..........

Max. 1000 m

BT 777(Busterminal)

0B1B2B3B4B

*)

SINEC L1master(addr. 0)

TTY interface(with power supplyfor BT 777)

ASM 420

addr. 1ASM 420

addr. 2ASM 420

addr. 16

SLG SLG SLG

z4 z8b6b8 z4 z8b6b8 z4 z8b6b8z6b4


--- 16 ---RD: 07/99


Or: Topology for 2 km bus:

ASM 420

addr. 8

Control computer

CP530

BT 777(Busterminal)

0A1A2A3A4A

0B1B2B3B4B

..........

Max. 1000 mMax. 1000 m

..........

or1A2A3A4A

1B2B3B4B

b6b8z4z8

z8b6b8

*)*)

ASM 420

addr. 1ASM 420

addr. 9ASM 420

addr. 16

RS 485

*) The driver block on the ASM 420 must be terminated at the end of the SINEC L1 bus:jumpers from pin z6 - b8 and pin b4 - b6.

Note: The ASM 420 on the BT 777 is wired differently on the “A side” of the terminal thanon the “B side”.

Pin ass. X1 ASM 420BT 777 BT 777

SLGSLGSLGSLG

z6b4

Pin ass X1 ASM 420

z4

The addresses of the individual ASMs can be distributed as required on the bus.The power supply of the ASM module is not shown in the diagram.

Note:No other L1 device may be driven from this bus if an ASM 420 with an RS 422 interface is connecteddirectly to the SINEC L1 bus. If other L1 devices are to be connected to the L1 bus (e.g., programmablecontrollers), the ASM 420 with a TTY interface must be operated on the BT 777 bus terminal.

Caution: During installation, it is essential that layout, wiring, and connection to ground of thecable shield be correct. If not, the bus will be very sensitive to interference. Strongfields of interference (e.g., thunder storms) may destroy the hardware of the ASM 420and the bus terminal.


--- 17 ---RD: 07/99


Bus topology: ASM 420 / TTY on SINEC L1

220 V

24 V

220 V

5 V

+---

+---

BT 777busterminal

BT 777busterminal

BT 777busterminal

BT 777busterminal

SIMATICPLC 100U

TTYinterface

Control computer

CP530

220 V

24 V

220 V

5 V

+---

+---

BT 777busterminal

SIMATICPLC 100U

ASM 420

addr. 1ASM 420

addr. 2

SLG SLG

15---waysubmin. Dconnector,slide lock

Customer’sdistributionbox

A separate distribution boxmust beprovided if the ASM420 is to beoperated via the bus terminal on theSINEC L1 bus. The distribution box performs the following functions:

--- Provide 5 V DC to the bus terminal

--- Provide 24 V DC to the ASM 420

--- Adapter between the 15-waybus terminal connector and the32-wayASM420maleconnector

--- Housing for the bus terminal

--- Housing for the ASM 420

--- Optional: distribution of DI/DO of the attached ASM 420 (not shown in the diagram)

When an indirect bus setup via theBT777bus terminals is used, data canbe sent to and received fromaASM 420.In this case, a bus station which sends a command to ASM 420 will receive a response telegram in re-turn.


--- 18 ---RD: 07/99


2.4.8 SINUMERIK Cabling

The cabling shown below can also be used to connect any computer with the 3964R protocol. This en-ables up to 4 ASM 420 to be driven from one physical interface. Take note of the telegram structuredescribed in section 3.2.2.

Connection diagram

Dig.I/O

CP 315 / 373

DPR

COM

MPR

PLC NC

ASM 420

No. 2

ASM 420

No. 3

ASM 420

No. 4

ASM 420

No. 1

One hardware sig-nal per ASM 420indicates that anMDS is in theSLG’s transmissionwindow.

ASM 420 / TTY:Can be driven directlyon CP 315 / 373

ASM 420 / RS 422:Can only be drivenby CP 315/373using a V.24!RS 422 adapter

ASM 420 / V.24:One ASM 420 only (no.1) can be driven direct-ly by CP 315/373.

3964R protocolviaCP315 or CP373 module

SLG SLGSLG SLG

The Hardware signal:The hardware signal is on the DO0 output of the ASM 420 (see chapter 5).The presence of an MDS is indicated to the PLC by a falling edge on DO0.


--- 19 ---RD: 07/99


Control of the 3964R protocol:

If more than one ASM 420 (max. of 4) is being operated on a single physical interface, ASM no. 1 isalways the master protocol (i.e., ASM no. 1 picks up the “DLE” following the “STX” in the case of com-mands from the CP).ASM no. 1 must always be present.

TTY interface

CPorcomputer

Passive

+TxD

--- TxD

+RxD

---RxD

Max. 1000 m

470

+24 V

470

+24 V

Active Passive Passive

.......

470

470

.......

* * *

* * *

Dig.inputs

*) This line must be looped through from the computer to the last ASM.

SLG

ASM 420 no. 1 ASM 420 no. 2 ASM 420 no. 4

b14

b4

b6

b14

z6

z4 b4

b6

b14

z6

z4b4

b6

SLG SLG

z2

z2

b32

b32

z4

z6

See also section 2.4.3.Where possible, the computer should handle the active part of the TTY interface, inwhich case the resis-tors shown on ASM no. 1 will not be needed.

If this is not possible (as shown in the diagram), the active part of the interface must be simulated in theconnector of ASM no. 1 using 4 resistors (R = 470 Ohm).

The numbers in the diagram refer to pins in the 48-way female connector.

Note: With this cabling, all the wired ASMs must actually be connected. Otherwise an openelectric circuit will be created.


--- 20 ---RD: 07/99


RS 422 interfaceSee section 2.4.4

CPorcomputer

+E

---E

+D

---D

Max. 1000 m

.......

.......Enable Enable Enable

Dig.inputs

SLG

ASM no. 1 ASM no. 2 ASM no. 4

SLG SLG

z4z8

z4z8

z4z8

z4z8

b6b8

b6b8

b6b8

b6b8

b14 b14 b14

2.4.9 DI/DO Cabling

Cable lengthmax. 100 m

(shielded or unshielded)

220 V AC

24 V DC

DO 1

DO 2

DI 1

DI 2

Imax = 200 mA

(per DO or

Relay, miniature motorlamps, etc.

Proximity switch+ ---

total current)

ASM 420

z2

z14b14

z12

b12

b2


--- 21 ---RD: 07/99


3 Programming the ASM 420 Module

3.1 Software and Driver

Various drivers for the control computer are available to the user.

3964R protocol:

PC users: 3964R driver for MS-DOS usersUses PC interfaces 1 and/or 2The driver can drive 4 interfaces if additional hardware is included.Runs on IBM-XT, IBM-AT 01, IBM-AT 03, Siemens PC 16-05, Siemens PC16-20, Siemens PC 32-05, PG 750 and compatibles

System SX microcomputer :3964R protocol available as standard

ES 120: Can be called up directly in BASIC using the commands PUT, REQUEST orRECEIVE. (See ES 120 manual and example in section 3.4.)

SICOMP M: ASM connected via DU04 module(Set byte 3 of the parameter record to hexadecimal 80 and then transfer theparameter record to the DU04 with the “PARAM” command.)

SINEC L1:

Where a CP530 module is being used, COM 530 software is also available for configuring and testingthe bus. Standard function blocks handle communication between the user and the CP530 module.

TheDF301XandDF32L1modules are available for all AT-compatible PCs. A SINECL1 package runningunder either FlexOS, MS-DOS, C-DOS XM or C-DOS 386 can be used to program the module.

Lauf:

The simplest way of communicating with ASM 420; for all computers that do not support 3964R orSINEC L1 (see section 3.3.2 and programming example in section 3.4).

SINUMERIK interface:

The computer interface is available for telegram control if the SINUMERIK is connected via a CP315 orAS512.

The SINUMERIK protocol can also be used with any computer or PC that supports the 3964R protocol.


--- 22 ---RD: 07/99


3.2 Telegram Layout

General:The telegrams shown in this section contain user data only. Additional bytes transmitted for protocolcontrol are described in section 3.3.

3.2.1 Standard Telegrams

The standard telegrams shown below are identical for all types of MDS and are provided for the

. 3964R

. SINEC L1

. Laufprotocols.

General telegram layout:

AB Command Stat. Command specific data

Byte: 0 1 2 .............. n

The command related data are described in more detail in thefollowing pages. The minimum length is 00 and the maximum datalength 253 bytes.

The status byte always has the value 00 when the command is output.The byte will have the following value in a response or error telegram.

The available commands are described in the following pages.They are divided into:--- System commands (see section 3.2.1.1)

Process all types of MDS normally (write/read/initialize) (see section 3.2.1.2)ECC driver active: process all types of MDS (see section 3.2.1.3)

------

Number of bytesLength of user data in telegram (no. of characters minus AB byte)

Minimum: AB = 2AB = 254 (depends on the length of the data blocks specified in the command)Maximum:

Batt.1 Batt.2 ECC E r r o r c o d e (00 to 1F)

Bit: 7 6 5 4 3 2 1 0

000102030405060708090A0B0C0D0E0F10

19

1D1E1F

No error (default)ANW error: MDS not in field when command activeANW error: MDS passed SLG without command.Error in connection to SLG

Too many transmission errors

INIT: Timeout during initializationINIT: Write error during initialization

ECC mode: Data in MDS incorrectReset signal following return of power

Previous command is active.

ASM command aborted with RESET

ECC correction was performed (data in responsetelegram OK)

Only for MDS 507/407E: Status of the dialog battery on the MDS

Battery voltage on MDS has fallen below threshold level.

(Detailed errordescription:see chap. 7)

Not enough RAM on the ASMIncorrect no. of characters in telegram

MDS memory error (not initialised)Unknown command from ASMField interference on SLG

INIT: CRC errorINIT: MDS cannot be initialized.

Address error

Next command invalid

(This bit is always set in the case of MDSs with EEPROM memory.)

1 = Battery too lowWith other MDSs, the bit can have a value of 0 or 1.


--- 23 ---RD: 07/99


3.2.1.1 System Commands

Command table:

Comm.(hex.) Description

00 RESET 1) 2)

01 Check status 1)

DI/DO command 1)06

07 Next

Returns the status byte as the response. The status command canbesent to the ASM at any time. The ASM replies to it immediately. It canbe used to check whether an MDS is present.Note:The ANWbit in the acknowledgment is only reportedwhen some typeof presence check is activated (cf. chapter 5).The status command has no effect on the MDS.

ASM is reset. The active command is aborted.The ASM requires about 200msec to execute this command. (The re-set acknowledgment returns the error 1F when an MDS command isaborted.)The following can be set during a RESET with parameter transmis-sion.- Operation with MDS 507/407E- ASM 420 operates as dialog module(CAUTION: Activated dialog operation can only be deactivated byturning off the module.)

- MOBY-V procedure for SLG 65

Two digital output bits can be addressed directly. The response tele-gram contains the value of the two digital input bits.

The following command(s) should refer to the nextMDS. This enablesthe user to initiate a command immediately even when the old MDSis still in the field. TheNEXTcommand should only be used if proximitydetection has been enabled on switches 7 and 8. If proximity detec-tion is enabled, the NEXT command will flip the DOs (see chapter 5).

1) These commands are always accepted by the ASM module and processed with priority treatment.“Check status” and “DI/DO command” do not interrupt a pending MOBY command.

2) Caution:Before processing an MDS 507/407E, an extended RESET command with the parametertABTAST > 0 must be transferred to the module.


--- 24 ---RD: 07/99


Detailed telegram layout:

00(RESET)

01(Status)

06(DI/DO)

07(Next)

02 00 00 02 00 00

02 00 0F

02 01 00

02 06 xx

03 01

02 06 xx

02 07 00 02 07 00

0 0 0 DI1 DI0 DO10/1 DO0Bit: 7 6 5 4 3 2 1 0

Control DOs Read DIs

0 DOs must be set or reset.1 DOs to be OR-linked or left unchanged

(interrogate DI/DO only)

--- --- --- --- --- ---

Status/error

ANW/BUSY

0 0 0 ANW0 BusyBit: 7 6 5 4 3 2 1 0

1 MDS command to ASM active0 No command to ASM active;

ASM can be programmed withread/write commands

0 No MDS in window1 MDS in window

0 0

Command Command Telegram to ASM 420 Response Telegram from ASM 420

RESET signal followingpower failure:is automatically transmittedonce when power returns

RESET withparametertransfer

05 00 00 02 00 00Param. 00

Scan intervals(Cf. MDS 507/407E description)

00 = Continuous scanning forANW check with fieldscanning (default)

Time value: 01 to 3F (is multiplied by thetime base)

Bit: 7 6 5 4 3 2 1 0

Time base: 00= Time value times 10 msec01= Time value times 100 msec10= Time value times 1 sec11= Time value times 10 sec

tABTAST*

When dialog is activated, errormessage 03 is returned if noSLG is connected to the ASM.

00 = No specialparameterization

81 = Activate dialog.C0 = Activate MOBY-V

procedure.D0 = MOBY-V w. ANW Switches 7 and 890 = MOBY-I w. ANW must be on 00 (cf. chap. 2.3).

*) Function of tABTAST (important for MDS 507):If noMDS is in the field, the ASMcontinuously scans its surroundings for anMDS.When anMDShas been detected (i.e., ANW=1, green LEDON), the surroundings are only scanned at the time interval specified by tABTAST. This means that the ANW signalcan only be removed at the tABTAST time intervals.


--- 25 ---RD: 07/99


3.2.1.2 Process All MDS Types (Normal Operation)

Command table

End Addr. +1

CommandHex. Description

50

51

18

Read data block from MDS

Write data block to MDS

Decimal

80

81

24 Initialise MDS62 bytes RAM MDS: 0.1 sec

sec128 bytes EEPROM MDS: 6

8 kbytes EEPROM MDS: 25 sec32 kbytes RAM MDS: 2 sec

00 00 4000 00 80

00 20 0000 80 00

MDS Type INIT Duration

2 kbytes RAM MDS: 0.3 sec 00 08 00


*) If an error was detected, the response telegram will always be 3 bytes in length.

Command Command Telegram to ASM 420 Response Telegram from ASM 420 *)

50

51

18

05 50 00

02 Command Error

Address LNG

AB 51 00 LNG D1 to Dn 02 51

06 18 00 Data

Where: D1 to Dn User data (max. of 248 bytes per command)

LNG

Address

AB

Length of data block (max. of 248 bytes)Note:

Start address of the data to be processed on the MDS

Number of subsequent characters in telegram

MSB LSB

End addr. +100 MSB LSB

AB 50 LNG D1 to Dn

02 18

end address of the MDS.

MSBLSB = Least significant byte

= Most significant byte

AB = LNG + 5

Data ”Data” is written to the MDS duringinitialisation.

End addr. +1 Memory size of MDS

Address + LNG must be less than the

(40,C0)00** Address

MSB LSB

AddressMSB LSB

**) The status byte of the response telegram depends on the MDS type (status of battery).

(40,C0)00**

(40,C0)00**


--- 26 ---RD: 07/99


3.2.1.3 ECC Special Driver Active (All MDS Types)

The ECC driver

The ECC driver (Error-Correction-Code) can be activated by the command code in the telegram.

Data correction:

If 1 bit of information should be lost from MDS memory at any time (e.g. in the case of an MDS with anEEPROM that has beenwrite-accessed frequently), theECCdriver can reconstruct the lost data bit. Theuser canbe certain of receiving the correct data. The user can examine and evaluate the data correctionusing the status byte in the response telegram (e.g. initiate prompt replacement of the used MDS).

Command table

End addr. +1

CommandHex. Description

40

41

1A

Read data block from MDS with ECC

Write data block to MDS with ECC

Decimal

64

65

26 Initialise MDS62 bytes RAM MDS: 0.2 sec

sec128 bytes EEPROM MDS: 12

8 kbytes EEPROM MDS: 50 sec32 kbytes RAM MDS: 53 sec

00 00 4000 00 80

00 20 0000 80 00

MDS Type INIT Duration

2 kbytes RAM MDS: 4 sec 00 08 00


Where: D1 to Dn User data (max. of 248 bytes per command)

LNG

Address

AB

Length of data block (max. of 248 bytes)Note:

Start address of the data to be processed on the MDS

Number of subsequent characters in telegram

end address of the MDS

MSBLSB = Least significant byte

= Most significant byte

AB = LNG + 5

Data ”Data” is written to the MDS duringinitialisation.

End addr. +1 Memory size of MDS

Address + LNG must be less than the

Command Command Telegram to ASM 420 Response Telegram from ASM 420 *)

40 05 40 00 Address LNGMSB LSB

AB 40 LNG D1 to Dn(40,C0)00** Address

MSB LSB

41

1A

AB 41 00 LNG D1 to Dn 02 41

06 1A 00 Data And addr. +100 MSB LSB

02 1A

AddressMSB LSB (40,C0)

00**

(40,C0)00**

*) If an error was detected, thw response telegram will always be 3 bytes in length.

02 Command Error

**) The status byte of the response telegram depends on the MDS type (status of battery)


--- 27 ---RD: 07/99


Function:

The ECC driver divides MDS memory into 16-byte blocks, of which 14 bytes are user data and 2 bytesECC information. At least one block is read or written each time the MDS is accessed (even if the userhas only specified one byte). This slows down access to the MDS data (see table in catalogue). If anECCMDS is readwithout theECC driver (e.g. by the STG), the ECCbytes between the user data canberecognised. If an ECC MDS is written without the ECC driver, the data structure of the MDS will be de-stroyed. The MDS (or the corrupted data block) will no longer be able to be read by the ECC driver.

Application:

The ECC driver provides increased accuracy of the data on the MDS. Manufacturers of MDSs withEEPROMs will only guarantee up to 10,000 write operations. If the ECC driver is activated, the user canbe assured of data integrity for the entire lifetime of the MDS.For reliability reasons, theECCdriver can alsobeusedwithMDSshavingRAMmemory if extremelyhighlevels of interference are likely to affect the memory of the MDS.

Example:

Data structure of a 62-byte MDS. (The following table is for clarification purposes only and can be ig-nored by the programmer/user.)

MDS Address asSeen by User

Address on MDS Function

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 MDS memory can-not be used for user data.

1st block

2nd block

3rd block



Note:

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

--- The net capacity of the MDS will be reduced.

--- When performing data correction, the response may be delayed by up to one second.

--- A normal MDS must be initialised before going into service with an active ECC driver (e.g., with anSTG).


--- 28 ---RD: 07/99


3.2.2 SINUMERIK Telegrams

SINUMERIK telegrams use the 3964R protocol (see section 3.3.1). The ASM is always the SLAVE.

In addition to the normal SINUMERIK applications, the telegrams described below can also be handledby all computers supporting the 3964R protocol.

The difference between the SINUMERIK telegram and the standard 3964R telegram lies in the ex-tended telegram header. An advantage of this type of telegram is that it allows up to 4 ASM 420 stationsto be driven like a bus by a single serial interface (see section 2.4.8).

The format of the SINUMERIK telegram as used in the System 800 forms the basis for the telegramlayout and the exchange of telegrams between the controller and the ASM.

The requirements for interfacing to SINUMERIK are described in the following section.

The user (SINUMERIK)must always ensure that a command is only sent to one ASM at a time. The nextcommand may only be transmitted after a response telegram has been received. If this rule is not fol-lowed, data on the serial interface may be corrupted, which would result in the ASM aborting the com-mand. The sender would then not receive a response to his command.

A commandmust always be sent from the SINUMERIK to an ASMwhen the corresponding digital inputsignals the presence of an MDS. If data carriers arrive at more than one SLG read/write device at thesame time, they must be processed in sequence by the user.

System commands, as used in the standard telegrams, are not possible with the SINUMERIK protocol.

Note: --- When using the SINUMERIK protocol, one of the proximity detection mechanis-mus described in chapter 5 must be enabled.If this is not done, the ASM will not respond to telegrams.

--- When the SINUMERIK protocol is used, no startup telegram is sent by the ASM420 when power returns.

--- When the SINUMERIK protocol is used, the dialog function cannot be used.


--- 29 ---RD: 07/99


General telegram layout:

Minimum telegram length

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 n (bytes)

DWno.

Telegram header(e.g., AS512)

TEDAL T e l e g r a m d a t a

IDENTIFICATION(ASCII)

fnr(fixedpoint)

User data(coded by user)

(TEDAL + 2)2

(hex)

Data in the telegram header arenot evaluated by the ASM. TheSINUMERIK receives thetelegram header back in theresponse (i.e., positive ornegative).

The DW no. (hex.) iscorrected and returned inthe response telegram. It iscalculated as:

Length of data in telegram.The sum of

and is at least 10 bytes long.

”IDENTIFICATION +fnr + user data”

IDENTIFICATION containsthe type of command andis described below.

Error numbers(see chapter 7)

The length of user dataranges from 0 to 224 bytes.The data can contain anyvalues.

Reading data carriers:

Command telegram from SINUMERIK to ASM 420:

‘T’ 20 ‘C’ ‘R’ 20 20 20 20 00 00I/Fno.

ASMno. Type Amount

IDENTIFICATION fnr User Data

Address

Acknowledgment telegram:

Positive acknowledgment (with data):

‘R’ 20 ‘C’ ‘R’ 20 20 20 20 00 00I/Fno.

ASMno. Type Amount


Data read fromMDS (1 to 214)Address

Negative acknowledgment (with error):

‘T’ 20 ‘C’ ‘R’ 20 ‘F’ 20 20I/Fno.

ASMno.

IDENTIFICATION fnrUser

No. as inlist

Data


--- 30 ---RD: 07/99


Writing to data carrier:


‘R’ 20 ‘C’ 20 20 20 20 00 00I/Fno.

ASMno. Type Amount


Data to be written toMDS (1 to 214)‘W’ Address


Positive acknowledgment:

‘T’ 20 ‘C’ ‘W’ 20 20 20 20 00 00I/Fno.

ASMno. Type Amount


Address

Negative acknowledgment (with error):

‘R’ 20 ‘C’ ‘W’ 20 ‘F’ 20 20I/Fno.

ASMno.

IDENTIFICATION fnrUser

No. as inlist

Data

‘R’ 20 ‘C’ ‘W’ 20 ‘F’ 20 20

RESET command:

‘C’ 20 ‘C’ ‘R’ 20 20 20 20

IDENTIFICATION fnrUserData

00 00I/Fno.

ASMno.

The RESET command can be sent to a specified ASM at any time. It cancels any pending command and is used to synchronize the

ASM with SINUMERIK. The RESET command is best programmed during cold start and restart sequences.

Note: The ASM 420 does not send any further responsemessage or acknowledgment in re-sponse to the RESET command. An acknowledgment can be sent when the RESETcommand cannot be interpreted.


--- 31 ---RD: 07/99


NEXT command:


‘C’ 20 ‘C’ ‘N’ 20 20 20 20


00 00I/Fno.

ASMno.


Positive acknowledgment:

‘Q’ 20 ‘C’ ‘N’ 20 20 20 20

IDENTIFICATION frnUserData

I/Fno.

ASMno.

No. as inlist

Negative acknowledgment:

‘C’ 20 ‘C’ ‘N’ 20 ‘F’ 20 20


I/Fno.

ASMno.

No. as inlist

The NEXT command terminates the dialog with a data carrier.

If a newMDS is to be processed by the ASMwithout previous programming of a NEXT command, the logic in the ASMwill generate

an error.

The NEXT command directly affects the control of the ASM’s digital outputs (see chap. 5).


--- 32 ---RD: 07/99


Description of telegram data (with error numbers):

IDENTIFICATION:

1st byte: T = TransmitR = ReceiveC = CommandQ = Acknowledgment

3rd byte: C = Code carrier4th byte: R = Read

W = WriteN = NEXT commandR = RESET command

6th byte: F = Error telegram

fnr:

Error numbers from ASM to SINUMERIK (see chap. 7 for detailed description):

0001 = Read / write not possible since no MDS present0002 = Error in user data during read (type, address, amount or length of data)0003 = Read operation aborted since MDS has left the window0004 = Error in user data during write (type, address, amount or length of data)0005 = Write operation aborted since MDS has left the window0040 = Error in interface to SLG read/write device0041 = Error in MDS memory0042 = Previous command still active0043 = NEXT command not permitted0044 = Field interference in SLG read/write device0045 = Too many transmission errors0046 = Cannot write to MDS memory0047 = ECC error0050 = MDSbattery nearly discharged (not an error message; this message is transmitted to the user

in the acknowledgment telegram without the “F” identification.This message is standard for all MDSs with EEPROM memory.

0051 = The 2nd MDS battery is nearly discharged.0052 = ECC correction was performed.

Error numbers from SINUMERIK to ASM:

0302 = Watchdog period for response telegram from MDS has expired.! ASM performs a RESET.

All other error messages that the ASM receives are ignored.

I/F no.:

Interface number: This is provided by the user. This number is returned to the user in the responsetelegram (positive as well as negative). This enables the user program to allocate a response telegramto a specific channel.

Since the ASM does not use the “I/F no.” parameter for any other purpose, it can contain any value. Inthe special SINUMERIK environment it contains the numbers 0 to 3 (ASCII) (i.e., hex: 30 to 33).


--- 33 ---RD: 07/99


ASM no.:

Address from 0 to 3 (ASCII) (i.e., hex: 30 to 33). Address of the ASM to which the command isaddressed, or from which a response telegram is received.

The ASM no. is set using the ASM switch bank S1 (see section 2.3).

If more than one ASM is being driven from a serial interface, each ASM will be able to pick up the com-mand. The command will only be executed by the addressed ASM, however.

Type:

Command type: The following numbers are permitted.

0005 = Read/write all types of MDS; ECC = enabled (see section 3.2.1.3)0006 = Read/write all types of MDS; normal operation (without ECC)

Address:

Address specifies the start of a data block on the MDS.It depends on the type of MDS and the type of command.The address is coded in BCD.

Type Comm. Type Start Address

62 byte 5 00000000 ... 00000041

00000000 ... 00000111128 byte

8 kbyte

5

5

MDS

RAM

EEPROM

6

6

00000000 ... 00000061

00000000 ... 00000127

EEPROM 6

00000000 ... 00007153

00000000 ... 00008188

32 kbyte 5RAM 6

00000000 ... 00028657

00000000 ... 00032764

2 kbyte 5RAM 6

00000000 ... 00001777

00000000 ... 00002044


--- 34 ---RD: 07/99


Amount:

Indicates the size of the data block. The maximum size depends on the type of MDS. The number iscoded in BCD.

Type Comm. Type Block Length

62 byte 5 0001 ... 0042

0001 ... 0112128 byte

8 kbyte

5

5

MDS

RAM

EEPROM

6

6

0001 ... 0062

0001 ... 0128

EEPROM 60001 ... 0214

0001 ... 021432 kbyte5

RAM 6

2 kbyte 5RAM 6

0001 ... 0214

User data:

User data are user specific and can be in any format.

The amount of user data varies between 0 and 224 bytes. The user stores his data in a data block. Theuser data of the acknowledgment telegram are stored in a data block.

Other definitions:

If the ASM receives a telegram containing the error identification “F”, it ignores the telegramwithout anyvisible reaction. Some error telegrams are handled internally like a RESET command.

If theASM receives an “unknown IDENTIFICATION”, the unknown IDENTIFICATION is returnedwith theerror identification “F”.


--- 35 ---RD: 07/99


3.3 Protocols

Protocol

3964R

SINUMERIK

Lauf

SINEC L1

Yes

Yes (with CP 315

Yes

No

Yes

Yes (with CP 315)

Yes

Yes (direct connectionto SINEC L1)

Yes

Yes

Yes

Yes (connected viabus terminal)

only 1 ASM permitted)

ASM 420 (V.24/RS 232) ASM 420 (RS 422/RS 485/V.11) ASM 420 (TTY)

3.3.1 3964R Protocol

The 3964Rprotocol provides secure data transmission over a point-to-point connection. Security is pro-vided by transmitting data one block at a time, with parity check, block check character (BCC) andacknowledgment of receipt. All characters from 00hex to FFhex can be sent in the data block.

Feature of SINUMERIK protocol:

Up to 4 ASM 420 stations can be driven from a single serial interface on the computer. Control of theprotocol (command acknowledgment) is always handled by ASMno. 1. The other ASMs (nos. 2, 3, and4) can also pick up the command but the command will only be executed by the ASM specified in thetelegram.

Character frame:

Transmission: AsynchronousBaud rate: 2400, 4800, 9600 BaudData bits: 8Parity: odd parityStop bits: 1

The exact format of the protocol is described in a number of Siemens publications (e.g. order no.C71000-T8700-C25-1.

Control characters used in the 3964R protocol:

Character Code (Hex) Meaning

STXDLE ETXDLENAK

DLE DLE

0210 031015

10 10

Initializes a send procedure (signals readiness to send)End of transmission blockReady to receive (or duplicated DLE in data stream)Negative response following Block Check Error or start character

Duplicated DLE in data block; used when the value 10hex occursin the data stream

undetected


--- 36 ---RD: 07/99


Block transmission sequence:

Sender Receiver

STX DLE

1st user data byte2nd user data byte

Last user data byte

Datablock

DLE ETXBCC

DLE

........

t z = Watchdogtimer on ASM300 msect z

3.3.2 Lauf Protocol

Simple protocol for point-to-point connectionwith a parity check for data security. Thisprotocol doesnotsupport additional acknowledgment or error identification procedures.

The Lauf protocol is not uniform (i.e., the protocol cannot transmit all characters). For this reason, thetelegrams described in section 3.2.1 are recoded if the Lauf protocol is used.

Method:

1 user data byte (hex.) will be transmitted to/from the ASM as 2 ASCII bytes (see example).

Character frame:

Transmission: AsynchronousBaud rate: 2400, 4800, 9600 BaudData bits: 8Parity: odd parityStop bits: 1

Control characters:

STX (= 02hex) Start of telegramETX (= 03hex) End of telegramCR (= 0Ahex) New line (carriage return)

The control characters may not be used as user characters.


--- 37 ---RD: 07/99


Data format:

Data are transmitted as data blocks.

STX(02hex)

Data(only ASCII characters 0 to 9, A to F)

ETX(03hex)

The maximum block length including STX, ETX is 514 bytes.

Block transmission sequence:

Sender Receiver

STX

1st ASCII byte2nd ASCII byte

Datablock

t z

3rd ASCII byte4th ASCII byte

1st userdata byte2nd userdata byte

LastASCII byte

.

.

.

.

.

.

ETX

t z

t z = Watchdog timeron ASM 300 msec

CR*)

*) A CR as the next to the last character in the telegram is optional. The ASM does not necessarily ex-pect one in the command. The ASM always returns a CR in the response telegram.

Watchdog timer:The watchdog timer on the ASM is set to 300 msec for all baud rates (i.e., once the transmission of ablock has been started with STX to the ASM, the next bytemust arrive within 300msec). If thewatchdogtime interval expires, ASM ignores the corrupted telegram.

Data collision:If the ASM and the computer send a telegram at the same time, the ASM acts as the master and is al-lowed to send its telegram immediately. An incoming telegram can be handled by the ASM at the sametime as it transmits a telegram. (The ASM can operate in full-duplex mode.)

Ensuring security of transmission to the ASM 420

Corrupt telegrams and telegramswith parity errors are ignored by the Lauf protocol on theASM, andnoresponse is sent.

By using the status command at the telegram level, the user has a means of interrogating the ASM. Thestatus command returns the status byte immediately in response. Bit 0 of theANW/BUSYbyte indicateswhether the ASM is currently processing a command.


--- 38 ---RD: 07/99


Another way of monitoring transmission is by setting a watchdog timer for the response telegram. Arough guide for the duration of this timer is indicated below.

The ASM requires about 1 second to transmit 1000 bytes of data to/from the MDS,assuming the MDS is already in the transmission window.This only applies to RAM versions.

Example:

Transmission of the RESET command using the Lauf protocol:

Standard telegram (see section 3.2.1):

02 00 00 (hex.)

Telegram currently being transmitted:

02 30 32 30 30 30 30 03 (hex.)

STX ETXRESET command(coded in ASCII)

0A

(CR)

optional

All telegrams described in section 3.2.1 can be recoded in accordance with this method.

Example for read times with Lauf procedure:Reading 1250 bytes with 5 commands at 250 bytes each and a Baud rate to the PC:

9600 Baud: = 4.3 seconds38400 Baud: = 2 seconds

Other processing times on the PC are not included.

3.3.3 SINEC L1

The protocol on the SINEC L1 bus cannot be accessed by the user. It is processed automatically by theSINEC L1 master.

The SINEC L1 master consists of the SIMATIC CP530 module with COM530 software, for example.Standard function blocks (handling blocks) are provided for handling communication with the CP530module (SEND, RECEIVE, CONTROL, SYNCHRON).

Data in the data blocks for theSINECL1 function blocksmust be formatted as described in section 3.2.1(standard telegrams).

The DF30IX or DF32L1 module can be used in all IBM-AT compatible PCs. This permits a SINEC L1master to also be set up on the PC.

Additional information about the structure of the SINEC L1 bus can be found in the manual: “SIMATICS5; Bus System SINEC L1”, order no. 6ES5998-7LA11.

Note:In configurations withmany L1 bus stations, it may take a relatively long time (1 to 2 seconds) before thebus master fetches a telegram from the ASM. This time must be taken into account, particularly duringdynamic operation, if a point is to be set after an MDS has been read by MOBY. Some examples of tele-grams are shown in section 3.4.


--- 39 ---RD: 07/99


3.4 Telegram Examples

Example 1 (with ES120):

The ES120 is to read a data block (address 10 to 19) from the data memory using the 3964R protocol.

The terminal must first be parameterised with the IP command.

Program:

10 MDSA 5H, 40H, 0, 0, 10, 10

20 DIM E#[256], X$[4], Y$[4], Z$[4]30 REQUEST: CHN {1}40 REM Send read command to ASM

50 READ A&, B&, C&, D&, E&

60 PUT: CHN{1} FROM A&, B&, C&, D&, E&, F&70 REM Get result

80 PUT: MAS FROM “IM Get result”

90 RECEIVE E#

100 F% = E#[5:1]110 IF F% 0 THEN 300

120 REM Result in buffer from address 9 onwards

130 PUT: MAS FROM “Data:”, E#[9:10]140 GOTO 400

300 REM Error handling

310 X% = E#[3:1]320 Y% = E#[4:1]330 Z% = E#[5:1]340 X$ = HEX$(X%)

350 Y$ = HEX$(Y%)

360 Z$ = HEX$(Z%)

370 PUT: MAS FROM “Error:”, X$[3:2], Y$[3:2], Z$[3:2]400 RESTORE 10

410 END


--- 40 ---RD: 07/99


Example 2 (with ES120):

A data block is to be read from a 32-KB MDS and displayed:

Addr. 250, length 10 bytes

The system is to wait for the next data carrier following the read operation. The read and display pro-cedure is then repeated.

The program is written for an ES120. The LAUF driver is used. This example can be used for other PCsrelatively easily.

Program flowchart:

General definitions

Wait for telegram

Telegram =NEXT ?

Yes

Send command to ASM:Command = 50

Wait for response

Statusbyte = 00?

YesDisplay responsetelegram on screen.

Output error and error number(wait for error acknowledgment)

telegram from ASM

No

No

10 DIM E#[256], E1$[50], F#[256]20 REQUEST: CHN {1}30 REM NEXT Send command

40 PUT: CHN{1} FROM “020700”50 RECEIVE E#

60 E1$ = E#[3:6]70 IF E1$[1:6] “020700” THEN 400 ; Error80 REM Output chained command

100 PUT: CHN{1} FROM “05400001FA0A”110 REM Get response telegram from ASM

150 RECEIVE F#

160 E1$ = E#[3:6]170 IF E1$[5:2] “00” THEN 400180 REM Display data read

190 PUT: MAS FROM “IM Data:”, F#[15:20]200 GOTO 30

400 REM Output error

410 PUT: MAS FROM “M Error: ”, E1$[1:6]420 END

Program for example 2:

NEXT command to ASM:The next command refers to the next MDS

to enter the transmission window.


--- 41 ---RD: 07/99


Example 3:

Programming of function block calls using SINEC L1 in SIMATIC S5:

64 : KH= 0003;65 : KH= 0100; SINEC L1 header

666768699193

::::::

KH= 3F40;KH= 0001;KH= 003A;KC= MOBY-I, THE RELIABLE IDENTIFICATION SYSTEMKC= NR1

MOBY command executed (see standard telegrams)

; The data read from the data carrier are stored in the DB, starting at data word 69

--- Transmit telegram

:SPA FB247NAME :CONTROLSSNR : KYO,2A-NR : KYO,1ANZW : MW100PAFE : MB102

::U E 8.0:UN M 101.1:U M 150.4:R M 150.4:S M 150.6:SPB FB244

NAME :SENDSSNR : KYO,2A-NR : KYO,1ANZW : MW100QTYP : KCDBDBNR : KYO,150QANF : KF+0QLAE : KF+33PAFE : MB102

:

TRANSMIT SWITCH = ON ?TRANSMIT READY

New Transmit command

--> INTERNAL FLAG:The formatted

; Data block = 150; Send from address 0; Block length = 66 byte; of which 64 bytes are

; (= maximum length

0 : KH= 0000;1 : KH= 0540;2 : KH= 0001;3 : KH= 003A;

DB150 The command and response are stored in DB150

1st DW to be sent: must always be 0000Command starts here: Read 32 KB MDS... from address 256 (page 1, addr. 0); length = 58 bytes

(= maximum SINEC L1 block length)

; of data block)

telegram wassent

::SPA FB247

NAME :CONTROLSSNR : KY0,2A-NR : KY0,101ANZW : MW104PAFE : MB106

;:UN M 105.0:BEB -> STILL NO ‘DO’ TELEGRAM::SPA FB245

NAME :RECEIVESSNR : KY0,2A-NR : KY0,101ANZW : MW104ZTYP : KCDBDBNR : KY0,150ZANF : KF+64ZLAE : KF-1PAFE : MB106

::L DL64:L KB0:!=F:BEB --> NOTHING RECEIVED:T DL64 = RESET RECEIVE:L DW66 = 1st incoming user data word: (format as for

standard telegram): EVALUATION OF MDSs FOLLOWS: ****************************:L KB0 Error analysis: Status byte

must be “0” !!:L DL67:> Run error routine;

Invalid data::

; user data

--- Receive telegram


--- 42 ---RD: 07/99


4 Cold Start and Restart

ASM always executes the cold start and restart procedure following a failure of the 24 V supply.The presence of anMDS is checkedwhen power returns and the DOsare controlled accordingly (only ifANW check is enabled). The ASM then attempts to issue a RESET telegram.

02 00 0F

Lng Command Status No startup telegram forSINUMERIK and SINEC L1

This telegram tells the user that the ASM is operational (the startup process takes a maximum of1.5 secs). The ASM is still operational even if the computer does not accept the startup telegram. TheASM does not repeat the startup telegram, however.

Digital outputs:

Caution: Both DOs are active for about 200 ms after power is first switched on. This briefstartup time is caused by the ASM hardware and cannot be eliminated.

Proximity detection during startup:

The procedure to determine whether anMDS is in the SLG’s window during startup is always the same.The ASM scans its surroundings for about 200msec to determine whether amobile data carrier is pres-ent. DO0/DO1 are controlled, depending on whether an MDS is present, and the startup telegramshown above is then sent.

Note: If the 3964R protocol is being used and the startup telegram was not acknowledgedby the computer (computer not connected or switched off), the ASMwill need about 5 sec-onds before proximity detection becomes operational.

SINEC L1:The ASM, and consequently proximity detection, will not function if the SINEC L1 bus is inSTOP, or if the SINEC L1 master does not correspond to the number set on the ASM.

During startup, the ASM responds as follows if ....

a) No MDS is present:The ASM waits for an MDS or a read/write command.A NEXT command will be ignored.

b) An MDS is present:The ASMwaits for a read/write command before the MDS leaves the SLG window. A NEXT com-mand causes a subsequent read/write command to be performed on the next MDS that entersthe window, not the one that is already there.

Startup for SINUMERIK protocol:

Approximately 1.5 seconds after power returns, the computer can interrogate DO0 of the ASM (i.e.,digital input on computer) to establish whether there is an MDS in the SLG window.


--- 43 ---RD: 07/99


5 DI/DOs and Proximity Detection

Various modes of operation can be set using switches 7 and 8. The precise interaction between thesemodes and the components below are described in this chapter (see also section 2.3).

--- DI/DO--- Proximity detection--- Status byte--- DI/DO command--- NEXT command

Definitions:

-- Proximity detection

Proximity detection is a recognition logic in the ASM firmware that detects whether a mobile datacarrier is currently within range of the SLG read/write device. It can be controlled in three ways.

a) Via 2 DIs:The ASM receives a signal on DI0 when the data carrier enters the window.The ASM receives a signal on DI1 when the data carrier leaves the window.

b) Via field scanning:The ASM firmware constantly monitors its magnetic field to determine whether a mobile datacarrier is present. Hysteresis prevents the system toggling rapidly between ‘present’ and ‘notpresent’ when the data carrier stops at the edge of the field.

c) Via 1 DI:DI1 tells the ASM that an MDS has left the window. The ASM is ready for programming of thenext MDS. The presence of an MDS is determined by field scanning.

-- Presence:

A mobile data carrier is currently within range of the SLG. The ANW bit is set during the status com-mand (see section 3.2.1.1). The presence of an MDS can also be detected from the status of thedigital outputs. The digital output z18 (i.e., ANW) is the same as the ANWbit of the status command.


--- 44 ---RD: 07/99


-- Digital inputs DI0, DI1 for

a) Automatic control of the presence of an MDSb) One or two general-purpose digital inputs which can be interrogated by the computer with the

DI/DO command.

Note: The DIs can also be interrogated by the DI/DO command if operating under a).

-- Digital outputs DO0, DO1 for

a) Transport control when using proximity detectionDO0 controls the motor of a conveyor belt or is an output signal indicating the presence of amobile data carrier.DO1 controls a pallet stopper or indicates the presence of a mobile data carrier. DO0/DO1 canalso be wired directly to the inputs of a controller (e.g., in SINUMERIK applications).

b) 2 general-purpose digital outputs when working without proximity detectionThe status of the DOs can be interrogated and modified by the computer (set, reset).

-- ANW/Busy byte:

TheANW/Busybyte canbe interrogated using theSTATUScommand. Bit 1 indicateswhether a datacarrier is present, among other information. Bit 0 indicates whether an MDS command is currentlybeing processed (see section 3.2.1.1).

-- NEXT command:

TheNEXTcommand is used to advance the ASMcontroller to the nextmobile data carrier. TheNEXTcommand must always be programmed if proximity detection is being used. The NEXT commandtells the ASM to flip the digital outputs (see diagrams on the following pages).

A read/write command for the next MDS can be sent to the SLG read/write device as soon as theASM has acknowledged the NEXT command. The new command remains in the ASM until the oldMDS has left the window and a new MDS has entered.

This programming method means that an ASM command can be executed as soon as an MDSenters the SLGwindow. There is no difficulty in complying with the MOBY-I project design guidelinesas the response times of the computer or serial transmission speed to the ASM do not become fac-tors in the configuration.


--- 45 ---RD: 07/99


5.1 Proximity Detection with 2 DIs

Diagram:

a

Proximity switchon DI0

Direction ofMDSMDS

Proximity swichon DI1

a

Computeror PC

ASM 420

SLG

a: Distance from center of SLG read/write device to input/output proximity switch:10 cm < a < 50 cmThemaximum value of ‘a’ can also be larger. Remember that 2 MDSs cannot then be positionedbetween the input and output proximity switch at the same time.The minimum distances between each MDS must also be maintained. (See MOBY catalogue.)

DI0: Receives a signal when the MDS comes within range of the SLG read/write device. This signalcan be received before the MDS actually enters the SLG window. The input signal may also begenerated by a controller.

DI1: Receives a signal when theMDSgoes out of rangeof theSLG read/write device. TheASM is thenready toprocess the next data carrier.While a command is active, theMDScan leave and re-enterthe magnetic field of the SLG any number of times.The ASM command must have been completely executed before the MDS reaches the DI1switch.


--- 46 ---RD: 07/99


Timing diagram:

DI0

DI1

DO0

DO1

ANW**(Status command)

Pulse width at least 50 msecA number of pulses may occur in sucession.

ActivateASM:RESET

ASM ready toreceive (no MDS

MDS comes ASM has re- MDS

present)within rangeof SLG

Read/writecommandsexecutedby ASM

ceived a NEXTcommand.The DOsare setaccordingly. *)

leavesSLGwindow.

A commandfor a newMDS cannow comefrom thecomputer.

*) The DOs also flip when the MDS goes out of range of the SLG before a next command arives (signal on DI1).

**) The ANW signal on the basic connector is an inverted version of the signal shown above.

Error messages:

Error 01: A signal is received onDI1 while the ASM is executing a commandwith theMDS. The com-mand is aborted. The data are invalid.

Error 02: The ASMhas received a signal onDI0 (MDSenters) and then a signal onDI1 (MDS leaves)without receiving a data carrier command from the user.

Note: This error is not signalled to the control computer until the next commandhas been received.


--- 47 ---RD: 07/99


5.2 Field Scanning as Proximity Detection

How field scanning works

The SLG read/write device scans its surroundings for a data carrier. If one is detected, the ANWbit is setduring the status command.When theMDShas left themagnetic field, theANWbit is also reset during the status commandwhile theSLG scans the field for the next MDS.A hysteresis function ensures that the presence bit is not constantly flipped should the data carrier stopexactly on the boundary of the SLG’s magnetic field. This hysteresis function is handled by the pro-cessor on the ASM. Read/write commands are handled completely transparently by the ASM and haveno effect on proximity detection. Similarly, the presence bit retains its validity after the start of a com-mand.

MDS

SLG

W

a

bL

h

bc

L, W: Dimensions of the transmission window of an SLGread/write device at operational distance to MDS (seeMOBY catalogue)L = Field length; W = Field width

h: Hysteresis: Area in which anANWbit remains setonceit has been set

Hysteresis field forproximity detection

Transmission window:Exchange of databetween MDS and SLG

h = 0.1 to 15 mm(depends on type of MDS)

a: The point at which the mobile data carrier is detected by the SLG. The pending MOBYcommand will now be performed on the MDS. The presence bit remains set.

b: TheMOBY commandmust be completed by this point since the data carrier is about to leave thetransmission window. The presence bit still remains set.

c: The presence bit in the status byte is reset. The MDS has passed out of range of the SLG. Anycommand that has not yet been processed will be aborted and acknowledged with error 01.

DI0,DI1: Both digital inputs can be used as desired by the user. The inputs can be interrogated bythe DI/DO command.


--- 48 ---RD: 07/99


Timing diagram:

DO0

DO1


0.5 sec

ActivateASM 420:RESET

ASM ready to receive(no MDS present)

MDS comeswithin range ofSLG

Read/writecommandsexecuted bySLG

SLG hasreceiveda NEXTcommand.The DOsare setaccordingly.

MDSleavesSLGwindow.

A commandfor a newMDS cannow comefrom thecomputer.

DO1 goes ONagain 0.5 secsafter the MDSleaves thetransmissionwindow.

*) The DOs also flip when the MDS leaves the hysteresis field of the SLG without a NEXT command.


Error messages:

Error 01: The MDS passed out of range of the SLG while a command was being executed on theMDS. The command is aborted. The data are invalid.

Error 02: There is no command active on the ASM. During this time, an MDS passes through theSLGwindow shown above. This error is not signalled to the control computer until the nextcommand has been received.

Note: The ASM cannot tell whether the MDS has passed through the entire field,or whether it has just entered the field very briefly and then backed outagain.


--- 49 ---RD: 07/99


5.3 Proximity Detection with Field Scanning and 1 DI

Diagram:

a

Direction ofMDSMDS

Proximity switchon DI1

a

Computeror PC

ASM 420

SLG

The MDS is detected using field scanning (see section 5.2). The DOs flip when the SLG read/write de-vice detects anMDS. TheMDS remains present (bit 1 of theANW/Busybyte set) until a signal is receivedon DI1.

a: Distance from center of SLG to output proximity switch to be configured: 20 cm < a < 50 cmThemaximum value of ‘a’ can be also larger. Remember that 2 MDSs cannot then be positionedbetween the SLG and the output proximity switch at the same time.The minimum distances between each MDS must also be maintained. See MOBY catalogue.

DI0: This digital input canbeused as desired by the user. TheDI/DO commandcan beused to interro-gate the input.

DI1: Receives a signal when the MDSgoes out of range of the SLG. The DI1 switchmust not coincidewith the edge of the SLG field. If DI1 is outside the field, it makes no difference how often theMDSleaves and re-enters the field while a command is pendingon theASM. TheASM commandmusthave been completely processed before the MDS reaches the DI1 switch.


--- 50 ---RD: 07/99


Timing diagram:

DI1

DO0

DO1


Pulse width at least 50 msecA number of pulses may occur in rapid sucession.

ActivateASM:RESET

< 2 sec

ASM ready toreceive (no

MDS comes SLG has MDS

MDS present)within rangeof SLG.

Read/writecommandsexecutedby SLG

receiveda NEXTcommand.The DOsare setaccordingly. *)

leavesA commandfor a newMDS cannow comefrom thecomputer.

SLGwindow.

*) The DO’s also flip when the MDS goes out of range of the SLG before a NEXT command arrives (inputs on DI1).


Error messages:

Error 01: A signal is received on DI1 while the ASM is executing a command on the MDS. The com-mand is aborted. The data are invalid.

Error 02: The ASM registers a secondDI1 signal (after T> 2 sec). The ASMdid not receive any datacarrier command (incl. NEXT command) from the computer during this period.

Note: This error is not signalled to the control computer until the next commandhas been received.

6 SLG and MDS Configuration and Installation Guidelines

The configuration and installation guidelines for the SLG and the MDS can be found in chapter 2 of theMOBY catalogue or in the installation and service manual.

All types of SLGs can be connected to the ASM 420. All types of MDS can be processed.


--- 51 ---RD: 07/99


7 Error Diagnosis and Error Messages

Meaning of the LEDs

RED: This LED flashes when an error occurs.The most recently detected error status is indicated with the display being overwritten eachtime a new error occurs. The error indicator can only be reset through a RESET.The b18 pin on the basic connector (X1) carries the same signals as the red LED. Flashing isindicated with 0 V pulses.

Flashing of the red LED during normal operation is of secondary importance to theuser as long as the system continues to run normally. Some errors can be evaluatedby the programmer in his program and responded to accordingly.The error LED is particularly useful during commissioning and service activities.

YELLOW: Rapid, irregular flashing indicates that a dialogwith theSLGor themobile data carrier (MDS)is currently in progress. This LED is on continuously when proximity detection is enabled.

GREEN: This LED is only of significance if the user has enabled oneof the types of proximitydetectionon switch bank S1. It shows the presence of an MDS in the SLG field.OFF = No data carrier present or proximity detection disabledON = An MDS is currently within range of the SLG.The z18 pin on the basic connector (X1) carries the same signals as the green LED, but is aninverted version of the green LED.

Error indications

Errors are indicated on the red LED.

Hardware error on ASM:The ASM cannot be addressed following a hardware error. The error is not sent to the user. The ASMmust be replaced.

ON permanently (shines brightly, pin b18 static low):The PROM on the ASM is defective.

ON permanently (shines faintly, pin b18 toggles):The CPU on the ASM is defective.

Medium fast flashing:(Approx. 4 Hz). External RAM on the ASM is defective.

Flashing patterns:All other errors are indicated by an easily recognizable flashing pattern. The error is identi-fied by counting the number of pulses following one long pause and the next. These errorsare passed to the user (or STG service and test unit).


--- 52 ---RD: 07/99


TheASM is equippedwith LEDs for status and error indication. It is nevertheless helpful for commission-ing and diagnostic purposes to have test tools available.

STG service and test unit:The STG service and test unit is an important tool. The basic functions and hardware of the ASM can betested using the cable described in section 2.4.6 (only RS 422 at present).

Interface tester:An interface tester (line tracer) is essential for diagnosing errors at the telegram level. This instrument isconnected between the ASM and the computer and records all telegram communication. User pro-gramming errors or ASM malfunctions can be clearly identified.

Make sure that the ASM interface and that of the line tracer are identical (V.24, RS 232; RS 422, RS 485;TTY).

SINEC L1 test:The general functions of a SINEC L1 station can be tested by connecting a programming unit (e.g.PG 750) to the SINEC L1 master. If the functions on the PG do not provide a clear answer, a SINEC L1bus tester can be used. This consists

moby i asm 420 interface module - siemens...aaaa11 aaa = address of asm on sinec l1 bus (asm is...

Documents