Siemens SIMATIC Ident Function Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Other
  5. SIMATIC Ident
  6. Function manual

Siemens SIMATIC Ident Function Manual

For moby u, moby d, rf200, rf300
Hide thumbs Also See for SIMATIC Ident:
Table of Contents

Advertisement

Quick Links

FB 45 for MOBY U, MOBY D, RF200,
RF300
SIMATIC Ident
RFID systems
FB 45
for MOBY U, MOBY D, RF200,
RF300
Function Manual
07/2012
J31069-D0166-U001-A4-7618
___________________
Introduction
___________________
Description
___________________
Parameterizing
___________________
Commissioning
___________________
Error messages and
troubleshooting
___________________
Examples/applications
___________________
Brief description of the
hardware
___________________
Programming
communications modules
___________________
Service & Support
1
2
3
4
5
6
A
B
C

Advertisement

Table of Contents
loading

Related Manuals for Siemens SIMATIC Ident

Summary of Contents for Siemens SIMATIC Ident

  • Page 1 ___________________ FB 45 for MOBY U, MOBY D, RF200, Introduction RF300 ___________________ Description ___________________ Parameterizing SIMATIC Ident ___________________ Commissioning RFID systems ___________________ Error messages and FB 45 troubleshooting for MOBY U, MOBY D, RF200, ___________________ RF300 Examples/applications Function Manual ___________________...
  • Page 2 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.

  • Page 3: Table Of Contents

    Table of contents Introduction..............................5 Overview ............................5 Preface............................8 Navigating in the Function Manual ....................9 Description............................... 11 Block specification ........................11 Configuration scheme ........................12 Data structures of FB 45 ......................13 Number of RFID channels that can be connected...............14 Addressing of the RFID channels ....................15 Parameterizing ............................
  • Page 4 Table of contents Determing the memory requirement in the SIMATIC..............79 Brief description of the hardware ......................81 RF170C ............................81 RF180C ............................85 ASM 456............................89 ASM 475............................96 Programming communications modules ....................99 Programming the communication modules on PROFIBUS/PROFINET........99 Cyclic control word between master and communications module ..........

  • Page 5: Introduction

    A separate manual is available for the parameter assignment of the RF620R/RF630R readers. In the "Configuration Manual RF620R/RF630R (http://support.automation.siemens.com/WW/view/en/33287195)" manual, you will find all the important information about commissioning, parameter assignment, error messages and how to handle errors/faults as well as many examples and applications for using the RF600.
  • Page 6 Please note that a separate manual is available for parameter assignment of the RF620R/RF630R reader with function block FB 45. In the "Configuration Manual RF620R/RF630R (http://support.automation.siemens.com/WW/view/en/33287195)" manual, you will find all the important information about commissioning, parameter assignment, error messages and how to handle errors/faults as well as many examples and applications for using the RF600.
  • Page 7 Introduction 1.1 Overview PROFIBUS configuration A GSD file is available on the "RFID Systems Software & Documentation" DVD (6GT2080-2AA20) for the communications modules that can be connected directly to PROFIBUS. PROFINET configuration A GSDML file is available on the "RFID Systems Software & Documentation" DVD (6GT2080-2AA20) for the communications modules that can be connected directly to PROFINET.

  • Page 8: Preface

    Introduction 1.2 Preface 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 9: Navigating In The Function Manual

    Introduction 1.3 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 sections Introduction Purpose, layout and description of the important topics. Description Description of FB45 Parameter assignment Description of the parameter settings...
  • Page 10 Introduction 1.3 Navigating in the Function Manual FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 11: Description

    Description Block specification Block number: FB 45 Block name: FB 45 Symbolic name: "MOBY FB" Family: – Work memory requirement: 8256 bytes Local data: 100 bytes Version: Called blocks: SFB 52, SFB 53, SFC 20, SFC 21, SFC 1 Data block resources: MOBY Param = 50 bytes per channel (defined via UDT 10) Instance DB for FB 45 = 464 bytes per channel...

  • Page 12: Configuration Scheme

    Description 2.2 Configuration scheme Data is transmitted to the tag and data is transmitted between the CM and FB 45 at the same time. Usually no further time must be added for data transmission between the CM and FB 45 so that the time t calculated above represents the total duration of the command.

  • Page 13: Data Structures Of Fb 45

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

  • Page 14: Number Of Rfid Channels That Can Be Connected

    Description 2.4 Number of RFID channels that can be connected Number of RFID channels that can be connected Each reader channel occupies 1 word in the input and output area of a SIMATIC S7. The maximum number of bus nodes permitted by SIMATIC can always be operated. The following table provides an overview.

  • Page 15: Addressing Of The Rfid Channels

    Description 2.5 Addressing of the RFID channels Addressing of the RFID 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 16 Description 2.5 Addressing of the RFID channels Addressing via PROFIBUS When addressing via PROFIBUS, any addresses can be selected in HW Config for the communications modules. HW Config assigns a free address by default. Figure 2-3 Example: Automatic address generation of an ASM 456 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 17 Description 2.5 Addressing of the RFID channels Assignment of addresses in FB 45 The unique I/O addresses of the communications modules from HW Config must be saved in the parameter data block (UDT 10). Figure 2-4 Setting the physical address assignment in UDT 10 In addition to the address (ASM_address), the RFID channel (ASM_channel) must also be assigned uniquely.
  • Page 18 Description 2.5 Addressing of the RFID channels FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 19: Parameterizing

    Parameterizing Parameter data block Each RFID channel (reader) needs its own parameters. These are predefined in a data structure as UDT 10 (with commentary in English) or UDT 11 (with commentary in German) or UDT 14 (with commentary in Spanish). You need to call this UDT in a data block for each RFID channel in which the widest range of variables are defined: ●...
  • Page 20 Parameterizing 3.1 Parameter data block Address Name Type Initial value Comment +18.5 battery_low BOOL FALSE Battery check has indicated low voltage +18.6 error BOOL FALSE Error during command execution +18.7 ready BOOL FALSE Command chain has been finished. +19.0 cancel BOOL FALSE Set: abort command or command chain...

  • Page 21: Input Parameters

    Parameterizing 3.1 Parameter data block 3.1.1 INPUT parameters Table 3- 2 INPUT parameter for MOBY D, MOBY U, RF200 and RF300 Variable Description ASM_address Logical base address of the CM; this address must match the "start address" of the CM in HW Config of the SIMATIC Manager.
  • Page 22 Parameterizing 3.1 Parameter data block Variable Description scanning_time RF200, RF300, MOBY D: 00 hex (reserved) MOBY U: Scanning_time describes the standby time for the transponder. If the transponder receives an additional command before scanning_time has expired, this command can be executed immediately.
  • Page 23 Parameterizing 3.1 Parameter data block Variable Description distance_limiting MOBY D: HF power from 0.5 W to 10 W in steps of 0.25 W only effective for SLG D10S; a power of 1 W (04 hex) is set for SLG D11S / D12S and cannot be changed.
  • Page 24 Parameterizing 3.1 Parameter data block Variable Description field_ON_control MOBY D, RF200 and RF300: 00 hex (reserved) MOBY U: BERO mode; automatic activation/deactivation of the antenna field. The "Antenna ON/OFF" command is superimposed by the BERO mode. 00 hex without BEROs; no write/read device synchronization 01 hex one or two BEROs The BEROs are combined according to logic OR.
  • Page 25 Parameterizing 3.1 Parameter data block Variable Description Note: 1. The following ISO special functions are not supported: – AFI (Application Family Identifier) – DSFID (Data Storage Format Identifier) – Chip-specific added functions such as EAS, Kill commands, etc. 2. If a previously unknown tag cannot be identified based on the parameters above, an error message is generated (error_MOBY "0D"[hex]).

  • Page 26: Command And Status Word

    Parameterizing 3.1 Parameter data block 3.1.2 Command and status word The control bits of FB 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 FB 45 for MOBY U, MOBY D, RF200, RF300...
  • Page 27 Parameterizing 3.1 Parameter data block Table 3- 3 Variables in BEST Variable Description cancel The cancel variable is not available. A command termination must be executed via the init_run variable. The cancel command is not executed. command_start TRUE = Start a command or a command chain. FALSE = Reset occurs automatically triggered by FB 45.
  • Page 28 Parameterizing 3.1 Parameter data block Variable Description ANZ_MDS_present Indicates the presence of a transponder in the transmission window of the reader. ANZ_MDS_present is only indicated when the INPUT parameter MDS_control (see section "INPUT parameters (Page 21)") was set by the user. Remember that when an init_run is being executed, the ANZ_MDS_present indication disappears briefly even when a transponder is permanently located in the transmission window.

  • Page 29: Further Displays

    Parameterizing 3.2 RFID commands 3.1.3 Further displays Table 3- 4 Displays Variable Description ASM_busy No significance. This variable is always FALSE. command_rep_active The CM is currently running a command repetition. The bit is set as a response to the control variable repeat_command.

  • Page 30: Command Parameters

    Parameterizing 3.2 RFID commands Table 3- 5 UDT 21 "MOBY CMD_d" Address Name Type Initial value Comment STRUCT +0.0 command BYTE B#16#2 MDS: 2 = read, 1 = write +1.0 sub_command BYTE B#16#0 INIT = bit pattern; END, SET, MDS, SLG=mode +2.0 length Amount of data to be written/read in bytes...
  • Page 31 Parameterizing 3.2 RFID commands WRITE Table 3- 7 Write to the tag Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] – 1 to 32767 * 0000 to FFFF ** Pointer to user RF200: Length of The data is written to data to be written The data length transponder data...
  • Page 32 Parameterizing 3.2 RFID commands INIT Table 3- 9 Initialize tag Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 00 to FF – Memory size of – Hexadecimal value transponder to be that is written to the initialized transponder Transponder type Memory size...
  • Page 33 Parameterizing 3.2 RFID 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 UDT 110 – – Pointer to the result. MOBY U/D, The result is indicated RF200 and RF300 with the 02 = status after UDT 120...
  • Page 34 Parameterizing 3.2 RFID commands SET-ANT Table 3- 12 Switch antenna of reader ON/OFF Command sub_command length address_MDS DAT_DB Note [hex] [hex] [dec] [hex] [dec] 01 = antenna on – – – The antenna on/off command cannot be started by 02 = stand-by; antenna off command repetition (see section "Command repetition (Page 37)").

  • Page 35: Command Chaining

    Parameterizing 3.2 RFID commands 3.2.2 Command chaining Command chaining permits various address areas of the transponder 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 communications module and on the reader. A command chain is set up by the user by storing a succession of UDT 20s in a DB.
  • Page 36 Parameterizing 3.2 RFID commands Table 3- 15 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 RFID commands 3.2.3 Command repetition Operating principle After a new start (or init_run) of the CM, FB 45 transfers the command (or command chain) once to the CM. Command transmission is automatic with the first command_start. This command (or the last command or the command chain) always remains buffered on the CM. If command repetition is started now, the command buffered on the CM is executed again, and the result(s) transferred to FB 45.
  • Page 38 Parameterizing 3.2 RFID commands Programming There are two programming methods. ● Continuous reading (processing) of each passing transponder. After the CM 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 tag/transponder (repeat_command remains set) When permanent command repetition is used, data may be transferred to FB 45 slower than new tags are being processed (fast tag sequence, slow data transmission).
  • Page 39 Parameterizing 3.2 RFID commands ● Specific reading (processing) of a tag. The user starts the processing of each new tag in his/her application. The following time diagram illustrates this principle. Figure 3-3 Specific reading with repeat_command by the user Note In the case of RFID systems with unique tag IDs (UID) (e.g.

  • Page 40: Presence Check

    Parameterizing 3.3 Presence check Presence check This section explains the mechanism of the presence check. As default, the CM or the reader operates with the presence check. Presence check The presence check is detection logic in the firmware of the reader that detects whether or not a mobile data memory is currently located in the area of the reader.

  • Page 41: Commissioning

    ● PROFINET RF180C The GSDML file must be added to the device catalog using HW Config ("Options" > "Install new GSD..."): – GSDML-V2.2-SIEMENS-RF180C-20100329.xml NOTICE The "S7-compatible" setting results in addressing errors! To operate the ASM 456 using the GSD file, the DP interface of the DP master must be set to "DP-V1".
  • Page 42 Commissioning The following figure shows the position of the communications modules in the hardware catalog. Figure 4-1 Location of the communications modules in the hardware catalog When configuring the ASMs, make sure that the I address and the Q address have the same values.
  • Page 43 Commissioning Figure 4-2 Example of a hardware configuration If the project is downloaded to the hardware in this step (without a user program), the SIMATIC CPU and the PROFIBUS must change to RUN. If this is not the case, continue troubleshooting PROFIBUS/PROFINET (check the PROFIBUS address settings on the communications module or the IP address with PROFINET against the configuration in HW Config).
  • Page 44 Commissioning 4th step: Edit STEP 7 project This step is described based on the supplied sample program. ● Copy the sample program for FB 45 into the new STEP 7 project. ● Depending on the number of configured readers: – Declare the UDT 10 in DB 45 and the associated command(s) (UDT 20) in DB 47. –...
  • Page 45 Commissioning 5th step: Download and test the program ● Download the project to the SIMATIC CPU. ● Connect a reader of the selected RFID type to each RFID channel. ● After restarting the SIMATIC CPU (STOP → RUN), the CPU should not be in STOP mode.
  • Page 46 Commissioning The variables ready = TRUE and error = FALSE should now be indicated for each channel. If this is not the case continue troubleshooting (see section "Error messages and troubleshooting (Page 47)"). If ready = FALSE: ● This channel is not called in OB 100. ●...

  • Page 47: 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 FB 45 is called. ●...
  • Page 48 Error messages and troubleshooting 5.2 Error messages NOTICE When several error occur with chained commands, the "error variable" always indicates the first error detected. error_MOBY The ERR LED of the reader flashes when there are error messages. Some errors are also indicated by the flashing ERR LED of the CM.
  • Page 49 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#...) Error in the connection to the reader. The reader is not answering. The cable between the CM and reader is wired incorrectly or there • is a cable break The 24 V supply voltage is not connected or is not turned on or has •...
  • Page 50 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#...) CRC sending error The tag is signaling CRC errors frequently. • – The tag is in the boundary area of the reader. – The tag and/or reader have a hardware fault. Only during initialization: CRC error when receiving an acknowledgment from tag Cause same as error B#16#06.
  • Page 51 Error messages and troubleshooting 5.2 Error messages Error code Flashing of Description ERR LED (B#16#...) Internal CM communication error. Connector contact problem on the CM • Defective CM hardware • – Return CM for repair Start init_run command after error correction. •...
  • Page 52 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 CM although the last command was still active. Active command can only be terminated with an init_run. •...
  • Page 53 Error messages and troubleshooting 5.2 Error messages error_FB Table 5- 3 Error variable "error_FB" Error code Description (B#16#...) No error; default value if everything is ok. Params_DB not available in SIMATIC Params_DB too small UDT 10/11 was not used during definition •...
  • Page 54 Error messages and troubleshooting 5.2 Error messages Error code Description (B#16#...) The CM has failed. Loss of power on CM • 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 (Page 26)") was set in OB 122.
  • Page 55 The following table of bus errors does not claim to be complete. If you receive any messages that are not documented here, you will find them in "System and standard functions S7- 300/400, volume 1/2 (http://support.automation.siemens.com/WW/view/en/44240604)". Table 5- 4 Error variable "error_BUS" when operating via PROFIBUS/PROFINET...
  • Page 56 Error messages and troubleshooting 5.2 Error messages Error code Description (W#16#...) 8093 The area identifier contained in the configuration (SDB1, SDB2x) of the logical address is not permitted for these SFCs. Permitted: 0 = S7-400 • 1 = S7-300 • 2, 7 = DP modules •...
  • Page 57 Error messages and troubleshooting 5.2 Error messages Error code Description (W#16#...) 80C4 Communication error Parity error • SW ready not set • Error in block length management • Checksum error on CPU side • Checksum error on module side • 80C5 Distributed I/O not available FB 45 for MOBY U, MOBY D, RF200, RF300...
  • Page 58 Error messages and troubleshooting 5.2 Error messages FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 59: Examples/Applications

    Examples/applications FB 45 scanning by user Scanning of FB 45 takes place in accordance with the structogram in the following figure. Figure 6-1 Structogram for scanning of FB 45 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 60: 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 Transponder type 2 KB...
  • Page 61 Examples/applications 6.2 Processing of data memories/transponders Address space of the transponder/MDS variants according to ISO 15693 for RF200, RF300 and MOBY D System Addressing 16-bit hexadecimal number Integer number RF200, MDS D139 (I-Code 1; 44 bytes) RF300, Start address 0000 MOBY D End address 002B...
  • Page 62 Examples/applications 6.2 Processing of data memories/transponders Address space of the transponder versions for RF300 System Addressing 16-bit hexadecimal number Integer number RF300 20 bytes of data memory (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 63 Examples/applications 6.2 Processing of data memories/transponders System Addressing 16-bit hexadecimal number Integer number Start address 0000 End address FEFC – ID no.: (fixed-coded; can only be output as a whole) Start address FFF0 Length 0008 RF300: General notes on the meaning of the OTP memory RF300 tags and ISO tags have a memory area that can be protected against overwriting.
  • Page 64 Examples/applications 6.2 Processing of data memories/transponders RF300: Address mapping of OTP memory on the RF300 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.
  • Page 65 Examples/applications 6.2 Processing of data memories/transponders Address space of the transponder/MDS variants for MOBY U System Addressing 16-bit hexadecimal number Integer number MOBY U 2 KB data memory Start address 0000 End address 07FF +2047 Read OTP memory (write access only possible once. The OTP memory of MOBY U can only be processed completely, i.e.
  • Page 66 Examples/applications 6.2 Processing of data memories/transponders RF300: Address mapping of OTP memory on the ISO transponders For the OTP area, a 16-byte address space is always reserved at the end of the memory area. The subdivision of the blocks depends on the chip type. The corresponding addresses for the user data are therefore not available to the application when the OTP area is used.

  • Page 67: Cyclic Calling Of Fb 45 (E.g. In Ob 1)

    Examples/applications 6.3 Cyclic calling of FB 45 (e.g. in OB 1) Cyclic calling of FB 45 (e.g. in OB 1) The following program is an example of how to call and scan FB 45 in an application. The definition of the data structure is described in the section "Data structure definition (Page 70)".

  • Page 68: Programming A Cold And Warm Restart

    Examples/applications 6.4 Programming a cold and warm restart Programming a cold and warm restart The communications module and the reader are restarted by setting the "init_run" variable. The CM and FB 45 are reassigned parameters and synchronized with init_run. An init_run is necessary after ●...
  • Page 69 Examples/applications 6.5 Programming a module failure A feature implemented in FB 45 allows a normal error to be signaled to the user (error_FB=09) when an RFID PROFIBUS slave fails. To do this, the user sets bit "ASM_failure = 1" in OB 122 for the failed RFID channel. The following example shows a possible OB 122 implementation.

  • Page 70: Data Structure Definition

    Examples/applications 6.6 Data structure definition Data structure definition The developer can define different RFID data structures depending on the structure of the application. Some example structures are given below. 1st example 3 readers are configured. One command is assigned to each reader. RFID parameters (DB 45), RFID commands (DB 47), and data (DB 48) are assigned to different data blocks.
  • Page 71 Examples/applications 6.6 Data structure definition 2nd example 2 commands are assigned directly to each RFID channel. The RFID parameters and the RFID commands of all readers are stored in a "MOBY DB". A nested structure is used in the declaration. Figure 6-2 Example of when several RFID commands are assigned to one channel FB 45 for MOBY U, MOBY D, RF200, RF300...
  • Page 72 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 RFID 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 memory bit is used to prevent the command from being started several times: MOBY DB.channel[1].ready // 1st READER...
  • Page 73 Examples/applications 6.6 Data structure definition 3rd example A separate data block is assigned to each RFID channel. It contains the parameters, commands and data for a channel. Space for 10 RFID commands should be reserved on each channel. Declaration view Data view (schematic) DB 45: "Reader 1"...

  • Page 74: The Udts Of Fb 45 / Fc 45

    Examples/applications 6.7 The UDTs of FB 45 / FC 45 The UDTs of FB 45 / FC 45 The "MDS status" and "SLG 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 75 Examples/applications 6.7 The UDTs of FB 45 / FC 45 UDT 101: Result of transponder status Table 6- 3 UDT 101 "MOBY transponder status" Address Name Type Comment STRUCT +0.0 DWORD Tag (unique identifier) +4.0 MDS_type BYTE +6.0 sum_subframe_access DINT Sum of subframe access +10.0 sum_searchmode_access...
  • Page 76 Examples/applications 6.7 The UDTs of FB 45 / FC 45 UDT 121: Result of reader diagnostics I Table 6- 5 UDT 121 "MOBY SLG-Stat Diag 1" Address Name Type Comment STRUCT +0.0 status_info BYTE Reader status mode +1.0 number_functions BYTE Range: 1...33 +2.0 function_01_01...
  • Page 77 Examples/applications 6.7 The UDTs of FB 45 / FC 45 UDT 231: Result of MDS status (mode 3, RF200, RF300) Table 6- 8 UDT 231: "MDS status (mode 3, RF300)" Address Name Type Comment STRUCT +0.0 reserved0 BYTE +1.0 status_info BYTE Tag status mode +2.0...
  • Page 78 Examples/applications 6.7 The UDTs of FB 45 / FC 45 Address Name Type Comment +12.0 reserved1 ARRAY[1...6] *1.0 BYTE =18.0 END_STRUCT UDT 271: Result of MDS status (mode 2, RF300) Table 6- 10 UDT 271: "MDS status (mode 2, RF300)" Address Name Type...

  • Page 79: 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 80 Examples/applications 6.8 Determing the memory requirement in the SIMATIC FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 81: Brief Description Of The Hardware

    Brief description of the hardware This appendix covers the special features of the individual communications modules that can be addressed with FB 45. You will find a detailed hardware description of the communications modules with the installation instructions in the manual of the particular communications module. RF170C Area of application The RF170C communication module is a SIMATIC S7 module.
  • Page 82 For full functionality (e.g. firmware update), support for GSD revision 5 or higher is required. Integration into other PROFINET IO controllers is carried out by means of a GSDML file: ● GSDML-V1.0-SIEMENS-ET200pro-"Date in format yyyymmdd".xml for ET 200pro with IM 154- PN High Feature...
  • Page 83 Brief description of the hardware A.1 RF170C Command table of the RF170C for normal addressing (FB 45 / FC 45 / FB 55 / FC 55) Assignment is made in the UDT 20 by means of the "command" variable. You will find a list and description of the commands in the section "Command parameters (Page 30)".
  • Page 84 Brief description of the hardware A.1 RF170C After start-up or updating the firmware, the LEDs SF, PRE, ERR and ACT indicate the operating status or faults of the RF170C: PRE_1 ERR_1 ACT_1 PRE_2 ERR_2 ACT_2 Description Start-up active Checksum error at start-up * Firmware invalid * LED test for approximately 4 seconds;...

  • Page 85: Rf180C

    RF180C Area of application The RF180C communications module is a module for connecting Siemens Ident devices to PROFINET. The RF180C communications module can be connected both to SIMATIC S7 controllers as well as to any other controllers. Up to two readers can be operated on the RF180C at the same time.
  • Page 86 Brief description of the hardware A.2 RF180C The table below shows the possible settings: Table A- 5 Setting of RFID-relevant parameters Parameter name Value Note USER_Mode FB 45 Default FB 55 for multitag applications FB 56 With later firmware version RFID standard profile With later firmware version MOBY_Mode...
  • Page 87 Brief description of the hardware A.2 RF180C Diagnostics using LEDs The following figure shows details of the LEDs of the RF180C. Figure A-4 LEDs of the RF180C Table A- 7 Status LEDs for the RF180C LEDs Meaning Lights up when the RF180C has completed start-up without errors. 24 V DC Lights up when the 24 V supply voltage is connected to the RF180C.
  • Page 88 Brief description of the hardware A.2 RF180C Table A- 8 LED display for PROFINET diagnostics Cause of error Error correction – When the bus is configured correctly, this state ends a Communication module is in start- • few seconds after switching the module on. up mode.

  • Page 89: Asm 456

    Brief description of the hardware A.3 ASM 456 ASM 456 Area of application The ASM 456 communications modules are slave modules for operating RFID components via the PROFIBUS DP/DP-V1 on any control systems. Figure A-5 ASM 456 configurator FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 90 Brief description of the hardware A.3 ASM 456 Design The ASM has a connection block for connecting up to the PROFIBUS DP which is available as an option and the ECOFAST version or M12, 7/8". The following figure shows the basic design of the ASM 456. Figure A-6 Basic design of the ASM 456 Hardware configuration...
  • Page 91 Brief description of the hardware A.3 ASM 456 Parameter setting by means of GSD file In addition to the control parameters relevant for PROFIBUS, several control parameters relevant for RFID are also defined for the ASM 456 in the GSD file. The parameters relevant for RFID are set using the "Object properties"...
  • Page 92 Brief description of the hardware A.3 ASM 456 Table A- 12 Number of buffers for intermediate storage No. of buffers per channel Maximum amount of data for intermediate storage Number of buffers for intermediate 34 950 bytes storage of commands and results Diagnostics using LEDs The following figure shows details of the LEDs of the ASM 456.
  • Page 93 Brief description of the hardware A.3 ASM 456 Table A- 13 Status LEDs for ASM 456 LEDs Meaning Lights up when there is logic voltage applied to the CM (is generated from the 24 V supply voltage.) 24 V DC Lights up when the 24 V supply voltage is connected to the CM.
  • Page 94 Brief description of the hardware A.3 ASM 456 PRE_1 ERR_1 ACT_1 PRE_2 ERR_2 ACT_2 Description Start-up active Checksum error at start-up Firmware invalid LED test for approximately 4 seconds; otherwise firmware fault Checksum error at start-up Checksum error of the firmware External RAM defective DPC-RAM defective ID error firmware...
  • Page 95 Brief description of the hardware A.3 ASM 456 Table A- 16 Connection assignment for M12 connector (PROFIBUS DP) Assignment View of M12 connector (wiring side) Supply positive (P5V2) * Data line A (RxD / TxD-N) Data reference potential (M5V2) * Data line B (RxD / TxD-P) Shield Thread...

  • Page 96: Asm 475

    Brief description of the hardware A.4 ASM 475 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. Figure A-8 Configurator for ASM 475 (centralized layout) Hardware configuration The ASM 475 is integrated in the hardware configuration of the SIMATIC Manager by calling "Setup.exe"...
  • Page 97 Brief description of the hardware A.4 ASM 475 Command repetition: Command repetition as described in the section "Command repetition (Page 37)" is available on ASM 475 with order no. 6GT2 002-0GA10. Interfaces and indicators of the ASM 475 The following figure shows details of the LEDs of the ASM 475. MOBY ASM475 DC5 V...
  • Page 98 Brief description of the hardware A.4 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 99: Programming Communications Modules

    Programming communications modules Programming the communication modules on PROFIBUS/PROFINET 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 communication module.
  • Page 100 Programming communications modules B.1 Programming the communication modules on PROFIBUS/PROFINET Communication between communications module and PROFIBUS/PROFINET master It must be possible to transfer both the cyclic (DP) and the acyclic data DP-V1 via PROFIBUS DP. ① Cyclic communication via PROFIBUS/PROFINET. Status information is exchanged (see section "Cyclic control word between master and communications module (Page 102)"...
  • Page 101 Programming communications modules B.1 Programming the communication modules on PROFIBUS/PROFINET Principle of controlling non-cyclic communication with command and acknowledgment counter Figure B-1 Command and acknowledgement counter states As can be seen from the diagram above, an acyclic frame triggers the change from one defined status to the next.

  • Page 102: Cyclic Control Word Between Master And Communications Module

    Programming communications modules B.2 Cyclic control word between master and communications module The user must evaluate the acknowledgement state with higher priority. In other words, when the user wants to send a frame to the ASM but a frame from the CM is waiting to be fetched at the same time, the frame from the CM must be fetched first.
  • Page 103 Programming communications modules B.2 Cyclic control word between master and communications module Cyclic word from communications module: I/O input Figure B-3 Structure of the cyclic control word: Peripheral input After startup, the "cyclic word from the CM" appears as follows in sequence (bits 8 to 15 are shown): FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 104 Programming communications modules B.2 Cyclic control word between master and communications module Synchronizing of command and acknowledgment counters The command (BZ) and acknowledgment (QZ) counters are synchronized during a startup. The CM sets QZ = 0 and BZ = 1. The startup can be triggered by both the CM (return of power) and the user (init_run_).

  • Page 105: Methods Of Operation With The Communications Module

    Programming communications modules B.3 Methods of operation with the communications module Methods of operation with the communications module 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 CM. This type of programming involves the following characteristics.
  • Page 106 Programming communications modules B.3 Methods of operation with the communications module The following diagram shows the procedure used for command and acknowledgment communication between user (PROFINET/PROFIBUS master) and communications module when a chained command is used: Figure B-7 Command execution: Command chaining and buffering The following general conditions apply to the procedures shown in the diagram above.
  • Page 107 Programming communications modules B.3 Methods of operation with the communications module Command repetition The procedure for command repetition and its advantages were described earlier in the section "Command repetition (Page 37)". Programming of command repetition at the PN/PB level is described below. Command repetition is controlled by the I/O input or output word (see section "Cyclic control word between master and communications module (Page 102)").
  • Page 108 Programming communications modules B.3 Methods of operation with the communications module In this case, the command_repeat_active_ bit must be scanned to make sure the command repetition was accepted. Figure B-9 Focused command repetition FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 109: Command And Acknowledgement Telegrams

    Programming communications modules B.4 Command and acknowledgement telegrams Command and acknowledgement telegrams Commands and results are transmitted and received using the acyclic frame service of PROFIBUS/PROFINET. The frames are described in this section. General frame format The frame structure applies to both command frames to the CM module and result frames from the CM.
  • Page 110 Programming communications modules B.4 Command and acknowledgement telegrams Command table Comma Comman Command Description code code chained [hex] [hex] – RESET CM is reset. The active command is terminated. (If a tag command was terminated with RESET, the reset acknowledgment reports error 1F.) The RESET command can be used to switch the CM to various operating modes.
  • Page 111 Programming communications modules B.4 Command and acknowledgement telegrams Exact frame format FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 112 Programming communications modules B.4 Command and acknowledgement telegrams FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 113 Programming communications modules B.4 Command and acknowledgement telegrams FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 114 Programming communications modules B.4 Command and acknowledgement telegrams FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 115 Programming communications modules B.4 Command and acknowledgement telegrams FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...

  • Page 116: Profibus/Profinet Implementation

    Programming communications modules B.5 PROFIBUS/PROFINET implementation PROFIBUS/PROFINET implementation PROFIBUS/PROFINET is implemented on the communication modules 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 communications module.
  • Page 117 Programming communications modules B.5 PROFIBUS/PROFINET 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 communications module is addressed. The following data records are implemented on the CM for communication. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618...
  • Page 118 Programming communications modules B.5 PROFIBUS/PROFINET implementation Table B- 1 Data record numbers (index) Data record Exist on Description number CM/reader Parameter assignment channel 1 Parameter assignment channel 2 Parameter assignment channel 3 Parameter assignment channel 4 Data transmission channel 1 Data transmission channel 2 Data transmission channel 3 Data transmission channel 4...

  • Page 119: Example Of A Profibus Trace

    Programming communications modules B.6 Example of a PROFIBUS Trace Example of a PROFIBUS Trace The following trace shows all frames that were sent on the PROFIBUS interface during a CM startup or a read command. The trace is used to understand the sections Cyclic control word between master and communications module (Page 102) to PROFIBUS/PROFINET implementation (Page 116) and to help orientation or troubleshooting with customized implementations of the communications modules.
  • Page 120 Programming communications modules B.6 Example of a PROFIBUS Trace RESET and read command to channel 1 of a communications module (only acyclic frames are recorded) 68 0F 0F 68 83 82 7c 33 36 5f 01 65 06 05 00 00 00 2b 02 00 16 FB: RESET command to channel 1 68 05 05 68 83 82 7c 33 36 00 16 FB: request for an acknowledgment...

  • Page 121: Service & Support

    Contacts If you have any further questions on the use of our products, please contact one of our representatives at your local Siemens office. The addresses are found on the following pages: ● On the Internet (http://www.siemens.com/automation/partner) ● In Catalog CA 01 ●...
  • Page 122 A guide to the technical documentation for the various products and systems is available on the Internet: SIMATIC Guide manuals (http://www.siemens.com/simatic-tech-doku-portal) Online catalog and ordering system The online catalog and the online ordering system can also be found on the Industry Mall Homepage (http://www.siemens.com/industrymall).

This manual is also suitable for:

Fb 45

Table of Contents