Siemens MOBY FC 56 Parts list manual

Table of Contents
Introduction 1
Block Specifications 2
The Parameter Data Block 3
MOBY Commands 4
Sample Applications 5
Entry/Exit Check of an MDS
in an SLG Field 6
System Configuration 7
Commissioning Guidelines 8
Error Messages and
Trouble-Shooting 9
Short Description of the ASM
Hardware A
Programming MOBY-ASM on
PROFIBUS-DP-V1 B
Published in 02.2003
J31069-D0155-U001-A0-7618
FC 56
Technical Description
MOBY

!Danger
indicates that death, severe personal injury or substantial property damage will result if proper precautions
are not taken.
!Warning
indicates that death, severe personal injury or substantial property damage can result if proper precau-
tions are not taken.
!Caution
with warning triangle, indicates that minor personal injury or property damage can result if proper precau-
tions are not taken.
Caution
without warning triangle, indicates that property damage can result if proper precautions are not taken.
Attention
indicates that an undesired result or state may occur if the note is not adhered to.
Note
draws your attention to particularly important information on the product, handling the product, or to a
particular part of the documentation.
Qualified Personnel
The device/system may only be set up and operated in conjunction with this manual.
Only qualified personnel should be allowed to install and work on this equipment. Qualified persons are
defined as persons who are authorized to commission, to ground, and to tag circuits, equipment, and sys-
tems in accordance with established safety practices and standards.
Correct Usage
Note the following:
!Warning
This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers which
have been approved or recommended by Siemens.
This product can only function correctly and safely if it is transported, stored, set up, and installed cor-
rectly, and operated and maintained as recommended.
Trademarks
MOBYis a registered trademark of SIEMENS AG.
Some of the other designations used in these documentsare also registered trademarks; the owner’s
rights may be violated if they are used by third parties for their own purposes.
Safety Guidelines
This manual contains notices which you should observe to ensure your own personal safety, as well as to
protect the product and connected equipment. These notices are highlighted in the manual by a warning
triangle and are marked as follows according to the level of danger:
We have checked the contents of this manual for agreement with the
hardware and software described. Since deviations cannot be pre-
cluded entirely, we cannot guarantee full agreement. However, the
data in this manual are reviewed regularly and any necessary cor-
rections included in subsequent editions. Suggestions for improve-
ment are welcomed.
Disclaimer of LiabilityCopyright ESiemens AG 2003 All rights reserved
The reproduction, transmission or use of this document or its
contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or design, are
reserved.
Siemens AG
Automation and Drives (A&D)
Systems Engineering
P.O. Box 2355, D-90713 Fuerth
ESiemens AG 2003
Technical data subject to change.
Siemens Aktiengesellschaft Order No. J31069-D0155-U001-A0-7618

i
FC 56
J31069-D0155-U001-A0-7618
Table of Contents
1 Introduction 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Basic Information about the “Filehandler” 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 MDS Memory Structure 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Logical Structure of MDS Memory 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Configurable memory sizes 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3 Check sum 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Block Specifications 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Technical Data 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Configuration Overview 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Data Structures of the FC 56 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Number of MOBY Channels Which Can Be Connected 2-5. . . . . . . . . . . . . . .
2.5 Addressing of the MOBY Channels 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 The Parameter Data Block 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 INPUT Parameters 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Command and Status Word “BEST” 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Other Indications 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 MOBY Commands 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Command Set 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Parameterizing the Commands 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 FORMAT 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 CREATE 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 QUEUE-WRITE 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 QUEUE-READ 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 WRITE/UPDATE 4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6 READ 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.7 DELETE 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.8 ATTRIB 4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.9 COVER 4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.10 DIR 4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.11 END 4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.12 MDS-STATUS 4-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.13 TRACE 4-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.14 GET 4-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.15 NEXT 4-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.16 ASM/SLG-STATUS 4-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.17 SET-ANT 4-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.18 MOVE 4-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.19 LOAD 4-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
ii
FC 56
J31069-D0155-U001-A0-7618
5 Sample Applications 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Scanning the FC 56 by the User 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Calling the FC 56 Cyclically (e.g., in OB 1) 5-3. . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Programming of New Start and Restart 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Programming Module Failure 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Specifying the Data Structure 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 The UDTs of FC 56 5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Using the GET Command 5-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Determining the Memory Requirements on the SIMATIC 5-17. . . . . . . . . . . . . .
6 Entry/Exit Check of an MDS in an SLG Field 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Definition of Terms 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Entry/Exit Checking Mode 0 (MDS_IO_control 0) 6-3. . . . . . . . . . . . . . . . . . . .
6.3 Entry/Exit Checking Mode 1 (MDS_IO_control 1) 6-4. . . . . . . . . . . . . . . . . . . .
6.4 Entry/Exit Checking Mode 4 (MDS_IO_control 4) 6-4. . . . . . . . . . . . . . . . . . . .
6.5 Entry/Exit Checking Mode 5 (MDS_IO_control 5) 6-5. . . . . . . . . . . . . . . . . . . .
6.6 Diagram showing possible MDS states on an SLG 6-6. . . . . . . . . . . . . . . . . . .
7 System Configuration 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Example of a Fixed File Structure in a Manufacturing Process 7-1. . . . . . . . .
7.2 Example of a Variable File Structure in a Production Process 7-3. . . . . . . . . .
8 Commissioning Guidelines 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Error Messages and Trouble-Shooting 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 General Errors 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Error Classes 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 error_code 9-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Error Indication on the ERR-LED 9-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Short Description of the ASM Hardware A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1 ASM 475 A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 ASM 473 A-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3 ASM 452 A-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B Programming MOBY-ASM on PROFIBUS-DP-V1 B-1. . . . . . . . . . . . . . . . . . . . . . . . . .
B.1 Cyclic Control Word between Master and MOBY-ASM B-5. . . . . . . . . . . . . . . .
B.2 Working with the ASM B-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 Command and Acknowledgment Telegrams B-8. . . . . . . . . . . . . . . . . . . . . . . . .
B.4 Blocking of Long Data Sequences B-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.5 The Filehandler Commands – Without Multitag B-12. . . . . . . . . . . . . . . . . . . . . .
B.6 The Filehandler Commands – With Multitag B-19. . . . . . . . . . . . . . . . . . . . . . . . .
B.7 PROFIBUS Implementation B-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.8 Example of a PROFIBUS Trace B-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
iii
FC 56
J31069-D0155-U001-A0-7618
Figures
1-1 Interface modules for the FC 56 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 MDS memory 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1 Overview of configuring FC 56 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2 Slots on the S7-300 and analog addresses for ASM 475 2-6. . . . . . . . . . . . . .
2-3 Example: Automatic address generation of a MOBY-ASM in
ET 200 configuration 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4 Parameterizing the physical address allocation in UDT 10 2-8. . . . . . . . . . . . .
3-1 Command and status word BEST with names of variables 3-7. . . . . . . . . . . .
5-1 Flow chart of the FC 56 scan 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2 Example of several MOBY commands assigned to one channel 5-8. . . . . . .
5-3 Example of a separate data block assigned to each MOBY channel 5-10. . . .
8-1 Placement of the MOBY ASMs in the hardware catalog 8-1. . . . . . . . . . . . . . .
8-2 Example of a hardware configuration 8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-3 Parameterizing the object characteristics 8-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
8-4 Editing DB 56 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-5 Variables for function check – VAT1 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-1 Configuration for ASM 475 (centralized layout) A-2. . . . . . . . . . . . . . . . . . . . . .
A-2 Interfaces and indicators of the ASM 475 A-4. . . . . . . . . . . . . . . . . . . . . . . . . . .
A-3 Maximum configuration of ASM 473 on an ET 200X with
sample addressing A-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-4 Interfaces and indicators of the ASM 473 A-7. . . . . . . . . . . . . . . . . . . . . . . . . . .
A-5 ASM 452 configurator A-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-6 Switch settings, interfaces and indicators of the ASM452 A-10. . . . . . . . . . . . .
B-1 States of command and acknowledgment counter B-3. . . . . . . . . . . . . . . . . . .
B-2 Layout of the cyclic control word B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-3 Startup timing initiated by user B-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-4 Startup timing by ASM initiated by power failure B-6. . . . . . . . . . . . . . . . . . . . .
B-5 Command processing: command by command B-7. . . . . . . . . . . . . . . . . . . . . .
B-6 General telegram layout B-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables
1-1 Memory sizes which can be formatted 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1 Typical runtimes of FC 56 (cycle load of AS in msec) 2-1. . . . . . . . . . . . . . . . .
2-2 Overview of MOBY FC 56 configuration 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-3 Number of MOBY channels 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1 UDT 10 “MOBY Param” 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2 INPUT-Parameter 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3 Variables in BEST 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4 Indications 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1 UDT 50 “MOBY FH CMD” 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2 Command set 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3 UDT 50 “MOBY FH CMD” – FORMAT 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4 UDT 50 “MOBY FH CMD” – CREATE 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5 UDT 50 “MOBY FH CMD” – QUEUE-WRITE 4-10. . . . . . . . . . . . . . . . . . . . . . . .
4-6 Sample UDT for QUEUE-WRITE command 4-11. . . . . . . . . . . . . . . . . . . . . . . . .
4-7 UDT 50 “MOBY FH CMD” – QUEUE-READ 4-12. . . . . . . . . . . . . . . . . . . . . . . . .
4-8 Sample UDT for QUEUE-READ command 4-13. . . . . . . . . . . . . . . . . . . . . . . . . .
4-9 Sample UDT for acknowledgment of QUEUE-READ 4-14. . . . . . . . . . . . . . . . .
4-10 UDT 50 “MOBY FH CMD” – WRITE/UPDATE 4-15. . . . . . . . . . . . . . . . . . . . . . .
4-11 UDT 50 “MOBY FH CMD” – READ 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
iv
FC56
J31069-D0155-U001-A0-7618
4-12 UDT 50 “MOBY FH CMD” – DELETE 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13 UDT 50 “MOBY FH CMD” – ATTRIB 4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-14 UDT 50 “MOBY FH CMD” – COVER 4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-15 UDT 50 “MOBY FH CMD” – DIR 4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-16 UDT 220 “MOBY FH directory” 4-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-17 UDT 50 “MOBY FH CMD” – END 4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-18 UDT 50 “MOBY FH CMD” – MDS-STATUS 4-23. . . . . . . . . . . . . . . . . . . . . . . . .
4-19 UDT 160 “MDS STATUS FH” 4-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-20 UDT 100 “MDS-STATUS” 4-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-21 UDT 50 “MOBY FH CMD” – TRACE 4-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-22 UDT 50 “MOBY FH CMD” – GET 4-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-23 UDT 200 “MOBY UID4” 4-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-24 UDT 50 “MOBY FH CMD” – NEXT 4-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-25 UDT 50 “MOBY FH CMD” – ASM/SLG-STATUS 4-29. . . . . . . . . . . . . . . . . . . . .
4-26 UDT 50 “MOBY FH CMD” – SET-ANT 4-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-27 UDT 50 “MOBY FH CMD” – MOVE 4-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-28 UDT 50 “MOBY FH CMD” – LOAD 4-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1 Overview table of the UDTs 5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2 UDT 110 “MOBY SLG-STATUS” 5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3 UDT 120 “MOBY SLG status diag. 1” 5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4 UDT 130 “MOBY SLG status diag. 2” 5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-5 UDT 140 “MOBY SLG status diag. 3” 5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-6 UDT 170 “MOBY FH-STATUS” 5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1 Entry/exit checking of an MDS 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-1 Error classes of the FC 56 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-2 Error messages via the “error_code” variable 9-3. . . . . . . . . . . . . . . . . . . . . . . .
9-3 Error indications of the ERR-LED 9-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-1 Input parameters for ASM 475 A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2 Input parameters for ASM 473 A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-3 Settings of the MOBY-related parameters A-9. . . . . . . . . . . . . . . . . . . . . . . . . . .
A-4 Input parameters for ASM 452 A-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1 Filehandler commands – without multitag B-12. . . . . . . . . . . . . . . . . . . . . . . . . . .
B-2 Filehandler commands – with multitag B-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-3 Data record numbers B-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1
FC 56
J31069-D0155-U001-A0-7618
Introduction
The FC 56 is a STEP 7 function for MOBY identification technology. It can be used
with both the SIMATIC S7-300 and S7-400 for various MOBY interface modules.
ASM 452 ASM 475 PARAM ASM 473 PARAM
Figure 1-1 Interface modules for the FC 56
The configurations with the different interface modules are shown in appendix A.
The FC 56 can be used to all configurations.
SThe interface module is operated directly on a SIMATIC S7-300.
SThe interface module is located in the rack of an ET 200M or ET 200X. The
ET 200M/ET 200X is used on an S7-300 or S7-400.
SSince the interface module is a self-contained PROFIBUS slave, it is linked with
the integrated PROFIBUS connection to a SIMATIC S7-300 or S7-400.
These configurations can be mixed. Different interface modules can also be
connected.
Filehandler
The FC 56 uses the filehandler in ASM/SLG. This offers you the advantages listed
below.
SThe user addresses his data by logical name (file name) consisting of
8 alphanumeric characters. The absolute address of the data is no longer
needed.
SConsecutive data are called files.
SThe filehandler automatically manages the different file lengths.
SFiles can be assigned access rights.
1

Introduction
1-2
FC56
J31069-D0155-U001-A0-7618
Features of the FC 56
SAll MOBY systems (SLGs and MDSs) can be used with the FC 56.
SThe user can chain several commands together. This means that many small
data areas of an MDS can be processed with one command start.
SIt is easy to set up the data structures with “Universal Data Types” (UDTs). The
UDTs are available with English (UDT 10, 50 ...) and German (UDT 11, 51 ...)
commentary.
STransmission of the data to and from the ASM and execution of the commands
on the ASM take place in parallel. This means optimal data throughput.
SUse of the symbolic names for the block variables gives you a very well
organized user program even with complex configurations.
Features of the interface
For the features of the individual ASMs, see appendix A. Since the features of the
individual ASMs are continuously being added to, you should always use the latest
edition of this description.
PROFIBUS configuration
A GSD file on the “Software MOBY” product (6GT2 080-2AA10) is included for the
interface modules which can be directly connected to PROFIBUS.
Technically, the FC 56 uses the PROFIBUS-DP/V1 protocol. Important control data
are cyclically sent in a data word. Actual MOBY data are transmitted in non-cyclic
telegrams.
Non-SIMATIC applications
Applications which are programmed on remote controllers cannot use the FC 56.
The PROFIBUS interface is described in Appendix B for these applications.
Programmers of a remote controller can use this interface to develop their own
MOBY function. Together with the FC 56 description and the UDTs, data structures
which are the same or similar to the FC 56 can be created on a remote controller.
Prerequisites for use of the FC 56
Remember that the FC 56 uses non-cyclic telegrams (SFC 58/59). Older CPUs of
the SIMATIC family or a small model series may not have these services. Be sure
to check this during configuration.
SSTEP 7 version
The ASM 475 and ASM 473 modules require a STEP 7 version wV 5.1.

Introduction
1-3
FC 56
J31069-D0155-U001-A0-7618
1.1 Basic Information about the “Filehandler”
To give yourself a better idea of how the MOBY filehandler works, think of it as a
floppy disk system.
MOBY Filehandler Floppy Disk System
MDS:
Data is stored electronically
in the MDS on a memory
chip (RAM or EEPROM).
Floppy-Disk:
Data is written magnetically
on a floppy disk.
SLG:
The SLG modulates the
data stream arriving from
the ASM and demodulates
the data stream arriving
from the MDS.
The MDS must lie within the
transmission window of the
SLG. The size of the trans-
mission window depends on
the MDS/SLG configuration.
The MOBY interface module
(ASM) provides the user in-
terface. A USART module
on the ASM produces the
serial data stream for the
SLG.
Floppy-Gerät:
The floppy drive converts
the data impulses arriving
from the PC into a write
string for the read/write
head (or vice versa)
The floppy disk must be po-
sitioned very exactly over
the read/write head as this
generates only very small
magnetic fields.
A PC controls the floppy
drive and exchanges data
with it via an interface. The
coding and decoding of the
data takes place in a floppy
controller in the PC.
As with a floppy disk system, the filehandler also accesses data using logical file
names, not physical memory addresses. This in turn requires that the files are
created on a formatted (completely erased) data carrier. The data relating to a file
can then be processed by the appropriate command, e.g. READ, WRITE, DELETE
etc.

Introduction
1-4
FC56
J31069-D0155-U001-A0-7618
1.2 MDS Memory Structure
1.2.1 Logical Structure of MDS Memory
DIRECTORY
MDS
Block
The system area contains all MDS specific
data (e.g. MDS name, MDS type, last SLG
number etc).
The FAT (File Allocation Table) points to all
the blocks belonging to a file.
The user data area is divided into blocks. The
number of blocks and the block length de-
pends on the type of MDS.
SYSTEM AREA
BLOCK INDEX TABLE FAT
The directory contains the names of all ex-
isting files with their corresponding para-
meters. The number of directory entries
possible depends on the type of MDS.
Figure 1-2 MDS memory

Introduction
1-5
FC 56
J31069-D0155-U001-A0-7618
1.2.2 Configurable memory sizes
MDS units are available with memory chips (RAM/EEPROM) of various sizes.
When initialising (see section 4.2) the “filehandler” must be told what type of MDS
is involved so that the correct data management system can be created.
The following table shows how the filehandler structures the various types of MDS.
Table 1-1 Memory sizes which can be formatted
Typ
(Hex)
MDS-capacity
in bytes (gross)
Max. no. of files User data bytes
(nett)
Number of
blocks
Block size in
bytes
Enter this
parameter
when
initialising
Total MDS memory
capacity
Max. number of
files that can be
created
Max. no. of user
bytes that can be
written to the MDS
The product of no. of blocks and block
size gives the user data length (net) in
bytes
04H
84H
2.045
1.778 1
16
16
1.680
1.440
105
90
16
16
05H
85H
8.189
7.154 1
32
32
7.456
6.464
233
202
32
32
06H
86H
32.765
28.658 1
64
64
31.488
27.520
246
215
128
128
1 ...with ECC operation (MOBY I)
1.2.3 Check sum
To minimise the time it takes the SLG to process an MDS, a check sum (2 bytes
long) is maintained in the system area of the MDS. Use of the check sum
mechanism is essential in dynamic read and write operations (see section 7.1).
Each time the contents of the directory or the FAT are modified (execution of write
commands e.g. CREATE, WRITE, ATTRIB etc.), the filehandler calculates a check
sum on the two areas and places this in the MDS system area. If two consecutive
MDSs have the same check sum, their data structures (file names, file lengths
etc.) will be totally identical.
The filehandler does not therefore need to read the directory and FAT of the
second MDS (additional time requirement), but can continue to operate with the
current (internal to filehandler) parameters.
Note:
The check sum is created from the directory and FAT only, and not from the file
contents.

Introduction
1-6
FC56
J31069-D0155-U001-A0-7618

2-1
FC 56
J31069-D0155-U001-A0-7618
Block Specifications
2.1 Technical Data
Block number: FC 56
Block name: FC 56
Symbolic name: “MOBY FH-MT”
Family: –
Work memory requirements: 8932 bytes
Local data: 146 bytes
Version: 1.0
Blocks called: SFC 58, SFC 59, SFC 20, SFC 21, SFC 1
Assignment of data blocks: MOBY Param = 300 bytes per channel
(defined with UDT 10)
Flags used: None
Counters used: None
Registers used: AR1, AR2
Call: Cyclic
Table 2-1 Typical runtimes of FC 56 (cycle load of AS in msec)
S7-CPU Idle Pass ASM Centrally in S7-300 ASM Distributed on
PROFIBUS
Read MDS Write MDS Read MDS Write MDS
315-2 DP 1.9 3.7 + n * 0.023 3.6 + n * 0.022 3.4 3.6
318-2 DP 0.13 1 + n * 0.01 1.3 + n * 0.007 0.4 0.45
416-2 DP 0.1 – – 0.35 0.38
n = Amount in bytes of processed user data per read or write command
When a command processes more than 214 bytes of MDS data, n = 214 must
always be used in the table.
Remarks: The times of the ASM for data communications with the
data memories are described in the MOBY configuration manual.
2

Block Specifications
2-2
FC56
J31069-D0155-U001-A0-7618
Calculating MOBY data throughput
The formulas in the MOBY configuration manual (chapter 3) can be used to calcu-
late data throughput with the FC 56.
Configuration manuals are currently available MOBY I (6GT2 097-4BA00-0EA2)
and MOBY U (6GT2 597-4BA00-0EA2).
Applicable in general:
tkCommunication time between ASM, SLG and MDS
nAmount of user data
kConstants (see table in configuration manual)
tByte Transmission time for 1 byte
(see table in configuration manual)
Attention
Use the characteristic values for filehandler mode in the formula for data
throughput.
Transmission of the data to the MDS and transmission of the data between ASM
and FC 56 take place in parallel. Usually no further time must be added for data
transmission between ASM and FC 56 so that the time tkcalculated above
represents the total duration of the command.
However, commands may require more time under the following conditions.
SA very large number of MOBY channels are processed in parallel.
SVery few (or only one) system resources are available for non-cyclic telegrams.
SSlow transmission speeds are used on PROFIBUS.
SOther applications are running on the S7 which require the non-cyclic telegram
services (SFC 58/59) of the SIMATIC very frequently.
tk+kĂ)ĂtByteĂ n

Block Specifications
2-3
FC 56
J31069-D0155-U001-A0-7618
2.2 Configuration Overview
Table 2-2 Overview of MOBY FC 56 configuration
LAD Box Parameter Data Type Permissible
Range
Description
MOBY FC
Params DB
Params_DB
Params ADDR
INT
INT
2 to 32767
0 300 600 *
Parameter data block number for
a MOBY channel (SLG)
Address pointer in the parameter
P
arams_
DB
Params_ADDR
Params_ADDR INT 0, 300, 600,*.... Address pointer in the parameter
data block to the start of a UDT 10
* These values are examples when only type UDT-10 data structures are used. These values change when
UDT 10 is followed by the MOBY command (UDT 50).
Params_DB and Params_ADDR make up a pointer to a data structure. This data
structure is defined by calling UDT 10 (English) or UDT 11 (German). A separate
data structure must be defined for each MOBY channel (ASM or SLG). See
chapter 2.3.

Block Specifications
2-4
FC56
J31069-D0155-U001-A0-7618
2.3 Data Structures of the FC 56
The following figure shows an example of a definition of several MOBY channels
with the related MDS commands and the user data.
Call FC 56
Params_DB
Params_ADDR
MOBY_DB:
Channel 1
Channel 2
Channel 3
Channel 4
command_
DB_number
command_
DB_address
MOBY commands:
Single command (up to 32
KB can be processed) or
chained command
DAT_DB_number
DAT_DB_address
User data:
UDT 10
UDT 50
The user
defines the
size and the
data types in
his/her data
himself/
herself.
Call FC 56
Params_DB
Params_ADDR
Call FC 56
Params_DB
Params_ADDR
Call FC 56
Params_DB
Params_ADDR
Call 1st SLG Call 2nd SLG Call 3rd SLG Call 4th SLG
Figure 2-1 Overview of configuring FC 56
Each call of the FC 56 points to a separate parameter data block (Params_DB,
Params_ADDR) which is defined by a UDT 10.
UDT 10 contains two variables – “command_DB_number” and
“command_DB_address.” These variables point to the MOBY command which is
to be executed with the MDS.
The MOBY command is defined with UDT 50 (English) or UDT 51 (German).
Different commands or command chains can be defined by calling UDT 50 several
times (see chapter 4.2). The variables “DAT_DB_number” and “DAT_DB_address”
are defined in UDT 50. This variable definition is the pointer to the user data. The
MDS data which were read are stored there. With a write command, the user must
store his/her data here before the command is executed.

Block Specifications
2-5
FC 56
J31069-D0155-U001-A0-7618
2.4 Number of MOBY Channels Which Can Be Connected
Each MOBY channel occupies 1 word in the input and output area of a SIMATIC
S7. The maximum number of MOBY modules permitted by the SIMATIC can
always be used. The following table gives you an overview.
Table 2-3 Number of MOBY channels
S7 CPU Type 315-2 DP 316-2 DP; 318-2 DP 416; 417; CP 443-5 Ext.
Max. no. of
ASMs
Max. no. of
SLGs
(channels)
Max. no. of
ASMs
Max. no. of
SLGs
(channels)
Max. no. of
ASMs
Max. no. of
SLGs
(channels)
ASM 475 (central) 132 64 32 64 – –
ASM 475 (distributed
via ET 200M) 2
64 x 7 896 123 x 7 1722 123 x 7 1722
ASM 473 (distributed
via ET 200X) 3
64 x 7 448 123 x 7 861 123 x 7 861
ASM 452 64 64 123 123 123 123
1 The central layout can contain up to 3 expansion racks. A DP connection is not necessary with this layout.
2 With distributed layout, up to 7 MOBY modules (ASM 475) can be installed in each ET 200M.
3 Up to 7 ASM 473s can be installed in one distributed I/O ET 200X.

Block Specifications
2-6
FC56
J31069-D0155-U001-A0-7618
2.5 Addressing of the MOBY Channels
Central layout with ASM 475
With the central layout, HW Config assigns fixed slot-specific addresses for the
ASM 475. The ASM 475 is located in the analog area of a SIMATIC S7-300 and
starts at address 256.
Connection line 368
Connection line 368
Connection line 368
IM
1234567891011
Module
rack 3
34 5 6 7 8 9 10 11
34567891011
Slot number 34 5 6 7 8 9 10 11
Slot number
Slot number
Slot number
Module
rack 2
Module
rack 1
Module
rack 0
IM
IM
256 272 288 304 320 336 352 368Analog address
384 400 416 432 448 464 480 496Analog address
512 528 544 560 576 592 608 624Analog address
640 656 672 688 704 720 736 752Analog address
Figure 2-2 Slots on the S7-300 and analog addresses for ASM 475

Block Specifications
2-7
FC 56
J31069-D0155-U001-A0-7618
Addressing via PROFIBUS
When addressing takes place over PROFIBUS, any addresses can be selected in
HW Config for the MOBY ASM. HW Config specifies a free address as default.
Automatic generation of the next free address.
Input address and output address must be
identical.
Figure 2-3 Example: Automatic address generation of a MOBY-ASM in ET 200 configuration

Block Specifications
2-8
FC56
J31069-D0155-U001-A0-7618
Assignment of the addresses in the FC 56
The unique I/O ASM addresses assigned by HW Config must also be used in the
parameter data block (UDT 10).
Start addresses of
UDT 10 in the data
view of the MOBY DB
Physical address allocation as
specified in HW Config
Figure 2-4 Parameterizing the physical address allocation in UDT 10
In addition to the address (ASM_address), the MOBY channel (ASM_channel)
must also be assigned uniquely. When an ASM is used with several channels
(ASM 475), a separate UDT 10 must be defined for each channel. The entry
“ASM_address” remains the same. The “ASM_channel” is changed from 1 to 4.