1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Other
  5. SIMATIC FC 45
  6. Function manual

Siemens SIMATIC FC 45 Function Manual

Sensors
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SIMATIC Sensors RFID systems FC 45
SIMATIC Sensors
RFID systems
FC 45
Function manual
Release 03/2006
J31069-D0167-U001-A2-7618
______________
Introduction
______________
Description
______________
Parameterizing
______________
Commissioning
Error messages
______________
and troubleshooting
______________
Examples/applications
Brief description
______________
of ASM hardware
Programming the
______________
MOBY-ASM on PROFIBUS
______________
Service & Support
1
2
3
4
5
6
A
B
C

Advertisement

Table of Contents
loading

Related Manuals for Siemens SIMATIC FC 45

Summary of Contents for Siemens SIMATIC FC 45

  • Page 1 ______________ Introduction SIMATIC Sensors RFID systems FC 45 ______________ Description ______________ Parameterizing SIMATIC Sensors ______________ Commissioning RFID systems FC 45 Error messages ______________ and troubleshooting ______________ Examples/applications Function manual Brief description ______________ of ASM hardware Programming the ______________ MOBY-ASM on PROFIBUS ______________ Service &...
  • Page 2 Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

  • Page 3: Table Of Contents

    Table of contents Introduction............................. 1-1 Preface............................1-1 Navigating in the Function Manual .................... 1-2 Description.............................. 2-1 Block specification ........................2-3 Configuration scheme ........................ 2-5 Data structures of FC 45......................2-6 Number of MOBY channels which can be connected ............... 2-7 Addressing of MOBY channels ....................
  • Page 4 Table of contents Brief description of ASM hardware......................A-1 ASM 475.............................A-1 ASM 473.............................A-6 ASM 452...........................A-10 ASM 454...........................A-17 ASM 754...........................A-20 ASM 854...........................A-23 ASM 850...........................A-29 Programming the MOBY-ASM on PROFIBUS..................B-1 Programming the MOBY-ASM on PROFIBUS DP-V1...............B-1 Cyclic Control Word between Master and MOBY-ASM.............B-5 Methods of operation with the ASM ...................B-8 Command and acknowledgement telegrams................B-13 PROFIBUS implementation .....................B-22...
  • Page 5 Table of contents Tables Table 2-1 Typical runtimes of FC 45 (cycle load of AS in ms) ..............2-3 Table 2-2 MOBY FC configuration scheme ....................2-5 Table 2-3 Number of MOBY channels ....................... 2-7 Table 3-1 UDT 10 "MOBY Param"......................3-2 Table 3-2 INPUT parameters ........................
  • Page 6 Table of contents Table 6-10 UDT 280 "write/read device status (mode 6, RF300)" ............. 6-19 Table A-1 Input parameters for ASM 475 ....................A-2 Table A-2 Commands for ASM 475......................A-3 Table A-3 Input parameters for ASM 473 ....................A-7 Table A-4 Commands for ASM 473......................A-7 Table A-5 Pin assignment of sockets X3, X4 .....................A-8 Table A-6...

  • Page 7: Introduction

    Introduction Preface Purpose of this document This Function Manual contains all the information needed to configure and commission the system. It is intended both for programming and testing/debugging personnel who commission the system themselves and connect it with other units (automation systems, further programming devices), as well as for service and maintenance personnel who install expansions or carry out fault/error analyses.

  • Page 8: Navigating In The Function Manual

    Introduction 1.2 Navigating in the Function Manual Navigating in the Function Manual Structure of contents Contents Table of Contents Organization of the documentation, including the index of pages and chapters Introduction Purpose, layout and description of the important topics. Parameterizing Description of the parameter settings Commissioning Description of the commissioning procedure...

  • Page 9: Description

    Description The FC 45 is a STEP7 function for MOBY identification technology. It can be used with both the SIMATIC S7-300 and S7-400 for various MOBY interface modules. Figure 2-1 Interface modules for FC 45 Section "Brief description of ASM hardware" illustrates configurations with the various interface modules.
  • Page 10 Description Performance features of FC 45 • All MOBY systems (write/read devices and MDSs) can be used with the FC 45. • The user can process a complete MDS with one command (up to 32KB). • The user can chain several commands together. This means that many small data areas of an MDS can be processed with one command start.

  • Page 11: Block Specification

    Description 2.1 Block specification Block specification Block number: FC 45 Block name: FC 45 Symbolic name: "MOBY FC" Family: – Work memory requirement: 7260 bytes Local data: 132 bytes Version: Called blocks: SFC 58, SFC 59, SFC 20, SFC 21, SFC 1 Data block resources: MOBY Param = 300 bytes per channel (defined via UDT 10)
  • Page 12 Description 2.1 Block specification Calculating MOBY data throughput The formulas in the MOBY manual for configuration, mounting and service (Chapter 3) can be used to calculate data throughput with the FC 45. Configuration manuals are currently available for MOBY I (6GT2 097-4BA00-0EA2), MOBY E (6GT2 397-4BA00-0EA2), MOBY F (6GT2 497-4BA00-0EA2), MOBY U (6GT2 597-4BA00-0EA2) and MOBY D (6GT2 697-4BA00-0EA2).

  • Page 13: Configuration Scheme

    Description 2.2 Configuration scheme Configuration scheme Table 2-2 MOBY FC configuration scheme Ladder logic Parameters Data type Permissible range Description programming box Params_DB 2 to 32767 Parameter data block number for a MOBY channel (write/read device) MOBY FC Params_ADDR 0, 300, 600,*... Address pointer in the parameter data block to the start of a UDT 10 Params_DB...

  • Page 14: Data Structures Of Fc 45

    Description 2.3 Data structures of FC 45 Data structures of FC 45 The following figure shows an example of a definition of several MOBY channels with the related MDS commands and the user data. Figure 2-2 Configuration scheme of FC 45 Each FC 45 call points to a separate parameter data block (Params_DB, Params_ADDR), which is defined by a UDT 10.

  • Page 15: Number Of Moby Channels Which Can Be Connected

    Description 2.4 Number of MOBY channels which can be connected 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 supported by SIMATIC can always be operated. The following table provides an overview.

  • Page 16: Addressing Of Moby Channels

    Description 2.5 Addressing of MOBY channels Addressing of MOBY channels Centralized configuration with ASM 475 In the centralized configuration, 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 17 Description 2.5 Addressing of MOBY channels Addressing via PROFIBUS When addressing via PROFIBUS, any addresses for the MOBY communication module can be selected in HW Config. HW Config assigns a free address by default. Figure 2-4 Example: Automatic address generation for a MOBY PROFIBUS slave Figure 2-5 Example: Automatic address generation of a MOBY-ASM in ET 200 configuration Assignment of addresses in FC 45...
  • Page 18 Description 2.5 Addressing of MOBY channels Figure 2-6 Setting the physical address assignment in UDT 10 The MOBY channel (ASM_channel) must be assigned uniquely in addition to the address (ASM_address). When an ASM is used with several channels (ASM 475, 452, 454, 754, 854), a separate UDT 10 must be defined for each channel.

  • Page 19: Parameterizing

    Parameterizing Parameter data block Each MOBY channel (write/read device) requires its own parameters. These are predefined in a data structure as UDT 10 (with commentary in English), UDT 11 (with commentary in German) or UDT 14 (with commentary in Spanish). That UDT must be called in a data block for each MOBY channel.

  • Page 20: Table 3-1 Udt 10 "Moby Param

    Parameterizing 3.1 Parameter data block The following table shows the complete UDT 10. For programmers who prefer to address using absolute values, the first column specifies the relative addresses. Table 3-1 UDT 10 "MOBY Param" Address Name Type Initial Comment value STRUCT +0.0...

  • Page 21: Input Parameters

    Parameterizing 3.1 Parameter data block 3.1.1 INPUT parameters Table 3-2 INPUT parameters 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. Remember that this address has nothing to do with the PROFIBUS address which is set on the ASM or the ET 200M.
  • Page 22 Parameterizing 3.1 Parameter data block Variable Description Default -; Reserved for setting the operating mode with switch or GSD parameterization. Various interfaces without switches interpret MOBY mode = 0 as MOBY I mode. MOBY I or MOBY E (without MDS 507) MOBY I with MDS 507 452;...
  • Page 23 Parameterizing 3.1 Parameter data block Variable Description scanning_time MOBY U: Scanning_time describes the standby time for the MDS. If the MDS receives an additional command before scanning_time has expired, this command can be executed immediately. If the MDS receives a command after scanning_time has expired, command execution is delayed by sleep_time of the MDS.
  • Page 24 Parameterizing 3.1 Parameter data block Variable Description distance_limiting MOBY U: Range limitation Normal transmission power Reduced transmission power 05 hex = 0.5 m 85 hex Reduced sending capacity must be set when several 0A hex = 1.0 m 8A hex write/read devices are positioned close together or 0F hex = 1.5 m 8F hex...

  • Page 25: Command And Status Word

    Parameterizing 3.1 Parameter data block 3.1.2 Command and status word The control bits of FC 45 are defined in the command and status word. The command and status word and the variables are generated using UDT 10. The variables and the associated relative addresses in UDT 10 are shown in the following figure. Figure 3-1 Assignment of the command and status word (DBW 18) with variable names FC 45...

  • Page 26: Table 3-3 Variables In Command And Status Word

    Parameterizing 3.1 Parameter data block Table 3-3 Variables in command and status word Variable Description True cancel = Interrupts a running command or a command chain. FC 45 then sets the "ready" variable. MOBY U/D: The cancel variable is not available. A command termination must be executed via the init_run variable.
  • Page 27 Parameterizing 3.1 Parameter data block Variable Description ANZ_MDS_present Indicates the presence of an MDS in the write/read device's transmission window. ANZ_MDS_present is only indicated when the INPUT parameter MDS_control (see Section "INPUT parameters") was set by the user. Remember that when an init_run is being executed, the ANZ_MDS_present indication disappears briefly even when an MDS is permanently located in the transmission window.

  • Page 28: Further Displays

    Parameterizing 3.1 Parameter data block 3.1.3 Further displays Table 3-4 Displays Variable Description ASM_busy This bit is set when the ASM is processing a command. "ASM_busy" is normally inverse to "ready". The interface module signals ASM_busy via the cyclic word (see Section "Cyclic control word between master and MOBY-ASM"...

  • Page 29: Moby Commands

    Parameterizing 3.2 MOBY commands MOBY commands Note This chapter provides a description of all commands which can by processed by FC 45. The commands, which can actually be processed by the interface module you are using, are described here. Before you can start a MOBY command with command_start, you need to define the command.

  • Page 30: Command Parameters

    Parameterizing 3.2 MOBY commands 3.2.1 Command parameters Overview of commands Table 3-6 Overview of commands Command [hex] Command normal chained* Write data to MDS Read data from MDS Initialize MDS SLG status – NEXT END; conclude communication with the MDS Antenna on/off MDS status *) Chained commands are not supported by all write/read devices or ASMs.
  • Page 31 Parameterizing 3.2 MOBY commands Initialization Table 3-9 Initialize MDS Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 00 to FF, hex value – Memory size of the – with which the MDS MDS to be initialized is written MDS type Memory size Init duration...
  • Page 32 Parameterizing 3.2 MOBY commands SLG status Table 3-10 SLG status Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 01 = status after – – Pointer to MOBY U/D UDT 110 result. 02 = status after The result is MOBY U UDT 120 indicated with the...
  • Page 33 Parameterizing 3.2 MOBY commands Table 3-12 Terminate communication with MDS Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 00 = Processing with – – – ANZ_MDS_present is MDS has terminated reset. 01 = Processing pause with MDS ANZ_MDS_present remains set.
  • Page 34 Parameterizing 3.2 MOBY commands MDS status Table 3-14 MDS status and diagnosis Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 00 = status and – Today's date Pointer to Only MOBY U diagnosis (week/year) for result. (see Section "UDTs calculating the The result of FC 45")

  • Page 35: Command Chaining

    Parameterizing 3.2 MOBY commands 3.2.2 Command chaining Command chaining permits various address areas of the MDS to be processed by starting just one command. The advantage of command chaining is the optimum speed at which commands can be processed on the ASM. A command chain is set up by the user by storing a succession of UDT 20s in a DB.

  • Page 36: Table 3-16 Db 47 - Data View

    Parameterizing 3.2 MOBY commands Table 3-16 DB 47 - data view Name Initial value Comment Partial command [1].command Read command; followed by another Partial command [1].pattern command Partial command [1].length Partial command [1].adress_MDS 0000 Partial command [1].DAT_DB_number Partial command [1].DAT_DB_address Partial command [2].command Read command;...

  • Page 37: Command Repetition

    Parameterizing 3.2 MOBY commands 3.2.3 Command repetition Operating principle After a new start (or init_run) of the ASM, the FC 45 transmits the command (or command chain) once to the ASM. Command transmission is automatic with the first command_start. This command (or the last command or the command chain) always remains intermediately stored in the ASM.

  • Page 38: Table 3-17 Number Of Buffers On The Asm

    Parameterizing 3.2 MOBY commands Programming There are two programming methods. • Reading (processing) each MDS which comes by. After the ASM is programmed with a command, repeat_command is set and remains set. The following diagram shows the primary states. Figure 3-2 Continuous reading of each passing MDS/transponder (repeat_command remains set) When permanent command repetition is used, data may be transferred to the FC 45 slower than new MDSs are being processed (fast MDS sequence, slow data transmission).
  • Page 39 Parameterizing 3.2 MOBY commands • Specific reading (processing) of an MDS. The user starts the processing of each new MDS in his/her application. The following time diagram illustrates this principle. Figure 3-3 Starting specific reading with repeat_command by the user FC 45 3-21 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

  • Page 40: Presence Check And Mds Control

    Parameterizing 3.3 Presence check and MDS control Presence check and MDS control Various operating modes can be parameterized for MDS control (with parameter MDS_control). The exact interaction between these modes for the following components: • Presence check • MDS control •...
  • Page 41 Parameterizing 3.3 Presence check and MDS control NEXT command The Next command switches ASM control to the next mobile data memory. The Next command must always be programmed when MDS control is used (MDS_control = 2). After the ASM acknowledges the Next command, a read/write job for the next MDS can be sent immediately to the write/read device.

  • Page 42: No Mds Control, No Presence Check: Mds_Control = 0

    Parameterizing 3.3 Presence check and MDS control 3.3.1 No MDS Control, No Presence Check: MDS_control = 0 The magnetic field of the write/read device is not turned on unless a valid MDS command (read, write, initialize) is started. After a data memory has been detected and the command has been executed, the write/read device is turned off again.

  • Page 43: Field Scanning As Mds Control: Mds_Control = 2

    Parameterizing 3.3 Presence check and MDS control 3.3.3 Field Scanning as MDS Control: MDS_control = 2 After a new start or a restart of the AS or after a new start or RESET command of the FC 45, the write/read device is turned on and remains active until the AS or ASM is turned off. The ASM continuously scans the field around the write/read device for the presence of a data memory.
  • Page 44 Parameterizing 3.3 Presence check and MDS control Time diagram Figure 3-4 Time diagram for MDS_control = 2 ASM error messages Error 01 hex: The MDS leaves the write/read device's field while a command is being processed with this MDS. The command is aborted. The read data are invalid.

  • Page 45: Commissioning

    Commissioning 1st step: Install ASM in STEP 7 • ASM 475, 473: The installation program for the ASM 475, 473 must be executed once on the STEP 7 PC. • PROFIBUS-ASM: The GSD file (Siem809F.GSD for ASM 454, 754, 854, 850 or Siem80B6.GSD for ASM 452) must be linked to the device catalog with HW Config (Tools >...
  • Page 46 Commissioning When configuring the ASMs, make sure that the I address and the Q address have the same values. The value in the I address field must be copied later on into the ASM_address variable in the STEP 7 project. If a MOBY-ASM has more than one channel (e.g. ASM 475 = 2 channels, ASM 454 = 4 channels), the same I address must be used for every channel.
  • Page 47 Commissioning 3rd step: Set caracteristics of the ASM If the interfaces (e.g., ASM 452, 473, 475) are different, you can now set the basic function of the ASM (e.g., MOBY U, filehandler, etc.) in the object properties of the module. The object properties are shown in one of the following windows.
  • Page 48 Commissioning 4th step Process STEP 7 project This step is based on the sample program supplied with the system. • Copy the sample program for FC 45 into the new STEP 7 project. • Continue as shown below based on the number of MOBY channels (number of write/read devices).
  • Page 49 Commissioning 5th step: Download and test the program • Download the project onto the SIMATIC CPU • Connect a write/read device of the parameterized MOBY type to each MOBY channel. • After restarting the SIMATIC CPU (STOP → RUN), the CPU should not be in STOP mode.
  • Page 50 Commissioning The variables ready = TRUE and error = FALSE should 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 45 call in OB 1. If error = TRUE: •...

  • Page 51: Error Messages And Troubleshooting

    Error messages and troubleshooting General errors Automation system switches to STOP • OB 86 not programmed and a slave has failed. • A slave has failed, and OB122 is not programmed. The error does not occur until FC 45 is called. •...

  • Page 52: Error Messages

    Error messages and troubleshooting 5.2 Error messages Error messages An error condition exists in FC 45 whenever the "error" variable is enabled on a channel. If this is the case, the exact cause of the error can be determined from variable "error_MOBY", "error_FC"...

  • Page 53: Table 5-2 Error Messages Of The Moby-Asm Via The "Error_Moby" Variable

    Error messages and troubleshooting 5.2 Error messages error_MOBY The ERR LED flashes when the ASM reports error messages. Table 5-2 Error messages of the MOBY-ASM via the "error_MOBY" variable Error code Flashing of Description ERR LED (B#16#..) – No error Default value if everything is ok.
  • Page 54 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#..) Error in MDS's memory The MDS has never been write-accessed or has lost the contents of its memory due to battery failure. Replace MDS (if battery bit is set). •...
  • Page 55 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#..) Only during initialization: MDS is unable to perform the initialization command. MDS is defective. • MOBY I: Only during initialization: Timeout during initialization of the The MDS is positioned exactly on the boundary of the transmission •...
  • Page 56 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#..) Next command not possible or not permitted ASM is running without MDS control (MDS_control = 0,1). • ASM has already received a Next command. • ASM / write/read device doesn't recognize NEXT command.
  • Page 57 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#..) Previous command is active or buffer overflow. The user sent a new command to the ASM although the last command was still active. Active command can only be terminated with an init_run. •...

  • Page 58: Table 5-3 Error Variable "Error_Fc

    Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#..) – Running command canceled by RESET (init_run or cancel) or bus connector removed Communication with the MDS was terminated by init_run. • This error can only be reported on init_run or cancel •...
  • Page 59 Error messages and troubleshooting 5.2 Error messages Error code Description (B#16#..) The ASM has failed. Power failure on MOBY-ASM • PROFIBUS connector removed or PROFIBUS cable interrupted • ASM_address or ASM_channel not available • This error is indicated if the ASM_failure bit (see Section "Command and status word") was set in OB 122.

  • Page 60: Table 5-4 Error Variable "Error_Bus

    Error messages and troubleshooting 5.2 Error messages error_BUS Table 5-4 Error variable "error_BUS" Error code Description (W#16#...) 800A ASM is not ready (temporary message). This message is given to a user who is not using the FC 45 and is continuously •...
  • Page 61 Error messages and troubleshooting 5.2 Error messages Error code Description (W#16#...) 80A0 Negative acknowledgment while reading from module. FC fetches acknowledgment although no acknowledgment is ready. A user who is not using the FC 45 would like to fetch DS 101 (or DS 102 to104) although no acknowledgment is available.
  • Page 62 Error messages and troubleshooting 5.2 Error messages FC 45 5-12 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

  • Page 63: Examples/Applications

    Examples/applications FC 45 scanning by user Scanning of FC 45 takes place in accordance with the structogram in the following figure. Figure 6-1 Structogram for scanning of FC 45 FC 45 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

  • Page 64: Processing Of Data Memories/Transponders

    Examples/applications 6.2 Processing of data memories/transponders Processing of data memories/transponders Data memory types Mobile data memories with different storage capacities are available. The following table specifies the memory capacities currently available. Table 6-1 Available memory capacities Memory capacity Memory type MOBY family MDS type 2 (1.7) Kbytes...
  • Page 65 Examples/applications 6.2 Processing of data memories/transponders Address space of MDS versions for MOBY I, E, F, U and D System Addressing 16-Bit Hexadecimal Number Integer number MOBY I 2 KB data memory with RAM Start address 0000 0000 (with ECC) +0 (with ECC) End address 07FC...
  • Page 66 Examples/applications 6.2 Processing of data memories/transponders System Addressing 16-Bit Hexadecimal Number Integer number MOBY D MDS D139 (I-Code 1; 44 bytes) Start address 0000 End address 002B ID no.: (fixed-coded; can only be read as a whole) Start address FFF0 Length 0008 ISO-MDS (I-Code SLI;...
  • Page 67 Examples/applications 6.2 Processing of data memories/transponders System Addressing 16-Bit Hexadecimal Number Integer number RF300 8 KB data memory (FRAM/EEPROM) R/W or OTP memory (EEPROM) (The EEPROM user memory for RF300 can be used either as R/W memory or as an OTP memory (see RF300 system manual)) Start address FF00...
  • Page 68 Examples/applications 6.2 Processing of data memories/transponders RF300: Address mapping on the transponder R/W EEPROM memory and OTP memory is only available once on the transponder. The following table shows the mapping of addresses on the transponder. Data can be read via the R/W address or the OTP address. R/W EEPROM Write OTP once Address...

  • Page 69: Cyclic Calling Of Fc 45 (E.g. In Ob 1)

    Examples/applications 6.3 Cyclic calling of FC 45 (e.g. in OB 1) Cyclic calling of FC 45 (e.g. in OB 1) The following program is an example of how to call and scan FC 45 in an application. The definition of the data structure is described in Section "Data structure definition". The parameter settings for the MOBY command were set up during the definition of the "MOBY DB".

  • Page 70: Programming A Cold And Warm Restart

    Examples/applications 6.4 Programming a cold and warm restart Programming a cold and warm restart The MOBY-ASM is restarted by setting the "init_run" variable. The ASM and FC 45 are completely reparameterized and synchronized with init_run. An init_run is necessary after •...

  • Page 71: Programming A Module Failure

    Examples/applications 6.5 Programming a module failure Programming a module failure The failure of a PROFIBUS module can be detected primarily using the PROFIBUS system diagnostics. However, if a failed slave is addressed via FC 45, an I/O access error is generated in SIMATIC.
  • Page 72 Examples/applications 6.5 Programming a module failure Network: 2 Reset channel 2 on error L #OB122_MEM_ADDR "MOBY DB".SLG[2].ASM_address SRW 1 // Formula: // (#OB122_MEM_ADDR - SLG[x].ASM_address) / 2 + 1 // Compare with config. "MOBY DB".SLG[2].ASM_channel channel SPBN x2 // Power failure on ASM S "MOBY DB".write/read device[2].ASM_failure NOP 0...

  • Page 73: Data Structure Definition

    Examples/applications 6.6 Data structure definition Data structure definition The developer can define different MOBY data structures depending on the structure of the application. Some example structures are given below. 1st example Four SLGs are parameterized. One command is assigned to each write/read device. MOBY parameters (DB 45), MDS commands (DB 47), and data (DB 48) are assigned to different data blocks.
  • Page 74 Examples/applications 6.6 Data structure definition 2nd example 2 commands are assigned directly to each MOBY channel. The MOBY parameters and the MOBY commands of all write/read devices are stored in a "MOBY DB". A nested structure is used in the declaration. Figure 6-2 Example of several MOBY commands assigned to one channel FC 45...
  • Page 75 Examples/applications 6.6 Data structure definition The following shows an extract from a STEP 7 user program. It shows how a large number of MOBY channels can be handled easily using symbolic names. A command is started via each of the inputs 0.0, 0.1 and 0.3. An edge trigger flag is used to prevent the command from being started several times: MOBY DB.channel[1].ready // 1st MOBY...
  • Page 76 Examples/applications 6.6 Data structure definition 3rd example A separate data block is assigned to each MOBY channel. It contains the parameters, commands and data for a channel. Space for 10 MOBY channels should be reserved on each channel. Figure 6-3 Example of a separate data block assigned to each MOBY channel FC 45 6-14...

  • Page 77: Udts Of Fb 45 / Fc 45

    Examples/applications 6.7 UDTs of FB 45 / FC 45 UDTs of FB 45 / FC 45 The "MDS status" and "Write/read device status" commands supply a variety of data. The UDTs described in the following section can be used for clear presentation and easy definition of the data blocks for the result.

  • Page 78: Table 6-3 Udt 100 "Moby Mds Status

    Examples/applications 6.7 UDTs of FB 45 / FC 45 UDT 100: Result of MDS status Table 6-3 UDT 100 "MOBY MDS status" Address Name Type Comment STRUCT +0.0 DWORD MDS (unique identifier) +4.0 MDS_type BYTE +6.0 sum_subframe_access DINT Sum of subframe access +10.0 sum_searchmode_access Sum of searchmode...

  • Page 79: Table 6-5 Udt 120 "Moby Write/Read Device-Stat Diag 1"

    Examples/applications 6.7 UDTs of FB 45 / FC 45 UDT 120: Result of write/read device diagnosis I Table 6-5 UDT 120 "MOBY write/read device-Stat Diag 1" Address Name Type Comment STRUCT +0.0 status_info BYTE Write/read device status mode +1.0 number_functions BYTE Range: 1...33 +2.0...

  • Page 80: Table 6-8 Udt 260 "Mds Status (Mode 1, Rf300)

    Examples/applications 6.7 UDTs of FB 45 / FC 45 UDT 260: Result of MDS status (mode 1, RF300) Table 6-8 UDT 260 "MDS status (mode 1, RF300)" Address Name Type Comment STRUCT +0.0 status_info BYTE MDS status mode +1.0 ARRAY[1...8] Number of MDS (unique identifier) BYTE +9.0...
  • Page 81 Examples/applications 6.7 UDTs of FB 45 / FC 45 UDT 280: Result of read/write status (mode 6, RF300) Table 6-10 UDT 280 "write/read device status (mode 6, RF300)" Address Name Type Comment STRUCT +0.0 status_info BYTE Write/read device status mode +1.0 BYTE Error counter, passive (errors during idle...

  • Page 82: Determing The Memory Requirement In The Simatic

    Examples/applications 6.8 Determing the memory requirement in the SIMATIC Determing the memory requirement in the SIMATIC The memory resources used in SIMATIC S7 by a MOBY application should normally not reach the system limits on the PLC. However, if the following conditions occur simultaneously, the memory requirement must be considered: •...

  • Page 83: Brief Description Of Asm Hardware

    Brief description of ASM hardware This appendix discusses the special features of the individual interface modules which can be addressed with the FC 45. For a detailed hardware description of the interface modules with installation notes, see the appropriate MOBY manual on configuring, mounting and service. ASM 475 The ASM 475 is an S7-300 module.

  • Page 84: Asm 452

    Brief description of ASM hardware A.1 ASM 475 Write/read device / reader connection system Prefabricated write/read device connection cables are available in various lengths for the ASM 475. The cores at the open end to the ASM/communication module are marked with connection numbers.

  • Page 85: Asm 454

    Brief description of ASM hardware A.1 ASM 475 Table of commands for ASM 475 The assignment is made in UDT 20 using the "Command" variable (see Section "Command parameter settings"). Table A-2 Commands for ASM 475 Command code Description available in the MOBY system normal Chained...

  • Page 86: Asm 754

    Brief description of ASM hardware A.1 ASM 475 Interfaces and indicators of the ASM 475 System fault (hardware error on ASM) DC 5 V: 24V are connected to ASM and the 5V on ASM are okay. ACT_1, ACT_2: The corresponding write/read device is active in processing an application command.

  • Page 87: Asm 854

    Brief description of ASM hardware A.1 ASM 475 The following ASM states are indicated with the LEDs PRE, ERR and SF. PRE_1 ERR_1 PRE_2 ERR_2 Description, Causes, Remedy OFF/ON ON (perm.) OFF/ON ON (perm.) Hardware is defective (RAM, Flash, …) Loader is defective (can only be fixed at the plant).

  • Page 88: Asm 850

    Brief description of ASM hardware A.2 ASM 473 ASM 473 Figure A-2 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 89 Brief description of ASM hardware A.2 ASM 473 Input parameters for ASM 473 The assignment is made in UDT 10 (see Section "Parameter data block"). Table A-3 Input parameters for ASM 473 Address Name Permissible values Comment +0.0 ASM_address 256, 260, 264, 268, ... Automatic or manual address assignment Each ASM 473 occupies four bytes of I/O in the peripheral area of the...
  • Page 90 Brief description of ASM hardware A.2 ASM 473 Command repetition: Command repetition as described in Section "Command repetition" is available on ASM 473 with MLFB 6GT2 002-0HA10. Interfaces and indicators of the ASM 473 Figure A-3 Interfaces and indicators of the ASM 473 Table A-5 Pin assignment of sockets X3, X4 Socket...
  • Page 91 Brief description of ASM hardware A.2 ASM 473 LEDs for MOBY RxD: Indicates live communication with the write/read device. PRE: Indicates the presence of an MDS. ERR: Error indication by flashing pattern (see Section "Error messages") This indicator can be reset with the parameter option_1 (see Section "INPUT parameters").
  • Page 92 Brief description of ASM hardware A.3 ASM 452 ASM 452 The ASM 452 is a PROFIBUS DP-V1 slave with degree of protection IP67. Up to two write/read devices / readers can be connected in parallel to it. The two write/read devices are processed in pseudo parallel.
  • Page 93 Brief description of ASM hardware A.3 ASM 452 Parameter setting by means of GSD file In addition to the PROFIBUS-relevant control parameters, several MOBY-relevant control parameters are also defined for the ASM 452 in the GSD file. The MOBY-relevant parameters are set using the "Object properties" of the slave in the hardware configuration. The following table shows the possible settings: Table A-6 Setting of MOBY-relevant parameters...
  • Page 94 Brief description of ASM hardware A.3 ASM 452 Table of commands for ASM 452 The assignment is made in UDT 20 using the "Command" variable (see Section "Command parameter settings"). Table A-8 Commands for ASM 452 Command code Description available in the MOBY system normal Chained...
  • Page 95 Brief description of ASM hardware A.3 ASM 452 Interfaces and indicators of the ASM 452 LEDs for PROFIBUS DP, Meaning Power display System Fault (see Table "LED indication for PROFIBUS diagnosis") Bus Fault (see Table "LED indication for PROFIBUS diagnosis") Lights up when there is logic voltage at the ASM (is generated by the 24 V supply voltage).
  • Page 96 Brief description of ASM hardware A.3 ASM 452 Interface assignments Interface Connection for PROFIBUS Assignment X 11 and X 12 Signal B (red) PE (not wired) Signal A (green) L+ (not wired) M (not wired) Connection for power supply Assignment X 13 Connection for write/read device Assignment...
  • Page 97 Brief description of ASM hardware A.3 ASM 452 Change indication mode of the LEDs PRE/ERR1 and PRE/ERR2 INPUT parameter option_1 can be used to change the indication mode of LEDs PRE/ERR1 and PRE/ERR2 (see also the "INPUT parameters" table in Section "INPUT parameters"). Table A-9 Control of the LEDs PRE/ERR1 and PRE/ERR2 option_1...
  • Page 98 Brief description of ASM hardware A.3 ASM 452 PROFIBUS Diagnosis "ON" LED is not on or is flashing If the "ON" LED is not on, this means that either no supply voltage or too low voltage is available to the ASM452. Possible causes include a bad fuse or missing/too low supply voltage.
  • Page 99 Brief description of ASM hardware A.4 ASM 454 ASM 454 The ASM 454 is a PROFIBUS slave. Up to four MOBY I/E/V write/read devices can be connected. Figure A-5 Configurator for ASM 454 Hardware configuration The ASM 454 is integrated into the hardware configuration of the SIMATIC Manager or into another PROFIBUS Master by means of the GSD file SIEM809F.GSD.
  • Page 100 Brief description of ASM hardware A.4 ASM 454 Input parameters for ASM 454 The assignment is made in UDT 10 (see Section "Parameter data block"). Table A-11 Input parameters for ASM 454 Address Name Permissible values Comment +0.0 ASM_address 256, 264, 272, 280, ... Each ASM 454 occupies 8 byte of I/O in the I/O area of the control unit +2.0...
  • Page 101 Brief description of ASM hardware A.4 ASM 454 Switch settings, interfaces and indicators of the ASM 454 ASM 454: Write/read device / write/read device side Meaning PRE: "Presence" of an MDS in transmission window. RxD: SLG active with command ERR: Error indicated by flashing LED Interfaces 1-4 Connections for up to four write/read...
  • Page 102 Brief description of ASM hardware A.5 ASM 754 ASM 754 The ASM 754 is a PROFIBUS slave. Up to four MOBY E SLAs (read/write antenna) can be operated on it. The 4 SLAs are processed in "pseudo parallel." This means that, from the user's point of view, command processing takes place in parallel.
  • Page 103 Brief description of ASM hardware A.5 ASM 754 Processing times of MDS E6xx in multiple channel operation The following table shows the processing times when one command is started simultaneously on 1, 2, 3, or 4 channels. Table A-13 Processing times of MDS E6xx in multiple channel operation SLA per ASM Time to Read 752 Byte Time to Write 752 Byte...
  • Page 104 Brief description of ASM hardware A.5 ASM 754 Table of commands for ASM 754 The assignment is made in UDT 20 using the "Command" variable (see Section "Command parameter settings"). Table A-15 Commands for ASM 754 Command code Description normal Chained Write to MDS Read MDS;...
  • Page 105 Brief description of ASM hardware A.6 ASM 854 ASM 854 The ASM 854 is a PROFIBUS slave. Up to four MOBY F SLAs can be connected in parallel to it. In addition to standard programming with the FB 45, the ASM 854 can also directly process the fixed-code data memories (type MDS F1xx) using the process image.
  • Page 106 Brief description of ASM hardware A.6 ASM 854 Input parameters for ASM 854 The assignment is made in UDT 10 (see Section "Parameter data block"). Table A-16 Input parameters for ASM 854 Address Name Permissible values Comment +0.0 ASM_address 256, 264, 272, 280, Each ASM 854 occupies 8 byte of I/O in the I/O area of the control unit +2.0...
  • Page 107 Brief description of ASM hardware A.6 ASM 854 Parameterizing process image mode Note Process image mode does not use the FB 45. This section describes how to handle and program the process image mode. Only fixed-code MDSs of type "MDS F1xx" can be read in this mode.
  • Page 108 Brief description of ASM hardware A.6 ASM 854 Process image mode: Programming The data must be scanned by SFC 14 to ensure consistent representation of the information which was read. The following example shows the programming of the ASM 854 in process image mode.
  • Page 109 Brief description of ASM hardware A.6 ASM 854 Process image mode: data representation and evaluation The following figure shows the layout of the ASM data after SFC 14 is called. The presentation also applies when the ASM data are directly viewed in the process image. Figure A-9 Data presentation and evaluation in process image mode FC 45...
  • Page 110 Brief description of ASM hardware A.6 ASM 854 Process image mode: time diagram Figure A-10 Time diagram for process image mode FC 45 A-28 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 111 Brief description of ASM hardware A.7 ASM 850 ASM 850 The ASM 850 is a PROFIBUS slave. One MOBY F SLA can be connected. In addition to standard programming with the FB 45, the ASM 850 can also directly process the fixed-code data memories (type MDS F1xx) using the process image.
  • Page 112 Brief description of ASM hardware A.7 ASM 850 Input parameters for ASM 850 The assignment is made in UDT 10 (see Section "Parameter data block"). Table A-18 Input parameters for ASM 850 Address Name Permissible Comment values +0.0 ASM_address 256, 264, 272, Each ASM 850 occupies 8 byte 280, ...
  • Page 113 Programming the MOBY-ASM on PROFIBUS Programming the MOBY-ASM on PROFIBUS DP-V1 For whom is this Appendix intended? This section does not need to be considered by SIMATIC users. It is intended particularly for programmers of PCs and third-party PLCs. The information enables the programmer to develop customized function blocks or drivers for the MOBY-ASM.

  • Page 114: Programming The Moby-Asm On Profibus

    Programming the MOBY-ASM on PROFIBUS B.1 Programming the MOBY-ASM on PROFIBUS DP-V1 Communication between ASM and PROFIBUS master non-cyclic data PROFIBUS-DP must be able to transfer both the cyclic (DP) and the (DP- V1). The master may only send new commands to the slave (MOBY-ASM) when the ASM is Status information ready.
  • Page 115 Programming the MOBY-ASM on PROFIBUS B.1 Programming the MOBY-ASM on PROFIBUS DP-V1 Principle of controlling non-cyclic communication with command and acknowledgment counter Figure B-1 Command and acknowledgement counter states As you can see from the diagram above, a DP-V1 telegram triggers the change from one defined state next state to the next.
  • Page 116 Programming the MOBY-ASM on PROFIBUS B.1 Programming the MOBY-ASM on PROFIBUS DP-V1 The user must evaluate the acknowledgement state with higher 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 telegram from the ASM must be fetched first.

  • Page 117: Cyclic Control Word Between Master And Moby-Asm

    Programming the MOBY-ASM on PROFIBUS B.2 Cyclic Control Word between Master and MOBY-ASM Cyclic Control Word between Master and MOBY-ASM The cyclic control word is used to synchronize telegram communication between master (FB / FC) and slave (MOBY-ASM). The actual non-cyclic command and acknowledgment frames 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 118 Programming the MOBY-ASM on PROFIBUS B.2 Cyclic Control Word between Master and MOBY-ASM After start-up, the cyclic word of MOBY-ASM takes on the following states (bits 8 to 15 are shown). Synchronizing of command and acknowledgment counters The command (BZ) and acknowledgment (QZ) counters are synchronized during a start-up. The ASM sets QZ = 0 and BZ = 1.
  • Page 119 Programming the MOBY-ASM on PROFIBUS B.2 Cyclic Control Word between Master and MOBY-ASM Terminating a command with Cancel BZ and QZ are not reset with Cancel. Figure B-5 Cancel timing FC 45 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

  • Page 120: Methods Of Operation With The Asm

    Programming the MOBY-ASM on PROFIBUS B.3 Methods of operation with the ASM Methods of operation with the ASM Commands are executed one at a time 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 121 Programming the MOBY-ASM on PROFIBUS B.3 Methods of operation with the ASM Command chaining and command buffering on the ASM Command chaining is indicated when the chaining bit (bit 6 in the command) is set (see also Section "MOBY commands). Command buffering is a characteristic of the ASM.
  • Page 122 Programming the MOBY-ASM on PROFIBUS B.3 Methods of operation with the ASM • If the PROFIBUS master can be set to permit several non-cyclic telegrams between cyclic data communication, PROFIBUS data transmission can be accelerated in a bus configuration with many MOBY-ASMs. However, this has a negative effect on the cyclic data communication of I/O modules which are also part of the same PROFIBUS branch.
  • Page 123 Programming the MOBY-ASM on PROFIBUS B.3 Methods of operation with the ASM Command repetition The procedure for command repetition and its advantages have already been described in Section "Command repetition". Programming of command repetition at the PROFIBUS level will now be discussed. The I/O input or I/O output word controls command repetition (see Section "Cyclic control word between master and MOBY-ASM").
  • Page 124 Programming the MOBY-ASM on PROFIBUS B.3 Methods of operation with the ASM Command repetition can also be concretely controlled as shown below. • An external proximity switch is used to signal that a new MDS is entering the transmission window (see figure below: Ⓐ). •...

  • Page 125: Command And Acknowledgement Telegrams

    Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams Command and acknowledgement telegrams Commands and results are sent and received with the non-cyclic telegram service of PROFIBUS DP-V1. The telegrams are described in this section. General telegram format The telegram layout applies to both command telegrams to the MOBY-ASM and result telegrams from the MOBY-ASM.
  • Page 126 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams Command table Comma Comman Command Description code code chained [hex] [hex] – RESET ASM is reset. The active command is terminated. (If an MDS command was terminated with RESET, the reset acknowledgment reports error 1F.) The RESET command can be used to switch the ASM to various operating modes.
  • Page 127 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams Comma Comman Command Description code code chained [hex] [hex] Antenna Only MOBY F/U/D or RF300: on/off This command turns the antenna field on the write/read device off and on again. MDS status Returns the characteristics of the MDS in the result.
  • Page 128 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams Exact telegram format FC 45 B-16 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 129 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams FC 45 B-17 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 130 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams FC 45 B-18 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 131 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams FC 45 B-19 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 132 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams FC 45 B-20 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 133 Programming the MOBY-ASM on PROFIBUS B.4 Command and acknowledgement telegrams FC 45 B-21 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

  • Page 134: Profibus Implementation

    Programming the MOBY-ASM on PROFIBUS B.5 PROFIBUS implementation PROFIBUS implementation PROFIBUS is implemented on the MOBY-ASM strictly in accordance with 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.
  • Page 135 Programming the MOBY-ASM on PROFIBUS B.5 PROFIBUS implementation 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. FC 45 B-23 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...
  • Page 136 Programming the MOBY-ASM on PROFIBUS B.5 PROFIBUS implementation The following data records have been implemented on the MOBY-ASM for communication. Table B-1 Data record numbers (index) Data record Present on MOBY-ASM Description number Reserved Reserved Parameterization channel 1 ASM 452, 454, 475, 754, 854, 456, Parameterization channel 2 RF170C ASM 454, 754, 854...

  • Page 137: B.6 Example Of A Profibus Trace

    Programming the MOBY-ASM on PROFIBUS B.6 Example of a PROFIBUS Trace Example of a PROFIBUS Trace The following trace shows all telegrams which were sent on the PROFIBUS interface during an ASM start-up or a MOBY read command. The trace illustrates the information in Sections "Cyclic control word between master and MOBY-ASM"...
  • Page 138 Programming the MOBY-ASM on PROFIBUS B.6 Example of a PROFIBUS Trace RESET and read command to channel 1 of a MOBY-ASM (only acyclic telegrams are recorded) 68 0f 0f 68 83 82 7c 33 36 5f 01 65 06 05 00 00 00 2b 02 00 16 RESET command 68 05 05 68 83 82 7c 33 36 00 16 Acknowledgment that RESET is being processed...

  • Page 139: Service & Support

    Contacts If you have any further questions on the use of the products described in this manual, please contact one of our representatives at your local Siemens office. The addresses are found on the following pages: • On the Internet at: http://www.siemens.com/automation/partner •...

  • Page 140: Training

    C.3 Training Training Training center We offer appropriate courses to get you started. Please contact your regional training center or the central training center in D-90327, Nuremberg, Germany. Telephone: +49 (911) 895-3200 http://www.siemens.com/sitrain FC 45 Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618...

Table of Contents