ASM 410 Moby I Identification System: Release 12.98 Technical Description

MOBYI Identification System ASM 410 ASM 410 Interface Module
Technical Description Release 12.98
ASM 410 Technical Description
6GT2097-3AC00-0DA2
Table of Contents
Page 1. 2. 2.1 2.2 2.3 2.4 3. 3.1 3.2 3.3 3.4 3.5 3.6 3.6.1 3.6.2 3.6.3 3.7 3.8 3.8.1 3.8.2 4. 5. 6. 7. 8. 9. ASM 410: A Brief Description The ASM 410 Mechanical Design Block Diagram Pin Assignments Cable Connections of the ASM 410 Programming Representation of the ASM 410 in the Process Image Timing Diagram of Control Signals Programming Example Programming of Cold Start and Restart Procedures Application of SLG ON/OFF" and Presence" Using the ASM 410 as Decentralized Periphery Use in the ET 100U Use in the ET 200 Use with SIMATIC S7 via ET 200U Processing Mobile Data Carriers Dialog Operation How is the MOBYI Dialog Set Up? How Does the User Work with the MOBYI Dialog? The ECC Driver Error Evaluation Transmission Times Commissioning Technical Specifications of the ASM 410 Warnings 2 3 3 5 6 7 9 9 12 15 16 16 20 20 22 23 24 26 26 28 30 32 34 35 37 38
6GT2002-0BA00
ASM 410
-1-
Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98
6GT2097-3AC00-0DA2
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
Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618
-2-
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
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). Ventilation slits of the adapter capsule It is important to ensure that the slits are not covered during operation. Forced ventilation is not required. Label insert The English equivalent is on the reserve. Status and error LEDs (See table 1.)
A B
LEDs A1 A2 A3 B1 B2 B3 Fehler aktiv ANW 1.SLG 2.SLG Power
1 2 3
Betriebsart 0 1 2 3 4 5 6 7 normal ECC Testbetr. Test+ECC INIT norm INIT ECC res. res. TEST 8 1.SLG bzw. 2.SLG 9 res. F
Mode selection switch (See table 2.)
6 8 A 4 C 2 0 E
Connector to serial S5 bus 9way subminiature D connector for connecting the STG service and test unit with cable 6GT20910B... (screw lock) Coding plug (not shown; on reverse side of module). Fixed in position H" to denote analog module. 10-way connector to bus module (24 V supply, interface to SLG read/write device) See chapter 2.2
STG
Anschaltmodul MOBY - I
6GT2002-0BA00 1 2 3 4 5 6
Table 1
No. A1 A2 A3 Colour Red Yellow Green Description Error: The last command was terminated with an error , or the hardware of the module is defective. Rapid, irregular flashing indicates that a dialog with the SLG or the mobile data carrier (MDS) is currently in progress. This LED is on when presence detection is enabled. Mobile data carrier within range of SLG. The SLG that has detected the MDS is identified by the LEDs B1 and B2. (The LED is only on when presence detection is in operation; see chapter 3.1.) B1 = 1st SLG B2 = 2nd SLG B3 = Power ON: is in use is in use Note: Only one of the two LEDs (B1 or B2) should be on at a time. Check the cabling to the SLG if both LEDs are on at the same time. (See chapter 4.2.)
B1 B2 B3
Green Green Green
This LED is always on as long as the 24 V supply to the module is present. Use the STG service and test unit to test the module.
6GT2002-0BA00
ASM 410
-3-
6GT2097-3AC00-0DA2
Mode selection switch: Positions 0 to 7: Positions 8 to F: Setting the mode of operation: The ASM 410 uses the serial S5 bus. The STG interface is inactive. 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. Remember to perform a new start or RESET after changing the mode selec tion switch.
Attention:
Table 2 Mode of Operation Switch Position 0 1 2 Text on Label Insert Normal ECC driver Test operation Description
Normal operation; read from and write to all types of MDS; ECC driver is inactive. Read from and write to all types of MDS; the ECC driver is enabled (see chap. 4). All types of MDS can be processed in test mode. The ASM 410 tightens up its error controls while communicating with the MDS. Weak points and malfunctions can thus be detected during commissioning. The ECC driver is enabled (see chap. 4); - otherwise the same as position 2 Initialisation of the MDS. An INIT command is sent to the MDS at the start of a write command via the process image. This deletes the contents of the MDS. Initialisation of the MDS with the ECC driver; - Otherwise the same as position 4
3 4
Test + ECC INIT normal
5 6 7
INIT ECC
Reserved
Test (only for MOBYI operation) 8 9 F Reserved 1st or 2nd SLG An STG service and test device can be connected via the 9way subminiature D connector so that all MOBY-I hardware can be tested.
-4-
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
2.2 Block Diagram Galvanic isolation power supply

5 V DC 24 V DC
+24 V
+9 V SI Clear Clock Latch Ident S0

MOBY-I S5 SYAS processor + shift register
TxD RxD TxD RxD
Ext. power supply
+24 V GND + TxD - TxD + RxD - RxD
MOBY-I processor EPROM, RAM
STG
RS 422
GND
TxD
RxD
Multiplexer
Clamp or crimp connector for SLG (depends on bus module) Interface to 1st SLG Interface to 2nd SLG
SLG
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 is changed by the application programmer. The MOBYI processor sends the SYAS processor a telegram for changes in presence, acknowledgement of a command, finished message of a command and return of power. These telegrams appear in the 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).
6GT2002-0BA00 ASM 410 -5Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98
6GT2097-3AC00-0DA2
2.3 Pin Assignments Pin Assignments to STG: RS 422 Interface 9way subminiature D connector
Pin Assignment to STG Pin 1 2 3 4 5 6 7 8 9 Hsg. Function Not used + Transmit + Receive Not used - Receive - Transmit Ground (0 V) +24 V Not used Cable shield
Terminal Assignments on the Bus Module:
BUS MODULE (Left Side) (Right Side)
9 Bus module with screw or crimp connection
10
10
Terminal 1 2 3 4 5 6 7 8 9 10
Function +24 V external power supply for MOBY-I (ASM 410, STG and SLG) 0 V: Ground for ASM 410 and all SLGs and STG + TxD Transmit to 1st SLG - TxD Data cables to 1st SLG + RxD Receive from 1st SLG - RxD + TxD - TxD + RxD - RxD Transmit to 2nd SLG Receive from 2nd SLG Data cables to 2nd SLG
-6-
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
2.4 Cable Connections of the ASM 410 Number of ASM 410s and Addressing:
PLCs S5100U S595U S590U ET 100U ET 200U Max. Number of ASM 410s per Station 8 4/8 2 2 4 Addressing * * * Any Any 8 modules can be used with the S595U starting with release status 4/94. Limitation to 2 modules due to the power pack of the SIMATIC S590U Cf. chap. 3.6.1 Cf. chap. 3.6.2 Remarks
* Slotoriented addressing
S5100U 95U 90U 0 64 to 71 1 72 to 79 2 80 to 87 3 88 to 95 4 96 to 103 5 104 to 111 6 112 to 119 7 120 to 127 8 Slot number Address allocation for ASM 410 Free slots for additional digital modules
Overview of Cabling Options:
Bus module of S5100U with ASM 410 interface module
Service and test unit STG 4F
SIEMENS
SIEMENS
Read/write device SLG
Read/write device SLG
Mobile data carrier MDS
Mobile data carrier MDS
6GT2002-0BA00
ASM 410
-7-
6GT2097-3AC00-0DA2
Cabling of One or Two SLGs:
B U S MODULE 1 2
Shield +24 V 0V
+ RxD - RxD + TxD - TxD From external power supply +24 V 0V
Mounting rail
3 4
5 6
7 8
9 10
Terminal strip on bus module Cable shield gn ye wh br pk gr Colour coding3 of cable supplied by Siemens
1st SLG
Max. cable length = 1000 m1
+ RxD - RxD + TxD - TxD +24 V 0V
gn ye wh br pk gr
2nd SLG
Cable incl. SLG connector and open end with core end ferrule 6GT2091-0D... 2
1 2 3
The maximum cable length depends on which SLG is connected and the tolerance of the external 24 V supply. (See chapter 2 of MOBY catalogue.) MOBY length code Colour coding gn = green ye = yellow wh = white br = brown pk = pink gr = grey = = = = = = Pin 4 in SLG connector Pin 5 in SLG connector Pin 6 in SLG connector Pin 1 in SLG connector Pin 2 in SLG connector Pin 3 in SLG connector -86GT2002-0BA00 ASM 410
6GT2097-3AC00-0DA2
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 or a 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 can cause inconsistencies in the PIQ/PII for the MOBY modules. Adhere to the following rules when programming the ASM 410: a) Do not process an OB13. (System data word SD 97 of the SIMATIC must have the value 0". 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 enable alarm processing again with the AF" command. (See example in chapter 3.3.)
6GT2002-0BA00 ASM 410 -9Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98
6GT2097-3AC00-0DA2
Byte: 1 2 3 4 5 6 7 8
PIQ:
Control byte Address MSB Address LSB 1st byte / INIT 2nd byte 3rd byte 4th byte 5th byte Start address on MDS
Bit: 7
Res. Res. for FB
Expanded RESET4
User data: 5 bytes for a write command
SLG ON/OFF 5 (presence detection)
Command: 00 = ACKNOWLEDGE command 01 = Read 10 = Write/INIT 11 = Reset 0 = SLG no. 1 1 = SLG no. 2 0 = Normal operation 1 = Dialog
Dialog mode6:
Byte: 1 Status byte 2 Address MSB 3 Address LSB 4 1st byte / error 5 2nd byte 6 3rd byte 4th byte 7 8 5th byte
PII:
Bit: 7 Start address on MDS User data: 5 bytes for a read command
Ready
Battery 3 low MDS detected (1 = presence) Error2
00 = Nothing active1 01 = Read 10 = Write/INIT 11 = Reset 0 1 = SLG no. 1 = SLG no. 2
ECC correction: 1 = ECC correction was performed.
1 2 3
No command was processed since powering up the system or the MOBY CPU has been restarted (failure of 24 V supply). 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. 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.
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 6
The SLG ON/OFF bit must be set to 0 before switching the MOBY operating mode. 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.
- 10 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Special Commands PIQ: During initialisation. (Switch setting 4 or 5. See chapter 2.1.)
Byte Bit: Control byte 00 00 INIT data 00 MSB LSB End address +1: MSB LSB 00 00 00 00 00 00 00 00 00 00 08 20 80 02 00 00 40 80 00 00 00 F0 C0 10 MDS Type 62 bytes 128 bytes 2 Kbytes 8 Kbytes 32 Kbytes MOBY E MOBY F: MDS F4xx MOBY F: MDS F2xx Command: 00 = ACKNOWLEDGE 10 = INIT 1= Expanded RESET
2
1 2 3 4 5 6 7 8
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.
Byte:
1 2 3 4 5 6 7 8
Bit: Control byte
1st byte, tABTAST
Bit:
Command: 11 = RESET 00 = ACKNOWLEDGE

2
MOBY
Time factor:
Time value: 00 to 3F 00 = 11 = 10 = 11 = 4 3 0.01 0.1 1 10 2 1 0 sec sec sec sec
1= Expanded RESET (See bytes 4 and 5 in PIQ).
Bit: 7
00 91 92 93 81 1 2
= = = = =
MOBY I/E MOBY F: MDS F1xx MOBY F: MDS F4xx MOBY F: MDS F2xx Switch MOBYV operating mode on/off
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. 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. 4 3 2 1 0 01 = Read 00 = ACK 1 = Special command 01 = Perform FFT
PIQ: Perform FFT scan (only MOBYF)

1 2 3 4 5 6 7 8 00 00 00 00 XX 00 00 ASM 410 - 11 -
6GT2002-0BA00
6GT2097-3AC00-0DA2
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. 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 S S 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. 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). 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). 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.
- 12 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
The following timing diagram shows the exact representation of the data in the PII/PIQ.
Duration of one cycle Cycle change:
Output telegram from ASM 410 + Input telegram from ASM 410
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Read
Write
Address QB 2+3
Write data QB 4 to 8
Ready
Error
Address IB 2+3
Read data IB 4 to 8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 10
6 10
2 10
= Valid data
6GT2002-0BA00
ASM 410
- 13 -
6GT2097-3AC00-0DA2
No Initiated by 1 ASM
Description After a restart (power on) the ASM 410 comes up with READY. A RESET must be programmed in the cold start and restart OB. Start of read command. With the cycle change, the rising READ edge and the MDS address of QB2 and QB3 are passed to the ASM 410. The address and READY bit = 0 do not appear in the input telegram of the ASM 410 until the next cycle change. The ASM 410 is communicating with the MDS. READY = 1 Read is completed. The data which was read is located in bytes 4 to 8 of the input telegram. The last results remain in the PII until the start of the next command.
User
3 4 5 6 7 8 9
ASM ASM
User ASM ASM ASM
Start of a write command; address and data to be written is passed to the ASM 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 the input telegram. ACKNOWLEDGE command phase : After a new command is acknowledged by the ASM 410 with READY = 0, the user must issue an acknowledge command". The acknowledge command" must be issued 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 result in the PIQ as soon as this is available.
10
User
- 14 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
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.
PB 10: U I U I U I U Q UN Q BEB U U U UN U BEB UN UN BEB UN R R BEB O O BEB U S BEB I 64.7 Q 64.0 Q 64.1 Q 64.0 Q 64.0 I 64.6 ERROR I I I Q Q 64.0 64.1 64.7 64.0 64.1 64.0 64.1 64.7 64.0 64.1 If .. .. .. PII indicates that reset command has been executed, then send an acknowledge in PIQ to ASM 410
I 64.0 I 64.1
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 *************
L L
IW 67 . . IW 69 . . START Q 64.0
UNTIL START OF NEXT MOBY COMMAND, MOBY DATA READ ARE AVAILABLE IN PII STARTING AT IB 67. Userrelated processing of data NOTE: After a cold start or restart, this area of the PIQ contains zeros If START is set, start same command again
U S BE
If programming (with OB13) of the SIMATIC is timecontrolled, the MOBY call must be programmed as follows:
. . . AS JU AF . . . PB 10 ; Disable alarms and time control ; Process MOBY ; Enable alarms
6GT2002-0BA00
ASM 410
- 15 -
6GT2097-3AC00-0DA2 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
OB21 / OB22:
L T L T L T BE
KH0000 QB65 KB30 QB66 KB3 QB64
Start address on the MDS is 30 Issue RESET command for synchronisation (is sent to the ASM during first cycle change)
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 to process 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 multi plexer 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.
- 16 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Function Diagram:
SLG
L
b b
Hysteresis field for presence monitoring
a MDS
Transmission window: Exchange of data between MDS and SLG
L, B: Dimensions of the transmission window of an SLG read/write device at operational distance to MDS (see manual) L = Field length; B = Field width h: Hysteresis: Area in which the data carrier remains detected after 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
6GT2002-0BA00
ASM 410
- 17 -
6GT2097-3AC00-0DA2
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.
Diagram:
Overall start Reset pallet counter Issue MOBY command Control byte : RESET command SLG ON/OFF=1
Step pallet counter Status 4 Wait for presence = 1 Status 1 Wait for end of command READY=1 MDS could not be read completely Error if command = read READY =0; Presence = 0
Send ACK command to ASM
If command = read, then forward data (not for reset)
Status 3
Wait for READY=0
Wait for presence = 0 Start read command
Status 2
* *
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 T QB64 L KB0 T QB65 L KB0 T QB66 BE Start address on MDS = 0 Reset command; SLG on/off = 1
- 18 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Programming in a Function Block with STEP 5:

FB10 SEGMENT 1 U U U S UN JC UN UN UN S BEB UN BEB U S BEB R S U BEB L : L : L : BEB NXT:*** SEGMENT 2 UN JC U BEB R S R S BEA NXT:*** FB10 SEGMENT 3 UN JC=NXT U BEB R S R BEA NXT:*** SEGMENT 4 UN JC UN BEB R S L L +F T NXT:BE STATUS4 =NXT I 64.5 STATUS3 I 64.7 STATUS3 STATUS4 Q 64.0 Switch to next status if acknowledged STATUS2 =NXT I 64.5 STATUS2 STATUS3 Q 64.1 Q 64.0 Switch to next status Set Start bit for read I 64.0 I 64.1 I 64.7 STATUS4 STATUS1 =NXT Q 64.1 I 64.7 I 64.5 ERROR I 64.7 I 64.6 ERROR STATUS1 STATUS2 I 64.1 IB67 IB68 IB69 > MDS could not be read completely Check for errors Switch to next status Command was not a read command > Data not processed ) ) ) Process the 6digit number read ) ) ) Wait for Ready from ASM 410 The system waits for a new .. data carrier following a .. cold start or restart
Wait till MDS has left the SLG window
Wait for command acknowledgement from ASM 410
Wait for new data carrier Wait for presence = 1 Queued read command executed automatically if new MDS detected STATUS4 STATUS1 PALCNT KB1 PALCNT Switch to program status 1 Step pallet counter
Note:
The user can place the program variables anywhere in the flag area.
6GT2002-0BA00
ASM 410
- 19 -
6GT2097-3AC00-0DA2
3.6 Using the ASM 410 as Decentralized Periphery 3.6.1 Use in the ET 100U SIMATIC C P U Central controller: S5115U S5135U S5150U S5155U
ET 100U
Max. cable length 3000 m
Max. of 2 ASM 410s per ET 100U ET 100U
DI
DQ
DQ
Max. of 32 ET 100Us 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 4AX for 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 pro gramming sequence then causes the 8byte command telegrams to be forwarded to the ASM 410 with incorrect data.
- 20 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
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
t A max
t B max
tC
tC
Transmission distance Calculation as shown in manual of ET 100U
I/O bus Time for I/O bus transmission can be assumed to be a constant of 8 msec. (i.e., transmission of 8 bytes on the I/O bus)
Applicable to the ASM 410:
t trans max = t A max
+ t B max
+ 8 msec
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:
Wait for Ready = 0 Start read command Process read data Wait until timer expires
Send ack. cmd. to ASM Wait for Ready = 1 Start timer with trans mission time
6GT2002-0BA00
ASM 410
- 21 -
6GT2097-3AC00-0DA2
Programming Example : Three (3) bytes are to be written to the data carrier starting at address 5. The data to be written is in FY 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 ON ON JC L T M002: UN R UN UN BEB U JC L T BEA NXT1: O O BEB U S BEB UN BEB U BEB S L T L T L T L T L T L T BE
* **
I 80.0 I 80.1 I 80.7 =M002 KB0 QB64 START EFSTART I 80.0 I 80.1 I 80.7 =NXT1 KB0 QB80 * Q 80.0 Q 80.1 I 80.6 ERROR
Issue acknowledge after reset ..command ) ) > Edge flag for START ) ) ) ) ) ) identical to example in chap. 3.3 ) ) ) ) ) ) ) If read command, then start timer here with system transmission time before read data become valid
START > No new command start EFSTART EFSTART KB0 QB81 KB5 QB82 FW10 QB83 FW13 QB85 FY14 QB87 KH0002 QB80 ** > No new rising edge from Start **** START COMMAND **** Specify address MSB Specify address LSB...
...and write data... ...in PIQ Start write command
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 for setting 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. 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.
- 22 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
3.6.3 Use with SIMATIC S7 via ET 200U Configuration:

S7300/400 PROFIBUS SLG 1 SLG 2 PROFIBUSDP ET 200U 24 V ASM 410
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 LADDR :=W#16#80 RECORD :=P#DB100.DBX 20.0 BYTE 8 RET_VAL:=DB100.DBW10 CALL DPRD_DAT LADDR :=W#16#80 RET_VAL:=DB100.DBW11 RECORD :=P#DB100.DBX 30.0 BYTE 8 U DBX 30.0 U DBX 30.1 U DBX 30.7 R DBX 20.0 R DBX 20.1 UN DBX 30.0 UN DBX 30.1 BEB UN DBX 30.7 R DBX 20.0 R DBX 20.1 BEB O DBX 20.0 O DBX 20.1 BEB U DBX 30.6 S A 8.0 BEB U E 0.1 = DBX 20.0 U E 0.7 = DBX 20.2 BE //Write SFC 15 to DP slave //Addresse 128 //Length 8 bytes //SFC 15 error message //Read SFC 14 from DP slave //Addresse 128 //SFC 14 error message //Length 8 bytes //RESET was performed //in startup OB 100 //Then send acknowledge //If no RESET performed, then //wait here //If finished inactive, then //send acknowledge
//If command was started and //finished not yet returned, //then wait here //Error occurred? //Set output 8.0 //and stop program //Start read command //with input 0.0 //Input 0.7 causes switch //to SLG 2
6GT2002-0BA00
ASM 410
- 23 -
6GT2097-3AC00-0DA2
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
- 24 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
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
Normal
KH
with ECC Normal
KY
with ECC Normal
KF
with ECC
62-Byte Data Carrier with RAM Start address End address 0000 003D 0000 0029 00,00 00,61 0,0 0,41 +0 + 61 +0 + 41
128-Byte Data Carrier with EEPROM Start address End address 0000 007F 0000 006F 00,00 00,127 00,00 0,111 +0 + 127 +0 + 111
2-Kbyte Data Carrier with RAM Start address End address 0000 07FC 0000 06F1 00,00 07,252 00,00 06,241 +0 + 2044 +0 + 1777
8-Kbyte Data Carrier with EEPROM Start address End address 0000 1FFC 0000 1BF1 00,00 31,252 00,00 27,241 +0 + 8188 +0 + 7153
32-Kbyte Data Carrier with RAM Start address End address 0000 7FFC 0000 6FF1 00,00 127,252 00,00 111,241 +0 + 32764 +0 + 28657
752-Byte Data Carrier with EEPROM (MOBY E) Start address 0000 0000 End address 02EF 0291 Read out ID no. (can only be read in one piece) Start address 1FF0 Length 0004 0,0 2,239 31,240 0,4 0,0 2,145 +0 + 751 8176 4 +0 + 657
MOBY F MDS F1xx (5 Bytes) Start address End address 0000 0004 0,0 0,4 +0 +4
MOBY F MDS F2xx (32 Bytes) Start address 0010 End address 001F Read out ID no. (can only be read in one piece) Start address 0000 Length 0004 0,16 0,31 0,0 0,4 + 16 + 31 +0 +4
MOBY F MDS F4xx (256 Bytes) Start address 0040 End address 00FF Read out ID no. (can only be read in one piece) Start address 0000 Length 0004
6GT2002-0BA00 ASM 410
0,64 0,255 0,0 0,4

- 25 -
+ 64 + 255 +0 +4
6GT2097-3AC00-0DA2
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.
Station_N

Read or write the VMDS with FB 250 SLG_N SLG_D
MOBY-I interface in normal operation (e.g., ASM 400 in SIMATIC S5)
Station_D MOBY-I interface in dialog operation (e.g., ASM 410 in SIMATIC S5)

VMDS Read/write/ initialize the VMDS with FB 41 or via PIQ (Cf. chap. 3.1.) Station_N reads/writes the VMDS through the clearance in air.
- 26 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Designation Station_N
Explanation 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 usual way (i.e., as if the user wanted to exchange data with an MDS). An SLG (i.e., SLG 41, SLG 42, SLG 43 and SLG 44) which is connected to station_N. 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 as dialog ASM. During parameterization, a 16Kbyte memory area is defined on station_D. This memory area is called VMDS (i.e., virtual MDS). It is used as communications memory. Processing of station_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). An SLG (i.e., SLG 41, SLG 42, SLG 43 and SLG 44) which is connected to station_D. Virtual mobile data carrier. The VMDS is a 16Kbyte memory area on station_D. The VMDS is specified and cleared when station_D is turned on and parameterized.
SLG_N Station_D
SLG_D VMDS
6GT2002-0BA00
ASM 410
- 27 -
6GT2097-3AC00-0DA2
3.8.2 How Does the User Work with the MOBYI Dialog? Example The 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 dialog The 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 must be positioned at certain angles to each other). The following figure shows the transmission window during dialog.
SLG_D
Sg Sa Direction of movement from SLG_D to SLG_N
SLG_N
View of side
View of top
Enlargement of the transmission window when SLG_D and SLG_N use minimum working distance Sa = Sg = L = B = Working distance Limit distance Length of the transmission window Width of the transmission window
Positioning of SLG_D Transmission window
- 28 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Field data during dialog operation The following table lists the field data during dialog operation. Dimensions are shown in millimeters.
All Specifications in mm Length of the transmission window (L) Width of the transmission window (B) Working distance (Sa) Limit distance (Sg) Distance from SLG to SLG (D)
SLG 41SLG 41 60
SLG 42SLG 42 230
SLG 43SLG 43 600
SLG 44SLG 44 3000
30 0 to 15 30 > 200
80 0 to 70 130 > 800
280 20 to 250 450 > 2000
1300 200 to 1000 2500 > 10000
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.
6GT2002-0BA00
ASM 410
- 29 -
6GT2097-3AC00-0DA2
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 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 ! ECC driver is on.
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).
- 30 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
Example: Data structure of a 62byte MDS. This table is for clarification purposes only and can be ignored by the programmer/user).
MDS Address from User's View Point 0 1 13
Address on MDS 0 1 13 14 15 16 17 29 30 31 32 33 45 46 47 48 61
Meaning
14 bytes of user data ECC ECC 14 bytes of user data ECC ECC 14 bytes of user data ECC ECC
1st block
14 15 27
2nd block
28 29 41
3rd block
An incomplete block at the end of MDS memory cannot be used for user data.
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).
6GT2002-0BA00
ASM 410
- 31 -
6GT2097-3AC00-0DA2
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: General:
7 6
Meaning, causes and remedies

5 4 3 2 1 0
0 Error indication
PII, Byte 4
Flashing Pattern of Red LED Once 3 times
Description
______
No communication between ASM and SIMATIC has taken place yet. -> Perform reset via the PIQ. 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 Error in the memory of the MDS The MDS has never been writeaccessed, or its memory was lost during a battery failure (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) Unknown command The 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 during initialisation. 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 Field interference on the SLG The 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.
- 32 6GT2002-0BA00 ASM 410
00000011 (03)
00000100 (04)
4 times
00000101 (05)
5 times
00000110 (06)
6 times
6GT2097-3AC00-0DA2
PII, Byte 4
Flashing Pattern of Red LED 7 times
Description
00000111 (07)
Too many sending errors Despite several attempts, the MDS was unable to receive the command or the write data 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. 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. 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) Only during initialisation (mode selection switch in position 4 or 5): MDS cannot execute INIT command. -> MDS is defective. 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). Memory of MDS cannot be writeaccessed. -> Memory of MDS is defective. -> EEPROMMDS was writeaccessed too often (i.e., is worn out"). Address error Address area of MDS was exceeded. -> Start address in bytes 2 and 3 of PIQ was specified incorrectly. -> MDS is not the right model. 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. MOBY-F: Driver error -> Internal error -> FFT command with MDS F1xx in the field MOBY-F: Checksum error -> CRC check in data telegram is not correct. -> Data distorted -> Interface defective
00001000 (08)
8 times
00001001 (09)
9 times
00001010 (0A) 00001011 (0B)
10 times
11 times
00001100 (0C) 00001101 (0D)
12 times
13 times
00001110 (0E)
14 times
00001111 (0F) 00011011 (1B)
15 times
27 times
6GT2002-0BA00
ASM 410
- 33 -
6GT2097-3AC00-0DA2
6. Transmission Times
The following time diagram shows a MOBY command sequence from command start" to command ready".
S5 User pro gram incl. ASM 410 program ming and scanning the ASM 410 SYAS MOBY Start MOBY command in user program S5 cycle change: One S5 cycle change requires an additional 2 msec for each ASM 410 regardless of what task is being executed at the time. Transfer command from SYAS processor to MOBY CPU: 20 msec MOBY processor executes MOBY command: Time: Example: 16 msec + n x 0.8 msec n = number of bytes to be transferred to MDS = 5 -> t = 20 msec Acknowledgement telegram (does not affect execution of MOBY command) from MOBY CPU Ready = 0 Send ACKNOWLEDGE command to ASM 410 (does not delay execution of MOBY command) Transfer result to SYAS CPU: 20 msec Ready = 1 During next cycle change, SYAS CPU sends result 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 - Transfer acknowledgement telegram to PII - Transfer ACKNOWLEDGE command to MOBY - Transfer result to PII Total b) 20 20 20 20 msec msec msec msec
80 msec
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)
- 34 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
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 the 24 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. PIQ:
QB64 QB65 QB66 QB67 QB68 QB69 QB70 QB71 0000 0011 00 00 00 00 00 00 00
After the reset command, the PII looks like this: PII:
IB64 IB65 IB66 IB67 IB68 IB69 IB70 IB71 1000 0011 00 00 00 00 00 00 00
<-Command was executed correctly by the ASM 410.
If the ready bit" in the control byte is not set, check the following: " Mode selection switch: 0 to 5 " LED B3 is on (24 V is present). g) Now go to QB64, QB65 and QB66 in the PIQ on the monitor screen. Modify the process image before you proceed with the next item and start a read or write command. PIQ:
Issue ACKNOWLEDGE command". Process address block from address 5 to 9 on the MDS. Unchanged
6GT2002-0BA00
ASM 410
- 35 -
6GT2097-3AC00-0DA2
h) Now start the issued command by setting bit 0 (or bit 1) in the control byte. PIQ:
Start reading (from SLG no. 1)
No change
You will receive a reset ready bit" in the PII. PII:

IB64 IB65 IB66 IB67 IB68 IB69 IB70 IB71 0000 0001 00 05 00 00 00 00 00
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". PIQ:
<-- Acknowledge command
No change
The PII remains unchanged. Note: If you move the data carrier into the range of the SLG before outputting the ACKNOWLEDGE command" in the PIQ, you will not receive a com pleted" signal. The PII does not change until you have performed step i). You will then receive the result immediately (without wait time).
k) Now place a data carrier in the SLG field. Execution of the command will be reported back in the PII approximately 50 msec later. LEDs B1" and A2" go off. PII:
IB64 IB65 IB66 IB67 IB68 IB69 IB70 IB71 1000 0001 00 05 xx xx xx xx xx
Ready bit is set. No change Data read from MDS
You can now continue with step g) and issue the next command (e.g., read with SLG no. 2). l) Step k (or step c with the STG) completes commissioning. You can now load and test your ap plication program.
- 36 -
6GT2002-0BA00
ASM 410
6GT2097-3AC00-0DA2
8. Technical Specifications of the ASM 410

Weight Storage temperature Ambient temperature SIMATIC installed horizontally SIMATIC installed vertically Relative humidity at 25 C (without condensation) Operational voltage range Current consumption +9 V from S5: 0.25 kg -25 C to +70 C 0 C to + 60 C 0 C to + 40 C 15% to 95% 24 V (max. of 10% residual ripple) 20 V to 30 V Average Maximum +24 V external: All SLGs off SLG 40 in operation SLG 41 in operation SLG 42 in operation SLG 43 in operation SLG 44 in operation Power consumption Average (without SLG) Cooling Transfer rate to S5 20 to 60 mA (20 mA = long cycle time) (60 mA = short cycle time) 110 mA (S5 in STOP) 90 mA 180 mA 180 mA 270 mA 340 mA 170 mA 2.5 W Convection cooling 125 Kbaud In 5bit blocks; with a 90 msec time gap between two blocks 9600 baud - MDS model - ECC operation (See chapter 2 of catalogue.) (16 + n x 0.8) msec Direct via process image PIQ/PII No function block required 5 bytes are processed per command. C in accordance with VDE 0110 IP20 in accordance with IEC529 IEC 68-2-27 45 x 135 x 100 mm
- 37 Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98
Transfer rate between SYAS and MOBY processors Transfer rate to mobile data carrier Dependent on Average Programming
Isolation group Protection rating Mechanical stress Dimensions (W x H x D)

6GT2002-0BA00 ASM 410
6GT2097-3AC00-0DA2
9. Warnings
- 38 -
6GT2002-0BA00
ASM 410
Siemens AG Automation and Drives Systems Engineering PO Box 2355, 90713 Fuerth
Subject to change without notice Order no: 6GT20973AC000DA2 Printed in the Fed. Rep. of Germany
Siemens Aktiengesellschaft

ASM 410 Moby I Identification System: Release 12.98 Technical Description

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ASM 410 Moby I Identification System: Release 12.98 Technical Description

Загружено:

Авторское право:

Доступные форматы

MOBYI Identification System ASM 410 ASM 410 Interface Module

Technical Description Release 12.98

ASM 410 Technical Description

Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98

ASM 410 Technical Description

1. ASM 410: A Brief Description

Can be used in:

Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618

ASM 410 Technical Description

2. The ASM 410

LEDs A1 A2 A3 B1 B2 B3 Fehler aktiv ANW 1.SLG 2.SLG Power

Mode selection switch (See table 2.)

Green Green Green

Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98

ASM 410 Technical Description

Test + ECC INIT normal

Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618

ASM 410 Technical Description

2.2 Block Diagram Galvanic isolation power supply

+9 V SI Clear Clock Latch Ident S0

Ext. power supply

+24 V GND + TxD - TxD + RxD - RxD

MOBY-I processor EPROM, RAM

ASM 410 Technical Description

Terminal Assignments on the Bus Module:

BUS MODULE (Left Side) (Right Side)

9 Bus module with screw or crimp connection

Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618

ASM 410 Technical Description

Overview of Cabling Options:

Bus module of S5100U with ASM 410 interface module

Service and test unit STG 4F

Read/write device SLG

Read/write device SLG

Mobile data carrier MDS

Mobile data carrier MDS

Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98

ASM 410 Technical Description

Cabling of One or Two SLGs:

Max. cable length = 1000 m1

+ RxD - RxD + TxD - TxD +24 V 0V

Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618

ASM 410 Technical Description

ASM 410 Technical Description

Res. Res. for FB

User data: 5 bytes for a write command

SLG ON/OFF 5 (presence detection)

Battery 3 low MDS detected (1 = presence) Error2

00 = Nothing active1 01 = Read 10 = Write/INIT 11 = Reset 0 1 = SLG no. 1 = SLG no. 2

ECC correction: 1 = ECC correction was performed.

Subject to change without notice! RD: 12/98 (4) J31069D0125U001A07618

ASM 410 Technical Description

Bit: Control byte

1st byte, tABTAST

Command: 11 = RESET 00 = ACKNOWLEDGE

Time value: 00 to 3F 00 = 11 = 10 = 11 = 4 3 0.01 0.1 1 10 2 1 0 sec sec sec sec

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

PIQ: Perform FFT scan (only MOBYF)

Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98

ASM 410 Technical Description

ASM 410 Technical Description

Subject to change without notice! (4) J31069D0125U001A07618 RD: 12/98