Page 1 Table of Contents Introduction MOBY Block Specifications FC 56 The Parameter Data Block MOBY Commands Technical Description Sample Applications Entry/Exit Check of an MDS in an SLG Field System Configuration Commissioning Guidelines Error Messages and Trouble-Shooting Short Description of the ASM Hardware Programming MOBY-ASM on PROFIBUS-DP-V1...
Page 2 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. Copyright E Siemens AG 2003 All rights reserved Disclaimer of Liability...
Page 3 Table of Contents Introduction ............Basic Information about the “Filehandler”...
Page 4 Table of Contents Sample Applications ........... . Scanning the FC 56 by the User .
Page 5: Table Of Contents
....Overview of MOBY FC 56 configuration ......
Page 6: Udt 50 "Moby Fh Cmd
Table of Contents 4-12 UDT 50 “MOBY FH CMD” – DELETE ......4-17 4-13 UDT 50 “MOBY FH CMD”...
Page 7: Interface Modules For The Fc
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.
Page 8 Introduction Features of the FC 56 S All MOBY systems (SLGs and MDSs) can be used with the FC 56. S The user can chain several commands together. This means that many small data areas of an MDS can be processed with one command start. S It is easy to set up the data structures with “Universal Data Types”...
Page 9 Introduction 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: Floppy-Disk: Data is stored electronically Data is written magnetically in the MDS on a memory on a floppy disk.
Page 10: Mds Memory
Introduction MDS Memory Structure 1.2.1 Logical Structure of MDS Memory The system area contains all MDS specific SYSTEM AREA data (e.g. MDS name, MDS type, last SLG number etc). DIRECTORY The directory contains the names of all ex- isting files with their corresponding para- meters.
Page 11: Memory Sizes Which Can Be Formatted
Introduction 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.
Page 12 Introduction FC 56 J31069-D0155-U001-A0-7618...
Page 13: Typical Runtimes Of Fc 56 (Cycle Load Of As In Msec)
Block Specifications 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: 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)
Page 14 Block Specifications 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: Communication time between ASM, SLG and MDS Amount of user data...
Page 15: Overview Of Moby Fc 56 Configuration
Block Specifications Configuration Overview Table 2-2 Overview of MOBY FC 56 configuration LAD Box Parameter Data Type Permissible Description Range Params_DB 2 to 32767 Parameter data block number for MOBY FC a MOBY channel (SLG) Params DB Params_DB Params ADDR...
Page 16: Overview Of Configuring Fc 56
Block Specifications 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 2nd SLG Call 3rd SLG Call 4th SLG Call 1st SLG Call FC 56 Call FC 56 Call FC 56...
Page 17: Number Of Moby Channels
Block Specifications 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...
Page 18: Slots On The S7-300 And Analog Addresses For Asm
Block Specifications 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.
Page 19: Example: Automatic Address Generation Of A Moby-Asm In
Block Specifications 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.
Page 20: Parameterizing The Physical Address Allocation In Udt
Block Specifications 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). Physical address allocation as specified in HW Config Start addresses of UDT 10 in the data view of the MOBY DB Figure 2-4...
Page 21 The Parameter Data Block Each MOBY channel (SLG) requires its own parameters. These are predefined in a data structure as UDT 10 (with commentary in English) or UDT 11 (with commentary in German). This UDT must be called in a data block for each MOBY channel.
Page 22: Udt 10 "Moby Param
The Parameter Data Block Table 3-1 UDT 10 “MOBY Param” Address Name Type Starting Commentary Value STRUCT +0.0 ASM_address Input:address of ASM (cycle word) +2.0 ASM_channel Input: number of channel (1 to 4) +4.0 command_DB_number Input:number of command DB +6.0 command_DB_address Input:first address of commands in the command DB...
Page 23 The Parameter Data Block INPUT Parameters The permissible values of the INPUT parameters are listed in the hardware specifications in appendix A. Table 3-2 INPUT-Parameter Variable Description ASM_address Logical base address of the ASM. This address must match the “start address” of the ASM in HW Config of the SIMATIC Manager.
Page 24 The Parameter Data Block Table 3-2 INPUT-Parameter Variable Description Priority_RW These two variables are used to define which commands will be permitted for this Priority_RWD channel (cf. section 4). Priority_RW Priority_RWD Priority* Meaning “R” Only type “R” commands are allowed. The (Read) MDS does not need to be written.
Page 25 The Parameter Data Block Table 3-2 INPUT-Parameter Variable Description scanning_time MOBY I: Scanning_time is the scanning time for the MDS 507 of MOBY I. A value of 00 can be used here for all other types of MDSs. The scan time setting (ABTA) is shown below (see also configuration manual of SLG 44/MDS 507).
Page 26 The Parameter Data Block Table 3-2 INPUT-Parameter Variable Description distance_limiting MOBY U: Working range restriction 05 hex 0.5 m 0A hex 1.0 m 0F hex 1.5 m 14 hex 2.0 m 19 hex 2.5 m 1E hex 3.0 m 23 hex 3.5 m multitag Maximum number of MDSs being processed in parallel in the field...
Page 27: Command And Status Word Best With Names Of Variables
The Parameter Data Block Command and Status Word “BEST” The control bits of FC 56 are defined in the command and status word. The command and status word with the variables is generated with UDT 10. The following figure shows the variables and their relative addresses in UDT 10. ←...
Page 28: Variables In Best
The Parameter Data Block Table 3-3 Variables in BEST Variable Description command_start True = Starts a command init_run True = New start of the interface module. The FC 56 is reset and the ASM is parameterized again. All data and commands on the ASM are lost. This bit must be set in the new start OB (OB 100) for every MOBY channel or ASM.
Page 29 The Parameter Data Block Table 3-3 Variables in BEST Variable Description ANZ_Read_0 Warning 1. The file read has length 0. This warning is reported for READ or QUEUE-READ. 2. The MDS was outside the transmission window during command processing or a change of MDS has occurred (one MDS has left and another has entered the transmission window).
Page 30 The Parameter Data Block Other Indications Table 3-4 Indications Variable Description ASM_busy This bit is set when the ASM is processing a command. “ASM_busy” is usually inverted to “ready.” ASM_busy is reported by the ASM with the cyclic word (see appendix B.1: ASM_busy_).
Page 31 MOBY Commands Before you can start a MOBY command with command_start, you must define it. UDT 50 (commentary in English) or UDT 51 (commentary in German) is available for the simple definition of a command. Table 4-1 UDT 50 “MOBY FH CMD” Address Name Type...
Page 32: Command Set
MOBY Commands Command Set Table 4-2 Command set Command Function Command Priority MOBY System FORMAT Format the MDS “I” CREATE Create a new file on the formatted MDS “B” W, D QUEUE-WRITE Set up a complete data carrier “Q” QUEUE-READ Read several files with one command “E”...
Page 33 MOBY Commands FORMAT: Format (initialize) a data carrier (see chapter 4.2.1) After a data carrier is received from SIEMENS, it must be formatted before entering the manufacturing process (or it can be formatted in the manufacturing process itself). S The MDS is completely erased. All the user data (file directory and data) will therefore be lost (option = 00H or 01H).
Page 34 MOBY Commands WRITE: Write data to an existing file (see chapter 4.2.5) S A certain number of bytes is written to the existing file (“length” parameter in UDT 50) from DAT_DB_number. S The WRITE command overwrites existing file data from logical address 0 with length “length.”...
Page 35 MOBY Commands DIR: Read directory (see chapter 4.2.10) The parameters of all existing files are read to DAT_DB_number/ DAT_DB_address. MDS-STATUS: Read information about the operating status of the MDS (see chapter 4.2.12) Reads MDS specific data to DAT_DB_number/DAT_DB_address. This option can be used to set whether information is to be read via the physical MDS or the logical MDS (filehandler).
Page 36 MOBY Commands GET: Read UIDs of all MDSs (MOBY U) (see chapter 4.2.14) This command is extremely important if you are using more than one MDS in the field. It provides the UIDs (unique identifiers) of all MDSs currently present in the field.
Page 37 MOBY Commands RESET: Reset ASM and SLG (see chapter 3.2) S The connection between FC 56 and ASM is reinitialized. The filehandler parameters are set according to the FC 56 INPUT parameters of UDT 10. S If an MDS is present in the SLG field during “RESET”, all subsequent commands will refer to this (current) MDS.
Page 38: Udt 50 "Moby Fh Cmd" - Format
MOBY Commands Parameterizing the Commands 4.2.1 FORMAT Parameterizing the command in Command_DB Table 4-3 UDT 50 “MOBY FH CMD” – FORMAT Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’I’ MDS command: I = Format +5.0 sub_command_1 B#16#0...
Page 39: Udt 50 "Moby Fh Cmd" - Create
MOBY Commands 4.2.2 CREATE Parameterizing the command in Command_DB Table 4-4 UDT 50 “MOBY FH CMD” – CREATE Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’B’ MDS command: B = Create File +5.0 sub_command_1 B#16#0...
Page 40: Udt 50 "Moby Fh Cmd" - Queue-Write
MOBY Commands 4.2.3 QUEUE-WRITE Parameterizing the command in Command_DB Table 4-5 UDT 50 “MOBY FH CMD” – QUEUE-WRITE Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’Q’ MDS command: Q = QUEUE-WRITE +5.0 sub_command_1 B#16#0...
Page 41: Sample Udt For Queue-Write Command
MOBY Commands Structure of the file entries with the QUEUE-WRITE command The following structure must be stored under the pointer DAT_DB_number/DAT_DB_address. It contains both the file names and the related data. Table 4-6 Sample UDT for QUEUE-WRITE command Address Name Type Commentary STRUCT...
Page 42: Udt 50 "Moby Fh Cmd" - Queue-Read
MOBY Commands 4.2.4 QUEUE-READ Parameterizing the command in Command_DB Table 4-7 UDT 50 “MOBY FH CMD” – QUEUE-READ Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’E’ MDS command: E = QUEUE-READ +5.0 sub_command_1 B#16#0...
Page 43: Sample Udt For Queue-Read Command
MOBY Commands Structure of the file entries with the QUEUE-READ command The following structure must be stored under the pointer DAT_DB_number/DAT_DB_address. It contains the description of the files to be read (or not to be read). Table 4-8 Sample UDT for QUEUE-READ command Address Name Type...
Page 44: Sample Udt For Acknowledgment Of Queue-Read
MOBY Commands Acknowledgment data in the QUEUE-READ command The user data in the acknowledgment of the QUEUE-READ command are written to the address QUEUE_DB_number/QUEUE_DB_address. The ”length” parameter contains the actual length of all read data. Structure of the file entries with the acknowledgment of QUEUE-READ The following structure must be stored under the pointer QUEUE_DB_number/QUEUE_DB_address.
Page 45: Udt 50 "Moby Fh Cmd" - Write/Update
MOBY Commands 4.2.5 WRITE/UPDATE Parameterizing the command in Command_DB Table 4-10 UDT 50 “MOBY FH CMD” – WRITE/UPDATE Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, nur MOBY U mit multitag +4.0 command ’W’ / ’U’ MDS command: Write File/Update File WRITE The WRITE command can be used to write an entire file or only a part of the file.
Page 46: Udt 50 "Moby Fh Cmd" - Read
MOBY Commands 4.2.6 READ Parameterizing the command in Command_DB Table 4-11 UDT 50 “MOBY FH CMD” – READ Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’R’ MDS command: R = Read File +5.0 sub_command_1 B#16#0...
Page 47 MOBY Commands 4.2.7 DELETE Parameterizing the command in Command_DB Table 4-12 UDT 50 “MOBY FH CMD” – DELETE Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’D’ MDS command: D = Delete File +5.0 sub_command_1 B#16#0...
Page 48 MOBY Commands 4.2.8 ATTRIB Parameterizing the command in Command_DB Table 4-13 UDT 50 “MOBY FH CMD” – ATTRIB Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’Y’ MDS command: Y = Assign File Attribute +5.0 sub_command_1 B#16#0...
Page 49 MOBY Commands 4.2.9 COVER Parameterizing the command in Command_DB Table 4-14 UDT 50 “MOBY FH CMD” – COVER Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’C’ MDS command: C = Cover MDS +5.0 sub_command_1 B#16#0...
Page 50 MOBY Commands 4.2.10 Parameterizing the command in Command_DB Table 4-15 UDT 50 “MOBY FH CMD” – DIR Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’G’ MDS command: G = Get Directory +5.0 sub_command_1 B#16#0...
Page 51 MOBY Commands Acknowledgment data in the DIR command The user data contained in the acknowledgment in the DIR command are written to the address parameterized in the command. The “length” parameter contains the actual length of the read directory data. The structure of the directory data is stored in UDT 220.
Page 52 MOBY Commands 4.2.11 Parameterizing the command in Command_DB Table 4-17 UDT 50 “MOBY FH CMD” – END Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’K’ MDS command: K = END +5.0 sub_command_1 B#16#0 Set mode of the END command.
Page 53 MOBY Commands 4.2.12 MDS-STATUS Parameterizing the command in Command_DB Table 4-18 UDT 50 “MOBY FH CMD” – MDS-STATUS Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’F’ MDS command: F = Read MDS Status +5.0 sub_command_1 B#16#0...
Page 54 MOBY Commands Acknowledgment data in the MDS-STATUS command Starting at address DAT_DB_address, data block DAT_DB_number contains the required data. These data are defined in an UDT so that the user can evaluate the information. Presentation of the MDS data in UDT 100 with sub_command_1 = 00 Table 4-19 UDT 160 “MDS STATUS FH”...
Page 55 MOBY Commands Presentation of the MDS data in UDT 100 with sub_command_1 = 01 Table 4-20 UDT 100 “MDS-STATUS” Address Name Type Commentary STRUCT +0.0 DINT MDS number +4.0 MDS_type BYTE 84 Hex = MDS with 2 kbytes 86 Hex = MDS with 32 kbytes +6.0 sum_subframe_ DINT...
Page 56 MOBY Commands 4.2.13 TRACE Parameterizing the command in Command_DB Table 4-21 UDT 50 “MOBY FH CMD” – TRACE Address Name Starting Commentary Value +0.0 DW#16#0 MDS number, only MOBY U with multitag +4.0 command ’T’ MDS command: T = Trace (absolute read) +5.0 sub_command_1 B#16#0...
Page 57 MOBY Commands 4.2.14 Parameterizing the command in Command_DB Table 4-22 UDT 50 “MOBY FH CMD” – GET Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’P’ Command: P = GET. Fetch UIDs of all MDSs located in the field. +5.0 sub_command_1 B#16#0...
Page 58 MOBY Commands 4.2.15 NEXT Parameterizing the command in Command_DB Table 4-24 UDT 50 “MOBY FH CMD” – NEXT Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’N’ MDS command: N = NEXT MDS +5.0 sub_command_1 B#16#0 Not used +6.0 sub_command_2 B#16#0...
Page 59 MOBY Commands 4.2.16 ASM/SLG-STATUS Parameterizing the command in Command_DB Table 4-25 UDT 50 “MOBY FH CMD” – ASM/SLG-STATUS Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’S’ MDS command: S = fetch STATUS of the ASM/SLG +5.0 sub_command_1 B#16#0 Set mode of the ASM/SLG-STATUS command...
Page 60 MOBY Commands 4.2.17 SET-ANT Parameterizing the command in Command_DB Table 4-26 UDT 50 “MOBY FH CMD” – SET-ANT Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’A’ MDS command: A = Turn Antenna On/Off +5.0 sub_command_1 B#16#0 Transfer mode of the antenna Turn on antenna.
Page 61 MOBY Commands 4.2.18 MOVE Parameterizing the command in Command_DB Table 4-27 UDT 50 “MOBY FH CMD” – MOVE Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’M’ MDS command: M = MOVE +5.0 sub_command_1 B#16#0 Not used +6.0 sub_command_2 B#16#0...
Page 62 MOBY Commands 4.2.19 LOAD Parameterizing the command in Command_DB Table 4-28 UDT 50 “MOBY FH CMD” – LOAD Address Name Starting Commentary Value +0.0 DW#16#0 Not used +4.0 command ’O’ MDS command: O = LOAD +5.0 sub_command_1 B#16#0 Not used +6.0 sub_command_2 B#16#0...
Page 63 Sample Applications FC 56 J31069-D0155-U001-A0-7618...
Page 64: Flow Chart Of The Fc 56 Scan
Sample Applications Scanning the FC 56 by the User The procedure used to scan the FC 56 is shown in the structogram in figure 5-1. New start: Set “init_run” ! OB 100 Cyclic scan: Set “command_start” ! start command (only if ready = 1) ready = 1 ? error = 1 ? If desired, timeout...
Page 65 Sample Applications Calling the FC 56 Cyclically (e.g., in OB 1) The following program is an example of calling and scanning the FC 56 in an application. The definition of the data structure is described in chapter 5.5. Parameterization of the MOBY command was already covered in the definition of the “MOBY DB.”...
Page 66 Sample Applications Programming of New Start and Restart A new start of the MOBY-ASM is triggered by setting the “init_run” variable. The ASM and FC 56 are completely reparameterized and synchronized with init_run. An init_run is required after: S SIMATIC is turned on (OB 100). S Power supply of ASM is turned on.
Page 67 Sample Applications Programming Module Failure Failure of a PROFIBUS module can be scanned with the PROFIBUS system diagnosis. However, when a failed slave is addressed by the FC 56, an I/O access error is generated on the SIMATIC. After this, the following occurs. S OB 122 is called.
Page 68 Sample Applications Segment: 2 Reset channel 2 on error #OB122_MEM_ADDR “MOBY DB”.SLG[2].ASM_address –D Formula: (#OB122_MEM_ADDR – SLG[x].ASM_address) / 2 + 1 “MOBY DB”.SLG[2].ASM_channel // Compare with conf. channel SPBN x2 “MOBY DB”.SLG[2].ASM_failure // Power failure on ASM After the error on the ASM has been corrected and the ASM is ready for operation again, the user must send an init_run to the FC 56.
Page 69 Sample Applications Specifying the Data Structure The developer can also define the MOBY data structure in different ways depending on the structure of the application. Below are some examples of possible data structures. 1st example Four SLGs are parameterized. One command is assigned to each SLG. MOBY parameters (DB 56), MDS commands (DB 57), and data (DB 58) are assigned to different data blocks.
Page 70: Example Of Several Moby Commands Assigned To One Channel
Sample Applications 2nd example Two commands are directly assigned to each MOBY channel. The MOBY parameters and the MOBY commands of all SLGs are stored in a “MOBY DB.” A nested structure is used for the declaration. Declaration view Data view MOBY_DB: DB 56: Chan.
Page 71 Sample Applications Below is an excerpt from a STEP 7 user program. It shows how easy it is to handle many MOBY channels with symbolic names. A command is started for each of the inputs 0.0, 0.1 and 0.3. Edge flags are used to prevent the commands from being started more than once.
Page 72: Example Of A Separate Data Block Assigned To Each Moby Channel
Sample Applications 3rd example A separate data block is assigned to each MOBY channel. Each data block contains the parameters, commands and data for one channel. Space for 10 MOBY commands should be reserved on each channel. Declaration view Data view DB 56: “SLG 1”...
Page 73 Sample Applications The UDTs of FC 56 The “MDS status” and “SLG status” commands supply a variety of data. The following UDTs can be used for clear presentation and for easy definition of the data blocks for the result. Table 5-1 Overview table of the UDTs Description Described...
Page 74 Sample Applications UDT 110: Result of SLG-STATUS (sub_command = 01) Table 5-2 UDT 110 “MOBY SLG-STATUS” Address Name Type Starting Commentary Value STRUCT +0.0 status_info BYTE B#16#0 SLG status mode +1.0 hardware CHAR ’ ’ Type of hardware +2.0 hardware_version WORD W#16#0 Version of hardware...
Page 75 Sample Applications UDT 120: Result of SLG diagnosis I SLG diagnosis I is only for information purposes. The results are identical to the same-named command of FC 45 (normal addressing). The interpretation of the results is also described there. Table 5-3 UDT 120 “MOBY SLG status diag.
Page 76 Sample Applications UDT 140: Result of SLG diagnosis III Table 5-5 UDT 140 “MOBY SLG status diag. 3” Address Name Type Starting Commentary Value STRUCT +0.0 status_info BYTE B#16#0 SLG status mode +1.0 number_MDS BYTE B#16#0 Range 1 to 24 +2.0 ARRAY [1...24] DW#16#0...
Page 77 Sample Applications Using the GET Command Use of the GET command depends on the multitag application. Basically, there are 2 methods of use. Static operation Dynamic operation If the application only uses one MDS (multitag = 1), the GET command is not needed.
Page 78 Sample Applications Dynamic operation With this mode, MDSs can enter or leave the transmission field at all times. The programming sequence is shown below. Scan whether the number of MDSs in the field has changed. ANZ_presence_change Scan UID. The ANZ_presence_change bit is automatically reset.
Page 79 Sample Applications Determining the Memory Requirements on the SIMATIC Normally, a MOBY application should not require too much memory on the SIMATIC S7. However, memory requirements must be considered when the following general conditions are present. S SIMATIC S7 with small amount of memory S Many MOBY channels (SLGs) are processed in one S7.
Page 80 Sample Applications FC 56 5-18 J31069-D0155-U001-A0-7618...
Page 81 Entry/Exit Check of an MDS in an SLG Field This section describes various ways of detecting the presence of an MDS in the transmission window of an SLG. The user can select the most suitable method for the application using the parameter “MDS_IO_control.” See chapter 3.1. Table 6-1 Entry/exit checking of an MDS MDS_IO_...
Page 82 Entry/Exit Check of an MDS in an SLG Field Definition of Terms Each SLG that processes an MDS writes its station-specific SLG number (SLG_number) to the system area of the MDS. The SLG number is written automatically before the first command to be executed on the MDS. The SLG number can be used to detect whether it is a new or an old data carrier that is currently passing the SLG station.
Page 83 Entry/Exit Check of an MDS in an SLG Field Entry/Exit Checking Mode 0 (MDS_IO_control 0) After receiving a command from the FC 56, the filehandler continuously attempts to establish communication with the MDS via the connected SLG. As soon as an MDS appears in the transmission window, the filehandler begins to process the command.
Page 84 Entry/Exit Check of an MDS in an SLG Field Entry/Exit Checking Mode 1 (MDS_IO_control 1) If a command is issued to the filehandler, the user must ensure that an MDS is present in the SLG transmission window. The command will be executed immediately.
Page 85 Entry/Exit Check of an MDS in an SLG Field Entry/Exit Checking Mode 5 (MDS_IO_control 5) In this mode of operation absolutely no checking of MDS entry/exit is carried out by the filehandler. The MDS control must be handled entirely by the user. If a command is issued to the filehandler, it will be stored until an MDS arrives in the transmission window of the SLG.
Page 86 Entry/Exit Check of an MDS in an SLG Field Diagram showing possible MDS states on an SLG Notes for the understanding and use of the following diagram The following section describes all types of status which are important for correct processing.
Page 87 Entry/Exit Check of an MDS in an SLG Field In status 23 the following can occur. S an old MDS enters the transmission window. Since the Next MDS bit is set, no processing of the temporarily stored command occurs. Status 21 is valid. S a new/next MDS enters the transmission window.
Page 88 Entry/Exit Check of an MDS in an SLG Field The codes shown below are used in the diagram on the following page: These MDS states are possible at an SLG: MDS not present new/next MDS present current or old (no longer current) MDS present command present (has been issued by the FC 56) command not present (has not yet been issued by the FC 56) command in progress (a command is now being executed)
Page 89 Entry/Exit Check of an MDS in an SLG Field COMMAND ARRIVES Î Î Î NEXT Î Î Î ackn. NEXT RESET Î Î Î no MDS at SLG / EAKO 1,4 DEPARTS ARRIVES Î Î Î Î Î Î NEXT DEPARTS ackn.
Page 90 Entry/Exit Check of an MDS in an SLG Field FC 56 6-10 J31069-D0155-U001-A0-7618...
Page 91 System Configuration Example of a Fixed File Structure in a Manufacturing Process A fixed file structure in the manufacturing process is distinguished by the fact that the individual SLGs only perform READ or WRITE/UPDATE functions on the MDS. Commands such as DIR, MDS-STATUS, ASM/SLG-STATUS, DELETE, FORMAT or CREATE are only carried out at “i-points”...
Page 92 System Configuration Piece-part and pallet/MDS circulation Piece–parts Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó Ó i–point Pallets (process Ó Ó Ó Ó Í Í Í Í Í Í Í SLG 2 SLG 3 with MDS monitoring) Í...
Page 93 System Configuration Example of a Variable File Structure in a Production Process A variable file structure in the manufacturing process is distinguished by the fact that any commands can be processed by any SLG. For instance: – additional files can be opened –...
Page 94 System Configuration FC 56 J31069-D0155-U001-A0-7618...
Page 95: Placement Of The Moby Asms In The Hardware Catalog
Commissioning Guidelines 1st step: Install ASM in STEP 7 S ASM 475, 473: The installation program for the ASM 475, 473 must be executed once on the STEP 7 PC. S PROFIBUS-ASM: The device master file (Siem80B6.GSD for ASM 452) must be linked to the device catalog with HW Config (Extras/Neue GSD installieren ...).
Page 96: Example Of A Hardware Configuration
Commissioning Guidelines Figure 8-2 Example of a hardware configuration If the project is loaded to the hardware in this state (i.e., without user program), the SIMATIC CPU and PROFIBUS must assume the RUN state. If they don’t, continue with PROFIBUS trouble-shooting (check the PROFIBUS address settings on the ASM against the configuration in HW Config).
Page 97: Editing Db
Commissioning Guidelines 4th step: Edit STEP 7 project The description of this step is based on the included sample program. S Copy the sample program for the FC 56 to the STEP 7 project which you just set up. S Continue as shown below based on the number of MOBY channels (number of SLGs).
Page 98: Variables For Function Check - Vat1
Commissioning Guidelines 5th step: Load and test program S Load the project to the SIMATIC CPU. S Connect an SLG of the parameterized MOBY type to each MOBY channel. S After the new start of the SIMATIC CPU (STOP → RUN), the CPU may not assume the STOP state.
Page 99 Commissioning Guidelines The variables “ready = TRUE” and “error = FALSE” must now be indicated for each channel. If ready = FALSE: – This channel is not called in OB 100. – This channel is not processed cyclically by an FC 56 call in OB 1. If error = TRUE: –...
Page 100 Commissioning Guidelines FC 56 J31069-D0155-U001-A0-7618...
Page 101 Error Messages and Trouble-Shooting FC 56 J31069-D0155-U001-A0-7618...
Page 102 Error Messages and Trouble-Shooting General Errors Programmable controller assumes STOP. S A slave has failed, and OB 86 is not programmed. S A slave has failed, and OB 122 is not programmed. This error does not occur until the FC 56 is called. S The pointers Params_DB, command_DB or DAT_DB do not exist or are pointing to a nonexistent address area.
Page 103 Error Messages and Trouble-Shooting error_code Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) A0 03 Illegal receiver identifier System error. Cannot occur with FC 56 (see telegram layout in chapter B.3) A0 06 The started command is not permitted (not defined). Correct the “command” parameter in the UDT 50 call (see chapter 4.1).
Page 104 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) B0 02 MDS_IO_control 1: A command has been issued, but there is no MDS in the transmission window of the SLG. The dialog battery of the MDS 507 is dead. (It is not mandatory to set the LR_bat bit. Measure battery voltage.) MDS_IO_control 0: The old/current MDS has moved out of the transmission window and the next/new...
Page 105 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) C0 08 Field interference at the SLG. The SLG is being affected by interference from its surroundings. Some examples are listed below. External interference field The distance between two SLGs is too small and does not conform to the design guidelines.
Page 106 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) C0 17 The filehandler is not working correctly. Check command format and command sequence. The ASM hardware (firmware) is defective. C0 18 Operating system error (AMOS mailbox) Perform init_run of the ASM.
Page 107 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) D0 14 WRITE command: There is no longer enough memory available in the MDS. Not all the data has been written to the MDS. CREATE command: No data blocks can be reserved when creating a file.
Page 108 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) H1 02 The length of the parameterized Params_DB/Params_ADDR is less that 300 bytes. The pointer Params_DB/Params_ADDR for the call of FC 56 is wrong. The Params_DB was not declared with UDT 10.
Page 109 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) H1 32 init_run cannot be executed. Cyclic process image to the ASM is faulty. FC 56 reports timeout of the process image to the ASM. The timeout time can be adjusted as necessary in DBB 58 of UDT 10.
Page 110 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) H8 24 Area length error while reading a parameter H8 25 Area length error while writing a parameter This error code indicates that parameter x is located in an area which is not allowed for the system function.
Page 111 Error Messages and Trouble-Shooting Table 9-2 Error messages via the “error_code” variable Error Code Description (B#16#..) H8 B0 SFC not possible for module type Data record unknown to module Data record number w 241 is not allowed. Data records 0 and 1 are not permitted for SFC 58 “WR_REC.” H8 B1 The length specified in the RECORD parameter is wrong.
Page 112 Error Messages and Trouble-Shooting Error Indication on the ERR-LED Some error states are not only indicated with error_code on the FC 56 but simultaneously also with the ERR-LED on the interface module. The ERR-LED indicates error messages with a flashing pattern (see table 9-3) followed by break in flashing.
Page 113 Short Description of the ASM Hardware This appendix discusses the special features of the individual interface modules which can be addressed with the FC 56. For a detailed hardware description of the interface modules with installation notes, see the appropriate MOBY manual on configuring, mounting and service. FC 56 J31069-D0155-U001-A0-7618...
Page 114: Configuration For Asm 475 (Centralized Layout
Short Description of the ASM Hardware ASM 475 The ASM 475 is an S7-300 module. It can be used in a centralized layout with an S7-300 or in a distributed layout with an ET 200M. ASM 475 Other modules from the S7 family (also ASM 475) ASM_channel: 1 2...
Page 115 Short Description of the ASM Hardware Input parameters for ASM 475 Assignment takes place in UDT 10 (see chapter 3). Table A-1 Input parameters for ASM 475 Address Name Permissible Values Commentary +0.0 ASM_address 256, 272, 288 ... 752 Centralized layout: Addresses are specified by HW Config (see chapter 2.5).
Page 116: Interfaces And Indicators Of The Asm 475
Short Description of the ASM Hardware Interfaces and indicators of the ASM 475 MOBY ASM475 System fault (hardware error on ASM) DC5 V DC 5 V: 24 V are connected to ASM and the ACT_1 5 V on ASM are okay. ERR_1 ACT_1, ACT_2: S–...
Page 117: Maximum Configuration Of Asm 473 On An Et 200X With
Short Description of the ASM Hardware ASM 473 Max. of 7 ASM 473s can be operated in one ET 200X. ASM_address: ASM_channel: Figure A-3 Maximum configuration of ASM 473 on an ET 200X with sample addressing Depending on the PROFIBUS master, up to 126 ET 200X modules can be run on one PROFIBUS branch.
Page 118: Input-Parameter
Short Description of the ASM Hardware Input parameters for ASM 473 Assignment takes place in UDT 10 (see chapter 3). Table A-2 Input parameters for ASM 473 Address Name Permissible Values Commentary +0.0 ASM_address 0, 4, 8, 12, ... Automatic or manual address assignment Each ASM 473 occupies 4 bytes of I/O in the peripheral area of the controller.
Page 119 Short Description of the ASM Hardware Interfaces and indicators of the ASM 473 Socket Pin Assignment (SLG) +RxD +TxD –TxD –RxD +24 V n. c. n. c. LEDs for PROFIBUS-DP General indicators (SF, BF, ON, DC24 V) are located on the basic model of the ET 200X LEDs for MOBY RxD:...
Page 120: Asm 452 Configurator
Short Description of the ASM Hardware ASM 452 The ASM 452 is a PROFIBUS-DP-V1 slave with a protection rating of IP67. One SLG can be run with the FC 56. AT-comp. PC PROFIBUS-DP master module (e.g., S7-400 CPU) PROFIBUS line ASM_channel 24 V for ASM...
Page 121 Short Description of the ASM Hardware Parameterization with GSD file In addition to the PROFIBUS–related control parameters, the GSD file for the ASM 452 also specifies several MOBY–related control parameters. The MOBY–related parameters are set in “Objekteigenschaften” of the slave in HW Config.
Page 122: Switch Settings, Interfaces And Indicators Of The Asm452
Short Description of the ASM Hardware Switch settings, interfaces and indicators of the ASM 452 Example: Terminal resistance off (status on delivery) Example: PROFIBUS address 120 (status on delivery) = 8 + 16 + 32 + 64 = 120 Normal use ASM 451 compatible (Use GSD file siem 804d.
Page 123 Programming MOBY-ASM on PROFIBUS-DP-V1 For whom is this appendix written? SIMATIC users can skip this chapter. It is of primary interest to programmers of PCs and controllers of other manufacturers to show them how to create their own function block or driver for the MOBY-ASM. Note Some signals in this appendix have the same meaning as the variables in chapter 3.
Page 124 Programming MOBY-ASM on PROFIBUS-DP-V1 Communication between ASM and PROFIBUS master PROFIBUS-DP must be able to transfer both the cyclic (DP) and the non-cyclic data (DP-V1). PROFIBUS DP PROFIBUS DP/V1 master with DP V1 function Other field MOBY ASM devices MOBY ASM Cyclic communication with Non cyclic communication with PROFIBUS DP .
Page 125: States Of Command And Acknowledgment Counter
Programming MOBY-ASM on PROFIBUS-DP-V1 Principle of controlling non-cyclic communication with command and acknowledgment counter Command counter Acknowledgment counter DP-V1 telegram DP-V1 telegram DP-V1 telegram Status of the counters after ASM startup or after an init_run_. Figure B-1 States of command and acknowledgment counter As you can see from the diagram above, a DP/V1 telegram triggers the change from one defined state to the next.
Page 126 Programming MOBY-ASM on PROFIBUS-DP-V1 Two states must be coded. 1. Command state (command counter) to tell the user whether a new/next command may be transferred to the MOBY-ASM 2. Acknowledgment state (acknowledgment counter) to tell the user whether a new acknowledgment from the MOBY-ASM is waiting User evaluation of the acknowledgment state must always be given highest priority (i.e., when the user wants to send a telegram to the ASM but a telegram from the ASM is waiting to be fetched at the same time, the...
Page 127: Layout Of The Cyclic Control Word
Programming MOBY-ASM on PROFIBUS-DP-V1 Cyclic Control Word between Master and MOBY-ASM The cyclic control word is used to synchronize telegram communication between master (FC) and slave (MOBY-ASM). The actual non-cyclic command and acknowledgment telegrams via DP/V1 may not be started until this is indicated by the cyclic byte of the MOBY-ASM in the command or acknowledgment counter.
Page 128: Startup Timing Initiated By User
Programming MOBY-ASM on PROFIBUS-DP-V1 After startup, the cyclic word of MOBY ASM takes on the following states (bits 8 to 15 are shown).... Before acknowledgment Before command Before command Before acknowledgment After command ... Startup 1st command 2nd command 3rd command (RESET) Synchronizing of command and acknowledgment counters...
Page 129: Command Processing: Command By Command
Programming MOBY-ASM on PROFIBUS-DP-V1 Working with the ASM Command processing is handled command by command. This means that, after each command, the user must wait for the acknowledgment (result) before the next command is sent to the ASM. This type of programming involves the following characteristics.
Page 130 Programming MOBY-ASM on PROFIBUS-DP-V1 Command and Acknowledgment Telegrams Commands and results are sent and received with the non-cyclic telegram utility of PROFIBUS-DP/V1. This chapter describes the telegrams. General telegram layout – filehandler The telegram layout applies to both command telegrams to the MOBY-ASM and result telegrams from the MOBY-ASM.
Page 131: General Telegram Layout
Programming MOBY-ASM on PROFIBUS-DP-V1 Telegram heading (always present) ... 239 res. res. res. Command User data EMPF The user data depends on the command (Cf. appendices B.5 and B.6.) Length of user data following (dual) Current data block number (dual) Total number of data blocks to be transmitted (dual) Command index ’I’...
Page 132 Programming MOBY-ASM on PROFIBUS-DP-V1 Blocking of Long Data Sequences Since it is not possible to work with telegrams of indefinite length, the telegram is formed into blocks, i.e. telegrams are transmitted in segments. Blocking can be used with READ, WRITE, UPDATE, QUEUE-WRITE, QUEUE-READ, LOAD, MOVE, DIR and TRACE commands.
Page 133 Programming MOBY-ASM on PROFIBUS-DP-V1 Schematic sequence (example WRITE): File description CC CI ’I’ 0003 0001 User data 1st command telegram from user to ASM The command consists of three telegram segments Processing of 1st telegram segment by the filehandler on the ASM CC CI 0003...
Page 134 Programming MOBY-ASM on PROFIBUS-DP-V1 The Filehandler Commands – Without Multitag The following table gives you an overview of all filehandler commands without multitag. These commands have the parameter CI = “I” set. Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout FORMAT...
Page 135 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout QUEUE- Read several Command: READ files with one 11/12 13/21 22/24 25..239 command KK KI DBN DBL 00 0000 0001 0001 Option Length Data In reserve 1 byte 3 bytes 2 bytes...
Page 136 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout DELETE Delete file Command: 11/18 0000 ’D’ ’I’ 0001 0001 File name Acknowledgement: Status 0000 ’D’ 0001 0001 ATTRIB Assign file Command: attribute 11/18 0000 ’Y’...
Page 137 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout MDS- Read MDS Command: STATUS status DBN DBL (corresponds to sub_command = 0) 0000 0001 0001 0000 0001 0001 sub_command Year Acknowledgement (sub_command = 00): 8/9 10 11/18 20/22 23/25...
Page 138 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout MOVE Read MDS Command: directory from ASM 0000 ’M’ ’I’ 0001 0001 Acknowledgement: 11/12 13 ... KK Status ADB DBN DBL Data xx 0000 ’M’ xxxx 0001 Length...
Page 139 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout ASM/SLG- Read Command: STATUS ASM/SLG- status 0000 ’S’ ’I’ 0001 0001 0000 ’S’ ’I’ 0001 0001 sub_command Acknowledgement (sub_command = 00): 11/18 19/44 45/70 KK Status ADB 00 xx 0000 ’S’...
Page 140 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-1 Filehandler commands – without multitag Command Meaning Telegram Layout RESET RESET Command: command to 14/15 KK KI DBN DBL 0000 ’X’ ’I’ 0001 0001 07 RESET mode EAKO SLG No. Prior. Block len. 0000 ’X’...
Page 141 Programming MOBY-ASM on PROFIBUS-DP-V1 The Filehandler Commands – With Multitag The following table gives you an overview of all filehandler commands with multitag. These commands have the parameter CI = “U” set. Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout FORMAT...
Page 142 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout QUEUE- Read several Command: READ files with one 11/14 15/16 17/25 26/28 29 ... 239 command KK KI 00 0000 0001 0001 Option Length Data In reserve 1 byte 3 bytes...
Page 143 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout DELETE Delete file Command: 11/14 15/22 0000 ’D’ ’U‘ 0001 0001 File name Acknowledgement: 11/14 Status 0000 ’D’ 0001 0001 ATTRIB Assign file Command: attribute 11/14 15/22 0000...
Page 144 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout MDS- Read MDS Command: STATUS status 11/14 KK KI 00 0000 0001 0001 sub_command Year Acknowledgement (sub_command = 00): 8/9 10 11/14 15/22 24/26 27/29 30/31 33/35 Sta- ADB DBN DBL...
Page 145 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout SET-ANT Turn SLG Command: antenna on or off 0000 ’A’ ’U‘ 0001 0001 sub_command Acknowledgement: Status 0000 ’A’ 0001 0001 ASM/SLG- Read Command: STATUS ASM/SLG- status 0000 ’S’...
Page 146 Programming MOBY-ASM on PROFIBUS-DP-V1 Table B-2 Filehandler commands – with multitag Command Meaning Telegram Layout RESET RESET Command: command to 14/15 KK KI DBN DBL MDS_IO_ 0000 ’X’ ’U‘ 0001 0001 0D RESET mode SLG No. Prior. Blockl. Standby control 20/21 dili 0001...
Page 147 Programming MOBY-ASM on PROFIBUS-DP-V1 PROFIBUS Implementation PROFIBUS is implemented on the MOBY-ASM strictly in accordance with the standard IEC 61784-1:2002 Ed1 CP 3/1. Cyclic data communication (standard specified by EN 50170) and optional non-cyclic data communication are used. The following figure shows the communication interface to a MOBY-ASM. PAW and PEW are exchanged cyclically between ASM and function block.
Page 148 Programming MOBY-ASM on PROFIBUS-DP-V1 The following figure shows the layout of a non-cyclic data record. SAP 51 is used to transmit the data. The data unit (DU) indicates how the MOBY-ASM is addressed. DSAP SSAP 51/33H 51/33H x... Octet 1 Function code (e.g., DS_Read.req) (DS = Data Record) 0= Request/response okay...
Page 149 Programming MOBY-ASM on PROFIBUS-DP-V1 The following data records have been implemented on the MOBY-ASM for communication. Table B-3 Data record numbers Data Present on MOBY-ASM Description Record No. Reserved Reserved Parameterization channel 1 ASM 475 Parameterization channel 2 Data transmission channel 1 ASM 475 Data transmission channel 2 ASM 475, 473...
Page 150 Programming MOBY-ASM on PROFIBUS-DP-V1 Example of a PROFIBUS Trace The following trace shows all telegrams which were sent on the PROFIBUS interface during an ASM startup or a MOBY read command. The trace illustrates appendices B.1 to B.7. It can also be used for orientation or for trouble-shooting of customer-specific MOBY-ASM implementations.
Page 151 Programming MOBY-ASM on PROFIBUS-DP-V1 Startup of an ASM 452 and RESET sequence on 1st channel 68 0b 0b 68 03 02 5d 00 00 00 00 00 12 Startup of ASM 68 0b 0b 68 02 03 08 80 00 80 00 00 12 68 0b 0b 68 03 02 7d 80 00 80 00 00 12 FC sets the startup bit.
Page 152 Programming MOBY-ASM on PROFIBUS-DP-V1 FC 56 B-30 J31069-D0155-U001-A0-7618...
Page 153 Siemens AG A&D SE ES 4 PO Box 2355 D-90713 Fuerth FROM: Your name: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _...
Page 154 Your remarks and suggestions help us to improve the quality of our documentation. Please complete this questionnaire as soon as you have time, and return it to Siemens. Title of your manual:_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Order number of your manual:_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Please enter your personal evaluation from 1 (good) to 5 (poor).

Siemens MOBY FC 56 Technical Description

Quick Links

Related Manuals for Siemens MOBY FC 56

Summary of Contents for Siemens MOBY FC 56

Table of Contents