6GT2402-2EA00 - Siemens - Datasheet.Cloud

FB 45 for MOBY U, MOBY D, RF200,

RF300 

_________________

__________________

_________________

SIMATIC Ident

RFID systems

FB 45

for MOBY U, MOBY D, RF200,

RF300

Function Manual

07/2012

J31069-D0166-U001-A4-7618

Introduction

Description

Parameterizing

Commissioning

Error messages and

troubleshooting

Examples/applications

Brief description of the

hardware

Programming

communications modules

Service & Support

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 ® 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 NÜRNBERG

GERMANY

J31069-D0166-U001-A4-7618

Ⓟ 07/2012 Technical data subject to change

2009, 2012.

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 3

Table of contents

1 Introduction................................................................................................................................................ 5

1.1 Overview ........................................................................................................................................5

1.2 Preface...........................................................................................................................................8

1.3 Navigating in the Function Manual ................................................................................................9

2 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

3 Parameterizing ........................................................................................................................................ 19

3.1 Parameter data block...................................................................................................................19

3.1.1 INPUT parameters .......................................................................................................................21

3.1.2 Command and status word..........................................................................................................26

3.1.3 Further displays ...........................................................................................................................29

3.2 RFID commands ..........................................................................................................................29

3.2.1 Command parameters .................................................................................................................30

3.2.2 Command chaining ......................................................................................................................35

3.2.3 Command repetition.....................................................................................................................37

3.3 Presence check ...........................................................................................................................40

3.3.1 No tag control, no presence check: MDS_control = 0 .................................................................40

3.3.2 No tag control, presence control with field scanning: MDS_control = 1 ......................................40

4 Commissioning ........................................................................................................................................ 41

5 Error messages and troubleshooting ....................................................................................................... 47

5.1 General errors..............................................................................................................................47

5.2 Error messages............................................................................................................................47

6 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

Table of contents

FB 45 for MOBY U, MOBY D, RF200, RF300

4 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

6.8 Determing the memory requirement in the SIMATIC.................................................................. 79

A Brief description of the hardware ............................................................................................................. 81

A.1 RF170C....................................................................................................................................... 81

A.2 RF180C....................................................................................................................................... 85

A.3 ASM 456...................................................................................................................................... 89

A.4 ASM 475...................................................................................................................................... 96

B 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

C Service & Support.................................................................................................................................. 121

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 5

Introduction 1

1.1 Overview

FB 45 is a STEP 7 function for RFID technology. It can be used with both the SIMATIC S7-

300 and S7-400 for various RFID communications modules.

$60

5)& 5)& $60

Figure 1-1 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.

Introduction

1.1 Overview

FB 45 for MOBY U, MOBY D, RF200, RF300

6 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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)"

Introduction

1.1 Overview

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 7

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 third-

party 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

Introduction

1.2 Preface

FB 45 for MOBY U, MOBY D, RF200, RF300

8 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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.

Introduction

1.3 Navigating in the Function Manual

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 9

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

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

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 11

Description 2

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 Communication time between CM, reader and tag

Amount of user data

Constants (see table in configuration manual)

kbytes

tkt n=+ ⋅

bytes Transmission time for 1 byte (see table in configuration

manual)

Description

2.2 Configuration scheme

FB 45 for MOBY U, MOBY D, RF200, RF300

12 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 Configuration scheme

Table 2- 1 MOBY FB configuration scheme

Ladder logic

programming box

Parameters Data type Permissible range Description

"Inst-DB FB 45"

MOBY FB 45

Params_DB

Params_ADDR

Params_DB

Params_ADDR

INT

2 to 32767

0, 50, 100,*...

Parameter data block number for an

RFID channel (reader)

Address pointer in the parameter data

block to the start of a UDT 10

*) 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

Command parameters (Page 30)

Parameterizing

3.2 RFID commands

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 37

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

normal chained* Syntax Description

Permitted with

command repetition

01 41 WRITE Write data to transponder yes; but only with identical write

data

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

*) Chained commands are not supported by all readers. You should also note the

information in the relevant system manual.

Parameterizing

3.2 RFID commands

FB 45 for MOBY U, MOBY D, RF200, RF300

38 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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.

7KHXVHUVWDUWVWKHFRPPDQGIDVWHU

WKDQWUDQVSRQGHUVPRYHSDVWWKH

UHDGHU

7KHUHVXOWLVDYDLODEOHWRWKHXVHU

$60BEXV\ GLUHFWO\IROORZLQJ

SURFHVVLQJRIWKHFRPPDQG

$60BEXV\ 

7KHWUDQVSRQGHUVSDVVE\WKHUHDGHU

IDVWHUWKDQWKHXVHUIHWFKHVWKH

UHVXOWVKHUHWKHUHVXOWVDUH

WHPSRUDULO\VWRUHGRQWKHFRPPXQLFD

WLRQVPRGXOH7KHUHVXOWVDUHUHDGRXW

DWDODWHUSRLQWLQWLPH

5HVXOWVDUH

IHWFKHGRQWKH

FRPPXQLFD

WLRQVPRGXOH

UHDG\

FRPPDQGBVWDUW

UHSHDWBFRPPDQG

1=B0'6BSUHVHQW

Figure 3-2 Continuous reading of each passing tag/transponder (repeat_command remains set)

When permanent command repetition is used, data may be transferred to FB 45 slower than

new tags are being processed (fast tag sequence, slow data transmission). 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 No. of buffers per channel Max. user data which can be

processed with command

repetition

SLG U92

SLG D10S

SLG D11S/D12S

RF300 reader

150

100

246

34950 byte

23300 byte

233 byte

57318 byte

One buffer can hold up to 233 bytes of user data.

Parameterizing

3.2 RFID commands

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 39

● 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.

7KHIROORZLQJVHTXHQFHPXVWEHSURJUDPPHGE\WKHXVHU

Ⴠ $WWKHEHJLQQLQJRIWKHFRPPDQGWKHXVHUVHWVFRPPDQGBVWDUWDQGUHSHDWBFRPPDQGVLPXOWDQHRXVO\

Ⴠ 7KHXVHUWKHQZDLWVIRU$60BEXV\ DQGWKHQUHVHWVUHSHDWBFRPPDQG

Ⴠ 2QFHUHDG\ KDVEHHQVLJQDOHGE\WKH)%WKHFRPPDQGKDVEHHQSURFHVVHG

 7KHFRPPXQLFDWLRQVPRGXOHGRHVQRWDXWRPDWLFDOO\SURFHVVDQ\IXUWKHUWUDQVSRQGHUV

UHDG\

FRPPDQGBVWDUW

UHSHDWBFRPPDQG

$1=B0'6BSUHVHQW

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.

Parameterizing

3.3 Presence check

FB 45 for MOBY U, MOBY D, RF200, RF300

40 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 41

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

Commissioning

FB 45 for MOBY U, MOBY D, RF200, RF300

42 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

The following figure shows the position of the communications modules in the hardware

catalog.

$60LQ

DFHQWUDOL]HG

FRQILJXUDWLRQ

(J$60LQ

DGLVWULEXWHG

FRQILJXUDWLRQ

YLD(70

$60LQD

GLVWULEXWHG

FRQILJXUDWLRQYLD

352),%86

Figure 4-1 Location of the communications modules in the hardware catalog

When configuring the ASMs, make sure that the I address and the Q address have the same

values. 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:

Commissioning

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 43

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.

$60bREMHFWSURSHUWLHV $60REMHFWSURSHUWLHVDUHVWRUHG

LQWKH*6'ILOH

Figure 4-3 Configuring the object properties

Commissioning

FB 45 for MOBY U, MOBY D, RF200, RF300

44 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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).

These two variables

must be adapted for each

channel.

The pointer to the command_DB can retain

the default value on initial

commissioning.

During commissioning of

RF200/RF300 the value "5" is

correct here. Otherwise this value

must be adjusted.

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.

Commissioning

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 45

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"

Commissioning

FB 45 for MOBY U, MOBY D, RF200, RF300

46 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 47

Error messages and troubleshooting 5

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 non-

existent 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 Classification

error_MOBY 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

• There is a parameter error in "Params_DB" or "command_DB".

error_BUS The transport layer of PROFIBUS or PROFINET is signaling an error. A

PROFIBUS tracer and a PROFIBUS device (BT 200; order No. 6ES7181-

0AA00-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).

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

48 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 messages of the communication module/reader using the "error_MOBY" variable

Error code

(B#16#...)

Flashing of

ERR LED

Description

00 – 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 49

Error code

(B#16#...)

Flashing of

ERR LED

Description

03 3x 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

04 4x Error in tag memory

The tag has never been written to or has lost the contents of its

memory due to battery failure.

• Replace tag (possibly defective)

• Reinitialize tag (see section Parameterizing (Page 19)).

05 5x Unknown command

FB 45 is sending an uninterpretable command to the CM.

• Command_DB contains invalid command parameters.

• The command_DB was overwritten by the user

• The tag has signaled an address error

06 6x Field disturbance on reader

The reader is receiving interference pulses from the environment.

• 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).

07 7x 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

50 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Error code

(B#16#...)

Flashing of

ERR LED

Description

08 8x CRC sending error

• The tag is signaling CRC errors frequently.

– The tag is in the boundary area of the reader.

– The tag and/or reader have a hardware fault.

09 9x Only during initialization: CRC error when receiving an

acknowledgment from tag

• Cause same as error B#16#06.

0A 10x Only during initialization: Tag cannot execute the initialization

command.

• Tag is defective

0B 11x MOBY U: Memory of the tag cannot be read correctly

0C 12x 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

0D 13x 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 51

Error code

(B#16#...)

Flashing of

ERR LED

Description

12 18x Internal CM communication error.

• Connector contact problem on the CM

• Defective CM hardware

– Return CM for repair

• Start init_run command after error correction.

13 19x CM or reader does not have enough buffer space to store the

command temporarily.

14 20x 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.

15 21x 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.

16 22x 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.

17 23x 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.

18 – 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

52 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Error code

(B#16#...)

Flashing of

ERR LED

Description

19 25x Previous command is active or buffer overflow.

The user sent a new command to the CM although the last command

was still active.

• Active command can only be terminated with an init_run.

• 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.

1A – 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.

• Turn on the antenna with the "SET-ANT" command

• The antenna is turned on (off) and has received an additional turn-

on (turn-off) command.

1D – More transponders are located in the transmission window than can be

processed at the same time by the reader.

• Only 1 tag can be processed at a time with FB 45

1E 30x 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 DP-

V1").

1F – 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

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 53

error_FB

Table 5- 3 Error variable "error_FB"

Error code

(B#16#...)

Description

00 No error; default value if everything is ok.

01 Params_DB not available in SIMATIC

02 Params_DB too small

• 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

03 The DB after the "command_DB_number" pointer is not available in the SIMATIC.

04 "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

05 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

– Execute an init_run

06 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

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

54 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Error code

(B#16#...)

Description

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 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.

0C 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

0D 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 55

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 S7-

300/400, volume 1/2 (http://support.automation.siemens.com/WW/view/en/44240604)".

Table 5- 4 Error variable "error_BUS" when operating via PROFIBUS/PROFINET

Error code

(W#16#...)

Description

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

8x43

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.

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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

56 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Error code

(W#16#...)

Description

8093 The area identifier contained in the configuration (SDB1, SDB2x) of the logical

address is not permitted for these SFCs. Permitted:

• 0 = S7-400

• 1 = S7-300

• 2, 7 = DP modules

80A0 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.

Error messages and troubleshooting

5.2 Error messages

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 57

Error code

(W#16#...)

Description

80C4 Communication error

• Parity error

• SW ready not set

• Error in block length management

• Checksum error on CPU side

• Checksum error on module side

80C5 Distributed I/O not available

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

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 59

Examples/applications 6

6.1 FB 45 scanning by user

Scanning of FB 45 takes place in accordance with the structogram in the following figure.

5HVWDUW6HWWLQJLQLWBUXQ

ൺ2%

&\FOLFTXHU\6HWFRPPDQGBVWDUW

ൺVWDUWFRPPDQGRQO\LIUHDG\ ಻



(UURU

KDQGOLQJ

ൺHYDOXDWLRQ

RI

HUURUB02%<

HUURUB)%

DQG

HUURUB%86

&RPPDQG2.

ൺ3URFHVV

GDWD

+HUHWKHUHZDV

QR

FRPPXQLFDWLRQ

ZLWKWKH

WUDQVSRQGHU

&RPPDQG2.

3RVVLEO\

WLPHRXWPRQLWRULQJ

E\WKHXVHU

ൺH[HFXWHLQLWBUXQLI

WLPHRXW

$1=BUHVHWVHW

6HWFRPPDQGBVWDUW

ൺ6WDUWQH[WFRPPDQGLIUHTXLUHG

-1

UHDG\ 

HUURU 

Figure 6-1 Structogram for scanning of FB 45

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

60 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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.

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 61

Address space of the transponder/MDS variants according to ISO 15693 for RF200, RF300 and

MOBY D

System Addressing 16-bit hexadecimal number Integer number

MDS D139 (I-Code 1; 44 bytes)

Start address

End address

0000

002B

+43

ID no.: (fixed-coded; can only be read as a whole)

Start address

Length

FFF0

0008

-16

ISO-MDS (I-Code SLI; 112 bytes)

Start address

End address

0000

006F

+111

ID no.: (fixed-coded; can only be read as a whole)

Start address

Length

FFF0

0008

-16

ISO MDS (Tag-it HF-I; 256 bytes)

Start address

End address

0000

00FF

+255

ID no.: (fixed-coded; can only be read as a whole)

Start address

Length

FFF0

0008

-16

ISO MDS (my-d SRF55V10P; 992 bytes)

Start address

End address

0000

03DF

+991

ID no.: (fixed-coded; can only be read as a whole)

Start address

Length

FFF0

0008

-16

ISO-MDS (MB 89R118B, 2000 bytes)

Start address

End address

0000

07CF

+1999

ID no.: (fixed-coded; can only be read as a whole)

RF200,

RF300,

MOBY D

Start address

Length

FFF0

0008

-16

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

62 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Address space of the transponder versions for RF300

System Addressing 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

End address

FF00

FF13

-256

-237

ID no.: (fixed-coded; can only be output as a whole)

Start address

Length

FFF0

0008

-16

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

End address

FF00

FF13

-256

-237

R/W memory (FRAM)

Start address

End address

0000

1FFC

+8188

ID no.: (fixed-coded, can only be read as a whole)

Start address

Length

FFF0

0008

-16

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

End address

FF00

FF13

-256

-237

R/W memory (FRAM)

Start address

End address

0000

7FFC

+32764

ID no.: (fixed-coded; can only be output as a whole)

Start address

Length

FFF0

0008

-16

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

End address

FF00

FF13

-256

-237

RF300

R/W memory (FRAM)

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 63

System Addressing 16-bit hexadecimal number Integer number

Start address

End address

0000

FEFC

–

ID no.: (fixed-coded; can only be output as a whole)

Start address

Length

FFF0

0008

-16

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.

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

64 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

FF03 1 .. 17

FF04 1 .. 16 FF84 4,8,12,16

FF05 1 .. 15

FF06 1 .. 14

FF07 1 .. 13

FF08 1 .. 12 FF88 4,8,12

FF09 1 .. 11

FF0A 1 .. 10

FF0B 1 .. 9

FF0C 1 .. 8 FF8C 4,8

FF0D 1 .. 7

FF0E 1 .. 6

FF0F 1 .. 5

FF10 1 .. 4 FF90 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.

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 65

Address space of the transponder/MDS variants for MOBY U

System Addressing 16-bit hexadecimal number Integer number

2 KB data memory

Start address

End address

0000

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

+16

ID no.: (4 fixed-coded bytes; can only be read with the MDS status command)

32 KB data memory

Start address

End address

0000

7FFF

+32767

Read OTP memory (write access only possible once)*

Start address

Length

FFF0

-16

+16

MOBY U

ID no.: (4 fixed-coded bytes; can only be read with the MDS status command)

Examples/applications

6.2 Processing of data memories/transponders

FB 45 for MOBY U, MOBY D, RF200, RF300

66 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 Write

ISO OTP once

MDS D1xx MDS D2xx 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

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.

Examples/applications

6.3 Cyclic calling of FB 45 (e.g. in OB 1)

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 67

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 for 1st reader

memory bit 1.1 is set: Start MOBY command for 2nd reader

memory bit 1.2 is set: Start init_run for 1st reader

memory bit 1.3 is set: Start init_run for 2nd reader

memory byte 2: OB1 used as edge triggered memory

CALL "MOBY FB" , "Instance DB K1"

Params_DB :=45

Params_ADDR:=0

// Call FB 45 for each reader in each

cycle

CALL "MOBY FB" , "Instance DB K2"

Params_DB :=45

Params_ADDR:=50

"Strt_init_run_chn1"

M 2.2

"MOBY DB".SLG1.init_run

x01

// memory bit init_run for 1st reader

"MOBY DB".SLG1.ready

x01

"MOBY DB".SLG1.error

x01

"Strt_cmd_chn1"

M 2.0

"MOBY DB".SLG1.command_start

// memory bit command_start for 1st

reader

x01: A

"Strt_init_run_chn2"

M 2.3

"MOBY DB".SLG2.init_run

x02

// memory bit init_run for 2nd reader

"MOBY DB".SLG2.ready

x02

"MOBY DB".SLG2.error

x02

"Strt_cmd_chn2"

M 2.1

"MOBY DB".SLG2.command_start

// memory bit command_start for 2nd

reader

x02: NOP 0

Examples/applications

6.4 Programming a cold and warm restart

FB 45 for MOBY U, MOBY D, RF200, RF300

68 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

"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.

Examples/applications

6.5 Programming a module failure

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 69

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

-D

SRW

#OB122_MEM_ADDR

"MOBY DB".SLG1.ASM_address

// Temporary OB 122 variable

// Formula:

// (#OB122_MEM_ADDR -

SLG[x].ASM_address) / 2 + 1

==I

JCN

"MOBY DB".SLG1.ASM_channel

// Compare with conf. channel

SET

"MOBY DB".SLG1.ASM_failure

// Power failure on ASM

x1: NOP 0

Network 2: Reset channel 2 when error occurs

-D

SRW

#OB122_MEM_ADDR

"MOBY DB".SLG2.ASM_address

// Temporary OB 122 variable

// Formula:

// (#OB122_MEM_ADDR -

SLG[x].ASM_address) / 2 + 1

==I

JCN

"MOBY DB".SLG2.ASM_channel

// Compare with conf. channel

SET

"MOBY DB".SLG2.ASM_failure

// Power failure on ASM

x2: NOP 0

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.

Examples/applications

6.6 Data structure definition

FB 45 for MOBY U, MOBY D, RF200, RF300

70 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 Name Type Initial value Comment

0.0 STRUCT

+0.0 Reader ARRAY [1..4]

*50.0 UDT10

=200.0 END_STRUCT

Block: DB47; Command

Address Name Type Initial value Comment

0.0 STRUCT

+0.0 Command ARRAY [1..4]

*10.0 UDT20

=40.0 END_STRUCT

Block: DB48; Data

Address Name Type Initial value Comment

0.0 STRUCT

+0.0 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.

Examples/applications

6.6 Data structure definition

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 71

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.

'HFODUDWLRQYLHZ 'DWDYLHZVFKHPDWLF

&KDQQHO>@

&KDQQHO>@

&KDQQHO>@

&KDQQHO>@

FRPPDQG>@

&KDQQHO>@

FRPPDQG>@

7KH5),'FRQWURO

SDUDPHWHUVDQGWKHFRPPDQGV

DVVRFLDWHGZLWKHDFKFKDQQHO

DUHDOODYDLODEOHLQ

DGDWDEORFNIRUDOO5),'

FKDQQHOV

6758&7

FKDQQHO$55$<>@

8'7

6758&7

FRPPDQG$55$<>@

8'7

(1'B6758&7

'% 02%<B'%



FRPPDQGBVWDUW

LQLWBUXQ

FRPPDQGB'%BQXPEHU

FRPPDQGB'%BDGGUHVV

UHDG\

HUURU

FRPPDQG

DGGUHVVB0'6

OHQJWK

7B'%BQXPEHU

7B'%BDGGUHVV

Figure 6-2 Example of when several RFID commands are assigned to one channel

Examples/applications

6.6 Data structure definition

FB 45 for MOBY U, MOBY D, RF200, RF300

72 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

The following shows an extract from a STEP 7 user program. It shows how a large number

of RFID channels can be handled easily using symbolic names. A command is started via

each of the inputs 0.0, 0.1 and 0.3. An edge memory bit is used to prevent the command

from being started several times:

MOBY DB.channel[1].ready // 1st READER

MOBY DB.channel[1].error

I 0.0

Edgememorybit_1

MOBY DB.channel[1].command_start

Edgememorybit_1

I 0.0

Edgememorybit_1

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

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

Examples/applications

6.6 Data structure definition

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 73

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.

UDT 10

STRUCT

command:

ARRAY [1...10]

UDT 20

UDT 10

STRUCT

command:

ARRAY [1...10]

UDT 20

UDT 10

STRUCT

command:

ARRAY [1...10]

UDT 20

DB 45: "Reader 1"

DB 46: "Reader 2"

DB 47: "Reader 3"

Reader 3

Reader 2

Reader 1

ASM_add

Daten [1]

Daten [2]

Daten [3]

Befehl1.

command

Declaration view Data view (schematic)

Figure 6-3 Example of when a separate data block is assigned to each RFID channel

Examples/applications

6.7 The UDTs of FB 45 / FC 45

FB 45 for MOBY U, MOBY D, RF200, RF300

74 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

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

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)

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)

Section "The UDTs

of FB 45 / FC 45

(Page 74)"

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

Examples/applications

6.7 The UDTs of FB 45 / FC 45

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 75

UDT 101: Result of transponder status

Table 6- 3 UDT 101 "MOBY transponder status"

Address Name Type Comment

0.0 STRUCT

+0.0 UID DWORD Tag (unique identifier)

+4.0 MDS_type BYTE Tag

+6.0 sum_subframe_access DINT Sum of subframe access

+10.0 sum_searchmode_access INT Sum of searchmode

+12.0 ST_date_Week BYTE Date of last sleep-time change (week of year)

+13.0 ST_date_Year BYTE Date of last sleep-time change (year)

+14.0 battery_left INT Battery left (percentage)

+16.0 ST BYTE Set Sleep_time value on tag

=18.0 END_STRUCT

UDT 111: Result of reader status (mode 1)

Table 6- 4 UDT 111 "MOBY SLG Status"

Address Name Type Comment

0.0 STRUCT

+0.0 status_info BYTE Reader mode

+1.0 hardware CHAR Type of hardware

+2.0 hardware_version WORD HW version

+4.0 loader_version WORD Version of loader

+6.0 firmware CHAR FW

+8.0 firmware_version WORD Firmware version

+10.0 driver CHAR Type of driver

+12.0 driver_version WORD Version of driver

+14.0 interface BYTE Interface (RS 232/RS 422)

+15.0 baud BYTE Baud rate

+16.0 reserved1 BYTE Reserved

+17.0 reserved2 BYTE Reserved

+18.0 reserved3 BYTE Reserved

+19.0 distance_limiting_SLG BYTE Ranges/performance setting

(RF200/RF300: res.)

+20.0 multitag_SLG BYTE Multitag reader

+21.0 field_ON_control_SLG BYTE BERO operating mode

(RF200/RF300: res.)

+22.0 field_ON_time_SLG BYTE MOBY U: BERO time

MOBY D: transponder type

((RF200/RF300: ISO transponder type)

+23.0 sync_SLG BYTE Semaphore control (synchronization with reader)

(RF200/RF300: res.)

+24.0 status_ant BYTE Status of antenna

+25.0 stand_by BYTE Standby time after a command was executed

(RF200/RF300: res.)

+26.0 MDS_control BYTE Presence

=28.0 END_STRUCT

Examples/applications

6.7 The UDTs of FB 45 / FC 45

FB 45 for MOBY U, MOBY D, RF200, RF300

76 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

UDT 121: Result of reader diagnostics I

Table 6- 5 UDT 121 "MOBY SLG-Stat Diag 1"

Address Name Type Comment

0.0 STRUCT

+0.0 status_info BYTE Reader status mode

+1.0 number_functions BYTE Range: 1...33

+2.0 function_01_01 BYTE *

+3.0 function_01_02 BYTE *

+4.0 function_01_03 BYTE *

=234.0 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 Name Type Comment

0.0 STRUCT

+0.0 status_info BYTE Reader status mode

+1.0 number_errors BYTE Range: 1...235

+2.0 error_number ARRAY [1...235] Error that occurred on the reader

*1.0 BYTE

=238.0 END_STRUCT

UDT 141: Result of reader diagnostics III

Table 6- 7 UDT 141 "MOBY SLG-Stat Diag 3"

Address Name Type Comment

0.0 STRUCT

+0.0 status_info BYTE Reader status mode

+1.0 number_MDS BYTE Range: 1...24

+2.0 UID ARRAY [1...24] identified UID (tag number)

*4.0 DWORD

=98.0 END_STRUCT

Examples/applications

6.7 The UDTs of FB 45 / FC 45

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 77

UDT 231: Result of MDS status (mode 3, RF200, RF300)

Table 6- 8 UDT 231: "MDS status (mode 3, RF300)"

Address Name Type Comment

0.0 STRUCT

+0.0 reserved0 BYTE

+1.0 status_info BYTE Tag status mode

+2.0 UID ARRAY[1...1]

*0.0 STRUCT

+0.0 Byte_1_4 DWORD Tag number (unique identifier)

+4.0 Byte_5_8 DWORD

=8.0 END_STRUCT

+10.0 MDS_type BYTE Tag type

+11.0 IC_version BYTE Chip version (for my-d = 00h)

+12.0 Size WORD Memory size in bytes

+14.0 lock_state BYTE Size of the user memory

+15.0 block_size BYTE EEPROM write-protection status

+16.0 nr_of_blocks BYTE Number of blocks in user memory

=18.0 END_STRUCT

UDT 261: Result of MDS status (mode 1, RF300)

Table 6- 9 UDT 261 "MDS status (mode 1, RF300)"

Address Name Type Comment

0.0 STRUCT

+0.0 reserved0 BYTE

+1.0 status_info BYTE Tag status mode

+2.0 UID ARRAY[1...1]

*0.0 STRUCT

+0.0 Byte_1_4 DWORD Tag number (unique identifier)

+4.0 Byte_5_8 DWORD

=8.0 END_STRUCT

+10.0 MDS_type BYTE Tag type

+11.0 Lock_state BYTE EEPROM write protection status

1RWXVHG

%LW

%ORFN))))

%ORFN))))

%ORFN))))%

%ORFN))&)))

%ORFN))))

:ULWHSURWHFWLRQVWDWXV

 EORFNLVQRWSURWHFWHGUZ

಻ EORFNLVZULWHSURWHFWHGUR

   

Examples/applications

6.7 The UDTs of FB 45 / FC 45

FB 45 for MOBY U, MOBY D, RF200, RF300

78 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Address Name Type Comment

+12.0 reserved1 ARRAY[1...6]

*1.0 BYTE

=18.0 END_STRUCT

UDT 271: Result of MDS status (mode 2, RF300)

Table 6- 10 UDT 271: "MDS status (mode 2, RF300)"

Address Name Type Comment

0.0 STRUCT

+0.0 reserved0 BYTE

+1.0 status_info BYTE Tag status mode

+2.0 UID ARRAY[1...1]

*0.0 STRUCT

+0.0 Byte_1_4 DWORD Tag number (unique identifier)

+4.0 Byte_5_8 DWORD

+8.0 END_STRUCT

+10.0 LFD BYTE Power flux density: Relationship between the

limit value and measured value

+11.0 FZP BYTE Error counter, passive (errors during idle

time)

+12.0 FZA BYTE Error counter, active (errors during

communication)

+13.0 ANWZ BYTE Presence counter

+14.0 reserved1 ARRAY[1...3]

*0.0 BYTE

=18.0 END_STRUCT

UDT 281: Result of read/write status (mode 6, RF300)

Table 6- 11 UDT 281 "Reader status (mode 6, RF300)"

Address Name Type Comment

0.0 STRUCT

+0.0 status_info BYTE Reader status mode

+1.0 FZP BYTE Error counter, passive (errors during idle time)

+2.0 ABZ BYTE Abort counter

+3.0 CFZ BYTE Code error counter

+4.0 SFZ BYTE Signature error counter

+5.0 CRCFZ BYTE CRC error counter

+6.0 BSTAT BYTE Current command status

+7.0 ASMFZ BYTE Interface error counter for CM

+8.0

+26.0

res. BYTE Reserved

=28.0 END_STRUCT

Examples/applications

6.8 Determing the memory requirement in the SIMATIC

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 79

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 Total

FB 45 (needed once)

Instance DB

Parameter data block (UDT 10)

Command data block (UDT 20)

DB for tag data

–

0,45

0,1

0,01

9,1

0,2

Total 1,56 39,2

In this configuration, a SIMATIC CPU with only 48 KB memory can reach the memory limits

quickly if further programs are also running.

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

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

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

಻PDVWHUPRGXOH

಻HJ6&38

352),%86352),1(7

FDEOHWRDOO

352),%86352),1(7

VODYHV

9IRU5)&

DQGUHDGHU

,QWHUIDFHPRGXOH

಻RIWKH(7SUR

5HDGHU

7UDQVSRQGHU

5)&

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.

Brief description of the hardware

A.1 RF170C

FB 45 for MOBY U, MOBY D, RF200, RF300

82 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 Value Note

FB 45 / FC 45 Default

FB 55 / FC 55 -

FB 56 / FC 56 -

USER_Mode

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_Mode

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)

Baud rate reader

115.2 kBd MOBY U/D / RF200 / RF300 1)

None Standard diagnostics only Diagnostics with diagnostics

messages Hard errors Hardware-related messages

only

1) 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)".

Brief description of the hardware

A.1 RF170C

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 83

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 Meaning

SF 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 * Indicates the presence of a transponder.

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.

Brief description of the hardware

A.1 RF170C

FB 45 for MOBY U, MOBY D, RF200, RF300

84 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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 Description

Off Off Off On Off Off Off Start-up active

On Off On Off Off Off Off Checksum error at start-up *

On Off Off Off Off On Off Firmware invalid *

On On On On On On On LED test for approximately 4 seconds;

otherwise firmware fault *

On Off 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













+24 V

–RxD

0 V

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.

Brief description of the hardware

A.2 RF180C

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 85

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

HJ6&38

352),1(7,2FDEOH

9IRU5)&

DQGUHDGHU

WRIXUWKHU

352),1(7,2QRGHV

5HDGHU

7UDQVSRQGHU

5)&

;

;

Figure A-3 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.

Brief description of the hardware

A.2 RF180C

FB 45 for MOBY U, MOBY D, RF200, RF300

86 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

The table below shows the possible settings:

Table A- 5 Setting of RFID-relevant parameters

Parameter name Value Note

FB 45 Default

FB 55 for multitag applications

FB 56 With later firmware version

USER_Mode

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

MOBY_Mode

RF300 Filehandler -

19.2 kBd MOBY U/D / RF200 / RF300

57.6 kBd MOBY U/D / RF200 / RF300 1)

Baud rate reader

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

Diagnostics with

diagnostics messages

Hard/soft errors high priority All messages high-priority

1) 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

Brief description of the hardware

A.2 RF180C

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 87

Diagnostics using LEDs

The following figure shows details of the LEDs of the RF180C.

[ [

[ [

/LQN 5;7;

;

[ [

[ [

;

6) %) 21 '&9

;

;

*7-' *7-'

6,0$7,&5)&

6,0$7,&5)&

$&7B 35(B

5['B (55B

$&7B 35(B

5HDGHU

5HDGHU

5['B (55B

Figure A-4 LEDs of the RF180C

Table A- 7 Status LEDs for the RF180C

LEDs Meaning

ON Lights up when the RF180C has completed start-up without errors.

24 V DC Lights up when the 24 V supply voltage is connected to the RF180C.

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.

Brief description of the hardware

A.2 RF180C

FB 45 for MOBY U, MOBY D, RF200, RF300

88 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Table A- 8 LED display for PROFINET diagnostics

BF SF Cause of error Error correction

On – • Communication module is in start-

up mode.

• No cable inserted

When the bus is configured correctly, this state ends a

few seconds after switching the module on.

Flashes - • 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")

Off On • A PROFINET diagnostic signal

exists.

• Analyze the diagnostic data.

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 ACT_1 PRE_2 ERR_2 ACT_2 Description

Off Off Off Off Off Off Off Off Off Start-up active

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

Off Off Slow

flashin

Off Firmware update

(flashes with every described area)

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 89

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

಻PDVWHUPRGXOH

಻HJ6&38

352),%86FDEOH

9IRU$60

DQGUHDGHU

WRIXUWKHU

352),%86QRGHV

5HDGHU

7UDQVSRQGHU

$60

;

;

Figure A-5 ASM 456 configurator

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

90 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Design

The ASM has a connection block for connecting up to the PROFIBUS DP which is available

as an option and the ECOFAST version or M12, 7/8".

The following figure shows the basic design of the ASM 456.

&RQQHFWLRQVRFNHWIRUVWUHDGHU

6WDWXV/('VIRURSHUDWLRQRIWKHQGUHDGHU

6WDWXV/('VIRULQWHUIDFHPRGXOH

6WDWXV/('VIRURSHUDWLRQ

RIWKHVWUHDGHU

&RQQHFWLRQVRFNHWIRUQGUHDGHU

6SDFHIRUFRQQHFWLRQEORFN

3URWHFWLYHHDUWK

;

;

*7('

02%<$60

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"

the directory "daten\PROFI_GSD\ASM456".

For full functionality (diagnostics texts, firmware update), support for GSD revision 5 or

higher is required.

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 91

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 Value Note

FB 45 / FC 45 Default

FB 55 / FC 55 -

FB 56 / FC 56 -

USER_Mode

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)

MOBY_Mode

RF300 Filehandler -

19.2 kBd MOBY U/D / RF200 / RF300

57.6 kBd MOBY U/D / RF200 / RF300 1)

Baud rate reader

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

Diagnostics with diagnostic

messages (see Section

"Error messages and

troubleshooting" )

Hard/soft errors high priority All messages high-priority

1) 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)".

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

92 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

The following figure shows details of the LEDs of the ASM 456.

352),%86

6) %) 21 '&9

;

;

*7('

02%<$60

$&7B 35(B

5['B (55B

$&7B 35(B

5HDGHU

5['B (55B

5HDGHU

Figure A-7 LEDs of the ASM 456

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 93

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 * 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.

Table A- 14 LED display for PROFIBUS diagnostics

BF SF 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

On –

• Bus interrupt

• DP Master not functioning

• Check all cables on your

PROFIBUS DP network.

• Check whether the connector

plugs for the PROFIBUS DP are

securely plugged into the ASM.

Flashes On • The project data sent to the ASM by

the DP Master do not match the

configuration of the ASM.

• Check the project for the ASM

(input/output, PROFIBUS

address).

• Correct GSD file being used?

Flashes – • ASM has detected the baud rate, but

is not activated by the DP Master.

• ASM has not been assigned project

plans.

• Check the PROFIBUS address set

in ASM and/or in the project

software.

• Check the project for the ASM

(station type).

On Flashe

• 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:

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

94 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

ON SF PRE_1 ERR_1 ACT_1 PRE_2 ERR_2 ACT_2 Description

On Off Off Off On Off Off Off Start-up active

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 Connection assignment for ECOFAST connector plugs

Pin 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)

2 Ground for electronics/encoder supply

(1M)

3 Load voltage ground (2M)

4 Load voltage supply (2L+)

(unused on ASM 456)





/

/

6LJQDO$

6LJQDO%

(&2)$67K\EULGFDEOH

*) You will find the assembly instructions in the packaging of the Han Brid Cu cable connector

and/or Han Brid Cu cable socket.

Brief description of the hardware

A.3 ASM 456

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 95

Table A- 16 Connection assignment for M12 connector (PROFIBUS DP)

Pin Assignment View of M12 connector

(wiring side)

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 Shield



















6LJQDO$JUHHQ

6LJQDO%UHG

6KLHOG

6XSSO\'3

6LJQDO$JUHHQ

6LJQDO%UHG

6KLHOG

%XVFDEOH

FRUHVKLHOGHG

/RRSWKURXJK

FRQQHFWLRQ'3

*) 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 View of 7/8" connector

(wiring side)

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)



















/

/

/

/

6XSSO\;

FRUHFDEOH

/RRSWKURXJK

FRQQHFWLRQ;

Brief description of the hardware

A.4 ASM 475

FB 45 for MOBY U, MOBY D, RF200, RF300

96 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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'3಻PDVWHU

PRGXOH

಻HJ6ZLWK$60

5HDGHU

7UDQVSRQGHU

$60

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

Brief description of the hardware

A.4 ASM 475

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 97

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.

Status and error LEDs Reader connector diagram

The numbers for the

connector relate to

connector X1 of the

top part of the housing

T+

T-

R+

R-

T+

T-

R+

R-

ASM475

Reader 1Reader 2

DC5 V

ACT_1

ERR_1

PRE_1

RxD_1

ACT_2

ERR_2

PRE_2

RxD_2

6GT2 002-0GA10

MOBY

Table A- 19 Status LEDs for ASM 475

LEDs Meaning

SF System fault (hardware error on ASM)

5 V DC 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.

Brief description of the hardware

A.4 ASM 475

FB 45 for MOBY U, MOBY D, RF200, RF300

98 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

The following ASM states are indicated with the LEDs PRE, ERR and SF.

SF PRE_1 ERR_1 PRE_2 ERR_2 Description, Causes, Remedy

OFF

any

OFF

OFF/ON

OFF

2 Hz

5 Hz

OFF

ON (perm.)

OFF

2 Hz

5 Hz

1x flash

every 2 s

OFF/ON

OFF

2 Hz

5 Hz

OFF

ON (perm.)

OFF

2 Hz

5 Hz

1x flash

every 2 s

Hardware is defective (RAM, Flash, …)

Loader is defective (can only be fixed at

the plant).

Firmware loading process is active

and/or no firmware detected

→ load firmware

→ do not switch off ASM during this

process

Loading of firmware aborted due to error

→ restart needed

→ reload firmware

→ check update files

Operating system error

→ switch ASM off/on

ASM has booted and is waiting for a

RESET (init_run) from the user.

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 99

Programming communications modules B

B.1 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_).

Programming communications modules

B.1 Programming the communication modules on PROFIBUS/PROFINET

FB 45 for MOBY U, MOBY D, RF200, RF300

100 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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),%86352),

1(7PDVWHUPRGXOH

IXUWKHUILHOGGHYLFHV

352),%86352),1(7





$60

5)& 

$60

5)&

① 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.

Programming communications modules

B.1 Programming the communication modules on PROFIBUS/PROFINET

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 101

Principle of controlling non-cyclic communication with command and acknowledgment counter

&RPPDQGFRXQWHU $FNQRZOHGJHPHQWFRXQWHU

6WDWXVRIFRXQWHUVDIWHU&0VWDUWXSRUDIWHUDQLQLWBUXQB

&RPPDQG

UHDG\

DFWLYH

DFWLYH &RPPDQG

UHDG\

&RPPDQG

UHDG\

&RPPDQG

UHDG\

DF\FOIUDPH

















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.

Programming communications modules

B.2 Cyclic control word between master and communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

102 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

6WDUWXSRI352),%86352),1(7

PDVWHU

7KLVELWIRUFHVD&0

VWDUWXS%LWLVWKHQVHWLQWKH

SHULSKHUDOLQSXW



UHVHUYHGIRU'$

UHSHDWBFRPPDQGB

FRPPDQGUHSHWLWLRQ

RSWLRQDO

FDQFHOB

XQXVHG

 

Figure B-2 Structure of the cyclic control word: Peripheral output

Programming communications modules

B.2 Cyclic control word between master and communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 103

Cyclic word from communications module: I/O input





&RPPDQGFRXQWHUKLJKHUELW&+

&RPPDQGFRXQWHUORZHUELW&/

6WDUWXSPHVVDJH

7KLVELWVKRZVWKDWWKH&0KDVVWDUWHGXS

$1=BUHVHWB

:KHQLQLWBUXQBLVUHVHWWKH02%<&0FDQFHOV

WKLVELWDJDLQ2WKHUFRPPDQGV

H[FHSWIRU5(6(7RUDQLQYDOLG5(6(7FRPPDQG

DUHWKHQUHMHFWHGZLWKDQHUURU

PHVVDJH

$FNQRZOHGJHPHQWFRXQWHUKLJKHUELW$+

$FNQRZOHGJHPHQWFRXQWHUORZHUELW$/

5HVHUYHG

6/*BHUURU

WKHFRQQHFWLRQWRWKHUHDGHULV

LQWHUUXSWHG

$1=BFDQFHOB

FDQFHODFNQRZOHGJPHQWXQXVHG

0'6BSUHVHQFHB

FKDQJHGB

ZLWK)&)%

XQXVHG

QXPEHUB0'6B

$1=B0'6B

SUHVHQWB

SUHVHQFH

FRPPDQGBUHSHDWBDFWLYHB

7KLVELWLVWKHFRQILUPDWLRQPLUURULQJRI

UHSHDWBFRPPDQGB,WLVXVHGIRULQIRUPDWLRQ

DQGHUURUDQDO\VLV%HWZHHQVHWWLQJ

UHSHDWBFRPPDQGBDQGUHDGLQJRXWWKHVHW

FRPPDQGBUHSHDWBDFWLYHBELWVWKH

FRPPDQGUHSHWLWLRQKDVEHHQVWDUWHG

RQWKH&0

$60BEXV\B

QRWFXUUHQWO\XVHGIDOVH

 

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):

6WDUWXS QG

FRPPDQG

UG

FRPPDQG

DIWHU

FRPPDQG

EHIRUH

DFNQRZOHGJHPHQW

EHIRUH

FRPPDQG

EHIRUH

DFNQRZOHGJHPHQW

EHIRUH

FRPPDQG

5(6(7

VWFRPPDQG

              





Programming communications modules

B.2 Cyclic control word between master and communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

104 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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_).

5(6(7FRPPDQG

WRWKH&0

5(6(7DFNQRZOHGJ

PHQWIURPWKH&0

$F\FOLF

IUDPH

&&$&

DQ\

,IDFRPPDQGZDVLQWHUUXSWHGE\

5(6(7RU಻LQLWBUXQBHUURU

PHVVDJH಻)LVWULJJHUHGKHUH

UHDG\ UHDG\PHVVDJHLQXVHUSURJUDP

&& $& 

GHILQHGUHVHW

UHDG\

%=  4= 

LQLWBUXQB

$1=BUHVHWB

Figure B-4 Power-up timing initiated by user

ณณ

ณณ 5(6(7FRPPDQG

WRWKH&0

5(6(7DFNQRZOHGJ

PHQWIURPWKH&0

$F\FOLF

IUDPH

UHDG\ UHDG\PHVVDJHLQXVHUSURJUDP

UHDG\

%=  %=  %=  4= 

LQLWBUXQB

$1=BUHVHWB

Figure B-5 Startup timing of the CM initiated by power down

Programming communications modules

B.3 Methods of operation with the communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 105

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

313%PDVWHU &0

7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH

$VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU

&KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

&KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

1RFKDQJHWRF\FOLFGDWD

&RPPDQG

$FNQRZO

HGJH

7LPHD[LV

&RPPXQL

FDWLRQ

GLUHFWLRQ

([HFXWLRQRI

VWFRPPDQG

&RPPXQLFDWLRQ

ZLWKWKHWDJ

$FNQRZO

HGJH

([HFXWLRQRI

QGFRPPDQG

&RPPDQG

&RPPXQLFDWLRQ

ZLWKWKHWDJ

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.

Programming communications modules

B.3 Methods of operation with the communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

106 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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:

313%PDVWHU &0

7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH

$VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU

&KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

&KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

1RFKDQJHWRF\FOLFGDWD

7LPHD[LV

VW

FRPPDQG

QG

FRPPDQG

UG

FRPPDQG

([HFXWLRQRI಻VWFRPPDQGRQWKH&0

([HFXWLRQ

RIQGFRPPDQG

RQWKH&0

([HFXWLRQ

RIUGFRPPDQG

RQWKH&0

7UDQVIHURIFRPPDQGVRQWKH&0

7UDQVIHURIQG

UHVXOW

7UDQVIHURIUG

UHVXOW

7UDQVIHURIVW

UHVXOW

&RPPXQL

FDWLRQ

GLUHFWLRQ

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)".

Programming communications modules

B.3 Methods of operation with the communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 107

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:

7LPHD[LV

6LQJOH

SURJUDPPLQJ

RI&0

DVDOUHDG\

GHVFULEHGHDUOLHULQ

WKLV

VHFWLRQ

6ORZWDJVHTXHQFH

$IWHU

$1=B0'6BSUHVHQWB 

WKHFRPPDQGLV

UHVWDUWHGLPPHGLDWHO\

&RPPDQGKDVEHHQ

SURFHVVHG

DFNQRZOHGJPHQW

FRXQWHULV

LQFUHPHQWHGDQGWKH

UHVXOWLV

WUDQVIHUUHG

)DVWWDJVHTXHQFHWKH

GDWDLVWUDQVIHUUHG

VORZHUWKDQWKHQHZ

WDJVDUHSURFHVVHG

7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH

$VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU

&KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V

UHWDLQVWKHVDPHFRXQWHUYDOXH

&KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

1RFKDQJHWRF\FOLFGDWD

&RPPXQLFDWLRQGLUHFWLRQ

&RPPDQGKDVEHHQ

SURFHVVHG

DFNQRZOHGJPHQW

FRXQWHULV

LQFUHPHQWHGDQGWKH

UHVXOWLV

WUDQVIHUUHG

313%

PDVWHU &0

UHSHDWBFRPPDQGB

$1=B0'6BSUHVHQWB

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: Ⓑ).

Programming communications modules

B.3 Methods of operation with the communications module

FB 45 for MOBY U, MOBY D, RF200, RF300

108 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

In this case, the command_repeat_active_ bit must be scanned to make sure the command

repetition was accepted.

7LPHD[LV

6LQJOH

SURJUDPPLQJ

RIWKH&0

DVDOUHDG\

GHVFULEHGHDUOLHULQ

WKLVFKDSWHU

&RPPDQGKDVEHHQ

SURFHVVHG

DFNQRZOHGJPHQWFRXQWHU

LVLQFUHPHQWHGDQGWKH

UHVXOWLVWUDQVIHUUHG 7ULJJHUVLJQDOIRU

DFRPPDQGVWDUW

$1=B0'6BSUHVHQWBൺ

8VHUVWDUWVZLWK

UHSHDWBFRPPDQGB 

+DQGVKDNH

VHTXHQFHVRWKDW

FRPPDQG

SURFHVVLQJ

LVJXDUDQWHHG

7KHDSSOLFDWLRQ

LVZDLWLQJKHUH

IRUWKHQH[W

WDJ

3URFHVVLQJVHTXHQFH

IRUDIXUWKHU

WDJ

&RPPXQLFDWLRQ

GLUHFWLRQ

7KHFRPPDQGDQGDFNQRZOHGJHPHQWIUDPHLVDQDF\FOLFIUDPHZLWKDF\FOLFUHVSRQVH

$VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU

&KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V

UHWDLQVWKHVDPHFRXQWHUYDOXH

&KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

1RFKDQJHWRF\FOLFGDWD

&RPPDQGKDVEHHQSURFHVVHG

DFNQRZOHGJPHQWFRXQWHU

LVLQFUHPHQWHGDQGWKH

UHVXOWLVWUDQVIHUUHG

313%

PDVWHU &0

UHSHDWBFRPPDQGB

$1=B0'6BSUHVHQWB

FRPPDQGBUHSHDWBDFWLYHB

Figure B-9 Focused command repetition

Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 109

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.

UHV UHV UHV

&RPPDQG

6WDWXV &RPPDQGVSHFLILFGDWD

%\WH

7KHFRPPDQGVSHFLILFGDWDLVGHVFULEHGLQGHWDLORQWKHIROORZLQJSDJHV

7KHPLQOHQJWKLVWKHPD[GDWDOHQJWKLV E\WHV

7KHVWDWXVE\WHDOZD\VKDVWKHYDOXHZKHQDFRPPDQGLVLVVXHG

,QWKHUHVXOWRUHUURUIUDPHWKHE\WHKDVWKHIROORZLQJPHDQLQJ

7KHLPSOHPHQWHGFRPPDQGVDUHGHVFULEHGRQWKHIROORZLQJSDJHV

*HQHUDOFRPPDQGIRUPDW

1XPEHURIE\WHV

Q WRWDOQXPEHURIE\WHVLQIUDPH$%E\WHLVQRWFRXQWHG

PLQLPXP$% 

PD[LPXP$% PD[LPXPOHQJWKIRU352),%86'39LVE\WHV

(UURUFRGH)

%LW

'HWDLOHGHUURUGHVFULSWLRQVHHVHFWLRQ

(UURUFRGH)DFFRUGLQJWRWDEOHEHORZ

 FKDLQHGFRPPDQG

 UHVHUYHGIRUV\VWHPIXQFWLRQVHJILUPZDUHXSGDWH

7KHOHQJWKVSHFLILHGKHUHLVWKHPD[LPXPOHQJWKIRU352),%867KH$60

LVDQH[FHSWLRQZLWKDOHQJWKE\WHVKRUWHUPD[GDWDOHQJWK FRPPDQGVSHFLILFGDWD 

    Q



















Figure B-10 General frame format

Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

110 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Command table

Comma

code

[hex]

Comman

code

chained

[hex]

Command Description

0 – RESET CM is reset. The active command is terminated.

(If a tag command was terminated with RESET, the reset acknowledgment reports

error 1F.)

The RESET command can be used to switch the CM to various operating modes.

1 41 WRITE Write data block to transponder

2 42 READ Read data block from transponder

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

3 43 INIT

2 KB

32 KB

44 bytes

112 bytes

256 bytes

996 bytes

2000 bytes

20 bytes

8 KB

32 KB

64 KB

RAM

I-Code

I-Code SLI

Tag-it HF-I

my-d

FRAM

EEPROM

FRAM

(MOBY U)

(MOBY D)

(RF300)

approx. 1 s

approx. 1.5 s

approx. 0.4 s

approx. 0.5 s

approx. 1 s

approx. 3 s

approx. 0.2 s

0.9 s

3.6 s

7.2 s

00 08 00

00 80 00

00 00 2C

00 00 70

00 01 00

00 04 00

00 07 D0

00 00 14

00 20 00

00 80 00

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 MOBY U/D, RF200 or RF300 only:

This command turns the antenna field on the reader off and on again.

B 4B MDS-STATUS Returns the properties of the transponder in the result

Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 111

Exact frame format

6WDUWXS

7KHVWDUWXSRIWKH&0LVRQO\

VLJQDOHGWRWKHXVHUYLDWKH

F\FOLFZRUGVHH$SSHQGL[

%

6WDW3DUDPVWDQGE\ 9HUV+ 9HUV/ 5HVGLOL IFRQ IWLP$    



%LW

&RPPDQG

FRGH

&RPPDQGIUDPH

WRWKH&0UHDGHU

5HVXOWIUDPH

IURPWKH&0UHDGHU

5(6(7

)LUPZDUHYHUVLRQLQ&0

YHUVLRQB02%<

GLVWDQFHBOLPLWLQJB5DQJHOLPLWDWLRQVHHLQSXWSDUDPHWHU

$)(KH[ P

$)($KH[ VDPHZLWKUHGXFHGRXWSXWSRZHU

5)

GLVWDQFHBOLPLWLQJRQO\IRU5)5FKDQJHRIRXWSXWSRZHU

KH[ : KH[ :

KH[ : KH[ :

KH[ : KH[ :

KH[ :

5)UHVHUYHGKH[

02%<8

02%<'+)SRZHUVHHLQSXWSDUDPHWHU

ILHOGB21BWLPHBVHHLQSXWSDUDPHWHU

KH[ ZLWKRXW%(52V

KH[))KH[ V7XUQRQWLPH

IRUWKHWDJILHOG

02%<8

02%<'

7DJW\SHVHHLQSXWSDUDPHWHU

KH[ ,FRGH]%0'6'

KH[ ,620'6

KH[ 'XDOGULYHU,&RGHDQG,62

KH[ 0'6'RSWLPL]DWLRQRQO\ZLWK

6/*'6

KH[ 0'6'[[RSWLPL]DWLRQRQO\ZLWK

6/*'66

5)

ILHOGB21BWLPHVHHLQSXWSDUDPHWHU

KH[ 5)0RGHQR,62

KH[ ,62WDJ

KH[ ,62P\G,QILQHRQ65)93

KH[ ,62)XMLWVX0%5

KH[ ,62,&RGH6/,1;36/,&6

KH[ ,627DJLW+),7H[DV,QVWUXPHQWV

KH[ ,6267/5,.

5)KH[ ,627DJ

2SWLRQ02%<5)RU5)

 QRWXVHG

 5HVHW(55/('DW&0DQG5HDGHU

 'RQಬWUHVHW(55/('DW&0DQG5HDGHU

 QRWXVHG

 0XOWLWDJZLWK%\WH8,'

 0XOWLWDJZLWK%\WH8,'

3UHVHQFHFKHFNDQGWDJFRQWURO0'6BFRQWUROB

 QR$1:FRQWURO

 QRWDJFRQWURO$1:FKHFNRYHU

ILUPZDUHGHIDXOW

UHV

VFDQQLQJBWLPHB6WDQGE\WLPHIRUWKHWDJVHHLQSXWSDUDPHWHU

KH[ QRVWDQGE\RSHUDWLRQ

KH[&KH[ PVPVVWDQGE\WLPH

02%<'5)5)QRWXVHGKH[

02%<8

PXOWLWDJ

02%<8

ILHOGB21BFRQWUROVHHLQSXWSDUDPHWHU

%(52PRGH

KH[ RKQH%(52VQR6/*V\QFKURQL

]DWLRQ

KH[ ILHOGB21BWLPHVZLWFKHVWKHILHOG

RII

KH[ %(52VZLWFKHVWKHILHOGRQ

%(52VZLWFKHVWKHILHOGRII

KH[ $FWLYDWHZULWHUHDGGHYLFH

V\QFKURQL]DWLRQYLDFDEOHFRQQHFWLRQVHH

PDQXDOIRUFRQILJXULQJPRXQWLQJDQG

VHUYLFHIRU02%<8

02%<'5)5)QRWXVHGKH[

([SHFWHGQXPEHURIWDJVLQ

ILHOG







Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

112 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

$GGUHVV

&RPPDQG

FRGH

&RPPDQGIUDPH

WRWKH&0UHDGHU

5HVXOWIUDPH

IURPWKH&0UHDGHU

$GGUHVV

,1,7

SDWWHUQ

$% /1* ''Q

06% /6%

$% /1* ''Q

06% /6%

/1*

06% /6%

(QGDGGU

06% /6%

&RP )DXOW

,IDQHUURURFFXUVWKHUHVXOWIUDPHKDVWKHIROORZLQJVWUXFWXUH

7KH$%E\WHFDQVWRUHDYDOXH!IRUWKHUHDGFRPPDQG

,QWKLVFDVHWKHGDWDLVRQO\SDUWLDOO\FRUUHFWDQGPXVWEHGLVFDUGHG

DYRLGHG

7KHVWDWXVE\WHLQWKHUHVXOWIUDPHGHSHQGVRQWKHWDJW\SHEDWWHU\VWDWHV

''Q

/1*

$GGUHVV

,1,7SDWWHUQ

(QGDGGU

8VHUGDWDRIXVHUWRIRU$60WR

/HQJWKRIWKHGDWDEORFN''Q

1RWHDGGUHVV/1*PXVWEHVPDOOHUWKDQWKHHQGDGGUHVVRIWKHWDJ

6WDUWDGGUHVVRIWKHGDWDWREHSURFHVVHGRQWKHWDJ

06% PRVWVLJQLILFDQWDGGUHVVSDUW

/6% OHDVWVLJQLILFDQWDGGUHVVSDUW

1XPEHURIWKHIROORZLQJFKDUDFWHUVLQWKHIUDPH

$% /1*

1RWH$%PXVWQRWEHJUHDWHUWKDQWKHEXVFRQILJXUDWLRQ

7KHYDOXH,QLWSDWWHUQLVZULWWHQWRWKHWDJGXULQJLQLWLDOL]DWLRQ

0HPRU\VL]HRIWKHWDJ

0HDQLQJ



,1,7



5($'



:5,7(  &











&







 





&







  









Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 113

6WDW

PD[

6WDW

PD[

6WDW

QWK

WUDQVSRQGHU

PD[

6WDW IRUH[SHUWVRQO\

KH[KH[  PD[PHVVDJHIUDPHV

  DUHWUDQVIHUUHG

6/*VWDWXV

'LDJQRVWLFVGDWD

&RPPDQG

FRGH

&RPPDQGIUDPH

WRWKH&0UHDGHU

5HVXOWIUDPH

IURPWKH&0UHDGHU

PRGH UHDGHUGLDJQRVWLFV,9

 &RPPXQLFDWLRQTXDOLW\

PRGH UHDGHUGLDJQRVWLFV

PRGH UHDGHUGLDJQRVWLFV,,,

 LGHQWLILHGWDJ

PRGH UHDGHUGLDJQRVWLFV,,

 HUURUPHVVDJHV

PRGH UHDGHUGLDJQRVWLFV,

 IXQFWLRQFDOOV

PRGH 6/*VWDWXVDOO

 5)SURGXFWV

7KHPHDQLQJRIWKH6/*VWDWXV

LVGHVFULEHGLQ8'7

VW

FRPPDQG

)UDPHKHDGHUV

RIWKHFRPPDQGV

WKDWZHUHH[HFXWHGODVW

QWK

FRPPDQG

VWHUURU

,QGLFDWHVODVW

HUURUWKDWRFFXUUHG

QWKHUURU

KH[(%KH[  PD[HUURU

  PHVVDJHV

VW

WUDQVSRQGHU

,'VRIWKHWUDQVSRQGHU

ODVWGHWHFWHGLQWKH

WUDQVPLVVLRQ

ZLQGRZ

KH[KH[  PD[WUDQVSRQGHU,'V



UHDGHU

VWDWXV

7KHPHDQLQJVRIWKHGLDJQRVWLFVGDWDDUHGHVFULEHG

LQ8'7

UHV UHV UHV 

 PRGH



02%<8

02%<8

    

%  

    

$%   Q

 

$%   Q

    

$%   Q

$%  

$%   Q

02%<8

5)

Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

114 Function Manual, 07/2012, J31069-D0166-U001-A4-7618



(1' PRGH

6WDW

&RPPDQG

FRGH

&RPPDQGIUDPH

WRWKH&0UHDGHU

5HVXOWIUDPH

WRWKH&0UHDGHU

 3URFHVVLQJZLWKWUDQVSRQGHULV

FRPSOHWHG

 3URFHVVLQJSDXVHZLWKWUDQVSRQGHU

(QG6FDQQLQJBWLPHIRU

WKH02%<8WUDQVSRQGHU

LPPHGLDWHO\

PRGH

 6ZLWFKRQDQWHQQD

 6WDQGE\VZLWFKRIIDQWHQQD

$$

6(7

$17

6WDW

  

  

 $ 

$  $

$

Programming communications modules

B.4 Command and acknowledgement telegrams

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 115

7DJ

7\SH 'LDJQRVWLFVGDWD

'LDJQRVWLFVGDWD

E\WHWDJ,'QXPEHU

XQLTXHLGHQWLILHU

&RPPDQG

FRGH

&RPPDQGIUDPH

WRWKH&0UHDGHU

5HVXOWIUDPH

IURPWKH&0UHDGHU

ZHHN  &DOHQGDU

 ZHHN

 KH[

 KH[

 VWWR

 QGZHHN

\HDU  \HDU

  

&XUUHQWGDWH

ZHHN  

\HDU  

1RWUHOHYDQW

ZHHN  

\HDU  

1RWUHOHYDQW

E\WHWDJ,'QXPEHU 7KHPHDQLQJRIWKH

GLDJQRVWLFVGDWDLV

GHVFULEHGLQ8'7

7KHPHDQLQJRIWKH

GLDJQRVWLFVGDWDLV

GHVFULEHGLQ8'7

7KHPHDQLQJRIWKH

GLDJQRVWLFVGDWDLV

GHVFULEHGLQ8'7

%%

0'6

VWDWXV

'LDJQRVWLFVGDWD

ZHHN  

\HDU  

1RWUHOHYDQW

7KHPHDQLQJRIWKH

GLDJQRVWLFVGDWDLV

GHVFULEHGLQ8'7

'LDJQRVWLFVGDWD

PRGH 02%<8

PRGH 5)

PRGH 5)

PRGH 5)

5),6202%<'

    

 %

     

 % 

     



8,' % 

8,'

6WDW

  \HDUZHHN

% PRGH

%

     

8,' % 6WDW

Programming communications modules

B.5 PROFIBUS/PROFINET implementation

FB 45 for MOBY U, MOBY D, RF200, RF300

116 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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.

HJ$60

&RPPXQLFDWLRQPRGXOH

'6[

SDUDPHWHUV

'6[

GDWD

&RPPDQGV

'DWD

DFNQRZO

HGJPHQWV

)XQFWLRQ

EORFN

,QWHUIDFHWRXVHU

0'6

GDWD

02%<

GULYHU

6HTXHQFH

FRQWURO

[ FKDQQHO

Q QRRIFRPPDQGRQ&0QPD[ QXPEHURIEXIIHUVRQ&0VHHVHFWLRQ&RPPDQGUHSHWLWLRQ

 6,0$7,&6XVHV6$3DQG6$3IRUDF\FOLFFRPPXQLFDWLRQ

 7KHWUDQVIHURIWKHFRQWUROZRUG34:3,:XVHVWKHF\FOLFGDWDBH[FKDQJHVHUYLFH

 RI352),%866$3  1,/

%XV

$60BDGGUHVV

$60BFKDQQHO

0'6BFRQWURO

02%<BPRGH

VFDQQLQJBWLPH

3(:[

3$:[

3(:[

3$:[ 6$31,/

6$31,/

6$3

'6[Q

'6[

'6[

'6[

Programming communications modules

B.5 PROFIBUS/PROFINET implementation

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 117

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.

)XQFWLRQFRGHHJ'6B5HDGUHT

,QGH[ฬ GDWDUHFRUGQXPEHUIRUFKDQQHOV

 WRVHHWDEOHEHORZ

'DWDOHQJWK

6ORWB1XPEHU$605)& 

$60 WRFRUUHVSRQGVWRWKH

VORWLQDQ

(70

5)& WRFRUUHVSRQGVWRWKH

VORWLQDQ

(7SUR

 5HTXHVW5HVSRQVHRND\

 5HVSRQVH(UURU)UDPH

6' /( /(U 6' '$ 6$ )& '6$3 66$3 '8 )&6 ('

+ [ [ + [ [ [ + + [ [ +





%\WH

%\WH

%\WH

%\WH

The following data records are implemented on the CM for communication.

Programming communications modules

B.5 PROFIBUS/PROFINET implementation

FB 45 for MOBY U, MOBY D, RF200, RF300

118 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

Table B- 1 Data record numbers (index)

Data record

number

Exist on

CM/reader

Description

101

102

103

104

all

Parameter assignment channel 1

Parameter assignment channel 2

Parameter assignment channel 3

Parameter assignment channel 4

111

112

113

114

all

Data transmission channel 1

Data transmission channel 2

Data transmission channel 3

Data transmission channel 4

121

122

150

151

180

ASM 456, RF160C, (RF170C),

RF180C

ASM 456, RF160C, (RF170C),

RF180C

ASM 475

RF180C

System command to reader

(in preparation for RF170C)

System command to reader

(in preparation for RF170C)

Reserved (diagnosis of powerparameters)

Reserved (diagnostic buffer)

reserved

231

232

233

234

RF170C

I&M0

I&M1

I&M2

I&M3

239

246

247

248

255

ASM 456, ASM 475, RF160C,

RF170C, RF180C

ASM 475

(ASM 456, RF160C)

ASM 475, RF170C, (ASM 456,

RF160C)

ASM 456, RF160C

Firmware update

SSL reserved

System: SSL processing I&A

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).

Programming communications modules

B.6 Example of a PROFIBUS Trace

FB 45 for MOBY U, MOBY D, RF200, RF300

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 119

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

Programming communications modules

B.6 Example of a PROFIBUS Trace

FB 45 for MOBY U, MOBY D, RF200, RF300

120 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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

Function Manual, 07/2012, J31069-D0166-U001-A4-7618 121

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/support-

request)

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).

Service & Support

FB 45 for MOBY U, MOBY D, RF200, RF300

122 Function Manual, 07/2012, J31069-D0166-U001-A4-7618

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).