FB 45 for MOBY U, MOBY D, RF200, 1 ___________________ Introduction RF300 2 ___________________ Description SIMATIC Ident RFID systems FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual 3 ___________________ Parameterizing 4 ___________________ Commissioning Error messages and ___________________ 5 troubleshooting ___________________ 6 Examples/applications Brief description of the ___________________ A hardware Programming ___________________ B communications modules ___________________ C Service & Support 07/2012 J31069-D0166-U001-A4-7618 Legal information Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products 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. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. Trademarks All names identified by (R) are registered trademarks of 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. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Industry Sector Postfach 48 48 90026 NURNBERG GERMANY J31069-D0166-U001-A4-7618 07/2012 Technical data subject to change Copyright (c) Siemens AG 2006, 2009, 2012. All rights reserved Table of contents 1 2 3 Introduction................................................................................................................................................ 5 1.1 Overview ........................................................................................................................................5 1.2 Preface...........................................................................................................................................8 1.3 Navigating in the Function Manual ................................................................................................9 Description............................................................................................................................................... 11 2.1 Block specification .......................................................................................................................11 2.2 Configuration scheme ..................................................................................................................12 2.3 Data structures of FB 45 ..............................................................................................................13 2.4 Number of RFID channels that can be connected.......................................................................14 2.5 Addressing of the RFID channels ................................................................................................15 Parameterizing ........................................................................................................................................ 19 3.1 3.1.1 3.1.2 3.1.3 Parameter data block...................................................................................................................19 INPUT parameters .......................................................................................................................21 Command and status word ..........................................................................................................26 Further displays ...........................................................................................................................29 3.2 3.2.1 3.2.2 3.2.3 RFID commands ..........................................................................................................................29 Command parameters .................................................................................................................30 Command chaining ......................................................................................................................35 Command repetition.....................................................................................................................37 3.3 3.3.1 3.3.2 Presence check ...........................................................................................................................40 No tag control, no presence check: MDS_control = 0 .................................................................40 No tag control, presence control with field scanning: MDS_control = 1 ......................................40 4 Commissioning ........................................................................................................................................ 41 5 Error messages and troubleshooting ....................................................................................................... 47 6 5.1 General errors ..............................................................................................................................47 5.2 Error messages............................................................................................................................47 Examples/applications ............................................................................................................................. 59 6.1 FB 45 scanning by user ...............................................................................................................59 6.2 Processing of data memories/transponders ................................................................................60 6.3 Cyclic calling of FB 45 (e.g. in OB 1) ...........................................................................................67 6.4 Programming a cold and warm restart.........................................................................................68 6.5 Programming a module failure.....................................................................................................68 6.6 Data structure definition ...............................................................................................................70 6.7 The UDTs of FB 45 / FC 45 .........................................................................................................74 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 3 Table of contents 6.8 A B C Determing the memory requirement in the SIMATIC.................................................................. 79 Brief description of the hardware ............................................................................................................. 81 A.1 RF170C ....................................................................................................................................... 81 A.2 RF180C ....................................................................................................................................... 85 A.3 ASM 456...................................................................................................................................... 89 A.4 ASM 475...................................................................................................................................... 96 Programming communications modules .................................................................................................. 99 B.1 Programming the communication modules on PROFIBUS/PROFINET..................................... 99 B.2 Cyclic control word between master and communications module .......................................... 102 B.3 Methods of operation with the communications module........................................................... 105 B.4 Command and acknowledgement telegrams............................................................................ 109 B.5 PROFIBUS/PROFINET implementation ................................................................................... 116 B.6 Example of a PROFIBUS Trace ............................................................................................... 119 Service & Support.................................................................................................................................. 121 FB 45 for MOBY U, MOBY D, RF200, RF300 4 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 1 Introduction 1.1 Overview FB 45 is a STEP 7 function for RFID technology. It can be used with both the SIMATIC S7300 and S7-400 for various RFID communications modules. 5)& 5)& Figure 1-1 $60 $60 Communications modules for FB 45 The section "Brief description of the hardware" in the Appendix illustrates configurations with the various communications modules. FB 45 can be operated in various different configurations: The CM is operated directly in a SIMATIC S7-300. The communications module is located in the rack of an ET 200M or ET 200pro. The ET 200M/ET 200pro is used with an S7-300 or S7-400. The CM is a self-contained PROFIBUS slave and is connected to the integrated PROFIBUS connector of a SIMATIC S7-300 or S7-400. The CM can be operated both via PROFIBUS or PROFINET. The CM is operated on PROFINET via the IE/PB Link. These configurations can be mixed and different communications modules can also be connected. Assign parameters for the RF600 reader with FB 45 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. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 5 Introduction 1.1 Overview Compatibility note FB 45 is the successor to FC 45. FB 45 is almost completely compatible with FC 45. Users can run FC 45 application programs with FB 45 without modification. Unlike FC 45, a separate instance DB has to be assigned for each FB 45 call. UDT 10 has been shortened from 300 bytes to 50 bytes as a result. The application-related variables of UDT 10 are the same. Features of the interface The features of the individual CMs are described in the section "Brief description of the hardware (Page 81)". Since the features of the individual CMs are continuously being expanded, you should always use the latest edition of this description. Performance features of FB 45 All identification systems (RFID and code reading systems) can be operated with FB 45. The user can process a complete transponder with one command (up to 64KB). The user can chain several commands together. This means that many small data areas of a transponder can be processed with one command start. The data structures are set up conveniently via user-defined data types (UDTs). The UDTs are available with English (UDT 10, 20), German (UDT 11, 21) and Spanish (UDT 14, 24) commentary. In this description, the UDTs are always referred to by their English designation (UDT 10, 20). Data is transmitted to and from the CM and commands are executed on the CM at the same time. This means optimal data throughput. The use of symbolic names enhances the clarity in the user program, even where complex configurations are involved. Position in the information landscape This function manual describes the use of FB 45 for the RFID systems MOBY D, MOBY U, RF200 and RF300. MV400 code readers can also be used with FB 45. 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. You will find the documentation on parameter assignment of the code reading systems in: "Parameter assignment of the code reading systems (http://support.automation.siemens.com/WW/view/en/38845041)" FB 45 for MOBY U, MOBY D, RF200, RF300 6 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. Non-SIMATIC applications Applications programmed on third-party controllers cannot use FB 45. When programming the third-party controller, keep to the standard IEC 61131: The third-party controller can be programmed according to IEC 61131: Use the function block RFID standard profile. You will find the source code to match the block on the DVD "RFID Systems, Software & Documentation" (6GT2080-2AA20). You can compile the source code into the machine code of the target system. You will also find the documentation for this on the DVD. The third-party controller cannot be programmed according to IEC 61131: The relevant interface is described in the section "Programming the communication modules on PROFIBUS/PROFINET (Page 99)" of this manual. Programmers of a thirdparty controller can use this interface to develop their own RFID function. The same or similar data structures as in FB 45 can be reproduced on a third-party PLC in conjunction with FB 45 description and the UDTs. Requirements for using FB 45 FB 45 can access the communications module via any PROFIBUS/PROFINET master that has the system function blocks SFB 52/53. It is irrelevant whether the PROFIBUS/PROFINET master is integrated in the S7-CPU or plugged into the rack as an add-on module (e.g. IM 467). Please note that FB 45 uses acyclic frames (SFB 52/53). Older CPUs of the SIMATIC family or small model series may not have these services. Please check this during configuration. STEP 7 version The ASM 475 module requires a STEP 7 version V 5.1. TIA Portal FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 7 Introduction 1.2 Preface 1.2 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. Conventions The following terms/abbreviations are used synonymously in this document: Reader, read/write device, write/read device Transponder, mobile data memory, MDS Communications module, CM, interface module, ASM Validity of this documentation This documentation is valid for FB 45. The documentation describes the product shipped as of September 2011. History Previous edition(s) of these operating instructions: Edition Note 05/2005 First Edition 03/2006 Inclusion of the RF170C communication module 10/2009 Parameter assignment of the RF620R/RF630 reader. RF300 and ISO transponders 07/2012 The document is expanded by RF200. Various interface modules as well as MOBY I and MOBY E have been omitted. FB 45 for MOBY U, MOBY D, RF200, RF300 8 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Introduction 1.3 Navigating in the Function Manual 1.3 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 Commissioning Description of the commissioning procedure Error messages and troubleshooting Overview of error messages and troubleshooting guide Examples/applications Describes the application of FB 45 based on example applications. Appendix A: Brief description of the hardware Description of the communications modules that can be used for FB 45 Appendix B: Programming the communications modules on PROFIBUS Information for control using a PC or third-party control system Appendix C: Service & Support Service and support, contact partners, training centers FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 9 Introduction 1.3 Navigating in the Function Manual FB 45 for MOBY U, MOBY D, RF200, RF300 10 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 2 Description 2.1 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: 1.6 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 Bit memories used: None Counters used: None Registers used: AR1, AR2 Call: cyclic Note A calculation tool for calculating the data throughput is available for various communications modules. You will find this on the DVD "RFID Systems, Software & Documentation" (order number: 6GT2080-2AA20). RFID data throughput calculation The data throughput with FB 45 can be calculated according to the formulas in the relevant RFID system manual. A configuration manual is provided for each RFID system. The following applies in general: t = k + t n k bytes tk Communication time between CM, reader and tag n k t bytes Amount of user data Constants (see table in configuration manual) Transmission time for 1 byte (see table in configuration manual) FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 11 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 tk calculated above represents the total duration of the command. However, commands may require more time under the following conditions. A very large number of RFID channels are processed in parallel. Very few (or only one) system resources are available for non-cyclic frames. Slow transmission speeds are used on PROFIBUS. Other applications are running on the S7 which require the non-cyclic frame services (SFB 52/53) of the SIMATIC very frequently. High-speed identification systems are used (e.g. RF300). 2.2 Table 2- 1 Configuration scheme MOBY FB configuration scheme Ladder logic programming box "Inst-DB FB 45" MOBY FB 45 Parameters Data type Permissible range Description Params_DB INT 2 to 32767 Parameter data block number for an RFID channel (reader) Params_ADDR INT 0, 50, 100,*... Address pointer in the parameter data block to the start of a UDT 10 Params_DB Params_ADDR *) These values are exemplary whenever only data structures of the UDT 10 type are arranged in succession. These values change if UDT 10 is followed by a command structure (UDT 20). Params_DB and Params_ADDR form a pointer to a data structure. This data structure is defined by calling UDT 10 (English) or UDT 11 (German). A separate data structure must be defined for each RFID channel (reader). See also Data structures of FB 45 (Page 13) FB 45 for MOBY U, MOBY D, RF200, RF300 12 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Description 2.3 Data structures of FB 45 2.3 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. &DOOUHDGHU &DOOUHDGHU &DOOUHDGHU &DOO)% &DOO)% &DOO)% 3DUDPVB'% 3DUDPVB$''5 3DUDPVB'% 3DUDPVB$''5 3DUDPVB'% 3DUDPVB$''5 &DOOUHDGHU &DOO)% 3DUDPVB'% 3DUDPVB$''5 02%<B'% &KDQQHO &KDQQHO &KDQQHO 8'7 &KDQQHO FRPPDQGB '%BQXPEHU FRPPDQGB '%BDGGUHVV 02%<BFRPPD QGV 8'7 '$7B'%BQXPEHU '$7B'%BDGGUHVV 8VHUBGDWD 7KH XVHU GHILQHVWKH VL]HDQG WKH GDWDW\SHV LQKLV GDWDKLPVHOI 6LQJOHFRPPDQG XSWR.% FDQEHSURFHVVHG RU FKDLQHGFRPPDQG 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" and "command_DB_address" are stored in the UDT 10. These variables point to the RFID command that will be executed with the tag. UDT 20 is used to define the RFID command. Different commands or chains of commands can be defined by calling UDT 20 several times (see Section "Command chaining"). The variables "DAT_DB_number" and "DAT_DB_address" are defined in the UDT 20. This variable definition forms the pointer to the user data which is simply referred to as DAT_DB in this function manual. Tag data is stored there when it is read out. When using a write command, the user must store his data before executing the command. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 13 Description 2.4 Number of RFID channels that can be connected 2.4 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. Table 2- 2 Number of RFID channels 315-2 DP S7 CPU type1) Max. no. of CMs Max. readers (channels) 316-2 DP; 318-2 DP max. no. of CMs 416; 417; CP 443-5 Ext Max. readers (channels) Max. no. of CMs Max. readers (channels) ASM 475 (centralized)2) 32 64 32 64 - - ASM 475 (distributed via ET 200M)3 64 x 8 1024 123 x 8 1968 123 x 8 1968 RF170C (distributed via ET 200pro)4) 64 x 9 1152 123 x 9 2214 123 x 9 2214 ASM 456 64 128 123 246 123 246 RF180C 5) 1)The CPU types specified here may not be complete since the range of CPUs and the associated functions are being continuously expanded. 2) Central installation can include up to 3 expansion racks. A DP connector is not necessary in this configuration variant. 3) In the distributed configuration, up to 8 RFID modules (ASM 475) can be operated in each ET 200M. 4) In an ET 200pro distributed I/O, up to 9 RF170C can be plugged in. 5) The number of RF180C communications modules depends on the network and the CPU being used (number of IO addresses). The system configuration (redundancy) may lead to restrictions. Note the manuals of the CPUs and the manual "SIMATIC PROFINET system description". FB 45 for MOBY U, MOBY D, RF200, RF300 14 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Description 2.5 Addressing of the RFID channels 2.5 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. 5DFN 6ORWQXPEHU $QDORJDGGUHVV ,0 &RQQHFWLQJFDEOH 5DFN 6ORWQXPEHU $QDORJDGGUHVV ,0 &RQQHFWLQJFDEOH 5DFN 6ORWQXPEHU ,0 $QDORJDGGUHVV &RQQHFWLQJFDEOH 5DFN 6ORWQXPEHU $QDORJDGGUHVV Figure 2-2 Slots for S7-300 and analog addresses for ASM 475 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 15 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. $XWRPDWLFJHQHUDWLRQRIWKHQH[WIUHHDGGUHVV 7KH,DGGUHVVDQG4DGGUHVVPXVWEHLGHQWLFDO Figure 2-3 Example: Automatic address generation of an ASM 456 FB 45 for MOBY U, MOBY D, RF200, RF300 16 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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). 3K\VLFDODGGUHVVDVVLJQPHQW DVVHWLQ+:&RQILJ 6WDUWDGGUHVVHV RI8'7LQWKH GDWDYLHZRIWKH 02%<'% 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. If a communications module is operated with two channels, a separate UDT 10 must be defined for each channel. The "ASM_address" entry is the same. The "ASM_channel" is set from 1 to 2. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 17 Description 2.5 Addressing of the RFID channels FB 45 for MOBY U, MOBY D, RF200, RF300 18 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 3 Parameterizing 3.1 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: INPUT parameters: These variables must be entered by the user once during configuration (exception: command_DB_number/command_DB_address). Throughout the run time it is not necessary to change or scan these parameters. Please note that you need to execute an init_run after changing an INPUT parameter before the new setting is activated (see Section "Programming a cold and warm restart"). Control bits: The user starts his commands with these Boolean variables. Displays: The displays indicate the command progress to the user. Error analyses can be performed easily. FB-internal variables: These variables are not relevant for the user. They must not be changed by the application. Malfunctions and data corruption would otherwise ensue. The following table shows the complete UDT. The relative addresses are shown in the first column for programmers who prefer to address with absolute values. Table 3- 1 UDT 11 "MOBY Param_d" Address 0.0 Name Type STRUCT Initial value Comment +0.0 ASM_address INT 0 Input: Basic address of the ASM (cyclic word) Input: Number of the channel (1 to 4) Input: Command data block number Input: Start address of data in the BEDB Input: Presence check and tag(0, 1, 2) Input: mode with ECC Input: true: long RESET frame, only for MOBY mode 5 Input: Operating mode Input: Scanning time for MOBY U Input: Init_run Option 1 Input: Distance/capacity setting ** Input: Max. number of tags in field Input: BERO Input: MOBY U: BERO time MOBY D: Tag Type *** +2.0 +4.0 +6.0 ASM_channel command_DB_number command_DB_address INT INT INT * 1 47 0 +8.0 +9.0 +9.1 MDS_control ECC_mode RESET_long BYTE BOOL BOOL B#16#1 FALSE FALSE +10.0 +11.0 +12.0 +13.0 +14.0 +15.0 +16.0 MOBY_mode scanning_time option_1 distance_limiting multitag field_ON_control field_ON_time BYTE BYTE BYTE BYTE BYTE BYTE BYTE B#16#1 B#16#0 B#16#0 B#16#F B#16#1 B#16#0 B#16#0 +17.0 reserved0 BYTE B#16#0 +18.0 +18.1 +18.2 +18.3 ANZ_MDS_present ANZ_cancel ANZ_ECC reserved BOOL BOOL BOOL BOOL FALSE FALSE FALSE FALSE Presence of a tag Cancel-bit in the PIW is set. reserved +18.4 LR_bat BOOL FALSE reserved FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 19 Parameterizing 3.1 Parameter data block Address +18.5 Name battery_low BOOL Initial value FALSE +18.6 +18.7 +19.0 +19.1 error ready cancel command_start BOOL BOOL BOOL BOOL FALSE FALSE FALSE FALSE +19.2 +19.3 +19.4 +19.5 +19.6 +19.7 +20.0 +20.1 +21.0 +22.0 +23.0 +24.0 +26.0 +28.0 repeat_command init_run ASM_failure FB45_active ANZ_next ANZ_reset ASM_busy command_rep_active number_MDS error_MOBY error_FB error_BUS version_MOBY counter_customer BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BYTE BYTE BYTE WORD WORD BYTE FALSE TRUE FALSE FALSE FALSE FALSE FALSE FALSE B#16#0 B#16#0 B#16#0 W#16#0 W#16#0 B#16#2 *4.0 Type Comment Battery check has indicated low voltage Error during command execution Command chain has been finished. Set: abort command or command chain Set: start signal for command or command chain Set: repeat last command Set: reset CM and set new parameters OB122 Set: CM failed FB active NEXT command was last command Init_run was last command CM processes a command CM repeats command Number of tags actually in field Error indicated by CM Error indication of FB Error indicated for PROFIBUS/PROFINET Firmware version CM Setting for S7 cycles per command execution DWORD +44.0 initRUN_timeout INT 1000 +46.0 PEW_timeout_ASM_fail BYTE B#16#5 +47.0 PEW_timeout BYTE B#16#32 +48.0 reserved3 BYTE B#16#0 +49.0 Testbyte BYTE B#16#0 =50.0 FB-internal variables. You should not attempt to modify these variables. FB-internal variables. You should not attempt to modify these variables. FB-internal variables. You should not attempt to modify these variables. FB-internal variables. You should not attempt to modify these variables. FB-internal variables. You should not attempt to modify these variables. END_STRUCT *) Parameter data block UDT 60 is available for transponders > 32 KB. The data type here is WORD. **) RF300, reader only: 6GT2801-3AB10 *** ) RF300 reader in ISO mode FB 45 for MOBY U, MOBY D, RF200, RF300 20 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. Remember that this address has nothing to do with the PROFIBUS address that is set on the CM or the ET 200M. ASM_channel Number of the MOBY channel which is to be used CM type Value range ASM 475, 456; RF170C, RF180C 1, 2 command_DB_ number Number of the data block in which the tag command is specified command_DB_ address Address within the "command_DB". The next tag command starts at this address. "command_DB_number" and "command_DB_address" form a data pointer to the next command (see Section "Configuration scheme"). These INPUT parameters can be changed whenever ready = 1. An init_run does not need to be executed after changing these parameters. Please note: The input parameters command_DB_number and command_DB_address can be changed only when ready = 1. An init_run does not need to be executed after changing these parameters. MDS_control MDS_control turns on/off the presence check or the tag control on the CM (see section "Presence check and tag control"). Value Tag / transponder control CM type 0 Presence check is off. The variable ANZ_MDS_present does not indicate a valid value. all 1 Presence check is on. MDS control is off. The variable ANZ_MDS_present indicates a tag in the transmission window of a reader. all ECC_mode reserved RESET_long MOBY U/D, RF200 and RF300 = 1 MOBY_mode Setting the mode of the Ident system Value Operating mode Note 0 reserved reserved for the setting with the switch or GSD parameter assignment 1 reserved Short init_run (only the MOBY_mode and option1 parameters are transferred to the reader). 5 MOBY U/D, RF200 and RF300 - without multitag handling 475; 456; RF170C, RF180C 6 reserved for multitag handling (FB 55) (see description of FB 55) 7 reserved for multitag handling (FB 55) (see description of FB 55) Please note: MOBY_mode may only be changed after a CM is turned on. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 21 Parameterizing 3.1 Parameter data block Variable scanning_time Description 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. If the transponder receives a command after scanning_time has expired, command execution is delayed by sleep_time of the transponder. Scanning_time should only be set when both of the following conditions exist. * The transponder uses several commands and * command execution must be concluded within a minimum time. 00 hex = no standby time (default) 01 hex = 7ms standby time 02 hex = 14ms standby time : C8 hex = 1400ms standby time Remember: Scanning_time affects the life of the battery. The longer scanning_time is, the shorter the life of the battery. For precise calculations, see the MOBY U manual for configuration, mounting and service. option_1 This byte is bit-coded. Its standard value is B#16#0. It can be used for special control on the ASM/reader. %LW 7KHIODVKLQJRIWKH(55/('LVUHVHWE\DQ LQLWBUXQ :LWK5)5)WKLVUHVHWVWKHIODVKLQJRIWKH (55/('RQWKHFRPPXQLFDWLRQVPRGXOHDQG RQWKHUHDGHU FB 45 for MOBY U, MOBY D, RF200, RF300 22 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Parameterizing 3.1 Parameter data block Variable distance_limiting Description 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. 02 hex = 0.5 W : 10 hex = 4 W (default) : 28 hex = 10 W RF200: 00 hex (reserved) RF300: With this parameter, a change to the output power can only be made for the RF380R (order no. 6GT2801-3AB10). In doing this, you must take into consideration that the change to the output power will affect both the upper and lower limit range, as well as the minimum distance that is to be maintained between adjacent RF380Rs. Refer to the "RF300 system manual", section Field data The following settings are possible: Value 02 0.5 W 03 0.75 W 04 1.0 W 05 1.25 W 06 1.5 W 07 1.75 W 08 2.0 W Settings outside of the specified values mean that the default value of 1.25 W is set and no error message occurs for compatibility reasons! MOBY U: Range limitation Normal output power1) 05 hex = 0.5 m 0A hex = 1.0 m 0F hex = 1.5 m 14 hex = 2.0 m 19 hex = 2.5 m 1E hex = 3.0 m 23 hex = 3.5 m 1) multitag Reduced output power 85 hex 8A hex 8F hex 91 hex 99 hex 9E hex A3 hex Reduced output power must be set when several readers are positioned close together or when data memories located in the vicinity of a reader are detected later or not at all. Disadvantage: The field lobe becomes smaller and there is less time for communication or positioning must be more precise. Intermediate values in steps of 0.1 m are possible (02, 03, ..., 23 hex) MOBY U/D, RF200 and RF300: Maximum number of transponders being processed in the field at the same time. Permitted values: 1 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 23 Parameterizing 3.1 Parameter data block Variable field_ON_control Description 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. field_ON_time (ftim) 00 hex = without BEROs; no write/read device synchronization 01 hex = one or two BEROs The BEROs are combined according to logic OR. The field is ON during actuation of a BERO. 02 hex = One or two BEROs The 1st BERO switches the field on and the 2nd BERO switches the field off. If two BEROs exist and a field_ON_time is set, the field is automatically deactivated if the 2nd BERO does not switch within this BERO time. If no field_ON_time is set, the field remains on until the 2nd BERO is actuated. 03 hex = Activate write/read device synchronization via cable connection (see manual for configuring, mounting and service for MOBY U) RF200: Value 01 Transponder type Comment Any ISO tag - RF300: With the aid of the "ftim" parameter, a decision is made whether the reader is operated in RF300 mode or in ISO 15693 mode (mixed operation is not intended). The following values can be set: Value Transponder type Comment 00 RF300 To be used for all transponders of the type RF3xxT 01 Any ISO tag Activation of the general ISO mode with rudimentary ISO commands. With this setting, operation is basically guaranteed with every ISO-compatible tag. 03 ISO my-d (Infineon SRF 55V10P) e.g. MDS D324, D339 04 ISO (Fujitsu MB89R118) e.g. MDS D421, D422, D423, D424, D425, D426, D428, D460, 05 ISO I-Code SLI (NXP SL2 ICS20) e.g. MDS D100, D124, D126, D139, D150, D165 06 ISO Tag-it HFI (Texas Instruments) e.g. MDS D200 (order no. 6GGT26001AA00-0AX0), D261 07 ISO (ST LRI2K) e.g. MDS D200(order no. 6GGT26001AA01-0AX0), D261 FB 45 for MOBY U, MOBY D, RF200, RF300 24 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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]). 3. Invalid parameters are rejected with an error message (error_MOBY "15"[hex]). 4. By selecting the values 03 to 07, chip-specific commands are used if they exist. The commands have a positive effect on the communication time between the reader and tag and can therefore also allow faster data transfer depending on the tag. MOBY U: Time for BERO mode (field_ON_control = 02) 00 hex = Timeout monitoring is deactivated. The 2nd BERO is needed in order to switch the field off. 01 hex ... FF hex = 1 ... 255s turn on time for the write/read device field. Binary value: 0 ... 255 = Transponder type 00 hex = I-Code 1 (e.g. MDS D139, 6GT2600-0AA00) 01 hex = ISO transponder 02 hex = I-Code 1 and ISO transponder 03 hex = ISO-my-D (with SLG D10S only; the value 01 hex is set for ISO-my-D with SLG D11S / D12S) 04 hex = ISO-FRAM (with SLG D11S/D12S only; the value 01 hex is set for ISOFRAM with SLG D10S) * MOBY D: Transponder type counter_customer: Setting for S7 cycles per command execution. Default value is 02. 00 hex = FB requires 6 S7 cycles per command 01 hex = Depending on the ASM type and the overall configuration, the number of S7 cycles can be reduced to 3 per command 02 hex = Depending on the ASM type and the overall configuration, the number of S7 cycles can be reduced to 2 per command Note: If an optimum short cycle time is required on the PLC, "counter_customer" must be set to "0". Larger values can lengthen the cycle time in the PLC. The permissible values of the INPUT parameters are listed in the hardware specifications. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 25 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. '%: '%% '%%UHODWLYHDGGUHVVLQ8'7 FDQFHO UHVHUYHG FRPPDQGBVWDUW UHSHDWBFRPPDQG LQLWBUXQ $60BIDLOXUH )%BDFWLYH $1=BQH[W $1=BUHVHW $1=B0'6BSUHVHQW $1=BFDQFHO UHVHUYHG $1=B(&& UHVHUYHG UHVHUYHG /5BEDW UHVHUYHG EDWWHU\BORZ UHVHUYHG HUURU 7REHVHWE\WKHXVHUWKHVHFRQWUROELWVDUH UHVHWDXWRPDWLFDOO\E\)% H[FHSWIRU UHSHDWBFRPPDQG 0XVWEHTXHULHGE\WKH WKHXVHU 2SWLRQDOTXHU\ELWV UHDG\ Figure 3-1 Assignment of the command and status word (DBW 18) with variable names FB 45 for MOBY U, MOBY D, RF200, RF300 26 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. repeat_command TRUE = Command repetition: The last command or command chain stored on the CM is processed again with the next tag. Command processing for the tag is not started until the tag that has already been processed has left the transmission window (ANZ_MDS_present = 0) and a new tag has entered the transmission window of the reader (ANZ_MDS_present: 0 1). In the case of RFID systems with unique tag IDs (UID) (e.g. RF300, MOBY U), the next tag entering the field must have a different UID from the previous one for the command to be repeated. FALSE = No command repetition or command repetition is stopped after the command started with the repeat command has been processed. Remember that this bit must be reset by the user to stop command repetition. The result of command repetition is fetched when command_start is set by the user. The repeat_command is not automatically reset by FB 45 after command processing. The init_run command resets the repeat_command variable. This also interrupts a command repetition on the CM. The repeat_command can be set again by the application with the next command_start. The handling of command repetition is described in Section "Command repetition (Page 37). Refer to the system manual of the relevant RFID/MOBY system. RF200 does not support this function. init_run TRUE = Restart of the communications module. FB 45 is reset and the CM parameters are reassigned. All data and commands on the CM are lost. This bit must be set in the restart OB (OB 100) for each RFID channel. After a failure of the MOBY ASM, error_MOBY=0F is signaled to the user. The user must then perform an init_run. FALSE = FB 45 triggers an automatic reset. Note: ASM_failure * The init_run bit is initialized with TRUE when a parameter data block is downloaded from the programming device to SIMATIC. This causes an automatic restart on the CM. * The execution time of init_run is normally in the millisecond range. In the event of an error, the time may be up to 15s. TRUE = The CM has failed. This bit is set by the user in OB 122 (see section "Programming a module failure (Page 68)"). FB 45 signals an error to the user (error_FC = 09) and interrupts a command in progress. If OB 122 is not programmed by the user, the PLC changes to STOP if there is a CM failure. FALSE = Reset occurs automatically triggered by FB 45. FB45_active FB 45 is currently executing a command. This variable is set when the command is started (command_start=TRUE) and remains active until * FB 45 has received the last acknowledgment from the CM * the init_run bit has been set * An error message was signaled by the CM ANZ_next The "next" command is not supported by the readers (MOBY U/D, RF200 and RF300). ANZ_reset This bit indicates that the last command to be executed was a RESET. The RESET command was started by the user with "init_run". FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 27 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. ANZ_cancel The "cancel" command is not supported by the readers (MOBY U/D, RF200 and RF300). ANZ_ECC Not currently used reserved Not currently used LR_bat Not currently used battery_low Not currently used The battery status of a MOBY U transponder is queried with the MDS-status command. error FB 45 sets this bit if a command is terminated abnormally. The error bit is the checksum error bit for all errors which occur. The exact cause of the error is stored in the variable error_ MOBY, error_FB or error_BUS (see section "Further displays (Page 29)" or section "Error messages and troubleshooting (Page 47)"). The error bit is reset when a command is restarted. ready Ready message: error bit = FALSE must be checked after ready = TRUE is signaled. This ensures that the command was executed normally. Note: The ready bit does not need to be set in order to start "init_run". FB 45 for MOBY U, MOBY D, RF200, RF300 28 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. After an init_run, command_rep_active is first reset by FB 45 and then set again after a delay because FB 45 first transfers the RFID commands to the CM. number_MDS The number of transponders currently in the transmission window is displayed. If there are more than 15 transponders in the field, the number_MDS display remains set to 0F hex. The display is only available and valid if the reader being used has this function (MOBY U, MOBY D and RF300). error_MOBY This error was signaled by the CM or reader. The error is usually displayed by the ERR LED on the CM and/or reader (see Section "Error messages and troubleshooting (Page 47)"). error_FB Error message from FB 45 (see section "Error messages and troubleshooting (Page 47)") error_BUS The transmission path between FB 45 and the CM reports an error. This is usually a PROFIBUS/PROFINET error. (see section "Error messages and troubleshooting (Page 47)"). This error is signaled by system functions SFC 58/59. version_MOBY Display of the communications module firmware version. The value entered here is updated each time the CM starts up. It is ASCII-coded. ([DPSOH '%% '%% KH[ KH[ 9HUVLRQ All other variables of UDT 10 are for FB-internal use. They must never be changed by the user. 3.2 RFID commands Note Notation for the commands For reasons of compatibility the obsolete terms "MOBY", "MDS" and "SLG" have been retained in commands and the descriptions of the commands. These terms are stored in the program and in the data blocks and therefore continue to be used in this manual. Note This section provides a description of all commands that can by processed by FB 45. The commands that can actually be processed by the communications module you are using, are described in section Brief description of the hardware (Page 81). Before you can start an RFID command with command_start, you need to define the command. UDT 20 (commentary in English), UDT 21 (commentary in German) or UDT 24 (Spanish commentary) is available for the simple definition of a command. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 29 Parameterizing 3.2 RFID commands Table 3- 5 UDT 21 "MOBY CMD_d" Address 0.0 Name Type STRUCT Initial value Comment +0.0 +1.0 +2.0 command sub_command length BYTE BYTE B#16#2 B#16#0 1 MDS: 2 = read, 1 = write INIT = bit pattern; END, SET, MDS, SLG=mode Amount of data to be written/read in bytes +4.0 address_MDS W#16#0 +6.0 +8.0 DAT_DB_number DAT_DB_address Start address on transponder, memory size for INIT; date for transponder Number of DAT_DB, data for transponder Pointer to start word in DAT_DB INT *) WORD INT INT *) END_STRUCT =10.0 48 0 *) For transponder memory > 32 KB, UDT 70 must be used (data type WORD instead of INT). The "length" value is then specified as a hexadecimal value. The "actual value" of the variables can be modified using the editor in the data view of the DB or in the STEP 7 application program. Please note that the actual values can only be changed if no command is active (ready = 1). 3.2.1 Command parameters Overview of commands Table 3- 6 Overview of commands Command [hex] Command normal chained*) Syntax Description 01 41 WRITE 02 42 READ Read data from transponder 03 43 INIT Initialize transponder Write data to transponder 04 44 SLG STATUS Query reader status 08 48 END Terminate communication with the transponder 0A 4A SET-ANT Antenna on/off 0B 4B MDS-STATUS Query transponder status *) Chained commands are not supported by all readers or CMs. You should also note the information in the relevant system manual. FB 45 for MOBY U, MOBY D, RF200, RF300 30 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Parameterizing 3.2 RFID commands WRITE Table 3- 7 Write to the tag Command [hex] 01 sub_command [hex] - length [dec] address_MDS [hex] DAT_DB [dec] 1 to 32767 *) Length of transponder data to be written 0000 to FFFF **) The data is written to the transponder starting at this start address. Pointer to user data to be written to the transponder Note RF200: The data length can have a maximum value of 1024 [dec] *) When UDT 70 is used, "length" is specified as a hexadecimal value. The value range is then from 0001 to FFFF. This means that a complete 64 KB transponder can be processed. **) Please refer to section "Processing of data memories/transponders (Page 60)" for addressing individual transponder types. READ Table 3- 8 Read tags Command [hex] 02 sub_command [hex] - length [dec] 1 to 32767 *) Length of transponder data to be read address_MDS [hex] 0000 to FFFF **) The data is read from the transponder starting at this address. DAT_DB [dec] Pointer to user data. FB 45 stores the read transponder data here Note RF200: The data length can have a maximum value of 1024 [dec] *) When UDT 70 is used, "length" is specified as a hexadecimal value. The value range is then from 0001 to FFFF. This means that a complete 64 KB transponder can be processed. **) Please refer to section "Processing of data memories/transponders (Page 60)" for addressing individual transponder types. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 31 Parameterizing 3.2 RFID commands INIT Table 3- 9 Command [hex] Initialize tag sub_command [hex] 03 00 to FF Hexadecimal value that is written to the transponder 2 KB 32 KB 44 bytes 112 bytes 256 bytes 992 bytes 2000 bytes 20 bytes 8 KB 32 KB 64 KB MOBY U: MOBY U: MOBY D: MOBY D: MOBY D: MOBY D: MOBY D RF300: RF300: RF300: RF300 length [dec] - Transponder type RAM *) RAM *) I-Code 1 ISO I-Code SLI ISO Tag-it HF-I ISO my-d FRAM EEPROM FRAM *) FRAM *) FRAM *) address_MDS [hex] Memory size of transponder to be initialized DAT_DB [dec] Note - Memory size Init duration 08 00 80 00 00 2C 00 70 01 00 03 E0 07 D0 00 14 20 00 80 00 FF 00 Approx. 1 s Approx. 1.5 s Approx. 0.4 s Approx. 0.5 s Approx. 1 s Approx. 3 s Approx. 3 s Approx. 0.2 s 0.9 s 3.6 s 7.2 s *) The OTP memory is not initialized by this command. Note RF200 does not support the "initialize" command. Instead use the "Write" command. FB 45 for MOBY U, MOBY D, RF200, RF300 32 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Parameterizing 3.2 RFID commands SLG STATUS Table 3- 10 Command [hex] 04 1) SLG status sub_command [hex] length [dec] address_MDS [hex] DAT_DB [dec] Note 01 = status after UDT 110 1) - - Pointer to the result. MOBY U/D, The result is indicated RF200 and RF300 with the MOBY U corresponding UDT (see sub_command) MOBY U 02 = status after UDT 120 1) (last commands) - - 03 = status after UDT 130 1) (error messages) - - 04 = status after UDT 1401) (transponder in field) - - MOBY U 05 = status after UDT 150 (communication quality) - - MOBY U 06 = status after UDT 280 (diagnostics data) - - RF300 You will find the UDT description in the section "UDTs of FB45". END Table 3- 11 Command [hex] 08 Terminate communication with the transponder (MOBY U) sub_command [hex] 00 = Processing with transponder has terminated length [dec] - 01 = Processing pause with the transponder1) address_MDS [hex] - DAT_DB [dec] - Note ANZ_MDS_present is reset. ANZ_MDS_present remains set. MOBY U: This command is recommended when the selected scanning_time is greater than 0 (standby time). Use of this command optimizes the life of the transponder battery. Before another transponder command can execute, the sleep_time of the transponder must first expire. 1) FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 33 Parameterizing 3.2 RFID commands SET-ANT Table 3- 12 Switch antenna of reader ON/OFF Command [hex] 0A sub_command [hex] length [dec] 01 = antenna on - address_MDS [hex] - DAT_DB [dec] - Note The antenna on/off command cannot be started by command repetition (see section "Command repetition (Page 37)"). 02 = stand-by; antenna off This command is not needed for normal operation because, when a reader is turned on, its antenna is always on. The antennas must be turned off if two sensitive readers are positioned very close to each other. The application software must ensure that only one antenna is on at a time. MDS-STATUS Table 3- 13 Transponder status and diagnosis Command [hex] 0B sub_command [hex] length [dec] address_MDS [hex] DAT_DB [dec] Note 00 = status and diagnosis - Today's date (week/year) for calculating the battery life (e.g. 1401 hex = 20th week of the year 2001) Pointer to result. MOBY U only The result is (see section "The UDTs of presented with FB 45 / FC 45 (Page 74)") UDT 100. 01 = type and write protection status for RF300 tags - - Pointer to result. RF300 The result is (see Section "UDTs of presented with FB 45") UDT 260. 02 = diagnostic data - - Pointer to result. RF300 The result is (see section "The UDTs of presented with FB 45 / FC 45 (Page 74)".) UDT 270. 03 = Type and write protection ISO tags - - UDT 230 RF300 with ISO transponders RF200, MOBY D *) *) SLG D10S only FB 45 for MOBY U, MOBY D, RF200, RF300 34 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. The chained commands must all be command type 4x. The last command in a chain must be type 0x. FB 45 uses this to detect the end of a command chain. Example: A transponder must process 4 data records. The command structure is stored in DB 47. The transponder data is stored consecutively in DB 48. Read Transponder address 0000 hex Length 600 Read Transponder address 1000 hex Length 100 Read Transponder address 1200 hex Length 1 Write Transponder address 1200 hex Length 1 Execution steps: 1. Define structure Table 3- 14 DB 47 - declaration view Partial command STRUCT Partial command ARRAY [1 ... 4] Partial command UDT 20 Partial command END_STRUCT Note: 1 ... 4 = No. of partial commands 2. Specify the "starting values" in the data view FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 35 Parameterizing 3.2 RFID commands Table 3- 15 DB 47 - data view Name Initial value Comment Partial command [1].command Partial command [1].pattern Partial command [1].length Partial command [1].adress_MDS Partial command [1].DAT_DB_number Partial command [1].DAT_DB_address 42 00 600 0000 48 0 Read command; followed by another command Partial command [2].command Partial command [2].pattern Partial command [2].length Partial command [2].adress_MDS Partial command [2].DAT_DB_number Partial command [2].DAT_DB_address 42 00 100 1000 48 600 Read command; followed by another command Partial command [3].command Partial command [3].pattern Partial command [3].length Partial command [3].adress_MDS Partial command [3].DAT_DB_number Partial command [3].DAT_DB_address 42 00 1 1200 48 700 Read command; followed by another command Partial command [4].command Partial command [4].pattern Partial command [4].length Partial command [4].adress_MDS Partial command [4].DAT_DB_number Partial command [4].DAT_DB_address 01 00 1 1200 48 701 Write command, last command in chain See also Command parameters (Page 30) FB 45 for MOBY U, MOBY D, RF200, RF300 36 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. Advantages of command repetition The data transfer on PROFIBUS/PROFINET is minimized. This is particularly noticeable with extensive bus configurations and slow (bus) transmission speeds. The CM processes each tag independent of FB 45. In concrete terms, this means each tag is processed even in applications with a very fast sequence of tags. This takes place no matter what the (PROFI) BUS speed. Total data throughput is increased considerably particularly with controllers which have few system resources for non-cyclic frames. Command overview for use with command repetition Command [hex] Command Description Permitted with command repetition normal chained* Syntax 01 41 WRITE Write data to transponder 02 42 READ Read data from transponder yes 03 43 INIT Initialize transponder yes 04 44 SLG STATUS Query reader status No 08 48 END END; terminate communication with the transponder yes 0A 4A SET-ANT Switch antenna on/off No 0B 4B MDS-STATUS Query transponder status yes yes; but only with identical write data *) Chained commands are not supported by all readers. You should also note the information in the relevant system manual. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 37 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. UHDG\ FRPPDQGBVWDUW UHSHDWBFRPPDQG $1=B0'6BSUHVHQW 7KHXVHUVWDUWVWKHFRPPDQGIDVWHU WKDQWUDQVSRQGHUVPRYHSDVWWKH UHDGHU 7KHUHVXOWLVDYDLODEOHWRWKHXVHU $60BEXV\ GLUHFWO\IROORZLQJ SURFHVVLQJRIWKHFRPPDQG $60BEXV\ Figure 3-2 7KHWUDQVSRQGHUVSDVVE\WKHUHDGHU IDVWHUWKDQWKHXVHUIHWFKHVWKH UHVXOWVKHUHWKHUHVXOWVDUH WHPSRUDULO\VWRUHGRQWKHFRPPXQLFD WLRQVPRGXOH7KHUHVXOWVDUHUHDGRXW DWDODWHUSRLQWLQWLPH 5HVXOWVDUH IHWFKHGRQWKH FRPPXQLFD WLRQVPRGXOH 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). In this case, the results are temporarily stored on the CM. The CM or reader has a number of buffers for this intermediate storage. When the buffers are full and FB 45 has not fetched data and additional tags arrive, these tags are no longer processed. Table 3- 16 Readers that support command repetition Device type SLG U92 SLG D10S SLG D11S/D12S RF300 reader No. of buffers per channel 150 100 1 246 Max. user data which can be processed with command repetition 34950 byte 23300 byte 233 byte 57318 byte One buffer can hold up to 233 bytes of user data. FB 45 for MOBY U, MOBY D, RF200, RF300 38 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. UHDG\ FRPPDQGBVWDUW UHSHDWBFRPPDQG $1=B0'6BSUHVHQW 7KHIROORZLQJVHTXHQFHPXVWEHSURJUDPPHGE\WKHXVHU $WWKHEHJLQQLQJRIWKHFRPPDQGWKHXVHUVHWVFRPPDQGBVWDUWDQGUHSHDWBFRPPDQGVLPXOWDQHRXVO\ 7KHXVHUWKHQZDLWVIRU$60BEXV\ DQGWKHQUHVHWVUHSHDWBFRPPDQG 2QFHUHDG\ KDVEHHQVLJQDOHGE\WKH)%WKHFRPPDQGKDVEHHQSURFHVVHG 7KHFRPPXQLFDWLRQVPRGXOHGRHVQRWDXWRPDWLFDOO\SURFHVVDQ\IXUWKHUWUDQVSRQGHUV 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. RF300, MOBY U), the stored command is only repeated when the next tag entering the read field has a different UID from the previous one. If the same tag (identical UID) enters the field again and again, the tag will not be processed again. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 39 Parameterizing 3.3 Presence check 3.3 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. It can be controlled with various mechanisms. Selection is carried out using the parameter MDS_control. Currently the mechanism "with field scanning" is available with the MDS_control = 1 parameter. Field scanning (MDS_control = 1): The reader's firmware continuously scans its surroundings via the magnetic field to determine whether a transponder is present. A hysteresis during field scanning suppresses most of the switching back and forth of ANZ_MDS_present when a tag stops at the border of the field. Presence A transponder is currently within the operating range of the reader. The presence bit (ANZ_MDS_present in the command and status word) is set (see section "Command and status word (Page 26)"). The presence display is indicated by the PRE LED on the front of the communications module (see section Brief description of the hardware (Page 81)). Some of the readers have their own LEDs and display responses that can be found in the relevant manual. 3.3.1 No tag control, no presence check: MDS_control = 0 The message about the presence of a tag is suppressed by the ANZ_MDS_present variable. 3.3.2 No tag control, presence control with field scanning: MDS_control = 1 In this mode, the field of the selected reader is always on. As soon as a tag moves into the field of the reader, this is indicated to the user via the ANZ_MDS_present bit (see section "Command and status word (Page 26)"). The user can then start a command at any time. No error message is generated if the tag leaves the field during processing. FB 45 for MOBY U, MOBY D, RF200, RF300 40 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Commissioning 4 1st step: Install communications module in STEP 7 To install the communications modules in STEP 7, follow the steps below depending on the communications modules you are using: RF170C, ASM 475 The installation program for RF170C and ASM 475 must be run once on the STEP 7 PC. PROFIBUS ASM 456 The GSD file must be added to the device catalog using HW Config ("Options" > "Install new GSD..."): - Siem8114.GSD for ASM456 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". 2nd step: Configure hardware in STEP 7 To configure the hardware in STEP 7, follow the steps below depending on the communications module and the configuration you are using: ASM 475: Centralized configuration in S7-300 ASM 475: Distributed configuration with PROFIBUS and ET 200M RF170C: distributed configuration via PROFIBUS or PROFINET and ET 200pro ASM 456: Distributed configuration with PROFIBUS RF180C: Distributed configuration with PROFIBUS FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 41 Commissioning The following figure shows the position of the communications modules in the hardware catalog. $60LQ DFHQWUDOL]HG FRQILJXUDWLRQ Figure 4-1 (J$60LQ DGLVWULEXWHG FRQILJXUDWLRQ YLD(70 $60LQD GLVWULEXWHG FRQILJXUDWLRQYLD 352),%86 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. The value in the I address field must be copied later on into the ASM_address variable in the STEP 7 project. If a communications module has more than one channel (e.g. ASM 475 = 2 channels), the same I address must be used for every channel. The following figure shows an example of a hardware configuration: FB 45 for MOBY U, MOBY D, RF200, RF300 42 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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). 3rd Step: Set the properties of the communications module You can set the basic function of the communications module in the object properties of the module (e.g. MOBY U, serial baud rate). The object properties are shown in one of the following windows. The possible options are shown in the drop-down lists. $60bREMHFWSURSHUWLHV Figure 4-3 $60REMHFWSURSHUWLHVDUHVWRUHG LQWKH*6'ILOH Configuring the object properties FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 43 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. - Then display DB 45 in the "data view" of the editor and modify the "input parameters" in the "Actual value" column. For simple commissioning of RF200/RF300, all you have to do is adjust the ASM_address and ASM_channel parameters to the HW Config addresses. Constraint: Each reader uses the same command (DB 47) and the same data (DB 48). During commissioning of RF200/RF300 the value "5" is correct here. Otherwise this value must be adjusted. These two variables must be adapted for each channel. The pointer to the command_DB can retain the default value on initial commissioning. Figure 4-4 Edit DB 45 Edit OB 1 and program a cyclic FB 45 call for each channel; declare a memory bit for the command start for each RFID channel. Set the variable "init_run" in the parameter DB in OB 100 for each RFID channel. FB 45 for MOBY U, MOBY D, RF200, RF300 44 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. If the CPU does indicate STOP, you should continue by troubleshooting. This is done by evaluating the diagnostic messages of the CPU (function: "PLC - Module Information"). The main causes of errors are: - There is a mismatch between the I/O address of the modules in HW Config and the ASM_address configured in the MOBY DB (UDT 10) or the ASM_address does not exist on the I/O. - A slave has failed and OB 122 is not programmed. Since the default parameter assignment of FB 45 is set with MDS_control = B#16#1, the presence check on the reader must already be active now. You can recognize this on the CM by the flickering RxD LED or on the reader by the permanently lit LED. If you now place a transponder in the transmission window of a reader, the PRE or ANW LED must light up. If the RxD LED does not go on, continue with trouble-shooting as described in the next point. Checking operation using the programming device Use the "Modify variables" function to monitor the status of communication between FB 45 and the CM and to track errors and start commands. The following figure shows the necessary variables: This variable table can be found in the sample project under the name "Status Channel 1": Figure 4-5 Variables for checking functions - VAT "Status Channel 1" FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 45 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. This channel is not processed cyclically by an FB 45 call in OB 1. If error = TRUE: Read out the precise cause of the error using the variables error_MOBY, error_FB or error_BUS. The causes of errors and their remedies are described in the section Error messages and troubleshooting (Page 47). The variable ANZ_MDS_present now indicates the presence of a tag as soon as you place a tag in the transmission window of the reader. This is the same display as the PRE LED on the CM or the yellow/orange LED on the reader. You can now start the selected MOBY command with the auxiliary variable "Strt_cmd_chn1" = TRUE. If there is no tag in the reader's transmission window, the command is processed on the CM for an indefinite length of time. The status is indicated by the ready bit "MOBY DB.SLG1.ready" = FALSE. Now place a tag in the transmission window. As soon as the tag has been processed, the result is transferred to FB 45 and "ready" = TRUE is indicated. Commissioning of the RFID components is now complete. You can now program your own Ident application based on the sample program. FB 45 for MOBY U, MOBY D, RF200, RF300 46 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 5 Error messages and troubleshooting 5.1 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. The pointer Params_DB, command_DB or DAT_DB does not exist or is pointing to a nonexistent address area. 5.2 Error messages An error condition exists in FB 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_FB" or "error_BUS". Table 5- 1 Classification of error messages Error variable error_MOBY Classification This error is reported by the communications module or reader. There are two main reasons for this: * Errors have occurred in communication between the communications module and the reader or between the reader and the transponder. * The CM cannot process the command. Error_MOBY is indicated on the CM by the ERR LED with the corresponding flashing pattern. error_FB This error is signaled by FB 45. Main cause * error_BUS There is a parameter error in "Params_DB" or "command_DB". The transport layer of PROFIBUS or PROFINET is signaling an error. A PROFIBUS tracer and a PROFIBUS device (BT 200; order No. 6ES71810AA00-0AA0) or a diagnostics repeater (order no. 6ES7972-0A801-0XA1) are invaluable tools for accurate troubleshooting. The PROFIBUS system diagnostics can provide further information about the cause of the error. The error shown here is reported by the SFB 52/53 system function in the RET_VAL parameter. For a detailed description of the RET_VAL parameter, please refer to the SIMATIC S7 system manuals (see System software for S7-300/400). FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 47 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. Table 5- 2 Error code Error messages of the communication module/reader using the "error_MOBY" variable (B#16#...) Flashing of ERR LED 00 - Description No error Default value if everything is ok. - 1x No error CM has started up and is waiting for an init_run. 01 2x Presence error: The tag has moved out of the transmission window of the reader. The command was executed only partially. Read command: No data are transmitted to FB 45. Write command: The tag that has just left the field contains an incomplete data record. * The operating distance from reader to tag is not being kept to. Configuration error: The data record to be processed is too large (in dynamic mode) The next command is automatically executed on the next tag. A read/write command is possible. * 02 2x Presence error: A tag has passed by a reader without being processed by a command. This error message is not reported immediately. Instead, the CM is waiting for the next command (read, write). This command is immediately replied to with this error. This means that a read or write command is not processed. Only the next command is executed normally by the ASM again. An init_run from FB 45 also resets this error state. FB 45 for MOBY U, MOBY D, RF200, RF300 48 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Error messages and troubleshooting 5.2 Error messages Error code (B#16#...) Flashing of ERR LED 03 3x 04 4x Description 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 failed briefly * The automatic fuse on the CM has blown * The hardware is defective * Another reader is in the vicinity and is active * Coupled interference on reader - or PROFIBUS cable * After eliminating the problem, run init_run Error in tag memory The tag has never been written to or has lost the contents of its memory due to battery failure. 05 5x * Replace tag (possibly defective) * Reinitialize tag (see section Parameterizing (Page 19)). Unknown command FB 45 is sending an uninterpretable command to the CM. 06 6x * Command_DB contains invalid command parameters. * The command_DB was overwritten by the user * The tag has signaled an address error Field disturbance on reader The reader is receiving interference pulses from the environment. 07 7x * External interference field * There is not enough distance between two readers and this does not correspond to the configuration guidelines * The connecting cable to the reader is subject to interference, is too long or does not comply with the specification * MOBY U: Tag has left the field during communication. * MOBY U: Communication between reader and tag was aborted due to a disruption (e.g. person/foreign body moving between reader and tag). Too many transmit errors The tag could not receive the command or the write data from the CM correctly even after several attempts. * The tag is positioned exactly in the boundary area of the transmission window * The data transmission to the tag is being disrupted by external interference. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 49 Error messages and troubleshooting 5.2 Error messages Error code (B#16#...) Flashing of ERR LED 08 8x Description CRC sending error * 09 9x 10x 11x 0C 12x 0D 13x The tag is in the boundary area of the reader. - The tag and/or reader have a hardware fault. Cause same as error B#16#06. Only during initialization: Tag cannot execute the initialization command. * 0B - Only during initialization: CRC error when receiving an acknowledgment from tag * 0A The tag is signaling CRC errors frequently. Tag is defective MOBY U: Memory of the tag cannot be read correctly The tag memory cannot be written to * Tag memory is defective * The EEPROM memory of the transponder has been written to too often and must be replaced Address error The address area of the tag is exceeded. * The start address in command_DB is invalid at command start (see Section "Processing data memories") * The tag is not the right type * RF300: Attempted write access to write-protected areas (OTP area) 0E 14x reserved 0F 1x Startup message from CM. The CM was off and has not yet received a RESET command. * Execute an init_run * The same physical CM channel is used in two (or more) UDT 10 structures. Check ASM_address and ASM_channel in all UDT 10 structures. 10 16x Note: The NEXT command is not supported by the readers (MOBY U/D, RF200 and RF300). 11 17x Short-circuit or brief undervoltage of the 24 V supply of the CM or overload of the 24 V outputs (error code, presence) * The affected output is turned off. * All outputs are turned off when total overload occurs. * A reset can only be performed by turning the 24 V voltage off and on again. * Then start init_run. FB 45 for MOBY U, MOBY D, RF200, RF300 50 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Error messages and troubleshooting 5.2 Error messages Error code (B#16#...) Flashing of ERR LED 12 18x Description Internal CM communication error. * Connector contact problem on the CM * Defective CM hardware - * 13 19x 14 20x 15 16 17 18 21x 22x 23x - Return CM for repair Start init_run command after error correction. CM or reader does not have enough buffer space to store the command temporarily. internal error. * Program execution error on the CM * Cycle power to the CM * Start init_run command after error correction. * MOBY U: Watchdog error on the reader. Bad parameter assignment of the CM or reader * Check INPUT parameters in UDT 10 * Check parameters in HW Config * RESET command is has incorrect parameter settings. * After a startup, the CM has not yet received an init_run. The FB command cannot be executed with the PROFIBUS/PROFINET parameter assignment. * Length of the input/output areas too small for the cyclic I/O word. Did you use the right GSD file? * The CM or the reader have received a data record that is too long (data length > 233 bytes). The FB being used does not match the CM/reader. Communication error between FB 45 and communications module. Handshake error * Params_DB (UDT 10) of this reader is being overwritten by other parts of the program. * Check the parameter assignment of the reader in UDT 10 * Check FB 45 command which caused this error. * Start init_run command after error correction. An error has occurred which must be acknowledged with an init_run. * A temporary short circuit has occurred on PROFIBUS. * The RESET command is faulty. * Start init_run command after error correction. * Check parameters ASM_address, ASM_channel, and MOBY_mode. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 51 Error messages and troubleshooting 5.2 Error messages Error code (B#16#...) Flashing of ERR LED 19 25x Description Previous command is active or buffer overflow. The user sent a new command to the CM although the last command was still active. 1A - * Active command can only be terminated with an init_run. * Before a new command can be started the READY bit must be 1 (exception: init_run). * Two FB 45 calls were assigned the same parameters ("ASM_address" and "ASM_channel"). * Two FB 45 calls are using the same Params_DB pointer. * Start init_run command after error correction. * When command repetition is used, no data is fetched from the tag. The data buffer on the CM has overflowed. Tag data has been lost. PROFIBUS DP error occurred. * The PROFIBUS DP bus connection was interrupted - Wire break on the bus - Bus connector on CM was briefly unplugged * PROFIBUS DP master no longer addressing CM * Execute an init_run The CM has detected a frame interruption on the bus. The PROFIBUS may have been reconfigured (e.g. with HW Config). This error is only indicated when access monitoring has been enabled in the PROFIBUS configuration. * 1B 27x Other application active (for example firmware download) 1C 28x The antenna of the reader is turned off. A tag command to the CM was started in this status. 1D - * Turn on the antenna with the "SET-ANT" command * The antenna is turned on (off) and has received an additional turnon (turn-off) command. More transponders are located in the transmission window than can be processed at the same time by the reader. * 1E 1F 30x - Only 1 tag can be processed at a time with FB 45 Error when processing the function * The data in UDT 10 are invalid (e.g. write command with length = 0); check UDT 10 and execute init_run * Hardware defect: CM receives wrong data with init_run. * The "number of bytes" byte does not match the user data length (see Section "Programming the MOBY-ASM on PROFIBUS DPV1"). Active command canceled by RESET (init_run) or bus connector was unplugged * Communication with the tag was aborted by init_run. * This error can only be reported on init_run or cancel FB 45 for MOBY U, MOBY D, RF200, RF300 52 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Error messages and troubleshooting 5.2 Error messages error_FB Table 5- 3 Error variable "error_FB" Error code Description (B#16#...) 00 No error; default value if everything is ok. 01 Params_DB not available in SIMATIC 02 Params_DB too small 03 04 05 * UDT 10/11 was not used during definition * Params_DB must be 300 bytes in length (for each channel) * Check that Params_DB and Params_ADDR are correct The DB after the "command_DB_number" pointer is not available in the SIMATIC. "command_DB" in the SIMATIC too small * UDT 20/21 was not used during command definition * The last command in "command_DB" is a chained command; reset the chaining bit * Check command pointer command_DB_number/command_DB_address Invalid command type. You will find a description of the valid commands in the section "RFID commands (Page 29)". * Check command pointer command_DB_number/command_DB_address * Check the current values in command_DB - 06 Execute an init_run Unexpected acknowledgement received. The parameters of the command and acknowledgement frame do not match (command, length, address_MDS). * The user changed the command_DB_number/_address pointer during command execution. * The user changed the command parameters in the MOBY CMD data block (UDT 20) during command execution. * Check the ASM_address and ASM_channel parameter settings. ASM_address and ASM_channel have the same parameters for different channels. * The acknowledgement counter and command counter (see section "Cyclic control word between master and communications module (Page 102)") between the CM and FB are no longer synchronized - Execute an init_run 07 The MOBY_mode or MDS_control parameter (defined in UDT 10) has an illegal value (see Section "Parameter data block"). 08 A bus error has occurred which is reported by system functions SFB 52/53. More information on this error is available in the error_BUS variable. * ASM_address or ASM_channel not available * Execute an init_run FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 53 Error messages and troubleshooting 5.2 Error messages Error code Description (B#16#...) 09 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. OB 122 is called if FB 45 can no longer access the cyclic word for the CM. 0A Another init_run was started without waiting for ready during execution of the init_run command * Do not set init_run cyclically The same physical channel/reader is used in two (or more) UDT 10 structures. Check ASM_address and ASM_channel in all UDT 10 structures. Note: If the init_run was set cyclically without waiting for ready, after the error has been detected, you will need to run a second init_run to end this error. * 0B 0C 0D init_run cannot be executed; cyclic process image for the CM is disrupted; FB 45 reports timeout of the process image for the CM The timeout time can be adapted in DBB 47 of UDT 10 if required. The default value is 50 (dec)=2 seconds. Greater values (255 max.) will increase the timeout time. * ASM_address in UDT 10 is set incorrectly. ASM_address may be for wrong module. * ASM_channel setting is >8 or 0 * CM hardware/firmware is faulty. * The same physical channel/reader is used in two (or more) UDT 10 structures. Check ASM_address and ASM_channel in all UDT 10 structures. Area length error on block move for FB 45. * DAT_DB does not exist or is too small. Check DAT_DB_number and DAT_DB_address in UDT 20 * Write command with length = 0 was issued. * Execute an init_run An init_run was not completed correctly. The process image is inconsistent. This message is equivalent to a timeout. A timeout is reported 15s after starting init_run. This time can be adjusted in DBW 44 if necessary. * Run init_run again * Turn CM off and on again * The RUN/STOP switch on the CPU was pressed rapidly several times in succession (particularly with slow PROFIBUS baud rates) * The same physical channel/reader is used in two (or more) UDT 10 structures. Check ASM_address and ASM_channel in all UDT 10 structures. FB 45 for MOBY U, MOBY D, RF200, RF300 54 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Error messages and troubleshooting 5.2 Error messages error_BUS Note 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 S7300/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 Error code Description (W#16#...) 800A CM is not ready (temporary message) * This message is received by a user who is not using FB 45 and is querying the CM acyclically in very quick succession. 8x7F Internal error on parameter x. Cannot be remedied by the user. 8x22 8x23 Area length error on reading parameter. Area length error on writing parameter. This error code indicates that parameter x is partially or completely outside the operand area or the length of a bit array for an ANY parameter is not divisible by 8. 8x24 8x25 Area error on reading parameter. Area error on writing parameter. This error code indicates that parameter x is within an area not allowed for the system function. 8x26 Parameter contains a time cell number which is too high. 8x27 Parameter contains a counter cell number which is too high. 8x28 8x29 Alignment error on reading parameter. Alignment error on writing parameter. The reference to parameter x is an operand whose bit address is not equal to 0. 8x30 8x31 The parameter is located within the write-protected global DB. The parameter is located within the write-protected instance DB. 8x32 8x34 8x35 The parameter contains a DB number which is too high. The parameter contains an FC number which is too high. The parameter contains an FB number which is too high. 8x3A 8x3C 8x3E The parameter contains a DB number which is not loaded. The parameter contains an FC number which is not loaded. The parameter contains an FB number which is not loaded. 8x42 An access error occurred while the system was attempting to read a parameter from the I/O area of the inputs. An access error occurred while the system was attempting to write a parameter to the I/O area of the outputs. 8x43 8x44 8x45 Error on nth (n > 1) read access after an error occurred. Error on nth (n > 1) write access after an error occurred. 8090 Specified logical base address is invalid: No assignment in SDB1/SDB2x exists, or it is not a base address. 8092 A type other than BYTE has been specified in an ANY reference. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 55 Error messages and troubleshooting 5.2 Error messages Error code Description (W#16#...) 8093 80A0 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 Negative acknowledgment while reading from module. FB fetches acknowledgment although no acknowledgment is ready. A user who is not using FB 45 would like to fetch DS 101 (or DS 102 to104) although no acknowledgment is available. * Perform an init_run for new synchronization between ASM and application. 80A1 Negative acknowledgment while writing to the module. FB sends command although a CM is unable to receive a command 80A2 DP protocol error with layer 2 * DP-V1 mode must be set in the header module for distributed I/O. * Possible hardware defect 80A3 DP protocol error in Direct-Data-Link-Mapper or User-Interface/User. Could be a hardware defect. 80B0 * SFC not possible for module type * Data record unknown to module * Data record number 241 is not allowed. * Data records 0 and 1 are not permitted for SFB 52/53 "WR_REC." 80B1 The length specified in the RECORD parameter is wrong. 80B2 The configured slot is not occupied. 80B3 Actual module type is not the module type specified in SDB1. 80B7 Incorrect length specified 80C0 * RDREC: The module has record, but it doesn't have any read data. * WRREC: CM is not ready to receive new data - Wait until the cyclic counter has been incremented 80C1 The data of the preceding write job on the module for the same data record have not yet been processed by the module. 80C2 The module is currently processing the maximum possible number of jobs for a CPU. 80C3 Required resources (memory, etc.) are currently in use. This error is not reported by FB 45. If this error occurs, FB 45 waits until the system is able to provide resources again. FB 45 for MOBY U, MOBY D, RF200, RF300 56 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Error messages and troubleshooting 5.2 Error messages Error code Description (W#16#...) 80C4 80C5 Communication error * Parity error * SW ready not set * Error in block length management * Checksum error on CPU side * Checksum error on module side Distributed I/O not available FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 57 Error messages and troubleshooting 5.2 Error messages FB 45 for MOBY U, MOBY D, RF200, RF300 58 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 6 Examples/applications 6.1 FB 45 scanning by user Scanning of FB 45 takes place in accordance with the structogram in the following figure. 5HVWDUW6HWWLQJLQLWBUXQ 2% &\FOLFTXHU\6HWFRPPDQGBVWDUW VWDUWFRPPDQG RQO\LIUHDG\ UHDG\ " - 1 HUURU " - 3RVVLEO\ WLPHRXWPRQLWRULQJ E\WKHXVHU H[HFXWHLQLWBUXQLI WLPHRXW 1 $1=BUHVHWVHW " 1 (UURU KDQGOLQJ HYDOXDWLRQ RI HUURUB02%< HUURUB)% DQG HUURUB%86 &RPPDQG2. 3URFHVV GDWD - +HUHWKHUHZDV QR FRPPXQLFDWLRQ ZLWKWKH WUDQVSRQGHU &RPPDQG2. 6HWFRPPDQGBVWDUW 6WDUWQH[WFRPPDQGLIUHTXLUHG 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 59 Examples/applications 6.2 Processing of data memories/transponders 6.2 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 RAM, 16 bytes OTP MOBY U e.g. MDS U315 32 KB RAM, 16 bytes OTP MOBY U e.g. MDS U525 44 bytes EEPROM MOBY D e.g. MDS D139/ I-Code 1 112 bytes EEPROM MOBY D, RF200, RF300 I-Code SLI / MDS D1xx 256 bytes EEPROM MOBY D, RF200, RF300 Tag-it HF-I/MDS D2xx 992 bytes EEPROM MOBY D, RF200, RF300 MDS D3xx 2000 bytes FRAM MOBY D, RF200, RF300 MDS D4xx 20 bytes EEPROM RF300 RF320T 8 KB FRAM RF300 e.g. RF340T 32 KB FRAM RF300 e.g. RF350T 64 KB FRAM RF300 e.g. RF370T (64 K) Addressing The data memories are addressed linearly from address 0000 (or the specified start address) to the end address. The CM or reader automatically recognizes the size of the memory on the transponder. If the end address on the transponder is exceeded, an error message is indicated in error_MOBY. The next table shows the address space of the individual tag versions. The address_MDS and length variables (see Table "UDT 20 MOBY CMD" in section "RFID commands (Page 29)") must be configured according to this address space. FB 45 for MOBY U, MOBY D, RF200, RF300 60 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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 RF200, RF300, Start address MOBY D End address 16-bit hexadecimal number Integer number MDS D139 (I-Code 1; 44 bytes) 0000 +0 002B +43 ID no.: (fixed-coded; can only be read as a whole) Start address Length FFF0 -16 0008 +8 ISO-MDS (I-Code SLI; 112 bytes) Start address 0000 +0 End address 006F +111 ID no.: (fixed-coded; can only be read as a whole) Start address FFF0 -16 Length 0008 +8 ISO MDS (Tag-it HF-I; 256 bytes) Start address 0000 +0 End address 00FF +255 ID no.: (fixed-coded; can only be read as a whole) Start address Length FFF0 -16 0008 +8 ISO MDS (my-d SRF55V10P; 992 bytes) Start address 0000 +0 End address 03DF +991 ID no.: (fixed-coded; can only be read as a whole) Start address FFF0 -16 Length 0008 +8 ISO-MDS (MB 89R118B, 2000 bytes) Start address 0000 +0 End address 07CF +1999 ID no.: (fixed-coded; can only be read as a whole) Start address FFF0 -16 Length 0008 +8 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 61 Examples/applications 6.2 Processing of data memories/transponders Address space of the transponder versions for RF300 System Addressing RF300 16-bit hexadecimal number Integer number 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 -256 End address FF13 -237 ID no.: (fixed-coded; can only be output as a whole) Start address Length FFF0 -16 0008 +8 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 -256 End address FF13 -237 Start address 0000 +0 End address 1FFC +8188 R/W memory (FRAM) ID no.: (fixed-coded, can only be read as a whole) Start address Length FFF0 -16 0008 +8 32 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 -256 End address FF13 -237 0000 +0 7FFC +32764 R/W memory (FRAM) Start address End address ID no.: (fixed-coded; can only be output as a whole) Start address Length FFF0 -16 0008 +8 64 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 -256 End address FF13 -237 R/W memory (FRAM) FB 45 for MOBY U, MOBY D, RF200, RF300 62 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Examples/applications 6.2 Processing of data memories/transponders System Addressing 16-bit hexadecimal number Integer number 0000 +0 FEFC - Start address End address ID no.: (fixed-coded; can only be output as a whole) Start address FFF0 -16 Length 0008 +8 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. This memory area is called OTP. Five block addresses are available for activating the OTP function: FF80, FF84, FF88, FF8C and FF90 A write command to this block address with a valid length (4, 8, 12, 16, 20 depending on the block address) protects the written data from subsequent overwriting. NOTICE OTP writing/locking should only be used in static operation. NOTICE Use of the OTP area is not reversible. If you use the OPT area, you cannot undo it, because the OPT area can only be written to once. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 63 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. R/W EEPROM Write RF300 OTP once Address Length Address Length FF00 1 .. 20 FF80 4,8,12,16,20 FF01 1 .. 19 FF02 1 .. 18 FF84 4,8,12,16 FF88 4,8,12 FF8C 4,8 FF90 4 FF03 1 .. 17 FF04 1 .. 16 FF05 1 .. 15 FF06 1 .. 14 FF07 1 .. 13 FF08 1 .. 12 FF09 1 .. 11 FF0A 1 .. 10 FF0B 1 .. 9 FF0C 1 .. 8 FF0D 1 .. 7 FF0E 1 .. 6 FF0F 1 .. 5 FF10 1 .. 4 FF11 1 .. 3 FF12 1 .. 2 FF13 1 NOTICE Write access to addresses starting at FF80 to FF93 activates the write protection (OTP function) on the EEPROM user memory. This operation is not reversible. Switching on write protection must always take place in ascending order without gaps, starting at address FF80. FB 45 for MOBY U, MOBY D, RF200, RF300 64 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Examples/applications 6.2 Processing of data memories/transponders Address space of the transponder/MDS variants for MOBY U System Addressing MOBY U 16-bit hexadecimal number Integer number 2 KB data memory Start address 0000 +0 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. the start address must always be specified with value FFF0 hex and the length with value 10 hex.) Start address Length FFF0 -16 10 +16 ID no.: (4 fixed-coded bytes; can only be read with the MDS status command) 32 KB data memory Start address 0000 +0 End address 7FFF +32767 Read OTP memory (write access only possible once)* Start address Length FFF0 -16 10 +16 ID no.: (4 fixed-coded bytes; can only be read with the MDS status command) FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 65 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. The last 16 bytes of the MDS address can be used as an OTP data area: R/W EEPROM MDS D1xx MDS D2xx Write ISO OTP once MDS D3xx MDS D4xx Start address (hex) Length Start address (hex) Length Start address (hex) Length Start address (hex) Length Start address (hex) Length Length with MDS D4x x 0060 1...16 00F0 1...16 03D0 1...16 07C0 1...16 FF80 4, 8, 12, 16 8, 16 0064 1...12 00F4 1...12 03D4 1...12 07C4 1...12 FF84 4, 8, 12 - 0068 1...8 00F8 1...8 03D8 1...8 07C8 1...8 FF88 4, 8 8 006C 1...4 00FC 1...4 03DC 1...4 07CC 1...4 FF8C 4 - NOTICE Write access to addresses starting at FF80 to FF8F activates the write protection (OTP function) on the EEPROM user memory. This operation is not reversible. Note With the RF2xx readers and MOBY D, the OTP memory remains readable. Writing via the address FF80, on the other hand, is not possible. FB 45 for MOBY U, MOBY D, RF200, RF300 66 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Examples/applications 6.3 Cyclic calling of FB 45 (e.g. in OB 1) 6.3 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)". The parameter settings for the RFID command were made during the definition of the "MOBY DB". Network 1: call FB45 memory bit 1.0 is set: Start MOBY command memory bit 1.1 is set: Start MOBY command memory bit 1.2 is set: Start init_run for memory bit 1.3 is set: Start init_run for memory byte 2: OB1 used as edge triggered CALL "MOBY FB" , "Instance DB K1" Params_DB :=45 Params_ADDR:=0 for 1st reader for 2nd reader 1st reader 2nd reader memory // Call FB 45 for each reader in each cycle CALL "MOBY FB" , "Instance DB K2" Params_DB :=45 Params_ADDR:=50 x01: x02: A FP S JC "Strt_init_run_chn1" M 2.2 "MOBY DB".SLG1.init_run x01 // memory bit init_run for 1st reader UN JC A JC "MOBY DB".SLG1.ready x01 "MOBY DB".SLG1.error x01 A FP S "Strt_cmd_chn1" M 2.0 "MOBY DB".SLG1.command_start // memory bit command_start for 1st reader A FP S JC "Strt_init_run_chn2" M 2.3 "MOBY DB".SLG2.init_run x02 // memory bit init_run for 2nd reader UN JC A JC "MOBY DB".SLG2.ready x02 "MOBY DB".SLG2.error x02 A FP S "Strt_cmd_chn2" M 2.1 "MOBY DB".SLG2.command_start NOP 0 // memory bit command_start for 2nd reader FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 67 Examples/applications 6.4 Programming a cold and warm restart 6.4 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 switching on the SIMATIC (OB 100) turning on the power supply of the CM plugging the reader onto the CM an interruption in PROFIBUS communication an error message in variable "error_BUS" OB100: "Complete restart" Network 1: set init_run bit for all channels that are configured in DB45 SET S S "MOBY DB".SLG1.init_run "MOBY DB".SLG2.init_run In a distributed configuration of a CM (e.g. via PROFIBUS), it is possible that the CM is switched off and on again as a result of the system(see section Programming a module failure (Page 68)). When this happens, the CM signals the power failure to FB 45 (and so to the user). The user must then send an init_run for this CM before an RFID command can be started again. Note: The "init_run" variable is set to TRUE in the project supplied with the system. This automatically triggers an "init_run" whenever the parameter data block is downloaded onto the PLC (see Table "INPUT parameters" in Section "INPUT parameters"). 6.5 Programming a module failure The failure of a PROFIBUS/PROFINET module can be detected primarily using PROFIBUS/PROFINET system diagnostics. However, if a failed slave is addressed via FB 45, an I/O access error is generated in SIMATIC. As a result OB 122 is called. the PLC changes to STOP if OB 122 is not programmed. FB 45 for MOBY U, MOBY D, RF200, RF300 68 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. OB122: "Module Access Error" Network 1: Reset channel 1 when error occurs x1: L L -D SRW L +D #OB122_MEM_ADDR "MOBY DB".SLG1.ASM_address // Temporary OB 122 variable 1 1 // Formula: // (#OB122_MEM_ADDR SLG[x].ASM_address) / 2 + 1 L ==I JCN SET S "MOBY DB".SLG1.ASM_channel // Compare with conf. channel NOP 0 x1 "MOBY DB".SLG1.ASM_failure // Power failure on ASM Network 2: Reset channel 2 when error occurs x2: L L -D SRW L +D #OB122_MEM_ADDR "MOBY DB".SLG2.ASM_address // Temporary OB 122 variable 1 1 // Formula: // (#OB122_MEM_ADDR SLG[x].ASM_address) / 2 + 1 L ==I JCN SET S "MOBY DB".SLG2.ASM_channel // Compare with conf. channel NOP 0 x2 "MOBY DB".SLG2.ASM_failure // Power failure on ASM OB 86 must also be available on the automation system in addition to OB 122 to prevent the system from switching to STOP if a PROFIBUS slave fails. No code needs to be programmed in OB 86 for the correct operation of FB 45. After the error on the CM has been corrected and the CM is ready for operation again, the user needs to start an init_run for FB 45. The CM is then ready for operation. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 69 Examples/applications 6.6 Data structure definition 6.6 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. The declaration view is shown. Block: DB45; MOBY DB Address 0.0 Name Type STRUCT +0.0 Reader ARRAY [1..4] *50.0 UDT10 =200.0 END_STRUCT Initial value Comment Block: DB47; Command Address 0.0 Name Type STRUCT +0.0 Command ARRAY [1..4] *10.0 UDT20 =40.0 END_STRUCT Initial value Comment Block: DB48; Data Address 0.0 +0.0 Name Type Initial value Comment STRUCT Data ARRAY [1..1024] *1.0 BYTE =1024.0 END_STRUCT When the data blocks have been defined, the "Actual value" of the data must be edited using the "View" > "Data View" menu. FB 45 for MOBY U, MOBY D, RF200, RF300 70 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. 'HFODUDWLRQYLHZ '% 'DWDYLHZ VFKHPDWLF 02%<B'% 6758&7 FKDQQHO$55$<>@ 8'7 6758&7 FRPPDQG$55$<>@ 8'7 (1'B6758&7 (1'B6758&7 &KDQQHO>@ &KDQQHO>@ &KDQQHO>@ FRPPDQGBVWDUW LQLWBUXQ FRPPDQGB'%BQXPEHU FRPPDQGB'%BDGGUHVV UHDG\ HUURU 7KH5),'FRQWURO SDUDPHWHUVDQGWKHFRPPDQGV DVVRFLDWHGZLWKHDFKFKDQQHO DUHDOODYDLODEOHLQ DGDWDEORFNIRUDOO5),' FKDQQHOV &KDQQHO>@ FRPPDQG>@ &KDQQHO>@ FRPPDQG>@ FRPPDQG DGGUHVVB0'6 OHQJWK '$7B'%BQXPEHU '$7B'%BDGGUHVV Figure 6-2 Example of when several RFID commands are assigned to one channel FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 71 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: A AN A AN S S AN R MOBY DB.channel[1].ready // 1st READER MOBY DB.channel[1].error I 0.0 Edgememorybit_1 MOBY DB.channel[1].command_start Edgememorybit_1 I 0.0 Edgememorybit_1 A AN A AN S S AN R MOBY DB.channel[2].ready // 2nd READER MOBY DB.channel[2].error I 0.1 Edgememorybit_2 MOBY DB.channel[2].command_start Edgememorybit_2 I 0.1 Edgememorybit_2 A AN A AN S S AN R MOBY DB.channel[3].ready // 3rd READER MOBY DB.channel[3].error I 0.3 Edgememorybit_3 MOBY DB.channel[3].command_start Edgememorybit_3 I 0.3 Edgememorybit_3 Call "MOBY FB", DB100 Params_DB: = 45 Params_ADDR: = 0 Call "MOBY FB", DB101 Params_DB: = 45 Params_ADDR: = 70 Call "MOBY FB", DB102 Params_DB: = 45 Params_ADDR: = 140 FB 45 for MOBY U, MOBY D, RF200, RF300 72 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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" UDT 10 STRUCT command: ARRAY [1...10] UDT 20 DB 46: "Reader 2" UDT 10 STRUCT command: ARRAY [1...10] UDT 20 Reader 3 Ad 0 : Ad : : 0 : : : : 49 : : : 49 50 : : : : : 59 DB 47: "Reader 3" UDT 10 STRUCT command: ARRAY [1...10] UDT 20 Figure 6-3 60 61 62 : : : : 10 50 : : : : : 59 60 61 62 : : : : 10 Reader 2 Reader 1 Ad Na 0 ASM_add : : : : : 49 50 Befehl1. : : command : : : 59 60 Daten [1] 61 62 Daten [2] : : Daten [3] : : 10 Example of when a separate data block is assigned to each RFID channel FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 73 Examples/applications 6.7 The UDTs of FB 45 / FC 45 6.7 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. Table 6- 2 UDT overview table UDT Description Described in English German Spanish 10 11 14 Parameter data block Section "Parameter data block (Page 19)" 20 21 24 RFID commands Section "RFID commands (Page 29)" 60 61 64 Parameter data block for transponder > 32 KB Section "Parameter data block (Page 19)" 70 71 74 RFID commands for transponder > 32 KB Section "RFID commands (Page 29)" 100 101 104 Result of transponder status 110 111 114 Result of reader status (sub_command = 01) Section "The UDTs of FB 45 / FC 45 (Page 74)" 120 121 124 Result of reader diagnostics I (sub_command = 02) 130 131 134 Result of reader diagnostics II (sub_command = 03) 140 141 144 Result of reader diagnostics III (sub_command = 04) 230 231 234 Result of transponder status (sub_command = 03, RF300) 260 261 264 Result of transponder status (sub_command = 01, RF300) 270 271 274 Result of transponder status (sub_command = 02, RF300) 280 281 284 Result of reader status (sub_command = 06, RF300) Sample project on software DVD FB 45 for MOBY U, MOBY D, RF200, RF300 74 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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 0.0 Name Type STRUCT Comment +0.0 +4.0 +6.0 +10.0 +12.0 +13.0 +14.0 +16.0 =18.0 UID MDS_type sum_subframe_access sum_searchmode_access ST_date_Week ST_date_Year battery_left ST DWORD BYTE DINT INT BYTE BYTE INT BYTE END_STRUCT Tag (unique identifier) Tag Sum of subframe access Sum of searchmode Date of last sleep-time change (week of year) Date of last sleep-time change (year) Battery left (percentage) Set Sleep_time value on tag UDT 111: Result of reader status (mode 1) Table 6- 4 UDT 111 "MOBY SLG Status" Address 0.0 Name Type STRUCT Comment +0.0 +1.0 +2.0 +4.0 +6.0 +8.0 +10.0 +12.0 +14.0 +15.0 +16.0 +17.0 +18.0 +19.0 status_info hardware hardware_version loader_version firmware firmware_version driver driver_version interface baud reserved1 reserved2 reserved3 distance_limiting_SLG BYTE CHAR WORD WORD CHAR WORD CHAR WORD BYTE BYTE BYTE BYTE BYTE BYTE +20.0 +21.0 multitag_SLG field_ON_control_SLG BYTE BYTE +22.0 field_ON_time_SLG BYTE +23.0 sync_SLG BYTE +24.0 +25.0 status_ant stand_by BYTE BYTE +26.0 =28.0 MDS_control BYTE END_STRUCT Reader mode Type of hardware HW version Version of loader FW Firmware version Type of driver Version of driver Interface (RS 232/RS 422) Baud rate Reserved Reserved Reserved Ranges/performance setting (RF200/RF300: res.) Multitag reader BERO operating mode (RF200/RF300: res.) MOBY U: BERO time MOBY D: transponder type ((RF200/RF300: ISO transponder type) Semaphore control (synchronization with reader) (RF200/RF300: res.) Status of antenna Standby time after a command was executed (RF200/RF300: res.) Presence FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 75 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 0.0 Name Type STRUCT Comment +0.0 +1.0 +2.0 +3.0 +4.0 . . . =234.0 status_info number_functions function_01_01 function_01_02 function_01_03 . . . BYTE BYTE BYTE BYTE BYTE Reader status mode Range: 1...33 * * * END_STRUCT *) An area of 7 bytes each is reserved for 33 commands. UDT 131: Result of reader diagnostics II Table 6- 6 UDT 131 "MOBY SLG-Stat Diag 2" Address 0.0 Name Type STRUCT Comment +0.0 +1.0 +2.0 *1.0 status_info number_errors error_number BYTE BYTE ARRAY [1...235] BYTE Reader status mode Range: 1...235 Error that occurred on the reader =238.0 END_STRUCT UDT 141: Result of reader diagnostics III Table 6- 7 UDT 141 "MOBY SLG-Stat Diag 3" Address 0.0 Name Type STRUCT Comment +0.0 +1.0 +2.0 *4.0 status_info number_MDS UID BYTE BYTE ARRAY [1...24] DWORD Reader status mode Range: 1...24 identified UID (tag number) =98.0 END_STRUCT FB 45 for MOBY U, MOBY D, RF200, RF300 76 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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 0.0 Name Type STRUCT +0.0 reserved0 BYTE +1.0 +2.0 status_info UID BYTE ARRAY[1...1] *0.0 +0.0 +4.0 Tag status mode STRUCT Byte_1_4 Byte_5_8 =8.0 +10.0 +11.0 +12.0 +14.0 +15.0 +16.0 =18.0 Comment DWORD DWORD Tag number (unique identifier) END_STRUCT MDS_type IC_version Size lock_state block_size nr_of_blocks BYTE BYTE WORD BYTE BYTE BYTE END_STRUCT Tag type Chip version (for my-d = 00h) Memory size in bytes Size of the user memory EEPROM write-protection status Number of blocks in user memory UDT 261: Result of MDS status (mode 1, RF300) Table 6- 9 UDT 261 "MDS status (mode 1, RF300)" Address 0.0 Name Type STRUCT +0.0 reserved0 BYTE +1.0 +2.0 status_info UID BYTE ARRAY[1...1] *0.0 +0.0 +4.0 Tag status mode STRUCT Byte_1_4 Byte_5_8 =8.0 +10.0 +11.0 Comment DWORD DWORD Tag number (unique identifier) END_STRUCT MDS_type Lock_state BYTE BYTE Tag type EEPROM write protection status %LW 1RWXVHG %ORFN )))) %ORFN ))&))) %ORFN ))))% %ORFN )))) %ORFN )))) :ULWHSURWHFWLRQVWDWXV EORFNLVQRWSURWHFWHG UZ EORFNLVZULWHSURWHFWHG UR FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 77 Examples/applications 6.7 The UDTs of FB 45 / FC 45 Address +12.0 Name reserved1 Type ARRAY[1...6] *1.0 BYTE =18.0 END_STRUCT Comment UDT 271: Result of MDS status (mode 2, RF300) Table 6- 10 UDT 271: "MDS status (mode 2, RF300)" Address 0.0 Name Type STRUCT +0.0 reserved0 BYTE +1.0 +2.0 status_info UID BYTE ARRAY[1...1] *0.0 +0.0 +4.0 Comment Tag status mode STRUCT Byte_1_4 Byte_5_8 +8.0 DWORD DWORD Tag number (unique identifier) END_STRUCT +10.0 LFD BYTE +11.0 FZP BYTE +12.0 FZA BYTE +13.0 +14.0 ANWZ reserved1 BYTE ARRAY[1...3] *0.0 BYTE =18.0 END_STRUCT Power flux density: Relationship between the limit value and measured value Error counter, passive (errors during idle time) Error counter, active (errors during communication) Presence counter UDT 281: Result of read/write status (mode 6, RF300) Table 6- 11 UDT 281 "Reader status (mode 6, RF300)" Address 0.0 Name Type STRUCT Comment +0.0 +1.0 +2.0 +3.0 +4.0 +5.0 +6.0 +7.0 +8.0 to +26.0 =28.0 status_info FZP ABZ CFZ SFZ CRCFZ BSTAT ASMFZ res. BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE Reader status mode Error counter, passive (errors during idle time) Abort counter Code error counter Signature error counter CRC error counter Current command status Interface error counter for CM Reserved END_STRUCT FB 45 for MOBY U, MOBY D, RF200, RF300 78 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Examples/applications 6.8 Determing the memory requirement in the SIMATIC 6.8 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: SIMATIC S7 with small memory configuration Processing of a large number of RFID channels (readers) on an S7 Processing of large volumes of data on each Ident channel The example below shows a configuration for the S7 memory required by FB 45. 20 readers with 1 KB tag data each are to be processed: Memory Requirements [KB] per channel FB 45 (needed once) Instance DB Total - ~8 0,45 9,1 Parameter data block (UDT 10) 0,1 2 Command data block (UDT 20) 0,01 0,2 1 20 1,56 39,2 DB for tag data Total In this configuration, a SIMATIC CPU with only 48 KB memory can reach the memory limits quickly if further programs are also running. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 79 Examples/applications 6.8 Determing the memory requirement in the SIMATIC FB 45 for MOBY U, MOBY D, RF200, RF300 80 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 A 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. A.1 RF170C Area of application The RF170C communication module is a SIMATIC S7 module. It can be plugged into the ET 200pro distributed I/O station. The ET 200pro is operated by the user over PROFIBUS DP V1 or PROFINET IO. An S7-300 or S7-400 with integrated PROFIBUS/PROFINET connection can be used as the controller. 352),%86'3 PDVWHUPRGXOH HJ6&38 7UDQVSRQGHU 352),%86352),1(7 FDEOHWRDOO 352),%86352),1(7 VODYHV 5HDGHU ,QWHUIDFHPRGXOH RIWKH(7SUR 5)& 9IRU5)& DQGUHDGHU Figure A-1 Configurator for an RF170C Hardware configuration The RF170C is integrated into the hardware configuration of the SIMATIC Manager preferably via the Object Manager. The object manager is available on the DVD "RFID Systems Software & Documentation" (6GT2080-2AA20) as "SETUP.exe". The object manager provides the functions for PROFIBUS DP and PROFINET IO. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 81 Brief description of the hardware A.1 RF170C Integration into the PROFIBUS master is carried out by means of a GSD file: SIEM8118.GSD for ET 200pro with IM 154-1 SIEM8119.GSD for ET 200pro with IM 154-2 High Feature The GSD file can be optionally incorporated into HW Config of the SIMATIC Manager using the function "Options > Install new GSD...". You will find the file under Support and ET 200pro. 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 Parameter setting by means of GSD file In addition to the PROFIBUS-relevant control parameters, several RFID-relevant control parameters are also defined for the RF170C in the GSD file. The RFID-relevant parameters are set using the object properties of the slave in HW Config. You will find a description of the parameters in the section "Parameterizing (Page 19)". The table below shows the possible settings: Table A- 1 Setting of RFID-relevant parameters Parameter name USER_Mode MOBY_Mode Baud rate reader Diagnostics with diagnostics messages 1) Value Note FB 45 / FC 45 Default FB 55 / FC 55 - FB 56 / FC 56 - RFID standard profile Available soon MOBY I, E normal addressing Default MOBY I filehandler only with FB 56/FC 56 MOBY U, D / RF300 standard addressing (also applies to RF200) MOBY U filehandler only with FB 56/FC 56 (multitag) 19.2 kBd MOBY U/D / RF200 / RF300 57.6 kBd MOBY U/D / RF200 / RF300 1) 115.2 kBd MOBY U/D / RF200 / RF300 1) None Standard diagnostics only Hard errors Hardware-related messages only Not permitted with MOBY D with SLG D11S/D12S Input parameters for RF170C with FB 45/FC 45 Assignment is made in UDT 10. You will find the list of the input parameters for RF170C in the section "Parameter data block (Page 19)". FB 45 for MOBY U, MOBY D, RF200, RF300 82 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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)". Table A- 2 Number of buffers for intermediate storage No. of buffers per channel Maximum amount of data for intermediate storage Number of buffers for intermediate storage of commands and results 150 34 950 bytes Diagnostics using LEDs The figure below shows the layout of the LED display of the RF170C connection module: Figure A-2 LED display on the RF170C communication module Table A- 3 Status and error LEDs for RF170C LEDs SF Meaning Group error ACT_1, ACT_2 The corresponding reader is active in processing a user command. ERR_1, ERR_2 A flashing pattern indicates the last error to occur (see section "Error messages (Page 47)"). PRE_1, PRE_2 * RxD_1, RxD_2 Indicates the presence of a transponder. Indicates live communication with the reader. May also indicate malfunctions on the reader. * In multitag operation, this LED uses a flashing interval to indicate the number of data carriers currently within the range of the reader. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 83 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: SF PRE_1 ERR_1 ACT_1 PRE_2 ERR_2 ACT_2 Off Off Off On On Off On Off On Off Off On On On Off Description Off Off Off Start-up active Off Off Off Checksum error at start-up * Off Off On Off Firmware invalid * On On On On On LED test for approximately 4 seconds; otherwise firmware fault * On On Off On On Checksum error at start-up * On On On On Off On On Checksum error of the firmware * On Off On On On On On External RAM defective * On On Off On On On On ESSA3 defective * On Off On On On Off On ID error firmware * - Off 1 x flash every 3 s Off Off 1 x flash every 3 s Off RF170C successfully started up, waiting for reset command - - n x flash every 3 s - - m x flash every 3 s - The number of flashes (n, m) indicates the last reported error on a given channel. - - Flashing Rapid flashing - Flashing Rapid flashing Firmware update; alternate flashing of the error LEDs at approximately 1 Hz - = not relevant * If this error recurs, the module is defective and must be replaced. Interfaces of the RF170C Table A- 4 Pin assignment of the interfaces of the RF170C X1, X2: Connector for reader Pin Signal 1 2 3 4 5 6 7 8 +24 V -RxD 0V RxD TxD -TxD free PE / shield Pre-assembled reader connecting cables are available for the RF170C. The appropriate cable and M12 connectors are available for users who want to assemble their own SIMATIC RFID cables. FB 45 for MOBY U, MOBY D, RF200, RF300 84 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Brief description of the hardware A.2 RF180C A.2 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. The user can start a command on 2 readers simultaneously (FB 45 when operating on a SIMATIC S7). &RQWUROOHU HJ6&38 7UDQVSRQGHU 5HDGHU 352),1(7,2FDEOH 5)& ; ; 9IRU5)& DQGUHDGHU Figure A-3 WRIXUWKHU 352),1(7,2QRGHV Configurator for RF180C Hardware configuration The RF180C is integrated into the hardware configuration by means of a GSDML file. The RF180C can then be configured using HW Config of the SIMATIC manager or another PROFINET tool. The GSDML file can be found on the "RFID Systems Software & Documentation" DVD or on the Internet (see section "Service & Support (Page 121)"). GSDML-V2.2-SIEMENS-RF180C-date in format "yyyymmdd.xml" The RF180C must have a valid IO device name. The default device name is RF180C Parameter setting by means of GSDML file The GSDML file contains four parameters relevant to RFID that must be set. They are set by selecting the "Object properties" for slot 0 of the RF180C in HW Config. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 85 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 USER_Mode MOBY_Mode Baud rate reader Diagnostics with diagnostics messages 1) Value Note FB 45 Default FB 55 for multitag applications FB 56 With later firmware version RFID standard profile With later firmware version MOBY I / E standard addressing - MOBY I filehandler reserved MOBY U/D / RF300 / RF600 standard addressing Default (also applies to RF200) MOBY U filehandler With later firmware version RF300 Filehandler - 19.2 kBd MOBY U/D / RF200 / RF300 57.6 kBd MOBY U/D / RF200 / RF300 1) 115.2 kBd MOBY U/D / RF200 / RF300 1) None Standard diagnostics only Hard errors Hardware-related messages only Hard/soft errors low priority All messages Hard/soft errors high priority All messages high-priority Not permitted with MOBY D with SLG D11S/D12S Input parameters for RF180C with FB 45/FC 45 Assignment is made in UDT 10. You will find the list of the input parameters for RF180C in the section "Parameter data block (Page 19)". Table of commands of the RF180C for standard addressing (FB 45) 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)". Table A- 6 Number of buffers for intermediate storage No. of buffers per channel Maximum amount of data for intermediate storage Number of buffers for intermediate storage of commands and results 150 34 950 bytes FB 45 for MOBY U, MOBY D, RF200, RF300 86 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Brief description of the hardware A.2 RF180C Diagnostics using LEDs The following figure shows details of the LEDs of the RF180C. ; $&7B 35(B 5['B (55B 6,0$7,&5)& 6,0$7,&5)& 5HDGHU ; 5HDGHU $&7B 35(B 5['B (55B ; ; *7-' *7-' 6) [ %) 21 '&9 [ /LQN 5;7; [ [ [ [ Figure A-4 Table A- 7 [ [ LEDs of the RF180C Status LEDs for the RF180C LEDs ON 24 V DC Meaning Lights up when the RF180C has completed start-up without errors. Lights up when the 24 V supply voltage is connected to the RF180C. ACT_1, ACT_2 The corresponding reader is active in processing a user command. ERR_1, ERR_2 A flashing pattern indicates the last error to occur (see section "Error messages (Page 47)"). PRE_1, PRE_2 * Indicates the presence of a tag. RxD_1, RxD_2 Indicates live communication with the reader. May also indicate malfunctions on the reader. *) In multitag operation, this LED uses a flashing interval to indicate the number of data carriers currently within the range of the reader. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 87 Brief description of the hardware A.2 RF180C Table A- 8 LED display for PROFINET diagnostics BF SF On - Flashes - Cause of error Error correction * Communication module is in start- When the bus is configured correctly, this state ends a few seconds after switching the module on. up mode. * No cable inserted * There is no connection to the PROFINET IO controller. * Check the PROFINET IO connection. * Check your PROFINET IO configuration (device name, GSDML file). * Reload the configuration into the RF180C (see the Section "Configuration parameters of the RF180C") Analyze the diagnostic data. Off On * A PROFINET diagnostic signal exists. * Off Off * Normal mode - - = Status not relevant Table A- 9 LEDs on connection block Link (green) Tx / Tx (yellow) Meaning Off Off No physical connection over PROFINET IO On Off Physical connection over PROFINET IO, no data communication On Flashes Physical connection over PROFINET IO, with data communication Off On Temporary state following switch-on The table is applicable to both left and right PROFINET IO connection. Other communication module operating modes are indicated by the PRE, ERR, ACT, SF and ON LEDs: Table A- 10 LED display for operating states ON BF SF PRE_1 ERR_1 ERR_2 ACT_2 Off Off Off Off Off ACT_1 PRE_2 Off Off Off Off Start-up active Description On On On On On On On On On LED test on start-up (start PROFINET IO) Off Off On On On Off On On Off Internal fault Off Off On On Off On On Off On Checksum error of the firmware Off Off On Off Slow flashin g Off Off Slow flashin g Off Firmware update (flashes with every described area) FB 45 for MOBY U, MOBY D, RF200, RF300 88 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Brief description of the hardware A.3 ASM 456 A.3 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. 352),%86'3 PDVWHUPRGXOH HJ6&38 7UDQVSRQGHU 5HDGHU 352),%86FDEOH $60 ; ; 9IRU$60 DQGUHDGHU Figure A-5 WRIXUWKHU 352),%86QRGHV ASM 456 configurator FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 89 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". ; 02%<$60 The following figure shows the basic design of the ASM 456. &RQQHFWLRQVRFNHWIRUVWUHDGHU 6WDWXV/('VIRURSHUDWLRQ RIWKHVWUHDGHU &RQQHFWLRQVRFNHWIRUQGUHDGHU ; 6WDWXV/('VIRURSHUDWLRQRIWKHQGUHDGHU 6WDWXV/('VIRULQWHUIDFHPRGXOH *7(' 6SDFHIRUFRQQHFWLRQEORFN 3URWHFWLYHHDUWK Figure A-6 Basic design of the ASM 456 Hardware configuration The ASM 456 is integrated into the hardware configuration of the SIMATIC Manager or into another PROFIBUS Master by means of the GSD file SIEM8114.GSD. The file is incorporated into HW-Config of the SIMATIC Manager using the function "Options - Install new GSD ...". You will find the file on the DVD "RFID Systems Software & Documentation" in the directory "daten\PROFI_GSD\ASM456". For full functionality (diagnostics texts, firmware update), support for GSD revision 5 or higher is required. FB 45 for MOBY U, MOBY D, RF200, RF300 90 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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" of the slave in HW Config. The following table shows the possible settings: Table A- 11 Setting of MOBY-relevant parameters Parameter name USER_Mode MOBY_Mode Baud rate reader Diagnostics with diagnostic messages (see Section "Error messages and troubleshooting" ) 1) Value Note FB 45 / FC 45 Default FB 55 / FC 55 - FB 56 / FC 56 - RFID standard profile dependent on the firmware version MOBY I, E normal addressing Default MOBY I filehandler only with FC 56 MOBY U, D / RF300 standard addressing (also applies to RF200) MOBY U filehandler only with FC 56 (multitag) RF300 Filehandler - 19.2 kBd MOBY U/D / RF200 / RF300 57.6 kBd MOBY U/D / RF200 / RF300 1) 115.2 kBd MOBY U/D / RF200 / RF300 1) None Standard diagnostics only Hard errors Hardware-related messages only Hard/soft errors low priority All messages Hard/soft errors high priority All messages high-priority Not permitted with MOBY D with SLG D11S/D12S Input parameters for ASM 456 Assignment is made in UDT 10. You will find the list of the input parameters for ASM 456 in the section "Parameter data block (Page 19)". Table of commands for ASM 456 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)". FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 91 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 storage of commands and results 150 34 950 bytes Diagnostics using LEDs 02%<$60 The following figure shows details of the LEDs of the ASM 456. ; $&7B 35(B 5HDGHU 5['B (55B $&7B 35(B 5HDGHU 5['B (55B ; 352),%86 *7(' 6) Figure A-7 %) 21 '&9 LEDs of the ASM 456 FB 45 for MOBY U, MOBY D, RF200, RF300 92 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Brief description of the hardware A.3 ASM 456 Table A- 13 Status LEDs for ASM 456 LEDs Meaning ON 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. ACT_1, ACT_2 The corresponding reader is active in processing a user command. ERR_1, ERR_2 A flashing pattern indicates the last error to occur (see section "Error messages (Page 47)"). PRE_1, PRE_2 * RxD_1, RxD_2 Indicates the presence of a tag. Indicates live communication with the reader. May also indicate malfunctions on the reader. *) In multitag operation, this LED uses a flashing interval to indicate the number of data carriers currently within the range of the reader. Table A- 14 LED display for PROFIBUS diagnostics BF SF On - Flashes Flashes On On - Cause of error Error correction * ASM is in start-up mode. - * Connection to DP Master failed. * * ASM not detecting a baud rate Check the PROFIBUS DP connection. * Check the DP Master * Check all cables on your PROFIBUS DP network. * Check whether the connector plugs for the PROFIBUS DP are securely plugged into the ASM. * Check the project for the ASM (input/output, PROFIBUS address). * Correct GSD file being used? * Bus interrupt * DP Master not functioning * The project data sent to the ASM by the DP Master do not match the configuration of the ASM. * ASM has detected the baud rate, but * is not activated by the DP Master. * ASM has not been assigned project plans. Flashe * s Check the PROFIBUS address set in ASM and/or in the project software. * Check the project for the ASM (station type). There is a hardware defect in the ASM. * Replace the ASM. Off On * Diagnostics available * Evaluate the diagnostic information. On Off * The set PROFIBUS address is incorrect or greater than 99. * Set the address in the range 1 to 99 and carry out new start-up. - = Status not relevant Other ASM operating modes are indicated by the PRE, ERR, SF, ACT and ON LEDs: FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 93 Brief description of the hardware A.3 ASM 456 ON SF PRE_1 ERR_1 ACT_1 On Off Off Off On PRE_2 ERR_2 Off Off ACT_2 Off Start-up active Description Off On Off On Off Off Off Off Checksum error at start-up Off On Off Off Off Off On Off Firmware invalid On On On On On On On On LED test for approximately 4 seconds; otherwise firmware fault Off On Off On On Off On On Checksum error at start-up Off On On On On Off On On Checksum error of the firmware Off On On On On On On On External RAM defective Off On On Off On On On On DPC-RAM defective Off On Off On On On On On ID error firmware On - Off 1 x flash every 3 s Off Off 1 x flash every 3 s Off ASM successfully started up, waiting for reset command On - - Flashing Rapid flashing - Flashing Rapid flashing Firmware update; alternate flashing of the error LEDs at approximately 1 Hz - = not relevant Pin assignment Table A- 15 Pin Connection assignment for ECOFAST connector plugs Assignment View of ECOFAST connector plug (wiring end for supply and loop-through connection) A PROFIBUS DP signal A B PROFIBUS DP signal B 1 Electronics / encoder supply (1L+) (voltage supply for ASM 456 and reader) $ Ground for electronics/encoder supply (1M) 2 6LJQDO$ 6LJQDO% % (&2)$67K\EULGFDEOH 3 Load voltage ground (2M) / 4 Load voltage supply (2L+) (unused on ASM 456) / *) You will find the assembly instructions in the packaging of the Han Brid Cu cable connector and/or Han Brid Cu cable socket. FB 45 for MOBY U, MOBY D, RF200, RF300 94 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Brief description of the hardware A.3 ASM 456 Table A- 16 Connection assignment for M12 connector (PROFIBUS DP) Pin Assignment 1 Supply positive (P5V2) * 2 Data line A (RxD / TxD-N) 3 Data reference potential (M5V2) * 4 Data line B (RxD / TxD-P) 5 Shield Thread View of M12 connector (wiring side) 6XSSO\'3 6LJQDO$ JUHHQ Shield 6KLHOG 6LJQDO% UHG /RRSWKURXJK FRQQHFWLRQ'3 %XVFDEOH FRUHVKLHOGHG 6LJQDO$ JUHHQ 6KLHOG 6LJQDO% UHG *) Can only be used for the M12 terminating resistor. Looping the voltage through to the next connector via a 5-core cable is not permitted. Table A- 17 Pin assignment for 7/8" connector (supply voltages) Pin Assignment 1 Load voltage ground (2M) 2 Ground for electronics/encoder supply (1M) 3 PE 4 Electronics / encoder supply (1L+) (voltage supply for ASM 456 and reader) 5 Load voltage supply (2L+) (unused on ASM 456) View of 7/8" connector (wiring side) 6XSSO\; / / /RRSWKURXJK FRQQHFWLRQ; FRUHFDEOH / / FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 95 Brief description of the hardware A.4 ASM 475 A.4 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. 352),%86'3PDVWHU PRGXOH HJ6ZLWK$60 $60 7UDQVSRQGHU 5HDGHU 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" in the directory "daten\S7_OM" on the DVD "RFID Systems, Software & Documentation". The integration of the ASM 475 in the third-party master is possible via the distributed I/O with an ET 200M. To do this, use the GSD file of the relevant ET 200 M head module. Note that the ASM 475 cannot be integrated in all head modules. You will find more information on this in the GSD file under the term "ASM 475". Reader connection system Pre-assembled reader connecting cables are available in various lengths for the ASM 475. At the open end to the ASM, the wires are marked with the connector numbers of the front plug. Please make sure that when you connect it up, the cable shield makes contact with the shield connection element. Input parameters for ASM 475 Assignment is made in UDT 10. You will find the list of the input parameters for ASM 475 in the section "Parameter data block (Page 19)". Table of commands for ASM 475 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)". Table A- 18 Number of buffers for intermediate storage No. of buffers per channel Maximum amount of data for intermediate storage Number of buffers for intermediate storage of commands and results 70 16 310 bytes FB 45 for MOBY U, MOBY D, RF200, RF300 96 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. SF DC5 V ACT_1 ERR_1 PRE_1 RxD_1 T+ R+ R- T+ TR+ R- ACT_2 ERR_2 PRE_2 RxD_2 Reader 1 T- Reader 2 MOBY ASM475 4 56 6GT2 002-0GA10 Status and error LEDs Table A- 19 Reader connector diagram The numbers for the connector relate to connector X1 of the top part of the housing Status LEDs for ASM 475 LEDs SF 5 V DC Meaning System fault (hardware error on ASM) Is lit when the 24 V supply voltage is connected to the ASM and the 5 V voltage on the ASM is OK. ACT_1, ACT_2 The corresponding reader is processing an application command. ERR_1, ERR_2 A flashing pattern indicates the last error to occur (see section "Error messages (Page 47)"). This display can be reset with the option_1 parameter (see section "INPUT parameters (Page 21)"). PRE_1, PRE_2 Indicates the application of a tag. RxD_1, RxD_2 Indicates live communication with the reader. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 97 Brief description of the hardware A.4 ASM 475 The following ASM states are indicated with the LEDs PRE, ERR and SF. SF PRE_1 ERR_1 ON OFF/ON ON (perm.) OFF/ON PRE_2 ERR_2 Description, Causes, Remedy ON OFF ON OFF OFF Loader is defective (can only be fixed at the plant). OFF 2 Hz OFF 2 Hz OFF Firmware loading process is active and/or no firmware detected load firmware do not switch off ASM during this process OFF 2 Hz 2 Hz 2 Hz 2 Hz Loading of firmware aborted due to error restart needed reload firmware check update files any 5 Hz 5 Hz 5 Hz 5 Hz Operating system error switch ASM off/on OFF OFF 1x flash every 2 s OFF 1x flash every 2 s ASM has booted and is waiting for a RESET (init_run) from the user. ON (perm.) Hardware is defective (RAM, Flash, ...) FB 45 for MOBY U, MOBY D, RF200, RF300 98 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.1 B 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. Note Some signals in this appendix have the same meaning as the variables in section "Parameter data block (Page 19)". In order to distinguish between them, an underscore "_" is appended to the relevant signals (e.g. ANZ_MDS_present_). FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 99 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. 352),%86352), 1(7PDVWHUPRGXOH 352),%86352),1(7 $60 5)& $60 5)& IXUWKHUILHOGGHYLFHV Cyclic communication via PROFIBUS/PROFINET. Status information is exchanged (see section "Cyclic control word between master and communications module (Page 102)" and "Methods of operation with the communications module (Page 105)"). Acyclic communication via PROFIBUS/PROFINET. Commands and acknowledgements are exchanged (see section "Command and acknowledgement telegrams (Page 109)"). The master may only send new commands to the slave (communications module) when the CM is ready. Status information is used in cyclic communication to indicate that the communications module is ready. The same applies to acknowledgments. The communications module may only fetch new acknowledgments when a new acknowledgment is actually waiting (i.e. has not yet been read). This information is also indicated by status information. Two condition codes are defined in the status information. Based on these, the PROFIBUS/PROFINET master can recognize whether an acylic frame can be sent to or from the communications module. FB 45 for MOBY U, MOBY D, RF200, RF300 100 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.1 Programming the communication modules on PROFIBUS/PROFINET Principle of controlling non-cyclic communication with command and acknowledgment counter &RPPDQGFRXQWHU $FNQRZOHGJHPHQWFRXQWHU &0 DFWLYH DF\FOIUDPH DF\FOIUDPH &RPPDQG UHDG\ &RPPDQG UHDG\ &0 DFWLYH DF\FOIUDPH DF\FOIUDPH &0 DFWLYH DF\FOIUDPH &RPPDQG UHDG\ DF\FOIUDPH &0 DFWLYH &RPPDQG UHDG\ DF\FOIUDPH DF\FOIUDPH 6WDWXVRIFRXQWHUVDIWHU&0VWDUWXSRUDIWHUDQLQLWBUXQB 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. A new acyclic frame is not permitted until the next status is reached. An acyclic frame is either a command to the CM or an acknowledgment from it. For this reason, it is important to inform the master whether a new acyclic frame can be executed. Each state is coded in 2 bits and counted up (as shown in the diagram above) The terms status buts or status counters are also used. The status bits are transferred cyclically via PROFIBUS DP or PROFINET IO to the master. The user must evaluate the bits in his program. When the state bit changes, a new state (new state = old state + 1) is created. Only now can the next acyclic frame be sent. Two states must be coded. 1. Command status (command counter) to indicate to the user whether a new/next command may be transferred to the CM. 2. Acknowledgment status (acknowledgment counter) to indicate to the user whether a new acknowledgment from the CM is pending. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 101 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. Both the command and the acknowledgment state are coded in 2 bits each. The two statuses are stored in one byte. B.2 Cyclic control word between master and communications module The cyclic control word is used to synchronize frame traffic between master (FB/FC) and slave (communications module). The actual acyclic command and acknowledgment frame may not be started until this is indicated by the cyclic byte of the communications module in the command or acknowledgment counter. Cyclic word to communications module: I/O output 5HVHUYHG LQLWBUXQB 6WDUWXSRI352),%86352),1(7 PDVWHU 7KLVELWIRUFHVD&0 VWDUWXS%LWLVWKHQVHWLQWKH SHULSKHUDOLQSXW Figure B-2 UHSHDWBFRPPDQGB FRPPDQGUHSHWLWLRQ RSWLRQDO UHVHUYHGIRU'$ FDQFHOB XQXVHG Structure of the cyclic control word: Peripheral output FB 45 for MOBY U, MOBY D, RF200, RF300 102 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.2 Cyclic control word between master and communications module Cyclic word from communications module: I/O input QXPEHUB0'6B $1=B0'6B SUHVHQWB SUHVHQFH 6/*BHUURU WKHFRQQHFWLRQWRWKHUHDGHULV LQWHUUXSWHG $60BEXV\B QRWFXUUHQWO\XVHG IDOVH 0'6BSUHVHQFHB FKDQJHGB ZLWK)&)% XQXVHG FRPPDQGBUHSHDWBDFWLYHB 7KLVELWLVWKHFRQILUPDWLRQ PLUURULQJ RI UHSHDWBFRPPDQGB,WLVXVHGIRULQIRUPDWLRQ DQGHUURUDQDO\VLV%HWZHHQVHWWLQJ UHSHDWBFRPPDQGBDQGUHDGLQJRXWWKHVHW FRPPDQGBUHSHDWBDFWLYHBELWVWKH FRPPDQGUHSHWLWLRQKDVEHHQVWDUWHG RQWKH&0 5HVHUYHG &RPPDQGFRXQWHUORZHUELW &/ &RPPDQGFRXQWHUKLJKHUELW &+ $FNQRZOHGJHPHQWFRXQWHUORZHUELW $/ $FNQRZOHGJHPHQWFRXQWHUKLJKHUELW $+ $1=BFDQFHOB FDQFHODFNQRZOHGJPHQW XQXVHG 6WDUWXSPHVVDJH 7KLVELWVKRZVWKDWWKH&0KDVVWDUWHGXS $1=BUHVHWB :KHQLQLWBUXQBLVUHVHWWKH02%<&0FDQFHOV WKLVELWDJDLQ2WKHUFRPPDQGV H[FHSWIRU5(6(7RUDQLQYDOLG5(6(7FRPPDQG DUHWKHQUHMHFWHGZLWKDQHUURU PHVVDJH 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): EHIRUH FRPPDQG 6WDUWXS DIWHU FRPPDQG EHIRUH DFNQRZOHGJHPHQW VWFRPPDQG 5(6(7 EHIRUH FRPPDQG EHIRUH DFNQRZOHGJHPHQW QG FRPPDQG UG FRPPDQG FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 103 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_). LQLWBUXQB $1=BUHVHWB $F\FOLF IUDPH 5(6(7FRPPDQG WRWKH&0 5(6(7DFNQRZOHGJ PHQWIURPWKH&0 UHDG\ &&$& DQ\ && $& GHILQHGUHVHW %= 4= ,IDFRPPDQGZDVLQWHUUXSWHGE\ 5(6(7 RULQLWBUXQB HUURU PHVVDJH)LVWULJJHUHGKHUH UHDG\ UHDG\PHVVDJHLQXVHUSURJUDP Figure B-4 Power-up timing initiated by user LQLWBUXQB $1=BUHVHWB $F\FOLF IUDPH UHDG\ %= 5(6(7FRPPDQG WRWKH&0 %= %= 5(6(7DFNQRZOHGJ PHQWIURPWKH&0 4= UHDG\ UHDG\PHVVDJHLQXVHUSURJUDP Figure B-5 Startup timing of the CM initiated by power down FB 45 for MOBY U, MOBY D, RF200, RF300 104 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.3 Methods of operation with the communications module B.3 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. Simple function block programming No optimal-speed data transmission for several consecutive commands The following diagram shows the sequence of the command and acknowledgement exchange between user (PROFINET/PROFIBUS master) and CM. RFID command execution &RPPDQG 7LPHD[LV &RPPDQG 313%PDVWHU &0 &RPPXQLFDWLRQ ZLWKWKHWDJ $FNQRZO HGJH ([HFXWLRQRI VWFRPPDQG &RPPXQLFDWLRQ ZLWKWKHWDJ $FNQRZO HGJH &RPPXQL FDWLRQ GLUHFWLRQ ([HFXWLRQRI QGFRPPDQG 7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH $VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU &KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG &KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG 1RFKDQJHWRF\FOLFGDWD Figure B-6 Command execution: one command at a time Command chaining and buffering on the CM Command chaining is indicated when the chaining bit (bit 6 in the command) is set (see also the section "RFID commands (Page 29)"). Command buffering is a characteristic of the CM or the reader. A variety of buffers are available to the CM/reader for intermediate storage of commands and results. Use of command chaining and command buffering involves the following properties: Programming a function block becomes more complex. Optimum data throughput to and from the tag. This is particularly noticeable with large amounts of data (> 1 KB) and slower PROFIBUS transmission rates. FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 105 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: 7LPHD[LV VW FRPPDQG QG FRPPDQG UG FRPPDQG 313%PDVWHU &0 7UDQVIHURIVW UHVXOW &RPPXQL FDWLRQ GLUHFWLRQ 7UDQVIHURIQG UHVXOW 7UDQVIHURIUG UHVXOW ([HFXWLRQRIVWFRPPDQGRQWKH&0 7UDQVIHURIFRPPDQGVRQWKH&0 ([HFXWLRQ RIQGFRPPDQG RQWKH&0 ([HFXWLRQ RIUGFRPPDQG RQWKH&0 7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH $VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU &KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG &KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG 1RFKDQJHWRF\FOLFGDWD Figure B-7 Command execution: Command chaining and buffering The following general conditions apply to the procedures shown in the diagram above. It is obvious that data transmission and execution of the commands take place parallel to each other. The sequences shown in the diagram above may vary depending on the bus transmission rate and the tag transmission rate. If the PN/PB master module only provides limited resources (buffers) for acyclic data transfer, data transmission may take quite some time. This is particularly noticeable in extensive bus configurations with CMs. If the master module can be set to permit several acyclic frames between cyclic data exchange, data transmission can be speeded up in a bus configuration with many CMs. However, this has a negative effect on the cyclic data exchange of I/O modules that are also part of the same PROFIBUS line. The cycle time of PN/PB becomes irregular and sporadically may become very high. When commands need to be processed by the CM or reader for which there is not enough buffer space on the CM/reader, the user must first fetch results from the CM before new commands can be sent to the CM. The CM does not necessarily need the chaining bit in the command. However, from the user's point of view, it is an elegant way to identify related partial commands. A chaining bit set in the command is returned by the CM in the acknowledgment. The number of buffers on the CM/reader depends on the CM or reader type. Refer to the table in the section "Command repetition (Page 37)" and section "Brief description of the hardware (Page 81)". FB 45 for MOBY U, MOBY D, RF200, RF300 106 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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)"). The following diagram shows frame exchange between user (PN/PB master) and CM: 7LPHD[LV 313% PDVWHU 6LQJOH SURJUDPPLQJ RI&0 DVDOUHDG\ GHVFULEHGHDUOLHULQ WKLV VHFWLRQ &0 &RPPXQLFDWLRQGLUHFWLRQ UHSHDWBFRPPDQGB $1=B0'6BSUHVHQWB 6ORZWDJVHTXHQFH $IWHU $1=B0'6BSUHVHQWB WKHFRPPDQGLV UHVWDUWHGLPPHGLDWHO\ &RPPDQGKDVEHHQ SURFHVVHG DFNQRZOHGJPHQW FRXQWHULV LQFUHPHQWHGDQGWKH UHVXOWLV WUDQVIHUUHG )DVWWDJVHTXHQFHWKH GDWDLVWUDQVIHUUHG VORZHUWKDQWKHQHZ WDJVDUHSURFHVVHG &RPPDQGKDVEHHQ SURFHVVHG DFNQRZOHGJPHQW FRXQWHULV LQFUHPHQWHGDQGWKH UHVXOWLV WUDQVIHUUHG 7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH $VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU &KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V UHWDLQVWKHVDPHFRXQWHUYDOXH &KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG 1RFKDQJHWRF\FOLFGDWD Figure B-8 Command repetition using I/O words Command repetition can also be concretely controlled as shown below. An external proximity switch is used to signal that a new tag is entering the transmission window (see figure below: ). A new tag is detected with the ANZ_MDS_present_ bit, and command repetition is then started (see figure below: ). FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 107 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. 7LPHD[LV 313% PDVWHU 6LQJOH SURJUDPPLQJ RIWKH&0 DVDOUHDG\ GHVFULEHGHDUOLHULQ WKLVFKDSWHU &RPPXQLFDWLRQ GLUHFWLRQ UHSHDWBFRPPDQGB &0 $ % FRPPDQGBUHSHDWBDFWLYHB $1=B0'6BSUHVHQWB +DQGVKDNH VHTXHQFHVRWKDW FRPPDQG SURFHVVLQJ LVJXDUDQWHHG 8VHUVWDUWVZLWK UHSHDWBFRPPDQGB 7KHDSSOLFDWLRQ LVZDLWLQJKHUH IRUWKHQH[W WDJ 3URFHVVLQJVHTXHQFH IRUDIXUWKHU WDJ &RPPDQGKDVEHHQ &RPPDQGKDVEHHQSURFHVVHG SURFHVVHG DFNQRZOHGJPHQWFRXQWHU DFNQRZOHGJPHQWFRXQWHU LVLQFUHPHQWHGDQGWKH LVLQFUHPHQWHGDQGWKH UHVXOWLVWUDQVIHUUHG 7ULJJHUVLJQDOIRU UHVXOWLVWUDQVIHUUHG DFRPPDQGVWDUW $1=B0'6BSUHVHQWB 7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH $VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU &KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V UHWDLQVWKHVDPHFRXQWHUYDOXH &KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXV F\FOLFZRUG 1RFKDQJHWRF\FOLFGDWD Figure B-9 Focused command repetition FB 45 for MOBY U, MOBY D, RF200, RF300 108 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.4 Command and acknowledgement telegrams B.4 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. %\WH $% &RPPDQG 6WDWXV Q &RPPDQGVSHFLILFGDWD 7KHFRPPDQGVSHFLILFGDWDLVGHVFULEHGLQGHWDLORQWKHIROORZLQJSDJHV 7KHPLQOHQJWKLVWKHPD[GDWDOHQJWKLV E\WHV 7KHVWDWXVE\WHDOZD\VKDVWKHYDOXHZKHQDFRPPDQGLVLVVXHG ,QWKHUHVXOWRUHUURUIUDPHWKHE\WHKDVWKHIROORZLQJPHDQLQJ %LW UHV UHV UHV (UURUFRGH ) 'HWDLOHGHUURUGHVFULSWLRQVHHVHFWLRQ 7KHLPSOHPHQWHGFRPPDQGVDUHGHVFULEHGRQWKHIROORZLQJSDJHV *HQHUDOFRPPDQGIRUPDW (UURUFRGH) DFFRUGLQJWRWDEOHEHORZ FKDLQHGFRPPDQG UHVHUYHGIRUV\VWHPIXQFWLRQV HJILUPZDUHXSGDWH 1XPEHURIE\WHV Q WRWDOQXPEHURIE\WHVLQIUDPH $%E\WHLVQRWFRXQWHG PLQLPXP$% PD[LPXP$% PD[LPXPOHQJWKIRU352),%86'39LVE\WHV 7KHOHQJWKVSHFLILHGKHUHLVWKHPD[LPXPOHQJWKIRU352),%867KH$60 LVDQH[FHSWLRQZLWKDOHQJWKE\WHVKRUWHU PD[GDWDOHQJWK FRPPDQGVSHFLILFGDWD Figure B-10 General frame format FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 109 Programming communications modules B.4 Command and acknowledgement telegrams Command table Command Description [hex] Comman d code chained [hex] 0 - RESET CM is reset. The active command is terminated. (If a tag command was terminated with RESET, the reset acknowledgment reports error 1F.) 1 41 WRITE Write data block to transponder 2 42 READ Read data block from transponder 3 43 INIT Comma nd code The RESET command can be used to switch the CM to various operating modes. This command is required when a new transponder is used that has not yet been written to or after failure/replacement of the battery or when the transponder is to be operated in ECC mode. The transponder is already initialized for normal use. Tag type INIT duration (normal) Memory size + 1 2 KB RAM (MOBY U) approx. 1 s 00 08 00 32 KB RAM (MOBY U) approx. 1.5 s 00 80 00 44 bytes I-Code (MOBY D) approx. 0.4 s 00 00 2C 112 bytes I-Code SLI (MOBY D) approx. 0.5 s 00 00 70 256 bytes Tag-it HF-I (MOBY D) approx. 1 s 00 01 00 996 bytes my-d (MOBY D) approx. 3 s 00 04 00 2000 bytes FRAM (MOBY D) approx. 3 s 00 07 D0 20 bytes EEPROM (RF300) approx. 0.2 s 00 00 14 8 KB FRAM (RF300) 0.9 s 00 20 00 32 KB FRAM (RF300) 3.6 s 00 80 00 64 KB FRAM (RF300) 7.2 s 00 FF 00 4 44 SLG STATUS Returns as result the status byte, the selected reader and the ANZ_MDS_present_ bit. This command checks whether a reader is connected to the CM and, if so, whether it is functioning and ready for operation. An appropriate error is reported, if necessary. With MOBY U various diagnostic data can be fetched from the reader. 6 - NEXT The command is not supported by the systems described here MOBY U/D, RF200 and RF300. 8 48 END Terminate communication with the transponder (MOBY U only) A 4A SET-ANT B 4B MDS-STATUS MOBY U/D, RF200 or RF300 only: This command turns the antenna field on the reader off and on again. Returns the properties of the transponder in the result FB 45 for MOBY U, MOBY D, RF200, RF300 110 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.4 Command and acknowledgement telegrams Exact frame format &RPPDQGIUDPH WRWKH&0UHDGHU &RPPDQG FRGH 5HVXOWIUDPH IURPWKH&0UHDGHU 7KHVWDUWXSRIWKH&0LVRQO\ VLJQDOHGWRWKHXVHUYLDWKH F\FOLFZRUG VHH$SSHQGL[ % 6WDUWXS 5(6(7 $ GLOL PXOWLWDJ VWDQGE\ 3DUDP IFRQ ([SHFWHGQXPEHURIWDJVLQ ILHOG IWLP 6WDW 9HUV+ 9HUV/ 5HV )LUPZDUHYHUVLRQLQ&0 YHUVLRQB02%< 02%<8 ILHOGB21BWLPHB VHHLQSXWSDUDPHWHU KH[ ZLWKRXW%(52V KH[))KH[ V7XUQRQWLPH IRUWKHWDJILHOG 02%<' 02%<8 ILHOGB21BFRQWURO VHHLQSXWSDUDPHWHU 7DJW\SH VHHLQSXWSDUDPHWHU %(52PRGH KH[ ,FRGH ]%0'6' KH[ RKQH%(52VQR6/*V\QFKURQL KH[ ,620'6 ]DWLRQ KH[ 'XDOGULYHU,&RGHDQG,62 KH[ ILHOGB21BWLPHVZLWFKHVWKHILHOG KH[ 0'6'RSWLPL]DWLRQRQO\ZLWK RII 6/*'6 KH[ %(52VZLWFKHVWKHILHOGRQ KH[ 0'6'[[RSWLPL]DWLRQRQO\ZLWK %(52VZLWFKHVWKHILHOGRII 6/*'66 KH[ $FWLYDWHZULWHUHDGGHYLFH 5) V\QFKURQL]DWLRQYLDFDEOHFRQQHFWLRQ VHH ILHOGB21BWLPH VHHLQSXWSDUDPHWHU PDQXDOIRUFRQILJXULQJPRXQWLQJDQG KH[ 5)0RGH QR,62 VHUYLFHIRU02%<8 KH[ ,62WDJ 02%<'5)5)QRWXVHG KH[ KH[ ,62P\G ,QILQHRQ65)93 KH[ ,62 )XMLWVX0%5 KH[ ,62,&RGH6/, 1;36/,&6 KH[ ,627DJLW+), 7H[DV,QVWUXPHQWV KH[ ,62 67/5,. 5)KH[ ,627DJ 02%<8 GLVWDQFHBOLPLWLQJB5DQJHOLPLWDWLRQ VHHLQSXWSDUDPHWHU $)(KH[ P $)($KH[ VDPHZLWKUHGXFHGRXWSXWSRZHU 02%<'+)SRZHU VHHLQSXWSDUDPHWHU 5) GLVWDQFHBOLPLWLQJRQO\IRU5)5FKDQJHRIRXWSXWSRZHU KH[ : KH[ : KH[ : KH[ : KH[ : KH[ : KH[ : 5)UHVHUYHG KH[ 2SWLRQ02%<5)RU5) %LW QRWXVHG %LW UHV QRWXVHG 5HVHW(55/('DW&0DQG5HDGHU 'RQWUHVHW(55/('DW&0DQG5HDGHU 0XOWLWDJZLWK%\WH8,' 0XOWLWDJZLWK%\WH8,' 3UHVHQFHFKHFNDQGWDJFRQWURO 0'6BFRQWUROB QR$1:FRQWURO QRWDJFRQWURO$1:FKHFNRYHU ILUPZDUH GHIDXOW 02%<8 VFDQQLQJBWLPHB6WDQGE\WLPHIRUWKHWDJ VHHLQSXWSDUDPHWHU KH[ QRVWDQGE\RSHUDWLRQ KH[&KH[ PVPVVWDQGE\WLPH 02%<'5)5)QRWXVHG KH[ FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 111 Programming communications modules B.4 Command and acknowledgement telegrams &RPPDQGIUDPH WRWKH&0UHDGHU &RPPDQG FRGH :5,7( 5($' ,1,7 0HDQLQJ ''Q $% $GGUHVV /1* 06% /6% 5HVXOWIUDPH IURPWKH&0UHDGHU ''Q $GGUHVV 06% /6% ,1,7 SDWWHUQ /1* (QGDGGU 06% /6% $% & $GGUHVV /1* ''Q & 06% /6% & 8VHUGDWDRIXVHU WRIRU$60WR /1* /HQJWKRIWKHGDWDEORFN ''Q 1RWHDGGUHVV/1*PXVWEHVPDOOHUWKDQWKHHQGDGGUHVVRIWKHWDJ $GGUHVV 6WDUWDGGUHVVRIWKHGDWDWREHSURFHVVHGRQWKHWDJ 06% PRVWVLJQLILFDQWDGGUHVVSDUW /6% OHDVWVLJQLILFDQWDGGUHVVSDUW 1XPEHURIWKHIROORZLQJFKDUDFWHUVLQWKHIUDPH $% /1* 1RWH$%PXVWQRWEHJUHDWHUWKDQWKHEXVFRQILJXUDWLRQ $% ,1,7SDWWHUQ 7KHYDOXH,QLWSDWWHUQLVZULWWHQWRWKHWDJGXULQJLQLWLDOL]DWLRQ (QGDGGU 0HPRU\VL]HRIWKHWDJ ,IDQHUURURFFXUVWKHUHVXOWIUDPHKDVWKHIROORZLQJVWUXFWXUH 7KH$%E\WH FDQVWRUHDYDOXH!IRUWKHUHDGFRPPDQG ,QWKLVFDVHWKHGDWDLVRQO\SDUWLDOO\FRUUHFWDQGPXVWEHGLVFDUGHG DYRLGHG 7KHVWDWXVE\WHLQWKHUHVXOWIUDPHGHSHQGVRQWKHWDJW\SH EDWWHU\VWDWHV &RP )DXOW FB 45 for MOBY U, MOBY D, RF200, RF300 112 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.4 Command and acknowledgement telegrams &RPPDQGIUDPH WRWKH&0UHDGHU &RPPDQG FRGH UHDGHU VWDWXV PRGH UHV UHV UHV PRGH 6/*VWDWXVDOO 5)SURGXFWV 5HVXOWIUDPH IURPWKH&0UHDGHU % 6WDW 6/*VWDWXV 7KHPHDQLQJRIWKH6/*VWDWXV LVGHVFULEHGLQ8'7 02%<8 PRGH UHDGHUGLDJQRVWLFV, IXQFWLRQFDOOV $% 6WDW PD[ Q VW FRPPDQG QWK FRPPDQG )UDPHKHDGHUV RIWKHFRPPDQGV WKDWZHUHH[HFXWHGODVW KH[KH[ 02%<8 PRGH UHDGHUGLDJQRVWLFV,, HUURUPHVVDJHV $% PD[PHVVDJHIUDPHV DUHWUDQVIHUUHG 6WDW Q VWHUURU PD[ QWKHUURU ,QGLFDWHVODVW HUURUWKDWRFFXUUHG KH[(%KH[ PD[HUURU PHVVDJHV 02%<8 PRGH UHDGHUGLDJQRVWLFV,,, LGHQWLILHGWDJ $% 6WDW PD[ Q VW WUDQVSRQGHU QWK WUDQVSRQGHU KH[KH[ 02%<8 PRGH UHDGHUGLDJQRVWLFV,9 &RPPXQLFDWLRQTXDOLW\ 5) PRGH UHDGHUGLDJQRVWLFV ,' VRIWKHWUDQVSRQGHU ODVWGHWHFWHGLQWKH WUDQVPLVVLRQ ZLQGRZ PD[WUDQVSRQGHU,' V $% 6WDW Q $% 6WDW 'LDJQRVWLFVGDWD IRUH[SHUWVRQO\ 7KHPHDQLQJVRIWKHGLDJQRVWLFVGDWDDUHGHVFULEHG LQ8'7 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 113 Programming communications modules B.4 Command and acknowledgement telegrams &RPPDQGIUDPH WRWKH&0UHDGHU &RPPDQG FRGH (1' 5HVXOWIUDPH WRWKH&0UHDGHU PRGH 6WDW 3URFHVVLQJZLWKWUDQVSRQGHULV FRPSOHWHG 3URFHVVLQJSDXVHZLWKWUDQVSRQGHU (QG6FDQQLQJBWLPHIRU WKH02%<8WUDQVSRQGHU LPPHGLDWHO\ $$ 6(7 $17 $ $ PRGH $ 6WDW $ 6ZLWFKRQDQWHQQD 6WDQGE\VZLWFKRIIDQWHQQD FB 45 for MOBY U, MOBY D, RF200, RF300 114 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.4 Command and acknowledgement telegrams &RPPDQGIUDPH WRWKH&0UHDGHU &RPPDQG FRGH %% 0'6 VWDWXV % % PRGH ZHHN 5HVXOWIUDPH IURPWKH&0UHDGHU \HDU &XUUHQWGDWH PRGH 02%<8 ZHHN &DOHQGDU ZHHN KH[ KH[ VWWR QGZHHN \HDU \HDU ZHHN \HDU 1RWUHOHYDQW 7DJ 7\SH E\WHWDJ,'QXPEHU PRGH 5) % 6WDW 8,' % 6WDW 7KHPHDQLQJRIWKH GLDJQRVWLFVGDWDLV GHVFULEHGLQ8'7 8,' E\WHWDJ,'QXPEHU XQLTXHLGHQWLILHU PRGH 5) ZHHN \HDU 1RWUHOHYDQW % 6WDW 'LDJQRVWLFVGDWD 8,' 'LDJQRVWLFVGDWD 7KHPHDQLQJRIWKH GLDJQRVWLFVGDWDLV GHVFULEHGLQ8'7 'LDJQRVWLFVGDWD 7KHPHDQLQJRIWKH GLDJQRVWLFVGDWDLV GHVFULEHGLQ8'7 PRGH 5) 5),6202%<' ZHHN \HDU 1RWUHOHYDQW % 6WDW 8,' 'LDJQRVWLFVGDWD 7KHPHDQLQJRIWKH GLDJQRVWLFVGDWDLV GHVFULEHGLQ8'7 FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 115 Programming communications modules B.5 PROFIBUS/PROFINET implementation B.5 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. PQW and PIW are exchanged cyclically between the CM and function block. PIW informs the function block when commands and data may be transferred to the communications module. Commands and data are put into data records. &RPPXQLFDWLRQPRGXOH ,QWHUIDFHWRXVHU $60BDGGUHVV $60BFKDQQHO 0'6BFRQWURO 02%<BPRGH VFDQQLQJBWLPH &RPPDQGV 'DWD DFNQRZO HGJPHQWV 3$:[ 3(:[ )XQFWLRQ EORFN HJ$60 %XV 6$3 1,/ 6$3 1,/ '6[ SDUDPHWHUV 6$3 '6[ GDWD 6$3 3$:[ 6HTXHQFH FRQWURO 3(:[ '6[ '6[ Q 02%< GULYHU 0'6 GDWD '6[ '6[ [ FKDQQHO Q QRRIFRPPDQGRQ&0 QPD[ QXPEHURIEXIIHUVRQ&0VHHVHFWLRQ&RPPDQGUHSHWLWLRQ 6,0$7,&6XVHV6$3DQG6$3IRUDF\FOLFFRPPXQLFDWLRQ 7KHWUDQVIHURIWKHFRQWUROZRUG 34:3,: XVHVWKHF\FOLFGDWDBH[FKDQJHVHUYLFH RI352),%86 6$3 1,/ FB 45 for MOBY U, MOBY D, RF200, RF300 116 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 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. 6' /( /(U 6' '$ 6$ )& + [ [ + [ [ [ %\WH '6$3 66$3 '8 )&6 (' + + [ [ + )XQFWLRQFRGH HJ'6B5HDGUHT 5HTXHVW5HVSRQVHRND\ 5HVSRQVH(UURU)UDPH %\WH %\WH 6ORWB1XPEHU$605)& $60 WR FRUUHVSRQGVWRWKH VORWLQDQ (70 5)& WR FRUUHVSRQGVWRWKH VORWLQDQ (7SUR ,QGH[ GDWDUHFRUGQXPEHUIRUFKDQQHOV WR VHHWDEOHEHORZ %\WH 'DWDOHQJWK 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 117 Programming communications modules B.5 PROFIBUS/PROFINET implementation Table B- 1 Data record numbers (index) Data record number Exist on CM/reader Description 101 all Parameter assignment channel 1 102 all Parameter assignment channel 2 103 - Parameter assignment channel 3 104 - Parameter assignment channel 4 111 all Data transmission channel 1 112 all Data transmission channel 2 113 - Data transmission channel 3 114 - Data transmission channel 4 121 ASM 456, RF160C, (RF170C), RF180C System command to reader (in preparation for RF170C) 122 ASM 456, RF160C, (RF170C), RF180C System command to reader (in preparation for RF170C) 150 ASM 475 Reserved (diagnosis of powerparameters) 151 ASM 475 Reserved (diagnostic buffer) 180 RF180C reserved 231 RF170C I&M0 232 RF170C I&M1 233 RF170C I&M2 234 RF170C I&M3 239 ASM 456, ASM 475, RF160C, RF170C, RF180C Firmware update 246 ASM 475 SSL reserved 247 (ASM 456, RF160C) SSL reserved 248 ASM 475, RF170C, (ASM 456, RF160C) System: SSL processing I&A 255 ASM 456, RF160C I&M PROFIBUS Data record 10x One RFID channel is assigned parameters with the data records (DS) 101 to 104. DR 10x must contain a RESET command. After the module starts up, DS 10x must be sent to each RFID channel. The channel is not ready for operation until this is done. A DR 10x is also accepted during normal operation. DS 10x interrupts a running command. The user receives no further acknowledgment for the interrupted command. Data record 11x DRs 111 to 114 are used for sending the actual commands and related acknowledgments (all commands except RESET). FB 45 for MOBY U, MOBY D, RF200, RF300 118 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Programming communications modules B.6 Example of a PROFIBUS Trace B.6 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. Note Using FB 45 on PROFINET If FB 45 is used on PROFINET, the PROFINET trace is similar to the PROFIBUS trace. The data contents are identical. The header data of the frames are different. Startup of an ASM 456 and RESET sequence on the 2nd channel 68 07 07 68 03 02 5d 00 00 00 00 00 16 68 07 07 68 02 03 08 80 00 80 00 00 16 FB: --CM: CM startup 68 07 07 68 03 02 7d 80 00 80 00 00 16 68 07 07 68 02 03 08 80 00 80 00 00 16 FB: sets the startup bit CM: --- 68 07 07 68 03 02 5d 80 00 80 00 00 16 68 07 07 68 02 03 08 88 00 88 00 00 16 FB: --CM: sets the command counter to 1 68 07 07 68 03 02 7d 00 00 00 00 00 16 68 07 07 68 02 03 08 88 00 88 00 00 16 FB: resets the startup bit CM: --- 68 07 07 68 03 02 5d 00 00 00 00 00 16 68 07 07 68 02 03 08 08 00 08 00 00 16 FB: --CM: resets the startup bit 68 0F 0F 68 83 82 5c 33 36 5F 01 66 06 05 00 00 00 2b 02 00 16 68 05 05 68 83 82 5c 33 36 00 16 68 09 09 68 82 83 08 36 33 5f 01 66 06 00 16 FB: RESET command to 2nd channel FB: request for acknowledgment CM: acknowledgment that RESET is being processed (PROFIBUS confirmation) 68 07 07 68 03 02 7d 00 00 00 00 00 16 68 07 07 68 02 03 08 08 00 10 00 00 16 FB: --CM: command counter for 2nd channel is incremented to 2 68 07 07 68 03 02 7d 00 00 00 00 00 16 68 07 07 68 02 03 08 08 00 30 00 00 16 FB: --CM: acknowledgment counter for 2nd channel is incremented to 1 68 07 07 68 03 02 7d 00 00 00 00 00 16 68 07 07 68 02 03 08 08 00 31 00 00 16 FB: --CM: sets presence 68 09 09 68 83 82 5c 33 36 5e 01 66 06 00 16 68 05 05 68 83 82 5c 33 36 00 16 68 0F 0F 68 82 83 08 36 33 5e 01 66 06 05 00 00 00 00 00 00 16 FB: confirmation of "RESET being processed" FB: request for acknowledgment CM: RESET acknowledgment --- no change FB stands for a function block, but could also be any HOST function FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 119 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 68 09 09 68 82 83 08 36 33 5f 01 65 06 00 16 CM: acknowledgment that RESET is being processed (PROFIBUS confirmation) 68 09 09 68 83 82 5c 33 36 5e 01 65 06 00 16 FB: Confirmation of "RESET being processed" 68 05 05 68 83 82 5c 33 36 00 16 FB: request for the acknowledgment 68 0F 0F 68 82 83 08 36 33 5e 01 65 06 05 00 00 00 00 00 00 16 CM: RESET acknowledgment 68 0F 0F 68 83 82 7c 33 36 5f 01 6f 06 05 02 00 00 40 0c 00 16 FB: read command: tag addr. = 0, length = 0c 68 05 05 68 83 82 7c 33 36 00 16 FB: request for the acknowledgment 68 09 09 68 82 83 08 36 33 5f 01 6f 06 00 16 CM: acknowledgment that read is being processed 68 09 09 68 83 82 7c 33 36 5e 01 6f 12 00 16 FB: confirmation of "read being processed" 68 05 05 68 83 82 7c 33 36 00 16 FB: request for the acknowledgment 68 1b 1b 68 82 83 08 36 33 5e 01 6f 12 11 02 00 00 40 0c aa aa bb bb cc cc dd dd ee ee ff ff 00 16 CM: read acknowledgment with the tag data FB 45 for MOBY U, MOBY D, RF200, RF300 120 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 Service & Support C Technical Support You can access technical support for all IA/DT projects via the following: Phone: + 49 (0) 911 895 7222 Fax: + 49 (0) 911 895 7223 E-mail (mailto:support.automation@siemens.com) Internet: Online support request form: (http://www.siemens.com/automation/supportrequest) 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 In Catalog ID 10 specifically for industrial communication / industrial identification systems Service & support for industrial automation and drive technologies You can find various services on the Support homepage (http://www.siemens.com/automation/service&support) of IA/DT on the Internet. There you will find the following information, for example: Our newsletter containing up-to-date information on your products. Relevant documentation for your application, which you can access via the search function in "Product Support". A forum for global information exchange by users and specialists. Your local contact for IA/DT on site. Information about on-site service, repairs, and spare parts. Much more can be found under "Our service offer". RFID homepage For general information about our identification systems, visit RFID homepage (http://www.siemens.com/ident/rfid). FB 45 for MOBY U, MOBY D, RF200, RF300 Function Manual, 07/2012, J31069-D0166-U001-A4-7618 121 Service & Support Technical documentation on the Internet 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). Training center We offer appropriate courses to get you started. Please contact your local training center or the central training center in D-90327 Nuremberg. Phone: +49 (0) 180 523 56 11 ( 0.14 /min. from the German landline network, deviating mobile communications prices are possible) For information about courses, see the SITRAIN homepage (http://www.sitrain.com). FB 45 for MOBY U, MOBY D, RF200, RF300 122 Function Manual, 07/2012, J31069-D0166-U001-A4-7618