Manual FB45 PDF

Introduction 1
Description 2
Parameterizing 3
SIMATIC Sensors
Commissioning 4
RFID systems Error messages and
FB 45 troubleshooting 5
Examples/applications 6
Function Manual
Brief description of ASM
hardware A
Programming the MOBY-
ASM on PROFIBUS B
Service & Support C
10/2009
J31069-D0166-U001-A3-7618
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 corresponding 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 for the specific task, 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 adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
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 J31069-D0166-U001-A3-7618 Copyright © Siemens AG 2006,

Industry Sector Ⓟ 09/2009 2009.
Postfach 48 48 Technical data subject to change
90026 NÜRNBERG
GERMANY
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 ..................................................................................................................13
2.3 Data structures of FB 45 ..............................................................................................................14
2.4 Number of MOBY channels which can be connected .................................................................15
2.5 Addressing of MOBY channels ....................................................................................................16
3 Parameterizing ........................................................................................................................................ 19
3.1 Parameter data block...................................................................................................................19
3.1.1 INPUT parameters .......................................................................................................................21
3.1.2 Command and status word ..........................................................................................................27
3.1.3 Further displays ...........................................................................................................................30
3.2 MOBY commands........................................................................................................................31
3.2.1 Command parameters .................................................................................................................32
3.2.2 Command chaining ......................................................................................................................36
3.2.3 Command repetition.....................................................................................................................38
3.3 Presence check and MDS control................................................................................................41
3.3.1 No MDS Control, No Presence Check: MDS_control = 0............................................................42
3.3.2 No MDS Control, Presence Control with Field Scanning: MDS_control=1..................................42
3.3.3 Field Scanning as MDS Control: MDS_control = 2......................................................................43
4 Commissioning ........................................................................................................................................ 47
5 Error messages and troubleshooting ....................................................................................................... 55
5.1 General errors ..............................................................................................................................55
5.2 Error messages............................................................................................................................56
6 Examples/applications ............................................................................................................................. 67
6.1 FB 45 scanning by user ...............................................................................................................67
6.2 Processing of data memories/transponders ................................................................................68
6.3 Cyclic calling of FB 45 (e.g. in OB 1) ...........................................................................................75
6.4 Programming a cold and warm restart.........................................................................................76
6.5 Programming a module failure.....................................................................................................77
6.6 Data structure definition ...............................................................................................................79
6.7 UDTs of FB 45 / FC 45 ................................................................................................................83
6.7.1 UDT 230: Result of MDS status (mode 3, RF300) ......................................................................86
FB 45
Function Manual, 10/2009, J31069-D0166-U001-A3-7618 3
Table of contents
6.8 Determing the memory requirement in the SIMATIC.................................................................. 88

A Brief description of ASM hardware........................................................................................................... 89
A.1 RF170C ....................................................................................................................................... 89
A.2 RF180C ....................................................................................................................................... 95
A.3 ASM 456.................................................................................................................................... 102
A.4 ASM 475.................................................................................................................................... 111
A.5 ASM 473.................................................................................................................................... 116
A.6 ASM 452.................................................................................................................................... 120
A.7 ASM 454.................................................................................................................................... 127
A.8 ASM 754.................................................................................................................................... 130
A.9 ASM 854.................................................................................................................................... 133
A.10 ASM 850.................................................................................................................................... 139
B Programming the MOBY-ASM on PROFIBUS....................................................................................... 141
B.1 Programming the MOBY-ASM on PROFIBUS DP-V1.............................................................. 141
B.2 Cyclic Control Word between Master and MOBY-ASM............................................................ 144
B.3 Methods of operation with the ASM .......................................................................................... 147
B.4 Command and acknowledgement telegrams............................................................................ 152
B.5 PROFIBUS implementation ...................................................................................................... 161
B.6 Example of a PROFIBUS Trace ............................................................................................... 164
C Service & Support.................................................................................................................................. 167
C.1 Contacts .................................................................................................................................... 167
C.2 Training ..................................................................................................................................... 168
FB 45
4 Function Manual, 10/2009, J31069-D0166-U001-A3-7618
Introduction 1
1.1 Overview
FB 45 is a STEP7 function for RFID technology. It can be used with both the SIMATIC S7-
300 and S7-400 for various RFID interface modules.
$60 5)& 5)&
$60 $60 $60$60 $60

$60$60
Figure 1-1 Interface modules for FB 45
Section "Brief description of ASM hardware" illustrates configurations with the various
interface modules. FB 45 can be operated in various different configurations:
● The interface module is operated directly in a SIMATIC S7-300.
● The interface module is located in the rack of an ET 200M, ET 200X or ET 200pro. The
ET 200M/ET 200X/ET 200pro is used on an S7-300 or S7-400.
● The interface module is a self-contained PROFIBUS slave and is connected to the
integrated PROFIBUS port of a SIMATIC S7-300 or S7-400.
● The interface module can be operated on PROFIBUS or PROFINET.
● The interface module is operated on PROFINET via an IE/PB Link.
These configurations can be mixed. Different interface modules can also be connected.
FB 45
Introduction
1.1 Overview
Compatibility notice
The FB 45 block is a 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 parameterized 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

For the features of the individual interface modules, see Section "Brief description of ASM
hardware".
Since the features of the individual ASMs are continuously being added to, you should
always use the latest edition of this description.
Performance features of FB 45
● All MOBY systems (write/read devices and MDSs) can be used with the FB 45.
● The user can process a complete MDS with one command (up to 64KB).
● The user can chain several commands together. This means that many small data areas
of an MDS 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).
● Transmission of the data to and from the ASM and execution of the commands on the
ASM take place in parallel. 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 use of the FB 45 for the RFID systems MOBY D/E/F/I/U and
RF300. MV400 code readers can also be used with the FB 45.
Please note that a separate manual is available for parameterizing the RF620R/RF630R
reader with function block FB 45. In the "Configuration Manual RF620R/RF630R
(http://support.automation.siemens.com/WW/view/en/33287195)", you will find all the
important information regarding commissioning, parameterization, error messages and error
rectification as well as many examples and applications for RF600.
PROFIBUS configuration
A GSD file on the CD RFID Systems Software & Documentation (6GT2 080-2AA10) is
included for the interface modules which can be connected directly to PROFIBUS.
PROFINET configuration
A GSDML file on the CD "RFID Systems Software & Documentation" (6GT2080-2AA10) is
included for the communications modules which can be connected directly to PROFINET.
FB 45
Introduction
1.1 Overview
Non-SIMATIC applications
Applications programmed on third-party PLCs cannot use FB 45. The PROFIBUS interface
for such applications is described in Section "Programming the MOBY-ASM on PROFIBUS
DP-V1". Programmers of a third-party PLC can use this interface to develop their own MOBY
function. The same or similar data structures as in FB 45 can be reproduced on a third-party
PLC in conjunction with the FB 45 description and the UDTs.
Requirements for using FB 45

The FB 45 can access the communication module (ASM) via any PROFIBUS master that
has the system function blocks SFB 52/53. It is irrelevant here whether the PROFIBUS
master is integrated into the S7-CPU or plugged into the rack as an add-on module (e.g.
IM 467).
Remember that the FB 45 uses non-cyclic telegrams (SFB 52/53). Older CPUs of the
SIMATIC family or a small model series may not have these services. Be sure to check this
during configuration.
● STEP7 Version
The ASM 475 and ASM 473 modules require a STEP7 Version ≥ V5.1.
FB 45
Introduction
1.2 Preface
1.2 Preface
Purpose of this document

This Function Manual contains all the information needed to configure and commission the
system.
It is intended both for programming and testing/debugging personnel who commission the
system themselves and connect it with other units (automation systems, further
programming devices), as well as for service and maintenance personnel who install
expansions or carry out fault/error analyses.
Conventions
The following terms/abbreviations are used synonymously in this document:
● Reader, read/write device, write/read device
● Transponder, mobile data memory, MDS
● Communication module, interface module (ASM)
Scope of this documentation

This documentation is valid for FB 45. The documentation describes the condition on
delivery as of September 2009
History
Previous edition(s) of these operating instructions:
Edition Note
10/2009 Parameterizing the RF620R/RF630 reader.
RF300 and ISO transponders
03/2006 Inclusion of the RF170C communication module
05/2005 First Edition
FB 45
Introduction
1.3 Navigating in the Function Manual
Structure of contents Contents

Table of Contents Organization of the documentation, including the index of pages and chapters
Introduction Purpose, layout and description of the important topics.
Parameterizing Description of the parameter settings
Commissioning Description of the commissioning procedure
Error messages and troubleshooting Overview of error messages and troubleshooting guide
Examples/applications Describes the application of FB 45 based on example applications.
Appendix: Brief description of ASM Description of the interface modules used for FB 45
hardware
Appendix: Programming the MOBY- Information for control using a PC or third-party control system
ASM on PROFIBUS DP-V1
Appendix: Service & Support Service and support, contact partners, training centers
FB 45
Introduction
FB 45
Description 2
2.1 Block specification
Block number: FB 45
Block name: FB 45
Symbolic name: "MOBY FB"
Family: –
Work memory requirement: 8668 bytes
Local data: 106 bytes
Version: 1.1
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 = 458 bytes per
channel
Bit memories used: None
Counters used: None
Registers used: AR1, AR2
Call: cyclic
Table 2- 1 Typical runtimes of FB 45 (cycle load of AS in ms)
S7-CPU Idle pass ASM Distributed ASM on PROFIBUS

centrally in S7-300
Read MDS Write MDS Read MDS Write MDS
315-2 DP 1,9 3.7 + n * 0.023 3.6 + n * 0.022 3,4 3,6
318-2 DP 0,13 1 + n * 0.01 1.3 + n * 0.007 0,4 0,45
416-2 DP 0,1 – – 0,35 0,38
315-2 PN/DP
317-2 PN/DP
318-2 PN/DP
n = Amount in bytes of processed user data per read or write command

When a command processes more than 233 bytes of MDS data, n = 233 must always be
used in the table.
Note:
The times of the ASM for data communication with the data memories are described in the
MOBY manual for configuration, mounting and service.
FB 45
Description
2.1 Block specification
Calculating MOBY data throughput

The formulas in the MOBY manual for configuration, mounting and service can be used to
calculate data throughput with the FB 45.
One configuration manual is provided for each RFID/MOBY system.
Where:
tk Communication time between ASM, write/read device

and MDS
n Amount of user data
t = k + t ⋅n
k bytes
k Constants (see table in configuration manual)
t bytes Transmission time for 1 byte (see table in
configuration manual)
Transmission of the data to the MDS and transmission of the data between ASM and FB 45
take place in parallel. Usually no further time must be added for data transmission between
ASM 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 MOBY channels are processed in parallel.
● Very few (or only one) system resources are available for non-cyclic telegrams.
● Slow transmission speeds are used on PROFIBUS.
● Other applications are running on the S7 which require the non-cyclic telegram services
(SFB 52/53) of the SIMATIC very frequently.
● High-speed identification systems are used (e.g. RF300).
Note
A throughput calculation tool is available for various different communication modules.
You can find this on the CD "RFID Systems Software & Documentation" (6GT2080-
2AA10).
FB 45
Description
2.2 Configuration scheme
2.2 Configuration scheme
Table 2- 2 MOBY FB configuration scheme
Ladder logic Parameters Data type Permissible range Description

programming box
"Inst-DB FB 45" Params_DB INT 2 to 32767 Parameter data block number for a
MOBY channel (write/read device)
MOBY FB 45 Params_ADDR INT 0, 50, 100,*... Address pointer in the parameter data
block to the start of a UDT 10
Params_DB
Params_ADDR
*) These values are exemplary whenever only data structures of the UDT 10 type are arranged in succession.
These values change if UDT 10 is followed by the MOBY command (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 MOBY channel (ASM or write/read device).
See also
Data structures of FB 45 (Page 14)
FB 45
Description
2.3 Data structures of FB 45
2.3 Data structures of FB 45

The following figure shows an example of a definition of several MOBY channels with the
related MDS commands and the user data.
&DOOUHDGHU &DOOUHDGHU &DOOUHDGHU &DOOUHDGHU

&DOO)% &DOO)% &DOO)% &DOO)%
3DUDPVB'% 3DUDPVB'% 3DUDPVB'% 3DUDPVB'%

3DUDPVB$''5 3DUDPVB$''5 3DUDPVB$''5 3DUDPVB$''5
02%<B'%
&KDQQHO
&KDQQHO
8'7 &KDQQHO
&KDQQHO
FRPPDQGB
'%BQXPEHU
8VHUBGDWD
FRPPDQGB
'%BDGGUHVV
7KHXVHU
GHILQHVWKH
02%<BFRPPDQGV VL]HDQG
GDWDW\SHVLQ
'$7B'%BQXPEHU KLVRZQGDWD
8'7
'$7B'%BDGGUHVV
6LQJOHFRPPDQGXSWR
.%FDQEH
SURFHVVHGRUFKDLQHG
FRPPDQG
Figure 2-1 Configuration scheme of FB 45
Each FB 45 call points to a separate parameter data block (Params_DB, Params_ADDR),

which is defined by a UDT 10 The variables "command_DB_number" and
"command_DB_address" are stored in the UDT 10. These variables point to the MOBY
command which is to be executed with the MDS.
UDT 20 is used to define the MOBY command. Different commands can be defined by
calling UDT 20 several times (see Section "Command chaining"). The variables
"DAT_DB_number" and "DAT_DB_address" are defined in the UDT 20. This variable
definition forms the pointer to the user data which is simply referred to as DAT_DB in this
function manual. MDS data are stored there when they are read out. When using a write
command, the user must store his data before executing the command.
FB 45
Description
2.4 Number of MOBY channels which can be connected
2.4 Number of MOBY channels which can be connected

Each MOBY channel occupies 1 word in the input and output area of a SIMATIC S7. The
maximum number of MOBY modules supported by SIMATIC can always be operated. The
following table provides an overview.
Table 2- 3 Number of MOBY channels
S7 CPU type5 315-2 DP 316-2 DP; 318-2 DP 416; 417; CP 443-5 Ext
Max. no. of Max. no. of Max. no. of Max. no. of Max. no. of Max. no.
ASMs write/read ASMs write/read ASMs of
devices devices write/read
(channels) (channels) devices
(channels)
ASM 475 (centralized)2 32 64 32 64 – –
ASM 475 (distributed via 64 x 8 1024 123 x 8 1968 123 x 8 1968
ET 200M) 3
RF170C (distributed via 64 x 9 1152 123 x 9 2214 123 x 9 2214
ET 200pro) 6
ASM 473 (distributed via 64 x 7 448 123 x 7 861 123 x 7 861
ET 200X) 4
ASM 452 64 64/128 1 123 123/246 1 123 123/246 1
ASM 456 64 128 123 246 123 246
ASM 454, 854 64 256 123 492 123 492
ASM 754 64 64/256 1 123 123/492 1 123 123/492 1
1) No. of channels in multiplex mode (only static operation possible)
2) The centralized configuration can contain up to three expansion racks. A DP connection is not necessary in this variant.
3) In the distributed configuration, up to eight MOBY modules (ASM 475) can be installed in each ET 200M.
4) Up to seven ASM 473 modules can be installed in a distributed ET 200X I/O.
5) The CPU types specified here may be incomplete, as the range of CPUs and associated functions is expanded
continuously.
6) Up to 9 RF170Cs can be installed in a distributed ET 200pro
FB 45
Description
2.5 Addressing of MOBY channels
Centralized configuration with ASM 475

In the centralized configuration, HW Config assigns fixed slot-specific addresses for the ASM
475. The ASM 475 is located in the analog area of a SIMATIC S7-300 and starts at address
256.
6XEUDFN
6ORWQXPEHU
,0
$QDORJDGGUHVV
&RQQHFWLQJFDEOH
6XEUDFN
6ORWQXPEHU ,0
$QDORJDGGUHVV
&RQQHFWLQJFDEOH
6XEUDFN
6ORWQXPEHU ,0
$QDORJDGGUHVV
&RQQHFWLQJFDEOH
6XEUDFN
6ORWQXPEHU
$QDORJDGGUHVV
Figure 2-2 Slots for S7-300 and analog addresses for ASM 475
FB 45
Description
Addressing via PROFIBUS

When addressing via PROFIBUS, any addresses for the MOBY interface module can be
selected in HW Config. HW Config assigns a free address by default.
$XWRPDWLFJHQHUDWLRQRIWKHQH[WIUHH
DGGUHVV7KH,DGGUHVVDQG4DGGUHVV
PXVWEHLGHQWLFDO
Figure 2-3 Example: Automatic address generation for a MOBY PROFIBUS slave
$XWRPDWLFJHQHUDWLRQRIWKHQH[WIUHH
DGGUHVV7KH,DGGUHVVDQG4DGGUHVV
PXVWEHLGHQWLFDO
Figure 2-4 Example: Automatic address generation of a MOBY-ASM/communication module in ET

200 configuration
FB 45
Description
Assignment of addresses in FB 45
The unique I/O addresses of the interface module of HW Config must be saved in the
parameter data block (UDT 10).
3K\VLFDODGGUHVVDVVLJQPHQW
DVGHILQHGLQ+:&RQILJ
6WDUWDGGUHVVHV
RI8'7LQ
GDWDYLHZRI
02%<'%
Figure 2-5 Setting the physical address assignment in UDT 10
The MOBY channel (ASM_channel) must be assigned uniquely in addition to the address
(ASM_address). When an ASM is used with several channels (RF170C, ASM 475, 456, 452,
454, 754, 854), a separate UDT 10 must be defined for each channel. The "ASM_address"
entry is the same. The "ASM_channel" is changed from 1 to 4.
FB 45
Parameterizing 3
3.1 Parameter data block
Each MOBY channel (reader) needs its own parameters. These are predefined in a data
structure as UDT 10 (with commentary in English) or UDT 11 (with commentary in German)
or UDT 14 (with commentary in Spanish). That UDT must be called in a data block for each
MOBY channel. Various variables are defined in UDT 10:
● INPUT parameters: These variables must be entered by the user once during
configuration (exception: command_DB_number/command_DB_address). Throughout the
run time it is not necessary to change or scan these parameters.
Please note that you need to execute an init_run after changing an INPUT parameter
before the new setting is activated (see Section "Programming a cold and warm restart").
● Control bits: The user starts his commands with these Boolean variables.
● Displays: The displays indicate the command progress to the user. Error analyses can be
performed easily.
● FB-internal variables: These variables are not relevant for the user. They must not be
changed by the application. Malfunctions and data corruption would otherwise ensue.
The following table shows the complete UDT 10. For programmers who prefer to address
using absolute values, the first column specifies the relative addresses.
Special information on UDT 10 for the RF620R/RF630R readers can be found in the
"Configuration Manual RF620R/RF630R".
Table 3- 1 UDT 10 "MOBY Param"

Address Name Type Initial Comment
value
0.0 STRUCT
+0.0 ASM_address INT 0 Input: Basic address of the ASM
(cyclic word)
+2.0 ASM_channel INT 1 Input: Number of the channel (1 to
4)
+4.0 command_DB_number INT 47 Input: Command data block number
+6.0 command_DB_address INT * 0 Input: Start address of data in
the BEDB
+8.0 MDS_control BYTE B#16#1 Input: Presence check and tag(0,
1, 2)
+9.0 ECC_mode BOOL FALSE Input: mode with ECC
+9.1 RESET_long BOOL FALSE Input: true: long RESET telegram,
only for MOBY mode 5
+10.0 MOBY_mode BYTE B#16#1 Input: MOBY mode
+11.0 scanning_time BYTE B#16#0 Input: Scanning time for MOBY I/U
+12.0 option_1 BYTE B#16#0 Input: Init_run Option 1
+13.0 distance_limiting BYTE B#16#F Input: Distance/capacity setting
**
+14.0 multitag BYTE B#16#1 Input: Max. number of tags in
field
+15.0 field_ON_control BYTE B#16#0 Input: BERO
+16.0 field_ON_time BYTE B#16#0 Input: MOBY U: BERO time
MOBY D: Tag Type ***
+17.0 reserved0 BYTE B#16#0
FB 45
Parameterizing

value
+18.0 ANZ_MDS_present BOOL FALSE Presence of a tag
+18.1 ANZ_cancel BOOL FALSE Cancel-bit in the PEW is set.
+18.2 ANZ_ECC BOOL FALSE Error correctionen done
+18.3 reserved BOOL FALSE
+18.4 LR_bat BOOL FALSE Battery of the MDS507
+18.5 battery_low BOOL FALSE Battery check has indicated low
voltage
+18.6 error BOOL FALSE Error during command execution
+18.7 ready BOOL FALSE Command chain has been finished.
+19.0 cancel BOOL FALSE Set: abort command or command
chain
+19.1 command_start BOOL FALSE Set: start signal for command or
command chain
+19.2 repeat_command BOOL FALSE Set: repeat last command
+19.3 init_run BOOL TRUE Set: reset ASM and set new
parameters
+19.4 ASM_failure BOOL FALSE OB122 Set: ASM failed
+19.5 FB45_active BOOL FALSE FB active
+19.6 ANZ_next BOOL FALSE NEXT command was last command
+19.7 ANZ_reset BOOL FALSE Init_run was last command
+20.0 ASM_busy BOOL FALSE A command is processed by ASM
+20.1 command_rep_active BOOL FALSE ASM command repetition has been
activated.
+21.0 number_MDS BYTE B#16#0 Number of tags actually in field
+22.0 error_MOBY BYTE B#16#0 Error indication of interface
module
+23.0 error_FB BYTE B#16#0 Error indication of FB
+24.0 error_BUS WORD W#16#0 Error indication of PROFIBUS
+26.0 version_MOBY WORD W#16#0 Firmware version of MOBY
+28.0 counter_customer BYTE B#16#2 Setting for S7 cycles per command
execution
*4.0 DWORD
+44.0 initRUN_timeout INT 1000 FB-internal variables. You should
not attempt to modify these
variables.
+46.0 PEW_timeout_ASM_fail BYTE B#16#5 FB-internal variables. You should
variables.
+47.0 PEW_timeout BYTE B#16#32 FB-internal variables. You should
variables.
+48.0 reserved3 BYTE B#16#0 FB-internal variables. You should
variables.
+49.0 Testbyte BYTE B#16#0 FB-internal variables. You should
variables.
=50.0 END_STRUCT
*) Parameter data block UDT 60 is available for data media > 32 KB. The data type here is WORD.
**) RF300, reader only: 6GT2801-3AB10
*** ) RF300 in ISO mode: 6GT2801-3AB10
-1AB10
FB 45
Parameterizing
3.1.1 INPUT parameters

Special information on the INPUT parameters for the RF620R/RF630R readers can be found
in the "Configuration Manual RF620R/RF630R".
Table 3- 2 INPUT parameters
Variable Description
ASM_address Logical base address of the ASM. This address must match the "start address" of the ASM in HW
Config of the SIMATIC Manager. Remember that this address has nothing to do with the PROFIBUS
address which is set on the ASM or the ET200M.
ASM_channel Number of the MOBY channel which is to be used
ASM type Value range
ASM 475, 452, 456; RF170C, RF180C 1, 2
ASM 454, 754, 854 1, 2, 3, 4
ASM 473, 850 1
command_DB_ These INPUT parameters can
Number of the data block in which the MDS command is specified
number be changed whenever
command_DB_ Address within the "command_DB". The next MDS command ready = 1. An init_run does not
address starts at this address. "command_DB_number" and need to be executed after
"command_DB_address" form a data pointer to the next command changing these parameters.
(see Section "Configuration scheme").
Note:
The input parameters command_DB_number and command_DB_address can be changed only
when ready = 1. An init_run does not need to be executed after changing these parameters.
MDS_control MDS_control turns on/off the presence check or the MDS control on the ASM* (see Section
"Presence check and MDS control").
Value MDS control ASM type
0 Presence check is off. The variable ANZ_MSD_present doesn't all
indicate a valid value.
1 Presence check is on. MDS control is off. The variable all
ANZ_MDS_present indicates an MDS is the transmission window of a
write/read device.
2 Presence check is on. MDS control is on, and control takes place with 454
the presence check of the MDS. The NEXT command must be sent to
the ASM each time an MDS is processed.
*) ASM/SLG (e.g. RF300)
ECC_mode Turns ECC mode on (true) or off (false). Remember that ECC mode can only be used with MOBY I.
RESET_long The init_run command transfers all INPUT parameters to the ASM. This bit must be set to TRUE
when MOBY U/D or RF300 are used (MOBY_mode = 5).
FB 45
Parameterizing
MOBY_mode Setting of the MOBY operating mode
Value Operating mode ASM type
0 Default Reserved for setting the operating
mode with switch or GSD
parameterization. Various interfaces
without switches interpret MOBY
mode = 0 as MOBY I mode.
1 MOBY I or MOBY E all
(without MDS 507)
4 MOBY I with MDS 507 452; 454; 456
5 MOBY U/D or RF300 - without multitag handling 475; 473; 452; 456; RF170C,
RF180C
6 Res. for MOBY U - with multitag handling (FB 55) –
7 Res. for MOBY D or RF300 - with multitag handling Available soon with:
(FB 55) 475, 473, 452, 456, RF170C,
RF180C
8 MOBY I dialog 454; 452; 456
9 MOBY V 452
A MOBY F with MDS F1xx 475; 473: 452; 854; 850
B MOBY F with MDS F4xx 475; 473: 452; 854; 850
C MOBY F (res. for MDS F2xx) –
Please note:
MOBY_mode may only be changed after an ASM is turned on.
scanning_time MOBY I/V:
Scanning_time is the scanning time for the MDS 507 of MOBY I and MOBY V. A value of 00 can be
used here for all other types of MDS. The scan time setting (ABTA) is shown below (see also
configuration manual of write/read device 44/MDS 507).
%LW
7LPHYDOXH)
7LPHIDFWRU
V
V
V
V
Example: A scanning time of 1 second results in ABTA = 81 hex for the parameter.
FB 45
Parameterizing
MOBY U:
Scanning_time describes the standby time for the MDS. If the MDS receives an additional command
before scanning_time has expired, this command can be executed immediately. If the MDS receives
a command after scanning_time has expired, command execution is delayed by sleep_time of the
MDS.
Scanning_time should only be set when both of the following conditions exist.
• The MDS uses several commands and
• command execution must be concluded within a minimum time.
00 hex = no standby time (default)

01 hex = 7ms standby time
02 hex = 14ms standby time
:
C8 hex = 1400ms standby time
Remember:
Scanning_time affects the life of the battery. The longer scanning_time is, the shorter the life of the
battery. For precise calculations, see the MOBY U manual for configuration, mounting and service.
MOBY D: 00 hex (reserved)

RF300: Set to 0 for use of RF300 as well as for ISO tags.
option_1 This byte is bit-coded. Its standard value is B#16#0. It can be used for special control on the
ASM/SLG.
%LW

7KHIODVKLQJRIWKH(55/('LVUHVHWE\DQ
LQLWBUXQ
distance_limiting MOBY U: Range limitation

Normal output power1) Reduced output power
05 hex = 0.5 m 85 hex Reduced output power must be set when several
0A hex = 1.0 m 8A hex write/read devices are positioned close together or when
0F hex = 1.5 m 8F hex data memories which are located in the vicinity of a
14 hex = 2.0 m 91 hex write/read device are detected later or not at all.
19 hex = 2.5 m 99 hex Disadvantage: The field lobe becomes smaller and there
1E hex = 3.0 m 9E hex is less time for communication or positioning must be
23 hex = 3.5 m A3 hex more precise.
1) Intermediate values in steps of 0.1 m are possible (02, 03, ..., 23 hex)
MOBY D: HF power from 0.5 W to 10 W in steps of 0.25 W
only effective for SLG D10S; a power of 1 W (04 hex) is set for SLG D11S / D12S and cannot be
changed.
02 hex = 0.5 W
:
10 hex = 4 W (default)
:
28 hex = 10 W
FB 45
Parameterizing
RF300
With this parameter, a change to the output power can only be made for the RF380R (MLFB
6GT2801-3AB10). In doing this, you must take into consideration that the change to the output
power will affect both the upper and lower limit range, as well as the minimum distance that is to be
maintained between adjacent RF380Rs. See the RF300 System Manual, field data, Chapter 4.2
The following settings are possible:
Value
02 0.,5 W
03 0.75 W
04 1.0 W
05 1.25 W
06 1.5 W
07 1.75 W
08 2.0 W
Settings outside of the specified values mean that the default value of 1.25 W is set and no error
message occurs for compatibility reasons!
multitag MOBY U/D or RF300:Maximum number of MDSs being processed in parallel in the field.
Permissible values: 1
field_ON_control MOBY U: BERO mode; automatic activation/deactivation of antenna field. The "Antenna ON/OFF"
command is superimposed by the BERO mode.
00 hex = without BEROs; no write/read device synchronization
01 hex = one or two BEROs
The BEROs are combined according to logic OR. The field is ON during
actuation of a BERO.
02 hex = One or two BEROs
The 1st BERO switches the field on and the 2nd BERO switches the field
off.
If two BEROs exist and a field_ON_time is configured, the field is
automatically deactivated if the 2nd BERO does not switch within that
BERO time.
If no field_ON_time is configured, the field remains on until the 2nd BERO is
actuated.
03 hex = Activate write/read device synchronization via cable connection (see
manual for configuring, mounting and service for MOBY U)
MOBY D or RF300: 00 hex (reserved)
FB 45
Parameterizing
field_ON_time (ftim) MOBY U: Time for BERO mode (field_ON_control = 02)
00 hex = Timeout monitoring is deactivated. The 2nd BERO is needed in order to
switch the field off.
01 hex ... FF hex = 1 ... 255s turn on time for the write/read device field.
MOBY D: MDS type
Binary value: = MDS type
0 ... 255
00 hex = I-Code 1 (e.g. MDS D139)
01 hex = ISO transponder
02 hex = I-Code 1 and ISO transponder
03 hex = ISO-my-D (with SLG D10S only; the value 01 hex is parameterized for ISO-
my-D with SLG D11S / D12S)
04 hex = ISO-FRAM (with SLG D11S/D12S only; the value 01 hex is parameterized
for ISO-FRAM with SLG D10S) *
RF300:
With the aid of the "ftim" parameter, a decision is made whether the reader is operated in RF300
mode or in ISO 15693 mode (mixed operation is not provided for).
Specifying the value 00 switches the reader into RF300 mode with the command "init_run"(RESET).
Values in the range 01 to 07 activate ISO15693 mode.
The value 01 activates the "general ISO mode" with rudimentary ISO commands (see note No. 4).
The performance is usually lower with this setting, but operation is normally possible with any ISO-
compatible tag.
The transponder chip types of the tags that are specified in Section 7.1 of the SIMATIC RF300
System Manual support these commands. By selecting the values 03 to 07, chip-specific commands
will be used wherever possible that permit faster data transfer.
The following values can be set:
Value ISO RF300
01 Any ISO tag To be assigned the value 0
03 ISO my-d (Infineon SRF 55V10P)
04 ISO (Fujitsu MB89R118)
05 ISO I-Code SLI (NXP SL2 ICS20)
06 ISO Tag-it HFI (Texas Instruments)
07 ISO (ST LRI2K)
Notes
1. The following special functions are not supported:
– AFI (Application Family Identifier)
– DSFID (Data Storage Format Identifier)
– Chip-specific added functions such as EAS, Kill commands, etc.
2. If a previously unknown tag cannot be identified based on the parameters above, an error
message occurs (error_MOBY "0D"[hex]).
3. Impermissible parameters are rejected with an error message (error_MOBY "15"[hex]).).
4. RF300 for "ftim" = 01: performance may be reduced.
FB 45
Parameterizing
counter_customer: Setting for S7 cycles per command execution. Default value is 02.
00 hex = FB requires 6 S7 cycles per command
01 hex = Depending on the ASM type and the overall configuration, the number of S7
cycles can be reduced to 3
02 hex = Depending on the ASM type and the overall configuration, the number of S7
cycles can be reduced to 2 per command
Note:
If an optimally short cycle time is required in the PLC, "counter_customer" must be set to "0". Larger
values can lengthen the cycle time in the PLC.
The permissible values of the INPUT parameters are listed in the hardware specifications.
FB 45
Parameterizing
3.1.2 Command and status word

The control bits of FB 45 are defined in the command and status word.
The command and status word and the variables are generated using UDT 10. The variables
and the associated relative addresses in UDT 10 are shown in the following figure.
'%:
'%% '%%൸UHODWLYHDGGUHVVLQ8'7

FDQFHO
FRPPDQGBVWDUW
UHSHDWBFRPPDQG
LQLWBUXQ
$60BIDLOXUH
)&BDFWLYH
$1=BQH[W
$1=BUHVHW
$1=B0'6BSUHVHQW
$1=BFDQFHO
7REHVHWE\WKHXVHUWKHVHFRQWUROELWVDUH
$1=B(&& UHVHWDXWRPDWLFDOO\E\)%H[FHSWIRU
UHSHDWBFRPPDQG
UHVHUYHG
0XVWEHFKHFNHGE\
/5BEDW WKHXVHU
EDWWHU\BORZ 2SWLRQDOVFDQQLQJELWV
(UURU
UHDG\
Figure 3-1 Assignment of the command and status word (DBW 18) with variable names
Special information on the command and status word "BEST" for the RF620R/RF630R
readers can be found in the "Configuration Manual RF620R/RF630R".
FB 45
Parameterizing
Table 3- 3 Variables in command and status word
cancel True = Interrupts a running command or a command chain. FB 45 then sets the "ready"
variable.
False = FB 45 performs an automatic reset.
MOBY U/D or RF300: The cancel variable is not available. A command termination must be
executed via the init_run variable.
command_start True = Starts a command or a command chain
repeat_command True = Command repetition: The last command or command chain stored on the interface
module is processed again with the next MDS. Command processing for the MDS is not
started until the MDS, which has already been processed, has left the transmission window
(ANZ_MDS_present = 0) and a new MDS has entered the transmission window of the
write/read device (ANZ_MDS_present: 0 → 1).
In the case of RFID systems with unique tag IDs (UID) (e.g. RF300, MOBY U), the next tag
entering the field must have a different UID from the previous one for the command to be
repeated.
False = No command repetition or command repetition is stopped after the command started
with the repeat command has been processed. Remember that this bit must be reset by the
user to stop command repetition. The result of command repetition is fetched when
command_start is set by the user.
repeat_command is not automatically reset by the FB 45 after command processing.
The init_run and cancel commands reset the repeat_command variable. This also interrupts a
command repetition on the ASM. repeat_command can be set again by the application with
the next command_start.
Handling of command repetition is described in Section "Command repetition".*
init_run True = Restart interface module FB 45 is reset and the interface module is initialized. All data
and commands on the ASM are lost. This bit must be set in the restart OB (OB 100) for each
MOBY channel or interface module.
After a MOBY-ASM failure, error_MOBY=0F is signaled to the user. The user must then
perform an init_run.
Note:
• The init_run bit is initialized with TRUE when a parameter data block is downloaded from
the programming device to SIMATIC. This causes an automatic new start for the ASM.
• The execution time of init_run is normally in the millisecond range. In the event of an error,
the time may be up to 15s.
ASM_failure True = The ASM has failed. This bit is set by the user in OB 122 (see Section "Programming
a module failure"). FB 45 signals an error to the user (error_FC = 09) and interrupts a
command in progress. If OB 122 is not programmed by the user, the PLC switches to the
STOP state on an interface module failure.
FB45_active FB 45 is currently executing a command. This variable is set when the command is started
(command_start=True) and remains active until
• FB 45 has received the last acknowledgment from ASM.
• the init_run bit has been set
• The Cancel bit was set.
• An error message was reported from the ASM.
ANZ_next This bit is set when the last command executed was a NEXT command.
FB 45
Parameterizing
ANZ_reset This bit indicates that the last command to be executed was a RESET. The RESET command
was started by the user with "init_run."
ANZ_MDS_present Indicates the presence of an MDS in the transmission window of the read/write MDS.
ANZ_MDS_present is only indicated when the INPUT parameter MDS_control (see Section
"INPUT parameters") was set by the user.
Remember that when an init_run is being executed, the ANZ_MDS_present indication
disappears briefly even when an MDS is permanently located in the transmission window.
ANZ_cancel The last command executed was a command interruption (cancel). The bit is set when the
ASM indicates a cancel acknowledgment with the cyclic word (see Section "Cyclic control
word between master and MOBY-ASM"). The bit is reset automatically when a new command
is started.
ANZ_ECC MOBY I only:
When the ECC driver is on (INPUT parameter "ECC mode" = TRUE), the bit indicates that the
data read by the MDS have been corrected. ANZ_ECC is not an error message since the
data are okay. ANZ_ECC is an indication that the MDS memory just processed may soon fail
completely.
reserved Not used at this time
LR_bat This bit only applies when MDS 507 is used with MOBY I. It indicates that a dialog battery of
the MDS 507 is dead. With all other MDSs, this bit can assume any state.
battery_low For MOBY I/V with RAM-MDS only:
The capacity of the backup battery of the RAM-MDS is below the threshold. Although, at
room temperature, it will continue functioning with its remaining capacity for several months,
we recommend changing the MDS's battery immediately or, when its battery cannot be
changed, replacing the entire MDS.
error FB 45 sets this bit if a command is terminated abnormally. The error bit is the checksum error
bit for all errors which occur. The exact cause of the error is stored in variable error_ MOBY,
error_FB or error_BUS (see Section "Further displays" and Section "Error messages and
troubleshooting"). The error bit is reset when a command is restarted.
ready Ready message: error bit = FALSE must be checked after ready = TRUE is signaled. This
ensures that the command was executed normally.
Please note:
The ready bit does not need to be set in order to start init_run or cancel.
*) You will find notes on the repeat_command in the system manual for the respective MOBY/RFID system.
FB 45
Parameterizing
3.1.3 Further displays

Special information on the other displays for the RF620R/RF630R readers can be found in
the "Configuration Manual RF620R/RF630R".
Table 3- 4 Displays
ASM_busy This bit is set when the ASM is processing a command. "ASM_busy" is normally inverse to
"ready". The interface module signals ASM_busy via the cyclic word (see Section "Cyclic
control word between master and MOBY-ASM" under "ASM_busy_"). When the
repeat_command automatic command start is used, this bit shows the processing of a new
MDS with the command to be executed.
MOBY U/D or RF300: No meaning. This variable is always false.
command_rep_active The ASM is processing a command repetition. The bit is set as a response to the control
variable repeat_command. After an init_run, command_rep_active is first reset by FB 45 and
then set again after a delay following the transfer of the MOBY commands to the ASM by FB
45.
number_MDS MOBY U/D or RF300:
The number of MDSs presently located in the transmission window is indicated.
If more than 15 MDSs are located in the field, number_MDS is indicated as 0F hex.
error_MOBY This error was reported by the ASM. The error is usually displayed on the ERR LED of the
ASM channel display (see Section "Error messages and troubleshooting").
error_FB Error messages from FB 45 (see Section "Error messages and troubleshooting")
error_BUS The transmission path between FB 45 and ASM reports an error. It is usually a PROFIBUS
error. (see Section "Error messages and troubleshooting" ). This error is signaled by system
functions SFC 58/59.
version_MOBY Indicates the firmware version of the MOBY-ASM. The value entered here is updated each
time the ASM starts up. It is ASCII-coded.
([DPSOH '%% '%%

KH[ KH[ ൺ9HUVLRQ
ಯರ ಯರ
All other variables of UDT 10 are for FB-internal use. They must never be changed by the
user.
FB 45
Parameterizing
3.2 MOBY commands
3.2 MOBY commands
Note
This chapter provides a description of all commands which can by processed by FB 45. The
commands, which can actually be processed by the interface module you are using, are
described in section Brief description of ASM hardware (Page 89).
Before you can start a MOBY command with command_start, you need to define the
command. UDT 20 (commentary in English), UDT 21 (commentary in German) or UDT 24
(Spanish commentary) is available for the simple definition of a command.
Table 3- 5 UDT 20 "MOBY CMD"

value
0.0 STRUCT
+0.0 command BYTE B#16#2 MDS: 2 = read, 1 = write
+1.0 sub_command BYTE B#16#0 INIT = bit pattern; END, SET, MDS,
SLG=mode
+2.0 length INT * 1 Amount of data to be written/read in
bytes
+4.0 address_MDS WORD W#16#0 Start address on MDS, memory size for
INIT; date for MDS
+6.0 DAT_DB_number INT 48 Number of DAT_DB, data for MDS
+8.0 DAT_DB_address INT * 0 Pointer to start word in DAT_DB
=10.0 END_STRUCT
*) UDT 70 (data type WORD instead of INT) must be used for MDS/transponder memory > 32 KB.
The "length" value is then specified in hexadecimal notation.
The "actual value" of the variables can be modified using the editor in the data view of the
DB or in the STEP 7 application program.
Please note that the actual values can only be changed if no command is active (ready = 1).
FB 45
Parameterizing
3.2 MOBY commands
3.2.1 Command parameters
Overview of commands
Special information on parameterizing the commands for the RF620R/RF630R readers can
be found in the "Configuration Manual RF620R/RF630R".
Table 3- 6 Overview of commands
Command [hex] Command

normal chained*
01 41 Write data to MDS
02 42 Read data from MDS
03 43 Initialize MDS
04 44 SLG status
06 – NEXT
08 48 END; conclude communication with the MDS
0A 4A Antenna on/off
0B 4B MDS status
*) Chained commands are not supported by all write/read devices or ASMs. Adhere to the information
in the MOBY manuals for configuration, mounting and service.
Write
Table 3- 7 Write MDS
Command sub_command length address_MDS DAT_DB Note

[hex] [hex] [dec] [hex] [dec]
01 – 1 to 32767 * 0000 to FFFF ** Pointer to the
length of the MDS The data are written to user data which
data to be written the MDS starting at this are to be written
start address. to the MDS
*) When UDT 70 is used, "length" is specified as a hexadecimal value. The
value range is then from 0001 to FFFF. A complete 64 KB MDS can thus be processed.
**) Please refer to section Processing of data memories/transponders (Page 68) for addressing individual transponder
types.
FB 45
Parameterizing
3.2 MOBY commands
Read
Table 3- 8 Read MDS

02 – 1 to 32767 * 0000 to FFFF ** Pointer to user
length of the The data are read data. FB 45
MDS data to be from the MDS starting at stores the read
read this start address. MDS data here.
*) When UDT 70 is used, "length" is specified as a hexadecimal value. The
value range is then from 0001 to FFFF. A complete 64 KB MDS can thus be processed.
**) Please refer to section for addressing individual transponder types.
Initialization
Table 3- 9 Initialize MDS

03 00 to FF, hex value – Memory size of the –
with which the MDS MDS to be initialized
is written
MDS type Memory size Init duration INIT duration

normal with ECC
1KB MOBY I: VMDS ASM452 05 00 < 0.1 s –
2KB MOBY I: RAM 08 00 0.4 s 5s
8KB MOBY I: FRAM 20 00 0.8 s 20 s
8KB MOBY I: EEPROM 20 00 18 s 54 s
32KB MOBY I: RAM/FRAM 80 00 3s 75 s
752 bytes MOBY E: EEPROM 02 F0 0.8 s –
192 bytes MOBY F: EEPROM 00 C0 2.2 s –
16 bytes MOBY F: EEPROM 00 10 0.25 s –
2KB MOBY U: RAM* 08 00 approx. 1 s –
32KB MOBY U: RAM* 80 00 approx. 1.5 s –
44 bytes MOBY D: I-Code 1 00 2C approx. 0.4 s
112 bytes MOBY D: ISO I-Code SLI 00 70 approx. 0.5 s
256 bytes MOBY D: ISO Tag-it HF-I ISO 01 00 approx. 1 s
992 bytes MOBY D: my-d 03 E0 approx. 3 s
2000 bytes MOBY D FRAM 07 0D approx. 3 s --
20 bytes RF300: EEPROM 00 14 approx. 0.2 s –
8KB RF300: FRAM* 20 00 0.3 s –
32KB RF300: FRAM* 80 00 1.2 s –
64KB RF300 FRAM * FF 00 2.4 s –
*) The OTP memory is not initialized with this command.
FB 45
Parameterizing
3.2 MOBY commands
SLG status
Table 3- 10 SLG status

04 01 = status after UDT 1101 – – Pointer to MOBY U/D or
02 = status after UDT 1201 result. RF300
(last commands) The result is indicated MOBY U
03 = status after UDT 1301 with the respective
(error messages) UDT (see
04 = status after UDT 1401 sub_command). MOBY U
(MDS in field)
05 = status after UDT 150
(communication quality) MOBY U
06 = status after UDT 280
(diagnostics data)
MOBY U
RF300
1) You will find the UDT description in Section "UDTs of FB45".
NEXT
Table 3- 11 NEXT

06 – – – – NEXT: Processing of this
MDS is finished.
The NEXT command can also be used in a command chain (see Section "Command
chaining"). However, the NEXT command must always be the last command in the chain.
END
Table 3- 12 Terminate communication with MDS

08 00 = Processing with MDS – – – ANZ_MDS_present is
has terminated reset.
01 = Processing pause
with MDS1 ANZ_MDS_present
remains set.
1) MOBY U:
This command is recommended when scanning_time parameter is greater than 0 (standby time). Use of this command
optimizes the life of the MDS battery. An additional MDS command must now wait for sleep_time of the MDS to expire
again.
FB 45
Parameterizing
3.2 MOBY commands
Antenna on/off
Table 3- 13 Antenna of write/read device ON/OFF

0A 01 = antenna on – – – The "antenna on/off"
02 = stand-by; antenna off command connot be started
by command repetition (see
09 = match antenna to
Section "Command
environment (FFT)
repetition").
Write/read device 80 only

(MOBY F)
With MOBY F/U/D or RF300 only:

This command is not needed for normal operation because, when a write/read device is
turned on, its antenna is always on.
The antennas must be turned off when two sensitive write/read devices are positioned very
close to each other. The application software must ensure that only one antenna is on at a
time.
MDS status
Table 3- 14 MDS status and diagnosis

0B 00 = status and diagnosis – Today's date Pointer to Only MOBY U
(week/year) for result. (see Section "UDTs of
calculating the The result is FB 45")
battery life (e.g. presented with
1401 hex = 20th UDT 100.
week of the year
2001)
01 = type and write – – Pointer to RF300
protection status for RF300 result. (see Section "UDTs of
tags The result is FB 45")
presented with
UDT 260.
02 = diagnostic data – – Pointer to RF300
result. (see Section "UDTs of
The result is FB 45")
presented with
UDT 270.
03 = type and write - - UDT 230 RF300 *
protection MOBY D
ISO tags for RF300
*) in ISO mode, reader 6GT2801-1AB10 or 6GT2801-3AB10 only
FB 45
Parameterizing
3.2 MOBY commands
3.2.2 Command chaining

Command chaining permits various address areas of the MDS to be processed by starting
just one command. The advantage of command chaining is the optimum speed at which
commands can be processed on the ASM.
A command chain is set up by the user by storing a succession of UDT 20s in a DB. The
chained commands must all be command type 4x. The last command in a chain must be
type 0x.
The FB 45 uses this to detect the end of a command chain.
Example:
An MDS is to process 4 data records. The command structure is stored in DB 47. The MDS
data are stored consecutively in DB 48.
Read MDS address 0000 hex Length 600

Write MDS address 1200 hex Length 1
Execution steps:
1. Define structure
Table 3- 15 DB 47 - declaration view
Partial command STRUCT

Partial command ARRAY [1 ... 4] Note:
1 ... 4 = No. of partial commands
Partial command UDT 20
Partial command END_STRUCT
FB 45
Parameterizing
3.2 MOBY commands
2. Specify the "starting values" in the data view
Table 3- 16 DB 47 - data view
Name Initial value Comment

Partial command [1].command 42 Read command; followed by another
Partial command [1].pattern 00 command
Partial command [1].length 600
Partial command [1].adress_MDS 0000
Partial command 48
[1].DAT_DB_number 0
Partial command
[1].DAT_DB_address 42
00 Read command; followed by another
Partial command [2].command 100 command
Partial command [2].pattern 1000
Partial command [2].length 48
Partial command
[2].DAT_DB_number 42
Partial command 00
[2].DAT_DB_address 1 Read command; followed by another
1200 command
Partial command [3].command 48
Partial command [3].pattern 700
Partial command [3].length
Partial command 00
[3].DAT_DB_number 1
Partial command 1200 Write command, last command in chain
[3].DAT_DB_address 48
701
Partial command [4].command
Partial command [4].pattern
Partial command [4].length
Partial command [4].adress_MDS
Partial command
[4].DAT_DB_number
Partial command
[4].DAT_DB_address
See also
Command parameters (Page 32)
FB 45
Parameterizing
3.2 MOBY commands
3.2.3 Command repetition
Operating principle
After a new start (or init_run) of the ASM, the FB 45 transmits the command (or command
chain) once to the ASM. Command transmission is automatic with the first command_start.
This command (or the last command or the command chain) always remains intermediately
stored in the ASM. If command repetition is started now, the intermediately stored command
on the ASM is executed again, and the result(s) transferred to the FB 45.
Advantages of command repetition

● Data transmission on the (PROFI) BUS is minimized. This is particularly noticeable with
extensive bus configurations and slow (bus) transmission speeds.
● The ASM processes each MDS independently of the FB 45. In concrete terms, this
means each MDS is processed even in applications with a very fast sequence of MDSs.
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 telegrams.
● Use of command repetition to read fixed-code MDSs also has its advantages (see
Section "Processing of data memories").
Command overview for use with command repetition
Command [hex] Command Permitted with command repetition

normal chained*
01 41 Write data to MDS Yes; but only with identical write data
02 42 Read data from MDS Yes
03 43 Initialize MDS Yes
04 44 SLG status No
06 – NEXT No
08 48 END; conclude communication with the Yes
MDS
0A 4A Antenna on/off No
0B 4B MDS status Yes
*) Chained commands are not supported by all write/read devices or ASMs. Adhere to the information
FB 45
Parameterizing
3.2 MOBY commands
Programming
There are two programming methods.
● Reading (processing) each MDS which comes by. After the ASM is programmed with a
command, repeat_command is set and remains set. The following diagram shows the
primary states.
UHDG\
FRPPDQGBVWDUW
UHSHDWBFRPPDQG
$60BEXV\
$1=B0'6BSUHVHQW
7KHXVHUVWDUWVKLVKHUFRPPDQG 7KH0'6VSDVVE\WKHZULWHUHDG 5HVXOWVDUH

IDVWHUWKDQWKH0'6VFDQSDVVWKH GHYLFHIDVWHUWKDQWKHXVHUFDQIHWFK IHWFKHGRQWKH
ZULWHUHDGGHYLFH WKHUHVXOWV,QVXFKFDVHVWKHUHVXOWV $60
7KHUHVXOWLVDYDLODEOHWRWKHXVHU DUHLQWHUPHGLDWHO\VWRUHGRQWKH$60
UHDG\ LPPHGLDWHO\DIWHUWKH 7KHUHVXOWVDUHWKHQUHDGODWHU
FRPPDQGLVSURFHVVHG$60BEXV\

Figure 3-2 Continuous reading of each passing MDS/transponder (repeat_command remains set)
When permanent command repetition is used, data may be transferred to the FB 45 slower
than new MDSs are being processed (fast MDS sequence, slow data transmission). In such
cases, the results are intermediately stored on the ASM. The ASM has a number of buffers
for this intermediate storage. When the buffers are full and the FB 45 has not fetched data
and additional MDSs arrive, these MDSs are no longer processed.
Table 3- 17 Number of buffers on the ASM/SLG
ASM type No. of buffers per channel Max. user data which can be
processed with command
repetition
RF170C 150 34950 bytes
ASM 475/473 70 16310 bytes
ASM 454 39 9087 bytes
ASM 754 9 2097 bytes
ASM 854 39 9087 bytes
ASM 452 3 699 bytes
ASM 456 150 34950 bytes
SLG U92* 150 34950 bytes
SLG D10S 100 23300 bytes
SLG D11S/D12S 1 233 bytes
RF300 246 57318 bytes
*) The number of buffers described here can always be used by MOBY U regardless of
the ASM type.
FB 45
Parameterizing
3.2 MOBY commands
One buffer can hold up to 233 bytes of user data.

● Specific reading (processing) of an MDS. The user starts the processing of each new
MDS in his/her application. The following time diagram illustrates this principle.
UHDG\
FRPPDQGBVWDUW
UHSHDWBFRPPDQG
$60BEXV\
$1=B0'6BSUHVHQW
7KHIROORZLQJVHTXHQFHPXVWEHSURJUDPPHGE\WKHXVHU
Ⴠ 7KHXVHUVHWVFRPPDQGBVWDUWDQGUHSHDWBFRPPDQGVLPXOWDQHRXVO\DWWKHVWDUWRIWKHFRPPDQG
Ⴠ 7KHXVHUZDLWVIRU$60BEXV\ DQGWKHQUHVHWVUHSHDWBFRPPDQG
Ⴠ 7KHFRPPDQGKDVEHHQSURFHVVHGDIWHUUHDG\ LVUHSRUWHGE\WKH)&
1RIXUWKHUWUDQVSRQGHUVDUHSURFHVVHGDXWRPDWLFDOO\E\WKHFRPPXQLFDWLRQPRGXOH
Figure 3-3 Specific reading with repeat_command by the user
Note
In the case of RFID systems with unique tag IDs (UID) (e.g. RF300, MOBY U), the stored
command is only repeated when the next tag entering the read field has a different UID
from the previous one. If the same tag (identical UID) enters the field again and again, the
tag will not be processed again.
FB 45
Parameterizing
3.3 Presence check and MDS control

Various operating modes can be parameterized for MDS control (with parameter
MDS_control).
The exact interaction between the modes of the following components
● Presence check
● MDS control
● Next command
is described in this chapter. In its default state, the ASM/SLG uses presence check and no
MDS control.
Presence check
The presence check is a piece of logic in the MOBY-ASM's firmware which recognizes
whether a mobile data memory is in the transmission window of the write/read device. It can
be controlled with various mechanisms. The selection is performed with parameter
MDS_control. A mechanism is currently available.
Field scanning (MDS_control = 1, 2):
The ASM/SLG's firmware continuously scans its surroundings via the magnetic field to
determine whether a mobile data memory is present. A hysteresis during field scanning
suppresses most of the switching back and forth of ANZ_MDS_present when a mobile data
memory stops on the border of the field.
Presence
A mobile data memory is located in the field of the write/read device. The presence bit
(ANZ_MDS_present in command and status word) is set (see Section "Command and status
word). The presence display is usually implemented via the PRE LED on the front of the
ASM (see Section "Brief description of ASM hardware").
MDS control
MDS control is turned on when "MDS_control = 2" is set. MDS control is an option of the
firmware of the ASM/SLG. It synchronizes the MDSs in the material flow with the user
program. It supplies an error message when synchronization is lost.
The following are considered asynchronous.
● MDS whose command was not fully processed by the ASM leaves the transmission
window.
● MDS which is moving through the transmissionn window but is not processed by the user
program.
An enabled MDS conrtol forces use of the NEXT command in the application.
FB 45
Parameterizing
NEXT command
The Next command switches ASM control to the next mobile data memory. The Next
command must always be programmed when MDS control is used (MDS_control = 2).
After the ASM acknowledges the Next command, a write/read job for the next MDS can be
sent immediately to the write/read device. The new command waits on the ASM until the old
MDS has left the field and a new one has entered.
This type of programming makes it possible to execute an ASM command as soon as an
MDS enters the field of the write/read device.
It can be very advantageous to add the NEXT command at the end of a command chain
(see Section "Command chaining").
3.3.1 No MDS Control, No Presence Check: MDS_control = 0

The magnetic field of the write/read device is not turned on unless a valid MDS command
(read, write, initialize) is started. After a data memory has been detected and the command
has been executed, the write/read device is turned off again. This makes it possible to
implement projects in which the distance from a write/read device to another write/read
device may be less than specified. Prerequisite: the write/read device stations which are
close to each other must be addressed in multiplex mode. This may become necessary in
applications in which large amounts of data must be transferred in dynamic operation.
Stopping the conveyor belt can be avoided by dividing up the data and spreading it over
several SLGs.
Note
The NEXT command cannot be used when the MOBY-ASM is run with MDS_control = 0. If
NEXT is started anyway, the error message error_MOBY = 10 hex is generated.
3.3.2 No MDS Control, Presence Control with Field Scanning: MDS_control=1

In this mode, the field of the selected write/read device is always ON. As soon as an MDS
moves into the field of the write/read device, this is indicated to the user via the
ANZ_MDS_present bit (see Section "Command and status word"). The user can then start a
command at any time. There is no error message if the MDS leaves the field during
processing.
Note
The NEXT command cannot be used when the MOBY-ASM is run without MDS control. If
NEXT is started anyway, the error message error_MOBY = 10 hex is generated.
FB 45
Parameterizing
3.3.3 Field Scanning as MDS Control: MDS_control = 2

After a new start or a restart of the AS or after a new start or RESET command of the FB 45,
the write/read device is turned on and remains active until the AS or ASM is turned off.
The ASM continuously scans the field around the write/read device for the presence of a
data memory. When the ASM detects a data memory, the ANZ_MDS_present bit is returned
to the user during the next bus cycle or FB call. Similarly, ANZ_MDS_present becomes 0
when the data memory moves out of the write/read device's field.
If the data memory stops exactly on the border of the magnetic field of the write/read device,
there is no danger of ANZ_MDS_present switching back and forth continuously. This
hysteresis function is handled by the processor on the ASM.
Read/write commands can be sent to the FB 45 with complete transparency for the MDS
control. The ANZ_MDS_present variable also retains complete validity after the start of a
command.
Table 3- 18 Field scanning as MDS control
:ULWHUHDG
GHYLFH K PP
GHSHQGVRQ0'6W\SH
F E
/
+\VWHUHVLVILHOGIRU
K
0'6FRQWURO
D
7UDQVPLVVLRQZLQGRZ
'LUHFWLRQRIPRWLRQRI
0'6 'DWDH[FKDQJHEHWZHHQ
0'6
0'6DQGZULWHUHDGGHYLFH
L, B: Dimensions of the transmission window of a write/read device / reader in working distance

to MDS / transponder (see MOBY I configuration manual)
L = field length; B = field width
h: Hysteresis: Area in which an ANZ_MDS_present bit which has been set once remains set
a: Point at which the mobile data memory is detected by the write/read device. From this
point on, the waiting MOBY command is processed with the MDS/transponder.
ANZ_MDS_present remains set.
b: The MOBY command must have been executed by this point since the data memory is
leaving the transmission window. ANZ_MDS_present still remains set.
c: Reset ANZ_MDS_present in command and status word. The MDS / transponder has left
the transmission window of the write/read device / reader. A command which has still not
been processed is terminated, and ASM error 01 hex is generated.
FB 45
Parameterizing
Time diagram
UHDG\
$GGLWLRQDOFRPPDQGVRSWLRQDO
FRPPDQGBVWDUW
5($'
FRPPDQGBVWDUW
1(;7
LQLWBUXQ
$1=B0'6BSUHVHQW
$SSO\ 5(6(7 0'6HQWHUV 5HDGZULWH $60KDV 0'6 $FRPPDQG

SRZHU FRPPDQGDIWHU ZULWHUHDG FRPPDQGV UHFHLYHGD OHDYHV IRUDQHZ
VXSSO\WR $60
VVWDUWXS GHYLFH
V DUHH[HFXWHG 1(;7 ZULWHUHDG 0'6FDQEH
$60 PHVVDJHQR ILHOG E\ FRPPDQG GHYLFH
V VWDUWHGE\WKH
0'6SUHVHQW ZULWHUHDG ILHOG )&)%
GHYLFH
൹7KHVHHGJHVPXVWEHFRQWUROOHGE\WKHXVHU
Figure 3-4 Time diagram for MDS_control = 2
ASM error messages
Error 01 hex: The MDS leaves the write/read device's field while a command is being
processed with this MDS. The command is aborted. The read data are
invalid. With a write command, the data on the MDS may be inconsistent.
Error 02 hex: No command is active on the ASM. During this time, an MDS passes
through the write/read device's field shown above or command processing
of the MDS is not concluded with NEXT. The error is reported during the
next FB 45 command.
NOTICE
• The ASM is unable to determine whether an MDS passed through the complete field or
whether the MDS moved into the field briefly and then backed out again.
• When using field scanning, it is essential to maintain the distance between two SLGs
specified in the configuration guidelines (see manual on configuration, installation and
service).
FB 45
Parameterizing
FB 45
Parameterizing
FB 45
Commissioning 4
Special information on commissioning the hardware and software for the RF620R/RF630R
readers can be found in the "Commissioning" section of the "Configuration Manual
RF620R/RF630R".
1. Step: Install ASM/communication module in STEP 7

● RF170C, ASM 475, ASM 473
The installation program for RF170C, RF180C, ASM 475, ASM 473 must be executed
once on the STEP 7-PC.
● PROFIBUS-ASM
The GSD file must be included in the device catalog using HW Config (Tools > Install
new GSD...):
– Siem8114.GSD for RF170C
– Siem809F.GSD for ASM 454, 754, 854, 850
– Siem80B6.GSD for ASM 452
● PROFINET communication module RF180C
The GSDML file must be included in the device catalog using HW Config (Tools > Install
new GSD...):
– GSDML-V1.0-SIEMENS-RF180C-20070122.xml
NOTICE
The "S7-compatible" setting results in addressing errors!
When using the ASM 452, 454, 456, 754, 850, 854 in conjunction with the GSD file,
the DP interface of the DP master must be set to "DP-V1".
FB 45
Commissioning
2. Step: Configure hardware in STEP 7

The configuration varies depending on which MOBY-ASM/communication module is being
used.
● ASM 475: Centralized configuration in S7-300
● ASM 475, 473: Distributed setup with PROFIBUS and ET 200M, ET 200X
● RF170C: distributed configuration via PROFIBUS or PROFINET and ET 200pro
● ASM 452, 456, 454, 754, 854, 850: Distributed setup with PROFIBUS
The following figure shows the placement of the MOBY-ASMs in the hardware catalog.
$60LQ HJ$60LQ $60

FHQWUDOL]HG GLVWULEXWHG LQGLVWULEXWHG
FRQILJXUDWLRQYLD FRQILJXUDWLRQYLD
Figure 4-1 Placement of the MOBY-ASMs in the hardware catalog
FB 45
Commissioning
When configuring the ASMs, make sure that the I address and the Q address have the same
values. The value in the I address field must be copied later on into the ASM_address
variable in the STEP 7 project. If a MOBY-ASM has more than one channel (e.g. ASM 475 =
2 channels; ASM 454 = 4 channels), the same I address must be used for every channel.
The following figure shows an example of a hardware configuration:
Figure 4-2 Example of a hardware configuration
If the project is downloaded onto the hardware in this state (without the user program), the
SIMATIC CPU and the PROFIBUS should switch to the RUN state. If they don't, continue
with PROFIBUS trouble-shooting (check the PROFIBUS address settings on the ASM
against the configuration in HW Config).
FB 45
Commissioning
3. Step: Set caracteristics of the ASM/communication module

If the interfaces (e.g., ASM 452, 473, 475) are different, you can now set the basic function
of the ASM (e.g., MOBY U, filehandler, etc.) in the object properties of the module. The
object properties are shown in one of the following windows. The possible options are shown
in the drop-down menus.
$60REMHFWSURSHUWLHV $60REMHFWSURSHUWLHVDUH
VWRUHGLQWKH*6'ILOH
Figure 4-3 Configuring the object properties
FB 45
Commissioning
4. Step: Edit STEP 7 project

This step is based on the sample program supplied with the system.
● Copy the sample program for FB 45 into the new STEP 7 project.
● Continue as shown below based on the number of MOBY channels (number of SLGs):
– Declare the UDT 10 in DB 45 and the associated MOBY 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 MOBY I/E, all you have to
do is adjust parameters ASM_address and ASM_channel to the HW Config
addresses. General requirement: All MOBY channels (write/read devices) use the
same command (DB47) and the same data (DB48).
7KHVHWZRYDULDEOHV :KHQFRPPLVVLRQLQJ02%<,(
PXVWEHPRGLILHGIRU WKHYDOXHLVFRUUHFWKHUH
HDFKFKDQQHO 2WKHUZLVHWKLVYDOXHPXVWEH
DGMXVWHG
7KHSRLQWHUWRFRPPDQGB'%FDQUHWDLQ
WKHGHIDXOWYDOXHRQLQLWLDOFRPPLVVLRQLQJ
Figure 4-4 Edit DB 45
● Edit OB 1 and program a cyclic FB 45 call for each channel; declare a bit memory for the
command start for each MOBY channel.
● Set the variable "init_run" in the parameter DB in OB 100 for each MOBY channel.
FB 45
Commissioning
5. Step: Download and test the program

● Download the project onto the SIMATIC CPU
● Connect a write/read device of the parameterized MOBY type to each MOBY channel.
● After restarting the SIMATIC CPU (STOP → RUN), the CPU should not be in STOP
mode. If the CPU does indicate STOP, you should continue by troubleshooting. This is
done by evaluating the diagnostic messages of the CPU (function: destination system -
module status).
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 parameterization of the FB 45 is set with MDS_control = B#16#1, the
presence check on the write/read device must already be active now. This is indicated by
the flickering RxD LED on the ASM. If you now place an MDS in the transmission window
of a write/read device, the PRE or ANW LED must go on.
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 variable" function to indicate the state of communication between FB 45
and ASM, examine errors and start commands. The following figure shows the necessary
variables: It can be found in the sample project under the name "Status Channel 1":
Figure 4-5 Variables for checking operation - VAT1
The variables ready = TRUE and error = FALSE should now be indicated for each channel.
If ready = FALSE:
● This channel is not called in OB 100.
● This channel is not processed cyclically by an FB 45 call in OB 1.
FB 45
Commissioning
If error = TRUE:
● The exact cause of the error is stored in variable error_MOBY, error_FB or error_BUS.
The error causes and their remedy are described in Section "Error messages and
troubleshooting".
The variable ANZ_MDS_present now indicates the presence of an MDS as soon as you
place an MDS in the transmission window of the write/read device. This is the same
indication as the PRE LED on the ASM.
You can now start the configured MOBY command via the auxiliary variable
"command_start" = TRUE. If there is no MDS in the write/read device's transmission
window, the command remains in processing on the ASM for an indefinite length of time.
This status is indicated by "ready" = FALSE in the "Modify variable" window. Now place
an MDS in the transmission window. As soon as the MDS has been processed, the result
is transferred to FB 45 and "ready" = TRUE is indicated.
● Commissioning of the MOBY components is thus complete. You can now program your
own MOBY application based on the sample program.
FB 45
Commissioning
FB 45
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.
FB 45
Error messages and troubleshooting
5.2 Error messages
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 was reported by the MOBY-ASM / write/read device.
There are two main reasons for this:
• Communication between ASM/communication module and write/read
device/reader or between write/read device/reader and MDS/transponder is
faulty.
• The ASM is unable to process the command.
Error_MOBY is indicated on the ASM on the ERR LED with an appropriate
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 is signaling an error. A PROFIBUS tracer and
a PROFIBUS tester (BT 200; Order No. 6ES7 181-0AA00-0AA0) is an
invaluable tool 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).
NOTICE
When several error occur with chained commands, the "error variable" always indicates the
first error detected.
FB 45
5.2 Error messages
error_MOBY
The ERR LED flashes when the ASM reports error messages.
Special information on error and flash codes for the RF620R/RF630R readers can be found
in the section "Error messages and troubleshooting" of the "Configuration Manual
RF620R/RF630R".
Table 5- 2 Error messages of the MOBY-ASM via the "error_MOBY" variable
Error code Flashing of Description

(B#16#..) ERR LED
00 – No error
Default value if everything is ok.
1x No error
ASM has executed a start-up and is waiting for an init_run.
01 2x Presence error: The MDS has moved out of the write/read device's
transmission window. The MOBY command was executed only
partially.
Read command: No data are transmitted to FB 45.
Write command: The MDS which just left the field contains an
incomplete data record.
• Distance between write/read device and MDS not adhered to
• Configuration error: The data record to be processed is too large (in
dynamic mode)
The next command is automatically executed on the next MDS. A
read, write or NEXT command is possible.
• With timeout: No MDS in field
02 2x Presence error: An MDS has passed by a write/read device without
being processed by a MOBY command.
Processing error: Command processing of an MDS (read and/or write)
was not concluded with NEXT.
This error message is not reported immediately. Instead, the ASM
waits for the next command (read, write, NEXT). This command is
immediately replied to with this error. This means that a read or write
command is not processed. The next command is executed normally
by the ASM again.
An init_run from the FB 45 also resets this error state.
Bit2 is set in parameter option_1 and no MDS is in the transmission
window.
03 3x Error in the connection to the write/read device. Write/read device does
not answer.
• Cable between MOBY-ASM and write/read device is wired
incorrectly or cable break.
• The 24 V supply voltage is not connected or is not on or has failed
briefly.
• Automatic fuse on the ASM has blown.
• Hardware defect
• Another write/read device is in the vicinity or is active.
• Interference on DI/DO, write/read device or PROFIBUS line
• Execute init_run after error correction
FB 45
5.2 Error messages

(B#16#..) ERR LED
04 4x Error in MDS's memory

The MDS has never been write-accessed or has lost the contents of its
memory due to battery failure.
• Replace MDS (if battery bit is set).
• Install MDS with the STG.
• Reinitialize MSD (see Section "Command parameter settings").
05 5x Unknown command
FB 45 is sending an uninterpretable command to the MOBY-ASM.
• Command_DB contains invalid command parameters.
• The command_DB was overwritten by the user
• The MDS reported an address error.
MOBY F:
• Read/write area is protected by password.
• FFT command can only be used when ANW check is off.
06 6x Field interference on write/read device
The write/read device is receiving interference from its environment.
• External interference field. The field of interference can be verified
with the "inductive field indicator" of the STG.
• The distance between two write/read devices is too small and does
not correspond to the configuration guidelines
• The connecting cable to the write/read device is defective or too
long or does not comply with the specification
• MOBY U: MDS has left the field during communication.
• MOBY U: Communication between write/read device and MDS was
terminated by interference (e.g., person/foreign body moving
between write/read device and MDS).
07 7x Too many transmit errors
The MDS was not able to correctly receive the command or the write
data from the ASM even after several attempts.
• The MDS is positioned exactly on the boundary of the transmission
window.
• Data transmission to the MDS is being affected by external
interference.
MOBY F: Another MDS was detected in the field while the command
was being processed.
08 8x CRC sending error
• The receiver monitor has detected at least one fault during
transmission.
– Cause same as error B#16#06.
• MDS signaling CRC error frequently.
– The MDS is positioned exactly on the boundary of the
write/read device.
– The hardware of the MDS and/or write/read device is defective.
09 9x Only during initialization: CRC error during acknowledgment receipt
from MDS
• Cause same as error B#16#06.
FB 45
5.2 Error messages

(B#16#..) ERR LED
0A 10x Only during initialization: MDS is unable to perform the initialization

command.
• MDS is defective.
0B 11x MOBY I: Only during initialization: Timeout during initialization of the
MDS
• The MDS is positioned exactly on the boundary of the transmission
window.
• The MDS needs too much current (defect).
• For MDS 507 only: Check FB 45 parameters MOBY_mode and
scanning_time
MOBY U: Memory of MDS cannot be read correctly.
0C 12x Memory of the MDS cannot be write-accessed.
• Memory of the MDS is defective.
• EEPROM MDS was written too frequently and has reached the end
of its service life
• MOBY E: The MDS left the transmission window while being write-
accessed. The data on the MDS may be incorrect.
0D 13x Address error
The address area of the MDS was exceeded.
• The start address in command_DB is invalid at command start (see
Section "Processing data memories")
• The start address must be ≥ 40 hex for MOBY F (MDS F4xx).
• The MDS is not the right type.
• RF300: Attempted write access to write-protected areas (OTP
area)
0E 14x ECC error (only possible when ECC_mode = TRUE)
The data could not be read by the MDS.
• Data of the MDS have been lost (MDS defective).
• The MDS was not initialized with ECC driver.
– Initialize MDS
• MDS with EEPROM has reached the end of its service life. The
data have been lost.
– Replace the MDS
• → The MDS was moved out of the transmission window while being
write-accessed.
– The MDS is not positioned correctly.
• → Command to ASM was issued incorrectly by user.
0F 1x Start-up message from ASM. The ASM was off and has not yet
received a RESET command.
• Execute an init_run
15x • The same physical ASM channel is used in two (or more) UDT 10
structures. Check ASM_address and ASM_channel in all UDT 10
structures.
Only with MOBY F:
• Internal driver error. Repeat command.
• FFT command was started with MDS F1xx in the field.
FB 45
5.2 Error messages

(B#16#..) ERR LED
10 16x Next command not possible or not permitted

• ASM is running without MDS control (MDS_control = 0,1).
• ASM has already received a Next command.
• ASM / write/read device doesn't recognize NEXT command.
11 – Short circuit or overload of the 24 V outputs (DQ, 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.
12 18x Internal ASM communication error
• Connector contact problem on the ASM
• Defective ASM hardware
– Return ASM for repair
• Start init_run command after error correction.
13 19x ASM / write/read device U does not have enough buffer to store the
command intermediately.
14 20x Internal ASM / write/read device error
• Program sequence error on the ASM
• Turn power of ASM off and on again.
• MOBY U: Watchdog errror on write/read device.
15 21x Wrong parameterization of the ASM/SLG
• Check INPUT parameters in UDT 10
• Check parameters in HW Config
• RESET command is parameterized incorrectly.
• After a start-up, the ASM has still not received an init_run.
16 22x The FB command cannot be executed with the ASM parameters on
PROFIBUS.
• Length of the input/output areas too small for the cyclic I/O word.
Did you use the right GSD file?
• FB command (e.g., read) with too much user data (data length >
233 bytes).
17 23x Communication error between FB 45 and MOBY-ASM
Handshake error
• Params_DB (UDT 10) of this ASM station is being overwritten by
other parts of the program
• Check parameters of MOBY-ASM in UDT 10
• Check FB 45 command which caused this error.
FB 45
5.2 Error messages

(B#16#..) ERR LED
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.
• Check parameters ASM_address, ASM_channel, and
MOBY_mode.
19 25x Previous command is active or buffer overflow.
The user sent a new command to the ASM although the last command
was still active.
• Active command can only be terminated with an init_run.
• Before a new command can be started the READY bit must be 1
(exception: init_run).
• Two FB 45 calls were parameterized with the same parameters
("ASM_address" and "ASM_channel").
• Two FB 45 calls are using the same Params_DB pointer.
• When command repetition (e.g., fixed code MDS) is used, no data
are fetched from the MDS. The data buffer on the ASM has
overflowed. MDS data have been lost.
1A – PROFIBUS DP error occurred.
• The PROFIBUS DP bus connection was interrupted
– Wire break on the bus
– Bus connector on ASM was removed briefly
• PROFIBUS DP master no longer addresses the ASM
• The ASM has detected a telegram 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 Only with MOBY F:
• CRC check in data telegram is incorrect. Checksum error between
ASM and write/read device
• Interface on ASM or write/read device is defective (hardware
defect).
• Check wiring of ASM-write/read device cable.
1C 28x The antenna of the write/read device is turned off. An MDS command
to the ASM was started in this state.
• Turn on the antenna with the command "antenna on/off."
• The antenna is turned on (off) and has received an additional turn-
on (turn-off) command.
• MOBY F: An FFT command was started when antenna was off
(antenna on/off with sub_command = 09).
1D – More MDSes are in the transmission window than the SLG is capable
of processing simultaneously.
• Only 1 MDS can be processed at a time with FB 45.
FB 45
5.2 Error messages

(B#16#..) ERR LED
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
• ASM hardware defect: ASM receives wrong data during 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 – Running command canceled by RESET (init_run or cancel) or bus
connector removed
• Communication with the MDS was terminated by init_run.
• This error can only be reported on init_run or cancel
FB 45
5.2 Error messages
error_FB
Table 5- 3 Error variable "error_FB"
Error code Description

(B#16#..)
00 No error; default value if everything is ok.
01 Params_DB not available in SIMATIC
02 Params_DB too small
• 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. The valid commands are described in Section "MOBY
commands".
• 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 telegram 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.
• Acknowledgement and command counters (see Section "Cyclic control word
between master and MOBY-ASM") between ASM and FB 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
09 The ASM has failed.
• Power failure on MOBY-ASM
• PROFIBUS connector removed or PROFIBUS cable interrupted
• ASM_address or ASM_channel not available
This error is indicated if the ASM_failure bit (see Section "Command and status
word") was set in OB 122. OB 122 is called if FB 45 can no longer access the cyclic
word for MOBY-ASM.
FB 45
5.2 Error messages

(B#16#..)
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 ASM channel is used in two (or more) UDT 10 structures.
Check ASM_address and ASM_channel in all UDT 10 structures.
0B init_run cannot be executed; cyclic Process image to the ASM is faulty; FB 45
reports timeout of the process image to the ASM
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 parameterized incorrectly. ASM_address may be for
wrong module.
• ASM_channel setting is ≥16 or ≤0
• ASM hardware/firmware is faulty.
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.
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 ASM off and on again.
• The RUN/STOP switch on the CPU was pressed rapidly several times in
succession (particularly with slow PROFIBUS baud rates)
FB 45
5.2 Error messages
error_BUS
Note
The following table of bus errors does not claim to be complete. If you receive any messages
that are not documented here, follow the instructions in the help file for SFB 52/53 in
SIMATIC Manager.
Table 5- 4 Error variable "error_BUS"

(W#16#...)
800A ASM is not ready (temporary message).
• This message is given to a user who is not using the FB 45 and is polling the
ASMs acyclically, one after the other, very quickly.
8x7F Internal error on parameter x. Cannot be remedied by the user.
8x22 Area length error on reading parameter.
8x23 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 Area error on reading parameter.
8x25 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 Alignment error on reading parameter.
8x29 Alignment error on writing parameter.
The reference to parameter x is an operand whose bit address is not equal to 0.
8x30 The parameter is located within the write-protected global DB.
8x31 The parameter is located within the write-protected instance DB.
8x32 The parameter contains a DB number which is too high.
8x34 The parameter contains an FC number which is too high.
8x35 The parameter contains an FB number which is too high.
8x3A The parameter contains a DB number which is not loaded.
8x3C The parameter contains an FC number which is not loaded.
8x3E The parameter contains an FB number which is not loaded.
8x42 An access error occurred while the system was attempting to read a parameter from
the I/O area of the inputs.
8x43 An access error occurred while the system was attempting to write a parameter to
the I/O area of the outputs.
8x44 Error on nth (n > 1) read access after an error occurred.
8x45 Error on nth (n > 1) write access after an error occurred.
8090 Specified logical base address is invalid: No assignment in SDB1/SDB2x exists, or it
is not a base address.
8092 A type other than BYTE has been specified in an ANY reference.
FB 45
5.2 Error messages

(W#16#...)
8093 The area identifier contained in the configuration (SDB1, SDB2x) of the logical
address is not permitted for these SFCs. Permitted:
• 0 = S7-400
• 1 = S7-300
• 2, 7 = DP modules
80A0 Negative acknowledgment while reading from module. FB fetches acknowledgment
although no acknowledgment is ready.
A user who is not using the 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
ASM 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.
80C0 • RDREC:
The module has record, but it doesn't have any read data.
• WRREC:
ASM 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 the FB 45. If this error occurs, the FB 45 waits until the
system is able to provide resources again.
80C4 Communication error
• Parity error
• SW ready not set
• Error in block length management
• Checksum error on CPU side
• Checksum error on module side
80C5 Distributed I/O not available
FB 45
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.
5HVWDUW6HWLQLWBUXQ
ൺ2%
&\FOLFVFDQQLQJ6HWFRPPDQGBVWDUW
ൺVWDUWFRPPDQGRQO\LIUHDG\
UHDG\
"
< 1
HUURU
" 3RVVLEOHWLPHRXW
< 1 PRQLWRULQJE\XVHUൺ
LQLWBUXQRU
$1=BUHVHWRU FDQFHORQWLPHRXW
$1=BFDQFHOVHW
"
1 <
EDWWHU\BORZ
"
< 1
ಯ&KDQJHEDWWHU\ರ
PHVVDJHRQ +HUHQR
SULQWHU FRPPXQLFDWLRQ
WRRNSODFHZLWK
(UURUKDQGOLQJ WUDQVSRQGHU
ൺHYDOXWLRQRI &RPPDQG2.
HUURUB02%<
HUURUB)&
DQG &RPPDQG2.
HUURUB%86 ൺSURFHVVGDWD
6HWFRPPDQGBVWDUW
ൺVWDUWQH[WFRPPDQGLIGHVLUHG
Figure 6-1 Structogram for scanning of FB 45
FB 45
Examples/applications
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 MDS type

2 (1.7) Kbytes RAM MOBY I e.g. MDS 302
8 (7) Kbytes EEPROM / FRAM MOBY I e.g. MDS 413E
32 (28) Kbytes FRAM MOBY I e.g. MDS 514
752 bytes EEPROM MOBY E e.g. MDS E600
5 bytes Fixed code MOBY F e.g. MDS F125
192 bytes EEPROM, 4 bytes of fixed MOBY F e.g. MDS F415
code
2 KB RAM, 16 bytes OTP MOBY U e.g. MDS U313
32 KB RAM, 16 bytes OTP MOBY U e.g. MDS U524
44 bytes EEPROM MOBY D e.g. MDS D139/
I-Code 1
112 bytes EEPROM MOBY D * I-Code SLI
256 bytes EEPROM MOBY D * Tag-it HF-I/MDS D2xx
992 bytes EEPROM MOBY D * MDS D3xx
2000 bytes FRAM MOBY D * MDS D4xx (available
soon)
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. RF350T (64K)
*) also for operation with RF300 readers that support ISO mode.
Special information on the data memory types of the RF600 system and on addressing can
be found in the section "Examples/Applications" of the "Configuration Manual
RF620R/RF630R".
Addressing
The data memories are addressed linearly from address 0000 (or the specified start
address) to the end address. The ASM or write/read device automatically recognizes the
size of the memory on the MDS. When the end address on the MDS is exceeded, the user
receives an error message in error_MOBY.
The next table shows the address space of the individual MDS versions. The variables
address_MDS and length (see Table "UDT 20 MOBY CMD" in Section "MOBY commands")
must be configured according to this address space.
FB 45
Address space of MDS versions for MOBY I, E, F, U and D
System Addressing 16-bit hexadecimal number Integer number

MOBY I 2 KB data memory with RAM
Start address 0000 0000 (with ECC) +0 +0 (with ECC)
End address 07FC 06F1 (with ECC) +2044 +1777 (with ECC)
8 KB data memory with EEPROM/RAM/FRAM
End address 1FFC 1BF1 (with ECC) +8188 +7153 (with ECC)
32 KB data memory with RAM/FRAM
End address 7FFC 6FF1 (with ECC) +32764 +28657 (with
ECC)
MOBY E 752 byte data memory with EEPROM
Start address 0000 +0
End address 02EF +751
ID No.: (fixed-coded; can only be read as a whole)
Start address 1FF0 +8176
Length 0004 +4
MOBY F MDS F1xx (5-byte fixed code)
Length 0005 +5
MDS F4xx (192 bytes)
End address 00FF +255
Length 0004 +4
MOBY U 2 KB data memory
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 FFF0 -16
Length 10 +16
ID No.: (4 fixed-coded bytes; can only be read with the MDS status command)
32 KB data memory
End address 7FFF +32767
Read OTP memory (write access only possible once)*
Length 10 +16
ID No.: (4 fixed-coded bytes; can only be read with the MDS status command)
FB 45

MOBY D MDS D139 (I-Code 1; 44 bytes)
End address 002B +43
Length 0008 +8
ISO-MDS (I-Code SLI; 112 bytes) *
End address 006F +111
Length 0008 +8
ISO MDS (Tag-it HF-I; 256 bytes) *
Length 0008 +8
ISO MDS (my-d SRF55V10P; 992 bytes) *
End address 03DF +991
Length 0008 +8
ISO-MDS (MB 89R118B, 2000 bytes) *
End address 07CF +1999
Length 0008 +8
*) also for operation with RF300 readers that support ISO mode.
FB 45
Address space of the transponder versions for RF300

RF300 20 bytes of data memory (EEPROM)
R/W or OTP memory (EEPROM)
(The EEPROM user memory for RF300 can be used either as R/W memory or as an OTP
memory (see RF300 system manual))
Start address FF00 -256
End address FF13 -237
ID No.: (fixed-coded; can only be output as a whole)
Length 0008 +8
8 KB data memory (FRAM/EEPROM)
R/W memory (FRAM)
End address 1FFC +8188
ID no.: (fixed-coded, can only be read as a whole)
Length 0008 +8
R/W memory (FRAM)
End address 7FFC +32764
Length 0008 +8
R/W memory (FRAM)
End address FEFC –
FB 45

Length 0008 +8
RF300: General notes on the meaning of the OTP memory

RF300 tags and ISO tags have a memory area that can be protected against overwriting.
This memory area is called OTP. Five block addresses are available for activating the OTP
function:
● FF80, FF84, FF88, FF8C and FF90
A write command to this block address with a valid length (4, 8, 12, 16, 20 depending on the
block address) protects the written data from subsequent overwriting.
NOTICE
OTP writing/locking should only be used in static operation.
NOTICE
Use of the OTP area is not reversible.
If you use the OPT area, you cannot undo it, because the OPT area can only be written to
once.
FB 45
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.
FB 45
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 always contains the OTP data:
R/W EEPROM Write ISO (MOBY D) OTP once

(all MDS types)
Tag Type Address Length Address Length Length MB89
ISO I-Code SLI 001B 1 .. 16 FF80 4,8,12,16 8,10

(NXP SL2 ICS20)
ISO Tag-it HFI 005F 1 .. 16 FF84 4,8,12 -
(Texas Instruments)
ISO my-d 03CF 1 .. 16 FF88 4,8 8
(Infineon SRF 55V10P)
ISO 07BF 1 .. 16 FF8C 4 -
(Fujitsu MB89R118)
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.
FB 45
6.3 Cyclic calling of FB 45 (e.g. in OB 1)
6.3 Cyclic calling of FB 45 (e.g. in OB 1)

The following program is an example of how to call and scan FB 45 in an application. The
definition of the data structure is described in Section "Data structure definition". The
parameter settings for the MOBY command were set up during the definition of the "MOBY
DB".
Block: OB1 cycle execution
Network: 1 call FB45

memory bit 1.0 is set: Start MOBY command for 1st SLG
memory bit 1.1 is set: Start MOBY command for 2nd SLG
memory bit 1.2 is set: Start init_run for 1st SLG
memory bit 1.3 is set: Start init_run for 2nd SLG
memory byte 2: OB1 used as edge triggered memory
CALL "MOBY FB", DB100 // Call FB 45 for each

Params_DB :=45 MDS in each cycle
Params_ADDR :=0
CALL "MOBY FB", DB101

Params_DB :=45
Params_ADDR :=50
A M 1.2 // memory bit init_run for

FP M 2.2 1st
S "MOBY DB".SLG[1].init_run MDS
SPB x01
UN "MOBY DB".SLG[1].ready
SPB x01
U "MOBY DB".SLG[1].error
SPB x01
A M 1.0 // memory bit command_start

FP M 2.0 for 1st MDS
S
"MOBY DB".SLG[1].command_start
x01: A M 1.3 // memory bit init_run for

FP M 2.3 2nd
S "MOBY DB".SLG[2].init_run MDS
SPB x02
AN "MOBY DB".SLG[2].ready
SPB x02
A "MOBY DB".SLG[2].error
SPB x02
A M 1.1 // memory bit command_start

FP M 2.1 for 2nd MDS
S
"MOBY DB".SLG[2].command_start
x02: NOP 0
FB 45
6.4 Programming a cold and warm restart
6.4 Programming a cold and warm restart

The MOBY-ASM is restarted by setting the "init_run" variable. The ASM and FB 45 are
completely reparameterized and synchronized with init_run.
An init_run is necessary after
● switching on the SIMATIC (OB 100)
● Power supply of ASM is turned on.
● an interruption in PROFIBUS communication
● an error message in variable "error_BUS"
Block: OB100 complete restart
Network: 1 set init_run bit for all channels which are configured in DB45
SET
S "MOBY DB".SLG[1].init_run
S "MOBY DB".SLG[2].init_run
In a distributed configuration of an ASM (e.g. via PROFIBUS), the ASM may be switched off
and on again due to system conditions (see Section "Programming a module failure"). When
this happens, the ASM reports the power failure to the FB 45 (and thus to the user). The
user must then perform an init_run for this ASM before a MOBY 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").
FB 45
6.5 Programming a module failure

The failure of a PROFIBUS module can be detected primarily using the PROFIBUS system
diagnostics.
However, if a failed slave is addressed via FB 45, an I/O access error is generated in
SIMATIC.
As a result
● OB 122 is called.
● the PLC switches to STOP if no OB 122 is programmed.
A feature implemented in FB 45 allows a normal error to be signaled to the user
(error_FB=09) when a MOBY PROFIBUS slave fails. To do this, the user sets bit
"ASM_failure = 1" in OB 122 for the failed MOBY channel. The following example shows a
possible OB 122 implementation.
Block: OB122
Network: 1 Reset channel 1 on error
L #OB122_MEM_ADDR // Temporary OB122

L
"MOBY DB".SLG[1].ASM_address
-D
SRW 1 // Formula:
L 1 // (#OB122_MEM_ADDR –
+D write/read
device[x].ASM_address) / 2 + 1
L "MOBY DB".write/read // Compare with config.

device[1].ASM_channel channel
==I
JCN x1
SET // Power failure on ASM

S
"MOBY DB".SLG[1].ASM_failure
x1: NOP 0
FB 45
Network: 2 Reset channel 2 on error
L #OB122_MEM_ADDR
L
"MOBY DB".SLG[2].ASM_address
-D
SRW 1 // Formula:
L 1 // (#OB122_MEM_ADDR -
+D write/read
device[x].ASM_address) / 2 + 1
L // Compare with config.

"MOBY DB".SLG[2].ASM_channel channel
==I
SPBN x2
SET // Power failure on ASM

S
"MOBY DB".SLG[2].ASM_failure
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 ASM has been corrected and the ASM is ready for operation again, the
user must send an init_run to the FB 45. The ASM is then ready for operation.
FB 45
6.6 Data structure definition

The developer can define different MOBY data structures depending on the structure of the
application. Some example structures are given below.
1st example
Four SLGs are parameterized. One command is assigned to each write/read device. MOBY
parameters (DB 45), MDS commands (DB 47), and data (DB 48) are assigned to different
data blocks. The declaration view is shown.
Block: DB45; MOBY parameters
Address Name Type Initial value Comment

0.0 STRUCT
+0.0 Write/ ARRAY [1..4]
read
device
*50.0 UDT10
=200.0 END_STRUCT
Block: DB47; 4 MDS commands

0.0 STRUCT
+0.0 Command ARRAY [1..4]
*10.0 UDT20
=40.0 END_STRUCT
Block: DB48; MOBY data

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.
FB 45
2nd example
2 commands are assigned directly to each MOBY channel. The MOBY parameters and the
MOBY commands of all write/read devices are stored in a "MOBY DB". A nested structure is
used in the declaration.
'HFODUDWLRQYLHZ 'DWDYLHZVFKHPDWLF
'% 02%<B'%
6758&7 &KDQQHO>@
FKDQQHO$55$<>@
8'7 &KDQQHO>@
6758&7
FRPPDQG$55$<>@
8'7 &KDQQHO>@
(1'B6758&7
(1'B6758&7
FRPPDQGBVWDUW
LQLWBUXQ
FRPPDQGB'%BQXPEHU 7KH02%<FRQWURO
FRPPDQGB'%BDGGUHVV SDUDPHWHUVDQGWKH
FRPPDQGVDVVRFLDWHG
UHDG\ ZLWKHDFKFKDQQHODUHDOO
HUURU DYDLODEOHLQDGDWDEORFN
IRUDOO02%<FKDQQHOV
&KDQQHO>@
&RPPDQG>@
&KDQQHO>@
&RPPDQG>@
FRPPDQG
DGGUHVVB0'6
OHQJWK
'$7B'%BQXPEHU
'$7B'%BDGGUHVV
Figure 6-2 Example of several MOBY commands assigned to one channel
FB 45
The following shows an extract from a STEP 7 user program. It shows how a large number
of MOBY channels can be handled easily using symbolic names. A command is started via
each of the inputs 0.0, 0.1 and 0.3. An edge trigger flag is used to prevent the command
from being started several times:
A MOBY DB.channel[1].ready // 1st MOBY

AN MOBY DB.channel[1].error
A I 0.0
AN EdgeTriggerFlag_1
S MOBY DB.channel[1].command_start
S EdgeTriggerFlag_1
AN I 0.0
R EdgeTriggerFlag_1
A MOBY DB.channel[2].ready // 2nd MOBY

A I 0.1
S EdgeTriggerFlag_2
AN I 0.1
R EdgeTriggerFlag_2
A MOBY DB.channel[3].ready // 3rd MOBY

A I 0.3
S EdgeTriggerFlag_3
AN I 0.3
R EdgeTriggerFlag_3
Call "MOBY FB", DB100

Params_DB: = 45
Params_ADDR: = 0

Params_DB: = 45
Params_ADDR: = 70

Params_DB: = 45
Params_ADDR: = 140
FB 45
3rd example
A separate data block is assigned to each MOBY channel. It contains the parameters,
commands and data for a channel. Space for 10 MOBY channels should be reserved on
each channel.
'HFODUDWLRQYLHZ 'DWDYLHZVFKHPDWLF
'%5HDGHU
5HDGHU'%
8'7
6758&7
FRPPDQG$55$<>@ $GG 5HDGHU'%
8'7
(1'B6758&7
$GG
GDWD$55$<>@ 5HDGHU'%

%<7(
(QG6758&7
$GG 1DPH

$60BDGGUHVV
$60BFKDQQHO

'%5HDGHU

8'7
6758&7
FRPPDQG$55$<>@
8'7

(1'B6758&7
GDWD$55$<>@
%<7(
(QG6758&7

&RPPDQGFRPPDQG
&RPPDQGDGGUHVVB

'%5HDGHU 0'6
&RPPDQGOHQJWK
8'7
6758&7
FRPPDQG$55$<>@

8'7
(1'B6758&7
GDWD$55$<>@

%<7(
(QG6758&7 'DWD>@
'DWD>@

'DWD>@
'DWD>@

Figure 6-3 Example of a separate data block assigned to each MOBY channel
FB 45
6.7 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.
Special information on the UDTs for the RF620R/RF630R readers can be found in the
"Configuration Manual RF620R/RF630R".
Table 6- 2 UDT overview table
UDT Description Described

in
English German Spanish
10 11 14 Parameter data block ChapterParameter
data block
(Page 19)
20 21 24 MOBY commands ChapterMOBY
commands
(Page 31)
60 61 64 Parameter data block for MDS > 32 KB ChapterParameter
data block
(Page 19)
70 71 74 MOBY commands for MDS > 32 KB ChapterMOBY
commands
(Page 31)
100 101 104 Result of MDS status Section "UDTs of
FB 45 / FC 45"
110 111 114 Result of write/read device status Section "UDTs of
(sub_command = 01) FB 45 / FC 45"
120 121 124 Result of write/read device diagnosis I Section "UDTs of
130 131 134 Result of write/read device diagnosis II Section "UDTs of
140 141 144 Result of write/read device diagnosis III Section "UDTs of
230 231 234 Result of MDS status Section "UDTs of
(sub_command = 03, RF300) FB 45 / FC 45"
260 261 264 Result of MDS status Sample project on
(sub_command = 01, RF300) software CD
270 271 274 Result of MDS status Sample project on
280 281 284 Result of write/read device status Sample project on
FB 45
UDT 100: Result of MDS status
Table 6- 3 UDT 100 "MOBY MDS status"

Address Name Type Comment
0.0 STRUCT
+0.0 UID DWORD MDS (unique identifier)
+4.0 MDS_type BYTE MDS
+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 Actual sleep-time value on MDS
=18.0 END_STRUCT
UDT 110: Result of write/read device status (mode 1)
Table 6- 4 UDT 110 "MOBY write/read device status"

0.0 STRUCT
+0.0 status_info BYTE Write/read device 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
+19.0 distance_limiting_writ BYTE Ranges/performance setting
e/read device (RF300: res.)
+20.0 multitag_write/read BYTE Multitag write/read device
device
+21.0 field_ON_control_write BYTE BERO operating mode
/read device (RF300: res.)
+22.0 field_ON_time_write/re BYTE MOBY U: BERO time
ad device MOBY D: MDS type
(RF300: res., RF300-ISO *)
+23.0 sync_write/read device BYTE Semaphore control (synchronization with
write/read device)
(RF300: res.)
+24.0 status_ant BYTE Status of antenna
+25.0 stand_by BYTE Time of standby after command execution
(RF 300: res.)
+26.0 MDS_control BYTE Presence
=28.0 END_STRUCT
*) also for operation with RF300 readers that support ISO mode: 6GT2801-3AB01 and 6GT2801-1AB10
MDS type MDS D139 can only be operated with reader 6GT2600-0AA10.
FB 45
UDT 120: Result of write/read device diagnosis I
Table 6- 5 UDT 120 "MOBY write/read device-Stat Diag 1"

0.0 STRUCT
+0.0 status_info BYTE Write/read device status mode
+1.0 number_functions BYTE Range: 1...33
+2.0 function_01_01 BYTE *
. .
. .
. .
=234.0 END_STRUCT
*) An area of seven bytes each is reserved for 33 commands.
UDT 130: Result of write/read device diagnosis II

0.0 STRUCT
+1.0 number_errors BYTE Range: 1...235
+2.0 error_number ARRAY [1...235] Error appeared on write/read device
*1.0 BYTE
=238.0 END_STRUCT
UDT 140: Result of write/read device diagnosis III

0.0 STRUCT
+1.0 number_MDS BYTE Range: 1...24
+2.0 UID ARRAY [1...24] Identified UID (MDS number)
*4.0 DWORD
=98.0 END_STRUCT
FB 45
6.7.1 UDT 230: Result of MDS status (mode 3, RF300)
UDT 230: Result of MDS status (mode 3, RF300)
Table 6- 8 UDT 230: "MDS status (mode 3, RF300)"

0.0 res. STRUCT
+1.0 status_info BYTE MDS status mode
+2.0 UID ARRAY[1...8] Number of MDS (unique identifier)
BYTE
+10.0 MDS_type BYTE MDS type
+11.0 IC_version BYTE Chip version (for my-d = 00h)
+12.0 Size BYTE Memory size in bytes
+14.0 lock_state BYTE Lock status, OTP information: per block
(4x4 bytes or 2x8 bytes) one bit (bit=1:
block is locked)
+15.0 block_size BYTE Block size of the transponder
+16.0 nr_of_blocks BYTE Number of blocks
=18.0 END_STRUCT
Table 6- 9 UDT 260 "MDS status (mode 1, RF300)"

0.0 STRUCT
BYTE
+9.0 MDS_type BYTE MDS type
01 = Tag without FRAM
02 = Tag with FRAM 8KB
+10.0 Lock_state BYTE EEPROM write protection status
%LW
QRWXVHG
%ORFN))))
%ORFN))&)))
%ORFN))))%
%ORFN))))
%ORFN))))
:ULWHSURWHFWLRQVWDWXV
EORFNQRWSURWHFWHGUZ
EORFNSURWHFWHGUR
+11.0 res. Reserved

to
+16.0
=18.0 END_STRUCT
FB 45
Table 6- 10 UDT 270: "MDS status (mode 2, RF300)"

0.0 res. STRUCT
BYTE
+10.0 LFD BYTE Relationship between power flow density
limit and actual 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 res. BYTE Reserved
to
+17.0
=18.0 END_STRUCT
UDT 280: Result of read/write status (mode 6, RF300)
Table 6- 11 UDT 280 "write/read device status (mode 6, RF300)"

0.0 STRUCT
+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 ASM
+8.0 res. BYTE Reserved
to
+26.0
=28.0 END_STRUCT
FB 45
6.8 Determing the memory requirement in the SIMATIC
6.8 Determing the memory requirement in the SIMATIC

The memory resources used in SIMATIC S7 by a MOBY application should normally not
reach the system limits on the PLC. However, if the following conditions occur
simultaneously, the memory requirement must be considered:
● SIMATIC S7 with small memory configuration
● Many MOBY channels (SLGs) are processed in one S7.
● Processing of large volumes of data on each MOBY channel
The example below shows a configuration for the S7 memory required by the FB 45. Twenty
SLGs with 1 KB of MDS data each are to be processed.
Memory Requirements [KB]

per channel Total
FB 45 (needed once) – ~8
Instance DB 0.14 2.8
Parameter data block (UDT 10) 0.05 1
Command data block (UDT 20) 0.01 0.2
DB for MDS data 1 20
Total 1.2 32
In this configuration, a SIMATIC CPU with only 48 KB memory can reach the memory limits
quickly if further programs are also running.
FB 45
Brief description of ASM hardware A
This appendix discusses the special features of the individual interface modules which can
be addressed with the FB 45.
For a detailed hardware description of the interface modules with installation notes, see the
appropriate MOBY manual on configuring, mounting and service.
A.1 RF170C
Area of application
The RF170C communication module is a SIMATIC S7 module. It can be plugged into the
ET 200pro distributed I/O station. The ET 200pro is operated by the user over
PROFIBUS DP V1 or PROFINET IO. An S7-300 or S7-400 with integrated
PROFIBUS/PROFINET connection can be used as the controller.
352),%86'3
PDVWHUPRGXOH
HJ6&38
0'6
352),%86FDEOHWR
5HDGHUZULWHUHDGGHYLFH
DOO
352),%86VODYHV ,QWHUIDFHPRGXOH
RIWKH(7SUR 5)&
9IRU5)&
DQGUHDGHUZULWHUHDGGHYLFH
P
VWDQGDUGFDEOHOHQJWK
Figure A-1 Configurator for an RF170C
FB 45
Brief description of ASM hardware
A.1 RF170C
Hardware configuration
The RF170C is integrated into the hardware configuration of the SIMATIC Manager
preferably via the Object Manager. The object manager can be found on the CD RFID
Systems Software & Documentation from Edition 03/2006 (6GT2080-2AA10) as SETUP.exe.
The object manager provides the functions for PROFIBUS DP and PROFINET IO.
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 Tools > 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 via the object properties of the slave in HW Config. Please consult the FC 45
Function Manual for a description of the parameters. The table below shows the possible
settings:
Table A- 1 Setting of RFID-relevant parameters
Parameter name Value Note

USER_Mode FB 45 / FC 45 Default
FC 55
FB 56 / FC 56
RFID standard profile Available soon
MOBY_Mode MOBY I, E normal addressing Default
MOBY I filehandler only with FB 56/FC 56
RF300 / MOBY U/D normal
addressing
MOBY U filehandler only with FB 56/FC 56
(multitag)
Data transfer rate write/read 19.2 Kbps
device 57.6 Kbps 1
RF300/MOBY U/D 115.2 Kbps Default 1

Diagnostics with diagnostics None Standard diagnostics only
messages Hard errors Hardware-related messages
only
1 not permitted with MOBY D with SLG D11S/D12S
FB 45
A.1 RF170C
Input parameters for RF170C with FB 45/FC 45

Assignment is made in UDT 10.
Special information on the input parameters for the RF620R/RF630R readers can be found
Table A- 2 Input parameters for RF170C

Address Name Permissible values Comment
+0.0 ASM_address 256, 260, 264, 268, Each RF170C occupies four bytes of
... I/O in the I/O area of the control
unit
+2.0 ASM_channel 1, 2
+8.0 MDS_control B#16#0, 1 0 = no presence check
1 = presence check
+9.0 ECC_mode TRUE, FALSE
+9.1 RESET_long TRUE, FALSE TRUE,
if MOBY_mode = 5 (MOBY U/D, RF300)
+10.0 MOBY_mode B#16#1, 4, 5, 6, 7, Special features of the MOBY I dialog
8, 9, A, B (8):
• Write/read device must be type
SLG4x.
• The VMDS memory size is 16KB. The
INIT command for the VMDS must be
specified using 4000 hex.
+11.0 scanning_time MOBY I: A value not equal to 00 is only
B#16#00 ... FF practical if MOBY_mode has been
MOBY U: parameterized accordingly.
B#16#00 ... C8 MOBY D, RF300 reserved (00).
+12.0 option_1 B#16#00, 02, 04
+13.0 distance_limiting MOBY U (normal MOBY U/D
output power): RF300 reserved (00)
B#16#05, 0A, 0F, 14,
19, 1E, 23
MOBY U (reduced
output power):
B#16#85, 8A, 8F, 94,
99, 9E, A3
MOBY D:
B#16#02 ... 28
RF380R:
B#16#00, 02 ... 08
+14.0 multitag B#16#1 MOBY U/D, RF300
+15.0 field_ON_control MOBY U: MOBY U/D, RF300
B#16#0, 1, 2, 3
MOBY D:
B#16#0
+16.0 field_ON_time MOBY U: MOBY U/D
B#16#00 ... FF RF300 reserved (00)
MOBY D:
B#16#00, 01
FB 45
A.1 RF170C
Command table of the RF170C for normal addressing (FB 45 / FC 45 / FC 55)

Assignment is made in the UDT 20 by means of the "command" variable.
Table A- 3 Commands of the RF170C
Command code Description available in

the RFID system
normal chained*
01 41 Write to transponder / MDS all
02 42 Read transponder/MDS; read fixed code all
03 43 Initialize transponder / MDS all
04 44 Reader / write/read device status RF300 / RF600 /
MOBY U / D
08 48 Switch off transponder / MDS U
0A 4A Turn antenna on/off RF300 / RF600 /
MOBY U / D
0B 4B Transponder / MDS status RF300 / RF600 /
MOBY U
*) Chained commands are not supported by all readers / write/read devices. Please note the
relevant information in the RFID system manuals.
Diagnosis 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
FB 45
A.1 RF170C
Table A- 4 Status and error LEDs for RF170C
LEDs Meaning*
SF Group error
ACT_1, ACT_2 The corresponding reader / write/read device is active in processing a user
command.
ERR_1, ERR_2 * A flashing pattern indicates the last error to occur.
PRE_1, PRE_2 ** Indicates the presence of a transponder/MDS.
RxD_1, RxD_2 Indicates live communication with the reader / SLG. May also indicate
malfunctions on the reader / SLG.
* The meaning of the individual flashing patterns is described in the relevant FB and FC
documentation. The associated error descriptions are also to be found there.
** In multitag operation, this LED uses a flash interval to indicate the number of data carriers
currently within the range
of the reader / write/read device.
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 Off Off 1 x flash Off RF170C successfully started up, waiting
every 3 s every 3 s for reset command
– – n x flash – – m x flash – The number of flashes (n, m) indicates the
every 3 s every 3 s last reported error on a given channel.
– – Flashing Rapid – Flashing Rapid Firmware update; alternate flashing of the
flashing flashing error LEDs at approximately 1 Hz
– = not relevant
* If this error recurs, the module is defective and must be replaced.
FB 45
A.1 RF170C
Interfaces of the RF170C
Table A- 5 Pin assignment of the interfaces of the RF170C
X1, X2: Connection for reader / write/read device

Pin Signal
1 +24 V
2 –RxD

3 0V
4 RxD

5 TxD
6 –TxD
7 free
8 PE / shield
Off-the-shelf reader / write/read device connection cables are available for the RF170C.
The appropriate cable and M12 connectors are available for users who want to make their
own cables.
FB 45
A.2 RF180C
A.2 RF180C
Area of application
The RF180C communication module is a SIMATIC S7 module. The RF180C communication
module is a module for operating RFID components via PROFINET IO on any controller. Up
to two readers / SLGs can be operated on the RF180C at the same time. The user can issue
a command to 2 readers / SLGs simultaneously (FB 45 when operating on a SIMATIC S7).
6WHXHUXQJ
]%6&38
5)&
;
352),1(7,2/HLWXQJ
;
9I¾U5)&XQG5HDGHU6/*
]XZHLWHUHQ
352),1(7,27HLOQHKPHUQ
5HDGHU 5HDGHU
7UDQVSRQGHU
Figure A-3 Configurator for RF180C
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" CD or on the Internet (see section Service & Support (Page 167)).
● GSDML-V1.0-SIEMENS-RF180C-"Date in yyyymmdd".xml
● The RF180C must have a valid IO device name. The default device name is RF180C
FB 45
A.2 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
The table below shows the possible settings:
Table A- 6 Setting of RFID-relevant parameters

USER_Mode FB 45 Default
FB 55 With later firmware version
FB 56 With later firmware version
RFID standard profile With later firmware version
MOBY_Mode MOBY I / E standard addressing
MOBY I filehandler With later firmware version
MOBY U / D / RF300 standard Default
addressing
MOBY U filehandler With later firmware version
Baud rate for write/read 19.2 Kbps
device RF300 / 57.6 Kbps 1)
MOBY U/D
115.2 Kbps Default 1)
Diagnostics with diagnostics None Standard diagnostics only
messages (see Diagnostics Hard errors Hardware-related messages
chapter) only
Hard/soft errors low priority All messages
Hard/soft errors high priority All messages high-priority
1) Not permitted with MOBY D with SLG D11S/D12S
FB 45
A.2 RF180C
Input parameters for RF180C with FB 45/FC 45

Table A- 7 Input parameters for RF180C with FB 45

+0.0 ASM_address 256, 260, 264, 268, Each RF180C occupies four bytes of
... I/O in the I/O area of the controller
1 = presence check
if MOBY_mode = 5 (MOBY U/D; RF300)
8, 9, A, B (8):
SLG4x.
B#16#00 ... C8 MOBY D, RF300 reserved (00)
+12.0 option_1 B#16#00, 02, 04
B#16#05, 0A, 0F, 14,
19, 1E, 23
MOBY U (reduced
output power):
B#16#85, 8A, 8F, 94,
99, 9E, A3
MOBY D:
B#16#02 ... 28
RF380R:
B#16#00, 02 ... 08
B#16#0, 1, 2, 3
MOBY D, RF300:
B#16#0
B#16#00 ... FF RF300 reserved (00)
MOBY D:
B#16#00, 01
MOBY D:
B#16#00, 01
FB 45
A.2 RF180C
Table of commands of the RF180C for standard addressing (FB 45)

Table A- 8 Commands for RF180C with standard addressing
Command code Description Available in

the RFID system
normal chained*
01 41 Write MDS all
02 42 Read MDS; read fixed code all
03 43 Initialize MDS all
04 44 SLG status RF300 / RF600 / MOBY U
/D
08 48 Switch off MDS MOBY U
0A 4A Turn antenna on/off RF300 / RF600 / MOBY U
/D
0B 4B MDS status RF300 / RF600 / MOBY U
*) Chained commands are not supported by all readers / write/read devices. Please note the relevant
information in the RFID system manuals.
FB 45
A.2 RF180C

The following figure shows details of the LEDs of the RF180C.
5HDGHU6/*
6,0$7,&5)&
6,0$7,&5)&
$&7B 35(B
;
5['B (55B
;
5HDGHU6/*
$&7B 35(B
5['B (55B ;
;
*7-' *7-'
6) %) 21 '&9
[ [
/LQN 5;7;
[ [
[ [
[ [
Figure A-4 LEDs of the RF180C
FB 45
A.2 RF180C
Table A- 9 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/SLG is active in processing a user command.
PRE_1, PRE_2 ** Indicates the presence of a tag/MDS.
RxD_1, RxD_2 Indicates live communication with the reader / SLG. May also indicate malfunctions on the
reader / SLG.
*) The meaning of the individual flash patterns and the associated fault descriptions can be found in the relevant FB
documentation.
**) In multitag mode, this LED uses a flash interval to indicate the number of data media currently within the range of
influence of the reader/SLG.
Table A- 10 LED display for PROFINET diagnostics
BF SF Cause of error Error correction

On – • Communication module is in start- When the bus is configured correctly, this state ends a
up mode. few seconds after switching the module on.
• No cable inserted
Flashes - • There is no connection to the • Check the PROFINET IO connection.
PROFINET IO controller. • 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 • Analyze the diagnostic data.
exists.
Off Off • Normal mode –
– = Status not relevant
Table A- 11 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:
FB 45
A.2 RF180C
Table A- 12 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 Off Off Slow Off Firmware update
flashin flashin (flashes with every described area)
g g
FB 45
A.3 ASM 456
A.3 ASM 456
Area of application
The ASM 456 interface modules are slave modules for operating MOBY components via the
PROFIBUS DP/DP-V1 on any control systems.
352),%86'3
0DVWHUPRGXOH
HJ6&38
$60b
;
352),%86&DEOH
;
P
9IRU$60DQG6/*V
WRRWKHU
352),%86EXVQRGHV
QG6/* VW6/*
0'6 0'6
6WDQGDUGFDEOHOHQJWK
Figure A-5 ASM 456 configurator
FB 45
A.3 ASM 456
Design
The ASM 456 has the same housing as the distributed I/O station ET 200eco.
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.
02%<$60
&RQQHFWRUVRFNHWIRUVWZULWHUHDGGHYLFH
; 6WDWXV/('VIRURSHUDWLRQ
RIVWZULWHUHDGGHYLFH
&RQQHFWRUVRFNHWIRUQGZULWHUHDGGHYLFH
; 6WDWXV/('VIRURSHUDWLRQRIWKH
QGZULWHUHDGGHYLFH
6WDWXV/('VIRULQWHUIDFHPRGXOH
*7('
6SDFHIRUFRQQHFWLRQEORFN
3URWHFWLYH(DUWK
Figure A-6 Basic design of the ASM 456
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 "Tools > Install new
GSD ...". You will find the file on the CD RFID Systems Software & Documentation in the
directory daten\PROFI_GSD\ASM456.
For full functionality (diagnostics texts, firmware update), support for GSD revision 5 or
higher is required.
FB 45
A.3 ASM 456

In addition to the PROFIBUS-relevant control parameters, several MOBY-relevant control
parameters are also defined for the ASM 456 in the GSD file. The MOBY-relevant
parameters are set using the "Object properties" of the slave in the hardware configuration.
The following table shows the possible settings:
Table A- 13 Setting of MOBY-relevant parameters

USER_Mode FB 45 / FC 45 Default
FC 55
FB 56 / FC 56
RFID standard profile with later firmware version
MOBY_Mode MOBY I, E normal addressing (Default)
MOBY I filehandler only with FB/FC 56
MOBY U/D/P normal addressing
MOBY U filehandler only with FB/FC 56 (multitag)
Data transfer rate write/read 19.2 Kbps
device 38.4 Kbps
MOBY U/D or RF300
57.6 Kbps 1
115.2 kbps (Default) 1

Diagnostics with diagnostic None Standard diagnostics only
messages (see Section "Error Hard errors Hardware-related messages
messages and only
troubleshooting" )
Hard/soft errors low priority All messages
Hard/soft errors high priority All messages high-priority
1) not permitted with MOBY D with write/read device D11S/D12S
FB 45
A.3 ASM 456
Input parameters for ASM 456

Table A- 14 Input parameters for ASM 456

+0.0 ASM_address 256, 260, 264, 268, Each ASM 456 occupies four bytes of
... I/O in the I/O area of the
controller.
1 = presence check
if MOBY_mode = 5 (MOBY U/D, RF300)
8, 9, A, B (8):
SLG4x.
B#16#00 ... C8 MOBY D, RF300 reserved (00).
+12.0 option_1 B#16#00, 02, 04
B#16#05, 0A, 0F, 14,
19, 1E, 23
MOBY U (reduced
output power):
B#16#85, 8A, 8F, 94,
99, 9E, A3
MOBY D:
B#16#02 ... 28
RF380R:
B#16#00, 02 ... 08
B#16#0, 1, 2, 3
MOBY D:
B#16#0
B#16#00 ... FF RF300 reserved (00)
MOBY D:
B#16#00, 01
FB 45
A.3 ASM 456
Table of commands for ASM 456

Table A- 15 Commands for ASM 456

the MOBY system
normal chained*
01 41 Write MDS all
04 44 SLG status RF300 / RF600 /
MOBY U / D
08 48 Switch off MDS U
0A 4A Switch antenna on/off RF300 / RF600 /
MOBY U / D
0B 4B MDS status RF300 / RF600 /
MOBY U
*) Chained commmands are not supported by all write/read devices. Please note the relevant
information
in the MOBY system manuals.
FB 45
A.3 ASM 456

The following figure shows details of the LEDs of the ASM 456.
02%<$60
$&7B 35(B
6/*
5['B (55B
;
$&7B 35(B
6/*
5['B (55B
;
*7(' 352),%86
6) %) 21 '&9
Figure A-7 LEDs of the ASM 456
Table A- 16 Status LEDs for ASM 456
LEDs Meaning*
ON Lights up when there is logic voltage at the ASM (is generated by the 24 V
supply voltage.)
24 V DC Lights up when the 24 V supply voltage is connected to the ASM.
ACT_1, ACT_2 The corresponding SLG is active in processing a user command.
PRE_1, PRE_2 ** Indicates the presence of an MDS.
RxD_1, RxD_2 Indicates live communication with the write/read device. May also indicate
malfunctions on the write/read device.
*) The meaning of the individual flash patterns and the associated fault descriptions can be
found in the relevant FB and FC documentation.
**) In multitag mode, this LED uses a flash interval to indicate the number of data carriers currently
within the range of the write/read device.
FB 45
A.3 ASM 456
Table A- 17 LED display for PROFIBUS diagnosis
BF SF Cause of error Error correction

On – • ASM is in start-up mode. –
• Connection to DP Master failed. • Check the PROFIBUS DP
• ASM not detecting a baud rate connection.
• Check the DP Master
• Bus interrupt • Check all cables on your
• DP Master not functioning 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 • Check the project for the ASM
the DP Master do not match the (input/output, PROFIBUS
configuration of the ASM. address).
• Correct GSD file being used?
Flashes – • ASM has detected the baud rate, but • Check the PROFIBUS address set
is not activated by the DP Master. in ASM and/or in the project
• ASM has not been assigned project software.
plans. • Check the project for the ASM
(station type).
On Flashe • There is a hardware defect in the • Replace the ASM.
s ASM.
Off On • Diagnosis available • Evaluate the diagnostic
information.
On Off • The set PROFIBUS address is • Set the address in the range 1 to
incorrect or greater than 99. 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:
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 Off Off 1 x flash Off ASM successfully started up, waiting
every 3 s every 3 s for reset command
On – – Flashing Rapid – Flashing Rapid Firmware update; alternate flashing of
flashing flashing the error LEDs at approximately 1 Hz
– = not relevant
FB 45
A.3 ASM 456
Pin assignment
Table A- 18 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 6LJQDO$
1 Electronics / encoder supply (1L+) 6LJQDO%
(voltage supply for ASM 456 and $ %
write/read device) (&2)$67K\EULGFDEOH

2 Ground for electronics/encoder supply
(1M) /
3 Load voltage ground (2M)
4 Load voltage supply (2L+) /
(unused on ASM 456)
*) You will find the assembly instructions in the packaging of the Han Brid Cu cable connector
and/or Han Brid Cu cable socket.
Table A- 19 Connection assignment for M12 connector (PROFIBUS DP)
Pin Assignment View of M12 connector

(wiring side)
1 Supply positive (P5V2) *
6XSSO\'3
2 Data line A (RxD / TxD-N) 6LJQDO$JUHHQ
3 Data reference potential (M5V2) *

4 Data line B (RxD / TxD-P)
6KLHOG
5 Shield
Thread Shield
6LJQDO%UHG
/RRSWKURXJK %XVFDEOH
FRQQHFWLRQ'3 FRUHVKLHOGHG
6LJQDO$JUHHQ

6KLHOG

6LJQDO%UHG
*) Can only be used for the M12 terminating resistor. Looping the voltage through to the
next connector via a 5-core cable is not permitted.
FB 45
A.3 ASM 456
Table A- 20 Pin assignment for 7/8" connector (supply voltages)
Pin Assignment View of 7/8" connector

(wiring side)
1 Load voltage ground (2M)
6XSSO\;
2 Ground for electronics/encoder supply (1M)
3 PE
/
4 Electronics / encoder supply (1L+)
(voltage supply for ASM 456 and write/read
device)

5 Load voltage supply (2L+) /
(unused on ASM 456)
/RRSWKURXJK
FRQQHFWLRQ; FRUHFDEOH
/

/
FB 45
A.4 ASM 475
A.4 ASM 475

The ASM 475 is an S7-300 module. It can be used in a centralized layout with an S7-300 or
in a distributed layout with an ET 200M.
$60b 2WKHUPRGXOHVIURP
WKH6UDQJH
LQFOXGLQJ$60
$60BFKDQQHO
:ULWHUHDGGHYLFH
:ULWHUHDGGHYLFH :ULWHUHDGGHYLFH DQG0'6IURPWKH
02%<(),8'
IDPLO\
0'6 0'6
Figure A-8 Configurator for ASM 475 (centralized layout)
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 RFID Systems Software & Documentation
CD. Currently, the ASM 475 cannot be integrated in masters of other manufacturers.
Write/read device / reader connection system

Prefabricated write/read device connection cables are available in various lengths for the
ASM 475. The cores at the open end to the ASM/communication module are marked with
connection numbers. When making the connections, make sure that the cable shield is led
over the shield connecting element. See MOBY manual on configuration, installation and
service for more information.
FB 45
A.4 ASM 475

The assignment is made in UDT 10 (see Section "Parameter data block").

+0.0 ASM_address 256, 272, 288 ... 752 Centralized layout:
Addresses are specified by HW
Config (see Section "Addressing of
256, 272, 288, ... 2 MOBY channels"). Distributed
layout:
1
Automatic or manual address
256, 260, 264, ... assignment
+2.0 ASM_channel 1, 2 2 parallel channels
+8.0 MDS_control B#16#0, 1 Enable/disable presence check
+9.0 ECC_mode TRUE, FALSE TRUE is only permitted when
MOBY_mode is parameterized with 1.
if MOBY_mode = 5 (MOBY U or RF300)
+10.0 MOBY_mode B#16#1, 5, A, B MOBY I/E/F/U1/D1
+11.0 scanning_time B#16#00 ... FF A value other than 00 is only
recommended when MOBY_mode was
parameterized appropriately (see
Section "INPUT parameters").
+12.0 option_1 B#16#00, 02, 04, ... See Section "INPUT parameters"
+13.0 distance_limiting B#16#05, 0A, 0F, 14, MOBY U1/D1/RF3001 (see Section "INPUT
19, 1E, 23 parameters")
+14.0 multitag B#16#1 MOBY U1/D1/RF3001 or RF3001
+15.0 field_ON_control B#16#0, 1, 2 MOBY U1/D1/RF3001 (see Section "INPUT
parameters")
+16.0 field_ON_time B#16#00 ... FF MOBY U1/D1/RF3001 (see Section "INPUT
parameters")
1) valid only for 6GT2 002-0GA10
2) valid only for 6GT2 002-0GA00
FB 45
A.4 ASM 475

The assignment is made in UDT 20 using the "Command" variable (see Section "Command
parameter settings").

the MOBY system
normal Chained3
01 41 Write MDS/transponder all
02 42 Read MDS/transponder. Read fixed all
code
03 43 Initialize MDS/transponder all
04 44 Write/read device status1 RF3002 /
RF600 /
MOBY U / D2
08 48 END1 U
0A 4A Switch antenna on/off RF300 / RF600 /
MOBY F / U / D
0B 4B MDS status1 RF300 / RF600 /
MOBY U
1) These commands are only available for 6GT2 002-0GA10.
2) Please read Section "Command parameters".
3) Chained commands are not supported by all write/read devices, please note the information in the
MOBY manuals for configuration, mounting and service.
Command repetition:
Command repetition as described in Section "Command repetition" is available on ASM 475
with MLFB 6GT2 002-0GA10.
FB 45
A.4 ASM 475
Interfaces and indicators of the ASM 475
02%<
$60
6)
'&9
$&7B
(55B 7
:ULWHUHDGGHYLFHb
35(B 7
5['B
5
5
:ULWHUHDGGHYLFHb
7
$&7B 7
(55B 5
35(B 5
5['B

*7*$
6WDWXVDQGHUURULQGLFDWRUV 5HDGHUFRQQHFWLRQ
GLDJUDP7KHQXPEHUV
IRUWKHFRQQHFWLRQUHIHU
WRSOXJFRQQHFWRU;RQ
WKHWRSRIWKHKRXVLQJ
SF: System fault (hardware error on ASM)

DC 5 V: 24V are connected to ASM and the 5V on ASM
are okay.
ACT_1, ACT_2: The corresponding write/read device is active in
processing an application command.
ERR_1, ERR_2: A flashing pattern indicates the last error to occur.
This indicator can be reset with the parameter
option_1 (see Section "INPUT parameters").
PRE_1, PRE_2: Indicates the application of an MDS.
RxD_1, RxD_2: Indicates live communication with the write/read
device. May also indicate malfunctions on the
write/read device.
FB 45
A.4 ASM 475
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

ON OFF/ON ON (perm.) OFF/ON ON (perm.) Hardware is defective (RAM, Flash,
ON OFF ON OFF OFF …)
Loader is defective (can only be fixed
OFF 2 Hz OFF 2 Hz OFF at the plant).
Firmware loading process is active
and/or no firmware detected
→ load firmware
OFF 2 Hz 2 Hz 2 Hz 2 Hz → do not switch off ASM during this
process
Loading of firmware aborted due to
error
→ restart needed
any 5 Hz 5 Hz 5 Hz 5 Hz → reload firmware
→ check update files
OFF OFF 1x flash OFF 1x flash Operating system error
every 2 s every 2 s → switch ASM off/on
ASM has booted and is waiting for a
RESET (init_run) from the user.
FB 45
A.5 ASM 473
A.5 ASM 473
0D[RI$60VFDQEH
RSHUDWHGLQRQH(7;

$60BDGGUHVV

$60BFKDQQHO
Figure A-9 Maximum configuration of ASM 473 on an ET 200X with sample addressing
Depending on the PROFIBUS master, up to 126 ET 200X modules can be run on one
PROFIBUS branch.
The ASM 473 is integrated in the hardware configuration of the SIMATIC Manager by calling
Setup.exe in the directory daten\S7_OM on the RFID Systems Software & Documentation
CD. Currently, the ASM 473 cannot be integrated in masters of other manufacturers.
Reader connection system

A write/read device always occupies the two M12 connection sockets X3 and X4 on the ASM
473. A prefabricated cable makes it easy to connect the write/read device. The standard
model of the connection cable is 2 m in length. Other lengths are available on request.
An SLG cable connector with screw-type terminals is available for users who want to make
their own cables. Cables and SLG cable connectors can be ordered from the MOBY catalog.
FB 45
A.5 ASM 473


+0.0 ASM_address 256, 260, 264, 268, ... Automatic or manual address assignment
Each ASM 473 occupies four bytes of
I/O in the peripheral area of the
controller.
+2.0 ASM_channel 1 1 channel per ASM
+8.0 MDS_control B#16#0, 1 Enable/disable presence check
+9.0 ECC_mode TRUE, FALSE TRUE is only permitted when MOBY_mode
is parameterized with 1.
if MOBY_mode = 5 (MOBY U or RF300)
+10.0 MOBY_mode B#16#1, 5, A, B MOBY I/E/F/U1/D1
+12.0 option_1 B#16#00, 02, 04, ... See Section "INPUT parameters"
+13.0 distance_limiting B#16#05, 0A, 0F, 14, MOBY U1/D1/RF3001
19, 1E, 23 (see Section "INPUT parameters")
+14.0 multitag B#16#1 MOBY U1/D1 or RF3001
+15.0 field_ON_control B#16#0, 1, 2 MOBY U1/D1/RF3001
(see Section "INPUT parameters")
+16.0 field_ON_time B#16#00 ... FF MOBY U1/D1/RF3001
(see Section "INPUT parameters")
1) valid only for 6GT2 002-0HA10


the MOBY system
normal Chained3
01 41 Write MDS all
04 44 Write/read device status1 U/D2 or RF3002
08 48 END1 U
0A 4A Switch antenna on/off F/U/D or RF300
0B 4B MDS status1 U or RF300
1) These commands are only available for 6GT2 002-0HA10.
3) Chained commands are not supported by all write/read devices. Please adhere to the information
Command repetition:
Command repetition as described in Section "Command repetition" is available on ASM 473
with MLFB 6GT2 002-0HA10.
FB 45
A.5 ASM 473
Figure A-10 Interfaces and indicators of the ASM 473
FB 45
A.5 ASM 473
Table A- 25 Pin assignment of sockets X3, X4
Socket Pin Pin Assignment (write/read device)

X3 1 +RxD
2 +TxD
3 -TxD
4 -RxD
5 PE
X4 1 +24 V
2 n. c.
3 0V
4 n. c.
5 PE
LEDs for PROFIBUS DP

General indicators (SF, BF, ON, DC24V) are located on the basic model of the ET 200X.
LEDs for MOBY
RxD: Indicates live communication with the write/read device.

PRE: Indicates the presence of an MDS.
ERR: Error indication by flashing pattern (see Section "Error messages")
This indicator can be reset with the parameter option_1 (see Section "INPUT
parameters").
The following ASM states are also indicated with the LEDs "PRE" and "ERR".
PRE ERR Description, Causes, Remedy

OFF/ON ON (perm.) Hardware is defective (RAM, flash,...)
ON OFF Loader is defective (can only be fixed at the plant).
2 Hz OFF Firmware loading process is active and/or no firmware detected
→ load firmware
→ do not switch off ASM during this process
2 Hz 2 Hz Loading of firmware aborted due to error
→ restart needed
→ reload firmware
→ check update files
5 Hz 5 Hz Operating system error
→ switch ASM or ET 200X base station OFF/ON
OFF 1x flash every ASM has booted and is waiting for a RESET (init_run) from the user.
2s
FB 45
A.6 ASM 452
A.6 ASM 452

The ASM 452 is a PROFIBUS DP-V1 slave with degree of protection IP67. Up to two
write/read devices / readers can be connected in parallel to it. The two write/read devices are
processed in pseudo parallel. This means that, from the user's point of view, command
processing takes place in parallel. Internally, however, the ASM/communication module
processes the two write/read devices in succession. The MDS / transponder which enters
the transmission window of a write/read device first is processed first. This may significantly
increase the processing time of the other write/read device. This is the reason dynamic
processing of several MDSs simultaneously has not been approved.
$7FRPS3&
352),%86'3
PDVWHUPRGXOH
HJ6&38
352),%86OLQH
$60BFKDQQHO

9
IRU$60DQG
ZULWHUHDGGHYLFH
WRRWKHU
352),%86
EXVQRGHV
QGZULWHUHDGGHYLFH
ವ1RWZLWK02%<,GLDORJ
ವ1RWZLWK02%<8'5)b
Figure A-11 ASM 452 configurator
another PROFIBUS Master by means of the GSD file SIEM80B6.GSD. The file is
incorporated in the hardware configuration of the SIMATIC Manager using the function
"Tools > Install new GSD ...". This file is located in the directory daten\PROFI_GSD\ASM452
of the RFID Systems Software & Documentation CD.
FB 45
A.6 ASM 452

In addition to the PROFIBUS-relevant control parameters, several MOBY-relevant control
parameters are also defined for the ASM 452 in the GSD file. The MOBY-relevant
parameters are set using the "Object properties" of the slave in the hardware configuration.
The following table shows the possible settings:
Table A- 26 Setting of MOBY-relevant parameters
Parameter name Value Comment

MOBY mode MOBY I, E, F normal addressing (Default)
MOBY I filehandler only with FC 46
MOBY U/D normal addressing
MOBY U filehandler only with FC 46 or FC 56
(multitag)
Baud rate for write/read 19.2 kbps
device MOBY U 57.6 Kbps (Default)


+0.0 ASM_address 256, 260, 264, 268, Each ASM 452 occupies four bytes of I/O
... in the I/O area of the controller.
+2.0 ASM_channel 1, 2 2 quasi parallel channels; channel 2 not
for MOBY U/D/I dialog
+8.0 MDS_control B#16#0, 1 0= no presence check
1= presence check
if MOBY_mode = 5 (MOBY U)
A, B (8):
• Write/read device must be type SLG4x.
• Write/read device must be connected to
channel 1 (ASM_channel = 1).
• Channel 2 is not available.
• The VMDS memory size is 1280 bytes.
The INIT command for the VMDS must be
Special features of the MOBY U/D (5):
• Channel 2 is not available.
+11.0 scanning_time B#16#00 ... FF A value other than 00 is only recommended
when MOBY_mode was parameterized
appropriately (see Section "INPUT
parameters").
+12.0 option_1 B#16#00, 02, 04 See Section "INPUT parameters"
+13.0 distance_limiting B#16#05, 0A, 0F, MOBY U/D (see Section "INPUT parameters")
14, 19, 1E, 23
+14.0 multitag B#16#1 MOBY U/D
+15.0 field_ON_control B#16#0, 1, 2 MOBY U/D (see Section "INPUT parameters")
+16.0 field_ON_time B#16#00 ... FF MOBY U/D (see Section "INPUT parameters")
FB 45
A.6 ASM 452


the MOBY system
normal Chained2
01 41 Write to MDS all
04 44 SLG status U1/D1
08 48 Turn off MDS U
0A 4A Turn antenna on/off. With MOBY F the F/U/D
command is only effective when one
write/read device is used on the ASM 452.
0B 4B MDS status U
2) Chained commands are not supported by all write/read devices, please adhere to the information
in the
MOBY manuals for configuration, mounting and service.
Setting the PROFIBUS address, activating/deactivating the terminating resistor
([DPSOH7HUPLQDOUHVLVWDQFHRIIFRQGLWLRQRQGHOLYHU\
21
2))
([DPSOH352),%86DGGUHVVFRQGLWLRQRQGHOLYHU\

21 1RUPDOXVH
$60FRPSDWLEOH
XVH*6'ILOH
VLHPG
FB 45
A.6 ASM 452

6)
%)
21 /('VIRU
&RQQHFWLRQV ; '&9 352),%86'3
IRU352),%86 3RZHULQGLFDWRU
; ;
6/*
;

5['

35((55 35((55 ,QWHUIDFHV

;;IRU
ZULWHUHDGGHYLFH
/('VIRU
; 6/* ; ZULWHUHDGGHYLFH
&RQQHFWRU
6XSSO\YROWDJH ; 5['
9'&

LEDs for PROFIBUS DP, Meaning

Power display
SF System Fault (see Table "LED indication for PROFIBUS diagnosis")
BF Bus Fault (see Table "LED indication for PROFIBUS diagnosis")
ON Lights up when there is logic voltage at the ASM (is generated by the 24 V supply voltage).
DC 24 V Lights up when the 24 V supply voltage is connected to the ASM.
LEDs for write/read Meaning
device
SLG 1 Write/read device 1 Only write/read device 1 or write/read device 2 can be selected.
is selected
SLG 2 Write/read device 2
is selected
PRE/ERR 1 Channel 1: MDS MDS present: The LED is permanently ON; if more than one MDS is in
present or error the field (multitag only), the number of MDSs is indicated by short
display interruptions of the LED.
PRE/ERR 2 Channel 2: MDS Error indication: The LED is permanently OFF. The last error number is
present or error indicated by brief light pulses.
display
RxD SLG active with command
FB 45
A.6 ASM 452
Interface assignments
Interface
Connection for PROFIBUS Pin Assignment
X 11 and X 12 1 Signal B (red)
2 PE
3 PE (not wired)
4 Signal A (green)
5 L+ (not wired)
6 M (not wired)
Connection for power supply Pin Assignment
X 13 1 PE
2 L+
3 M
4 PE
5 L+
6 M
Connection for write/read device Pin Assignment
X1/X3 1 +RxD
2 +TxD
3 -TxD
4 -RxD
5 PE
X2/X4 Pin X2 X4
1 +24 V +24 V
2 PRE/ERR2 res. (DE1)
3 0V 0V
4 PRE/ERR1 res. (DE0)
5 PE PE
FB 45
A.6 ASM 452
Change indication mode of the LEDs PRE/ERR1 and PRE/ERR2

INPUT parameter option_1 can be used to change the indication mode of LEDs PRE/ERR1
and PRE/ERR2 (see also the "INPUT parameters" table in Section "INPUT parameters").
Table A- 29 Control of the LEDs PRE/ERR1 and PRE/ERR2
option_1 Meaning of PRE/ERRx

The LED indicates both ANZ_MDS_present and error_MOBY.
When an MDS is in the field (ANZ_MDS_present = 1), errors are
not indicated by the LEDs.
The LED only indicates error_MOBY.

The LED only indicates ANZ_MDS_present.

The LED indicates both ANZ_MDS_present and error_MOBY.

When an error output is queued, no ANZ_MDS_present is
indicated. The error indication can only be reset with the init_run
command and setting bit 1 in option_1.
PROFIBUS Diagnosis
"ON" LED is not on or is flashing
If the "ON" LED is not on, this means that either no supply voltage or too low voltage is
available to the ASM452. Possible causes include a bad fuse or missing/too low supply
voltage. Flashing or absence of this LED may mean that the module is defective.
Diagnosis with LEDs
The following table lists possible error indications with their meanings and provides
remedies.
FB 45
A.6 ASM 452
Table A- 30 LED indication for PROFIBUS diagnosis
"BF" "SF" Cause of error Error correction

LED LED
On Status • ASM 452 is in start-up mode. –
not
• Connection to DP Master failed. • Check the PROFIBUS DP connection.
relevant
• ASM 452 not detecting a baud rate. • Check the DP master.
• Bus interrupt • Check all cables on your PROFIBUS DP network.
• DP Master not functioning • Check whether the connector plugs for PROFIBUS
DP are securely plugged into the ASM 452.
Flashes On • The configuration data sent to the ASM • Check the configuration of the ASM 452
452 by the DP master do not match the (input/output, PROFIBUS address).
configuration of the ASM 452. • Correct GSD file used?
(SIEM80B6.GSD)
Flashes Off • ASM 452 has detected the baud rate, but • Check the PROFIBUS address set on the ASM
is not being addressed by the DP Master. 452 or in the configuration software.
• ASM 452 has not been configured. • Check the configuration of the ASM 452 (station
type).
On Flashes • There is a hardware defect in the ASM • Replace the ASM 452.
452.
FB 45
A.7 ASM 454
A.7 ASM 454

The ASM 454 is a PROFIBUS slave. Up to four MOBY I/E/V write/read devices can be
connected.
352),%86PDVWHU
9
6)&)% '& a
6)&)% 9
352),%86 02%<SRZHU
2WKHUPDVWHU '39 SDFNRURWKHU9
WKLUGSDUW\)&)% FRQQHFWLRQ
$60BFKDQQHO
:ULWHUHDG
:ULWHUHDG :ULWHUHDG :ULWHUHDG :ULWHUHDG GHYLFHDQG0'6
GHYLFH GHYLFH GHYLFH GHYLFH IURP
02%<,(9
UDQJH
0'6 0'6 0'6 0'6
Figure A-12 Configurator for ASM 454
another PROFIBUS Master by means of the GSD file SIEM809F.GSD. The file is
"Tools > Install new GSD ...". You will find the file on the CDRFID Systems Software &
Documentation in the directory daten\PROFI_GSD\ASM454-754-85x.
FB 45
A.7 ASM 454


+0.0 ASM_address 256, 264, 272, 280, ... Each ASM 454 occupies 8 byte of I/O
in the I/O area of the control unit
+2.0 ASM_channel 1, 2, 3, 4 4 parallel channels
+8.0 MDS_control B#16#0, 1, 2 0 = no presence check
1 = presence check
2 = MDS control via NEXT activated
+9.1 RESET_long FALSE (no MOBY U)
+10.0 MOBY_mode B#16#1, 4, 8, 9 MOBY I dialog with 16KB VMDS on
request. (Dialog only possible with
write/read device of type
write/read device 4x.)
+13.0 distance_limiting B#16#0 Not relevant (no MOBY U)
+14.0 multitag B#16#1
+15.0 field_ON_control B#16#0
+16.0 field_ON_time B#16#0


the MOBY system
normal Chained1
01 41 Write to MDS all
06 – NEXT command. Only permitted when all
"MDS_control = 2" is used.
1) Chained commands are not supported by all write/read devices. Bitte beachten Sie entsprechende
Please adhere to the information
FB 45
A.7 ASM 454
Switch settings, interfaces and indicators of the ASM 454
ASM 454: Write/read device / write/read device side LED Meaning

PRE: "Presence" of an MDS in transmission
35(
(55 window.
5[' RxD: SLG active with command
ERR: Error indicated by flashing LED
Interfaces 1-4 Connections for up to four write/read

devices
,QWHUIDFHV
ASM 454: PROFIBUS side LED Meaning

ON: (green) 24 V on ASM
352),%86 ACT: (green) This LED flashes once
briefly when a command is
finished.
6(5,$/ '&9 SF/BF: (red) System Fault/Bus Fault
RAM Error
Interfaces Meaning
6)%)
PROFIBUS PROFIBUS DP interface
21 $&7
SERIAL RS 232/RS 422 interface

21 (only relevant for firmware
download)
DC 24 V Power supply for
ASM 454
QRWDVVLJQHG
6(5,$/LQWHUIDFH
2156
2))56
RQO\UHOHYDQWIRUILUPZDUHGRZQORDG
6HW352),%86DGGUHVV
21
21
21
([DPSOH
352),%86DGGUHVV

FB 45
A.8 ASM 754
A.8 ASM 754

The ASM 754 is a PROFIBUS slave. Up to four MOBY E SLAs (read/write antenna) can be
operated on it. The 4 SLAs are processed in "pseudo parallel." This means that, from the
user's point of view, command processing takes place in parallel. However, in reality, the
ASM processes the 4 antennas in succession. The MDS which enters the transmission
window of an SLA first is processed first. This may considerably lengthen the processing
times of the other channels (SLAs). This is the reason dynamic processing of several MDSs
simultaneously has not been approved.
352),%86PDVWHU
9
6)&)% '& a
6)&)% 352),%86 9 02%<SRZHU
2WKHUPDVWHU '39 SDFNRURWKHU
WKLUGSDUW\)&)% 9FRQQHFWLRQ
$60BFKDQQHO
02%<(
6/$ 6/$ 6/$ 6/$ 6/$[DQG
0'6([[
0'6 0'6 0'6 0'6
"Tools > Install new GSD ...". Sie finden die Datei auf der CD RFID Systems Software &
FB 45
A.8 ASM 754
Processing times of MDS E6xx in multiple channel operation

The following table shows the processing times when one command is started
simultaneously on 1, 2, 3, or 4 channels.
Table A- 33 Processing times of MDS E6xx in multiple channel operation
SLA per ASM Time to Read 752 Byte Time to Write 752 Byte
Single Command Chained
Command
1 3.3 s 2.5 s
2 6.6 s 5s
3 9.8 s 7.5 s
4 13 s 10 s
The times in the table are minimum times.

Slow PROFIBUS baud rates and large bus configurations may increase these times.


+0.0 ASM_address 256, 264, 272, 280, Each ASM 754 occupies 8 byte of I/O
... in the I/O area of the control unit
+2.0 ASM_channel 1, 2, 3, 4 4 pseudo parallel channels
1 = presence check
+9.0 ECC_mode FALSE No ECC driver
+10.0 MOBY_mode B#16#1 Only MOBY I/E protocol permitted
+11.0 scanning_time B#16#00 No parameterization of the scanning
time
FB 45
A.8 ASM 754

Command code Description

normal Chained
01 41 Write to MDS
02 42 Read MDS; read fixed code

See Section "Switch settings, interfaces and indicators of the ASM 454" in Chapter "ASM
454"
FB 45
A.9 ASM 854
A.9 ASM 854

The ASM 854 is a PROFIBUS slave. Up to four MOBY F SLAs can be connected in parallel
to it. In addition to standard programming with the FB 45, the ASM 854 can also directly
process the fixed-code data memories (type MDS F1xx) using the process image.
Programming is described later (process image mode).
352),%86PDVWHU
9
6)&)% '& a
6)&)% 9 02%<SRZHU
2WKHUPDVWHU 352),%86
SDFNRURWKHU
WKLUGSDUW\)&)% '39
9FRQQHFWLRQ
$60BFKDQQHO
02%<)
6/$ 6/$ 6/$ 6/$ 6/$[DQG
0'6)[[[
0'6 0'6 0'6 0'6
FB 45
A.9 ASM 854


+0.0 ASM_address 256, 264, 272, 280, Each ASM 854 occupies 8 byte of I/O in
... the I/O area of the control unit
+2.0 ASM_channel 1, 2, 3, 4 4 parallel channels
1 = presence check (must always be set
when using MOBY_mode = A (MDS F1xx))
+10.0 MOBY_mode B#16#A, B Only MOBY F parameterization
+11.0 scanning_time B#16#00 No parameterization of the scanning time
+12.0 option_1 B#16#00, 01, 04, 08 (See Section "INPUT parameters")

Table A- 37 Commands of the ASM 854 when MOBY_mode = B

normal Chained
01 41 Write to MDS
02 42 Read MDS
The command table is valid for the FB 45. No commands are transferred to the ASM when
fixed-code MDSs are processed with the process image.
Special features of the fixed-code MDS (MOBY_mode = A)

When in this mode, the ASM automatically reads each new MDS as it arrives. The user does
not need to start a command.
The user issues the read command using UDT 20. repeat_command and command_start
must then be issued simultaneously to start the command and fetch the data.

See Section "Switch settings, interfaces and indicators of the ASM 454" in Chapter
"ASM 454"
FB 45
A.9 ASM 854
Parameterizing process image mode
Note
Process image mode does not use the FB 45. This section describes how to handle and
program the process image mode. Only fixed-code MDSs of type "MDS F1xx" can be read in
this mode.
Process image mode is parameterized in HW Config by selecting the appropriate entry from
the GSD file. Process image mode does not offer functions for the application.
2QO\RQH6/$LVXVHGRQ
WKH$60
$60BFKDQQHO
$OOIRXUFKDQQHOVRQWKH
$60DUHLQXVH
Figure A-15 Selecting process image mode for ASM 854/850 based on the number of channels
Process image mode: Operating principle

After the ASM and PROFIBUS have powered up, code 00 00 00 00 00 is stored in the
process image for each MDS. Each SLA channel immediately starts to scan its surroundings
for a new MDS no. As soon as the MDS no. has been read, the process image indicates the
fixed-code information. The new MDS no. is retained until an MDS with a new no. is read.
The new MDS overwrites the old number. The data must be read to a data block with SFC
14 to ensure that the number is always transferred consistently with PROFIBUS or is
indicated on the S7. In addition to the 5 bytes of fixed-code information, status information is
located in the 1st byte of the process image which the user can evaluate.
FB 45
A.9 ASM 854
Process image mode: Programming

The data must be scanned by SFC 14 to ensure consistent representation of the information
which was read. The following example shows the programming of the ASM 854 in process
image mode.
Block: OB1 MOBY F with ASM 854 in process image mode
Network: 1
The data of 9 MOBY F channels are read consistently to DB 20. The 9
channels are distributed over 3 ASM 854s.
CALL "DPRD_DAT" // = SFC14

LADDR :=W#16#0 // 1st ASM 854 has I/O address
RET_VAL :=MW0 0
RECORD :=P#DB20.DBX 0.0 BYTE 24 // The data are stored in DB
20 starting at address 0.
Since 4 channels are used, the
data length is 24 bytes.
CALL "DPRD_DAT" // 2nd ASM 854 has I/O address

LADDR :=W#16#24 24
RET_VAL :=MW1 // The data are stored in DB
RECORD :=P#DB20.DBX 24.0 BYTE 20 starting at address 24.
24 Since 4 channels are used, the
data length is 24 bytes.
CALL "DPRD_DAT" // 3rd ASM 854 has I/O address

LADDR :=W#16#48 48
RET_VAL :=MW2
RECORD :=P#DB20.DBX 48.0 BYTE 6 // The data are stored in DB
20 starting at address 48.
Since 1 channel is used, the
data length is
6 bytes.
// New data can be processed in DB20 starting here.
FB 45
A.9 ASM 854
Process image mode: data representation and evaluation

The following figure shows the layout of the ASM data after SFC 14 is called. The
presentation also applies when the ASM data are directly viewed in the process image.
&KDQQHO
6WDWXV>@
'DWD &KDQQHO
'DWD 6WDWXV>@
'DWD 'DWD &KDQQHO
'DWD 'DWD 6WDWXV>@
'DWD 'DWD &KDQQHO
'DWD
'DWD 'DWD 6WDWXV>@
'DWD 'DWD 'DWD 06%RIGDWD
'DWD 'DWD
'DWD 'DWD
'DWD
'DWD /6%RIWKHGDWD
5HODWLYHDGGUHVV
LQ'%RULQ
SURFHVVLPDJH
%LW
(UURU &K &K &K +5 35( = =
7ZRELWFRXQWHU7KLVFRXQWHULVDOZD\V
LQFUHPHQWHGE\RQHZKHQDQHZ0'6LVUHDG
$IWHUDFKDQJHLQWKHFRXQWHUGDWDWR
FRQWDLQDQHZ0'6QXPEHU
3UHVHQFHLQGLFDWHVWKHSUHVHQFHRIDQ0'6LQWKH
WUDQVPLVVLRQZLQGRZRIDQ6/$
+LVWRULFDOUHDGLQIRELW$VHWELWLQGLFDWHVWKDWWKH0'6PRYHG
DFURVVWKHILHOGDWPD[LPXPSRVVLEOHVSHHG7KHGDWDFRXOGRQO\EH
UHDGRQFHIURPWKH0'6
,QIRUPDWLRQRQFKDQQHODOORFDWLRQRIWKHGDWD
&KDQQHO
&KDQQHO
&KDQQHO
&KDQQHO
(UURUPHVVDJHLIHUURU 7KHGDWDDUHLQYDOLG'DWDE\WHFRQWDLQVDQHUURUFRGH
7KHIROORZLQJHUURUFRGHVDUHSRVVLEOH
KH[ WKH0'6GDWDKDYHFKDQJHGZLWKRXWDSUHVHQFHFKDQJH
)KH[ $60SRZHUXSWKHFRXQWHUV=KDYHEHHQUHVHWWR
KH[ LQWHUQDOUXQWLPHHUURURQ$60
Figure A-16 Data presentation and evaluation in process image mode
FB 45
A.9 ASM 854
Process image mode: time diagram
(UURU
=
=
35(
(UURU) VW0'6 QG0'6 UG0'6 WK0'6 WK0'6

'DWD
6WDUWXSRI 1RUPDOUHDGLQJRI 7KHVDPH0'6HQWHUV

$60 QHZ0'6 WKHUHDGILHOGVHYHUDO
WLPHV1RFKDQJHRQ
=
Figure A-17 Time diagram for process image mode
FB 45
A.10 ASM 850
A.10 ASM 850

The ASM 850 is a PROFIBUS slave. One MOBY F SLA can be connected. In addition to
standard programming with the FB 45, the ASM 850 can also directly process the fixed-code
data memories (type MDS F1xx) using the process image. The programming is described in
Section "ASM 854".
352),%86PDVWHU
9
'& a
6)&)%
6)&)% 9
352),%86 02%<SRZHU
2WKHUPDVWHU '39 SDFNRURWKHU
WKLUGSDUW\)&)% 9FRQQHFWLRQ
$60BFKDQQHO
02%<)
6/$ 6/$[DQG
0'6)[[[
0'6
FB 45
A.10 ASM 850


Address Name Permissible Comment
values
+0.0 ASM_address 256, 264, 272, Each ASM 850 occupies 8 byte
280, ... of I/O in the I/O area of the
control unit
+2.0 ASM_channel 1 1 channel
+8.0 MDS_control B#16#0, 1 0= no presence check
1= presence check
+10.0 MOBY_mode B#16#A, B Only MOBY F parameterization
+11.0 scanning_time B#16#00 No parameterization of the
scanning time
+12.0 option_1 B#16#00, 01, 04, (See Section "INPUT
08 parameters")

Table A–18 Commands of the ASM 850

normal Chained
01 41 Write to MDS
02 42 Read MDS; read fixed code
The command table is valid for the FB 45. No commands are transferred to the ASM when
fixed-code MDSs are processed with the process image.

See Section "Switch settings, interfaces and indicators of the ASM 454" in Chapter
"ASM 454"
FB 45
Programming the MOBY-ASM on PROFIBUS B
B.1 Programming the MOBY-ASM on PROFIBUS DP-V1
For whom is this Appendix intended?

This section does not need to be considered by SIMATIC users. It is intended particularly for
programmers of PCs and third-party PLCs. The information enables the programmer to
develop customized function blocks or drivers for the MOBY-ASM.
Note
Some signals in this appendix have the same meaning as the variables in Section
"Parameter data block". In order to distinguish between them, an underscore "_" is appended
to the relevant signals (e.g. ANZ_MDS_present_).
Communication between ASM and PROFIBUS master

PROFIBUS-DP must be able to transfer both the cyclic (DP) and the non-cyclic data (DP-
V1).
352),%86'3
PDVWHUZLWK 352),%86'39
'39IXQFWLRQ
2WKHUILHOG
02%<$60 GHYLFHV
02%<$60
&\FOLFFRPPXQLFDWLRQYLD $F\FOLFFRPPXQLFDWLRQYLD
352),%86'36WDWXVLQIRUPDWLRQLV 352),%86'39&RPPDQGVDQG
H[FKDQJHGVHH6HFWLRQ&\FOLFFRQWUROZRUG DFNQRZOHGJHPHQWVDUHH[FKDQJHG
EHWZHHQPDVWHUDQG02%<$60 VHH6HFWLRQ&RPPDQGDQG
DFNQRZOHGJHPHQWWHOHJUDPV
FB 45
Programming the MOBY-ASM on PROFIBUS
The master may only send new commands to the slave (MOBY-ASM) when the ASM is
ready. Status information is used to indicate that the MOBY-ASM is ready. The same applies
to acknowledgments. The MOBY-ASM 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 a state info.
Two indications are defined in the state info. The PROFIBUS DP master uses these two
indications to decide whether a DP-V1 telegram can be executed to or from the MOBY-ASM.
Principle of controlling non-cyclic communication with command and acknowledgment counter
&RPPDQGFRXQWHU $FNQRZOHGJHPHQWFRXQWHU

'3
9
02 WH
P OHJ
DF %< UD UDP
WLYH $6 OHJ
0 WH
9 &R D QG
'3 UHD PPD PP
G\ QG &R G \
UH D
02%<$60 JUDP
'39WHOHJUDP WHOH
DFWLYH '39

0
$6
2 %<
0 LYH '39WHOHJUDP &R
W UDP
DF WHOHJ UHD PPD
02 '39 G\ QG
DF %< PDQ
G
UDP WLYH $6 &RP '3
HOHJ 0 UHDG
\ 9
W WH
OHJ
' 39 UDP

6WDWXVRIFRXQWHUVDIWHU$60SRZHUXSRUDIWHUDQLQLWBUXQB
Figure B-1 Command and acknowledgement counter states
As you can see from the diagram above, a DP-V1 telegram triggers the change from one
defined state to the next. A new DP-V1 telegram is not permitted until the next state is
reached. A DP-V1 telegram is either a command to the ASM or an acknowledgment from the
ASM.
For this reason, it is important to tell the master whether a new DP-V1 telegram can be
executed. Each state is coded in 2 bits and counted up (as shown in the diagram above)-
hence the name state bits or state counters.
The state bits are transmitted cyclically to the master via PROFIBUS DP. 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 DP-V1 telegram be sent.
FB 45
Two states must be coded.

1. Command state (command counter) to tell the user whether a new/next command may
be transferred to the MOBY-ASM
2. Acknowledgment state (acknowledgment counter) to tell the user whether a new
acknowledgment from the MOBY-ASM is waiting
The user must evaluate the acknowledgement state with higher priority. I.e. when the user
wants to send a telegram to the ASM but a telegram from the ASM is waiting to be fetched at
the same time, the telegram from the ASM must be fetched first.
Both the command and the acknowledgment state are coded in 2 bits each. Both states are
stored in a byte (see Section "Cyclic control word between master and MOBY-ASM").
FB 45
B.2 Cyclic Control Word between Master and MOBY-ASM

The cyclic control word is used to synchronize telegram communication between master (FB
/ FC) and slave (MOBY-ASM). The actual non-cyclic command and acknowledgment frames
via DP-V1 may not be started until this is indicated by the cyclic byte of the MOBY-ASM in
the command or acknowledgment counter.
&\FOLFZRUGWR02%<$60
3HULSKHUDORXWSXW

UHSHDWBFRPPDQGB
5HVHUYHG RSWLRQDO
LQLWBUXQB
6WDUWXSRI352),%86'3PDVWHU
7KLVELWIRUFHVD02%<$60VWDUWXS FDQFHOB
%LWLVVXEVHTXHQWO\VHWLQWKHSHULSKHUDO FRPPDQGWHUPLQDWLRQ 5HVHUYHGIRU'2
LQSXW
&\FOLFZRUGIURP02%<$60
3HULSKHUDOLQSXW

QXPEHUB0'6B
$1=B0'6B 02%<8RQO\
SUHVHQWB
5HDGHUBHUURU02%<8RQO\
SUHVHQFH
$60BEXV\B
0'6BSUHVHQFHB 2SHUDWLRQZLWKUHSHDWBFRPPDQGB
FKDQJHGB $1=BFDQFHOB $FRPPDQGLVFXUUHQWO\EHLQJ
IRU)&)% &DQFHO SURFHVVHGE\WKH0'6
XQXVHG DFNQRZOHGJH 7KHELWLVVHWDVVRRQDVDQ0'6
5HVHUYHG PHQW HQWHUVWKHILHOGRIWKHUHDGHUZKLOHWKH
UHSHDWBFRPPDQGELWLVVHW7KHELWLV
&RPPDQGFRXQWHUORZHUELW%/ UHVHWZKHQWKH0'6FRPPXQLFDWLRQ
&RPPDQGFRXQWHUKLJKHUELW%+ LVFRPSOHWH7KHUHVXOWVPD\QRW
KDYHEHHQWUDQVPLWWHGWRWKH$60
KRZHYHU
$FNQRZOHGJHPHQWFRXQWHUORZHUELW4/
2SHUDWLRQZLWKRXWUHSHDWBFRPPDQGB
$FNQRZOHGJHPHQWFRXQWHUKLJKHUELW4+
%LWLVDFWLYHDVVRRQDVWKH$60LV
6WDUWXSPHVVDJH SURFHVVLQJDFRPPDQG
7KLVELWLQGLFDWHVWKDWWKH02%<$60KDVVWDUWHGXS
$1=BUHVHWB FRPPDQGBUHSHDWBDFWLYHB
:KHQLQLWBUXQBLVUHVHWWKH02%<$60FDQFHOVWKLV 7KLVELWLVWKHFRQILUPDWLRQPLUURULQJRI
ELWDJDLQ2WKHUFRPPDQGVH[FHSWIRU5(6(7RUDQ
UHSHDWBFRPPDQGB,WLVXVHGIRULQIRUPDWLRQ
LQYDOLG5(6(7FRPPDQGDUHWKHQGHQLHGZLWKDQHUURU DQGHUURUDQDO\VLV7KHFRPPDQGUHSHWLWLRQ
PHVVDJH ZDVVWDUWHGRQWKH$60EHWZHHQVHWWLQJRI
UHSHDWBFRPPDQGBDQGUHDGRXWRIWKHHQDEOHG
FRPPDQGBUHSHDWBDFWLYHELW
Figure B-2 Structure of the cyclic control word
FB 45
After start-up, the cyclic word of MOBY-ASM takes on the following states (bits 8 to 15 are
shown).

%HIRUH $IWHU %HIRUHDFNQRZO %HIRUH %HIRUHDFNQRZO
FRPPDQG FRPPDQG HGJHPHQW FRPPDQG HGJHPHQW
3RZHUXS &RPPDQG &RPPDQG &RPPDQG
5(6(7
Synchronizing of command and acknowledgment counters

The command (BZ) and acknowledgment (QZ) counters are synchronized during a start-up.
The ASM sets QZ = 0 and BZ = 1. The start-up can be triggered by both the ASM (return of
power) and the user (init_run_).
LQLWBUXQB ณณ
ณณ
$1=BUHVHWB
$F\FOLF ณณ 5(6(7FRPPDQG 5(6(7FRPPDQG
WHOHJUDP WR$60 IURP$60
UHDG\ ณณ
%= %= %= 4=
UHDG\ UHDG\PHVVDJHLQXVHUSURJUDP
Figure B-3 Power-up timing initiated by user
LQLWBUXQB
$1=BUHVHWB
$F\FOLF 5(6(7FRPPDQG 5(6(7FRPPDQG
WHOHJUDP WR$60 IURP$60
UHDG\
%=4= %= 4= %= 4= ,IDFRPPDQGZDVLQWHUUXSWHG

DQ\YDOXH GHILQHGUHVHW E\D5(6(7RU
LQLWBUXQBHUURUPHVVDJH
)LVWULJJHUHGKHUH
Figure B-4 Power-up timing of ASM initiated by power failure
FB 45
Terminating a command with Cancel

BZ and QZ are not reset with Cancel.
FDQFHOB ณณ

$1=BFDQFHOB ณณ
$F\FOLF
WHOHJUDP ณณ $FNQRZOHGJHPHQWZLWK
HUURU)
ณณ
UHDG\

&DQFHOLIQRFRPPDQG 4= 4=
DFWLYDWHG
&DQFHOLI$60FXUUHQWO\SURFHVVLQJDFRPPDQG
RQO\RQHHUURUDFNQRZOHGJHPHQWLVPDGHLIVHYHUDOFRPPDQGVFRPPDQGFKDLQVDUHFDQFHOHG
WKHLQFUHPHQWDWLRQRI4=DQGZLWKGUDZDORI$Q]BFDQFHOBFDQEHLQGLFDWHGVLPXOWDQHRXVO\WRWKHXVHU
Figure B-5 Cancel timing
FB 45
B.3 Methods of operation with the ASM
Commands are executed one at a time

This means that, after each command, the user must wait for the acknowledgment (result)
before the next command is sent to the ASM. This type of programming involves the
following characteristics.
● Simple function block programming
● No optimal-speed data transmission for several consecutive commands
The following diagram shows the sequence of command and acknowledgement exchange
between user (DP master) and MOBY-ASM.
02%<FRPPDQGH[HFXWLRQ
&RPPDQG &RPPDQG 7LPHD[LV
'3PDVWHU 02%<$60
&RPPXQLFDWLRQ $FNQRZO &RPPXQLFDWLRQ $FNQRZO &RPPXQL

ZLWKWKH0'6 HGJPHQW ZLWKWKH0'6 HGJPHQW FDWLRQ
GLUHFWLRQ
([HFXWLRQRI ([HFXWLRQRI
VWFRPPDQG QGFRPPDQG
7KHFRPPDQGDQGDFNQRZOHGJHPHQWWHOHJUDPLVDQDF\FOLF'39WHOHJUDPZLWK'39UHVSRQVH
$VWDUWLVRQO\DOORZHGDIWHUFKDQJLQJWKHFRPPDQGDQGRUDFNQRZOHGJHPHQWFRXQWHU
&KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG
&KDQJHDFNQRZOHGJHPHQWFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG
1RFKDQJHWRF\FOLFGDWD
Figure B-6 Command execution: one command at a time
FB 45
Command chaining and command buffering on the ASM

Command chaining is indicated when the chaining bit (bit 6 in the command) is set (see also
Section "MOBY commands).
Command buffering is a characteristic of the ASM. A variety of buffers are available to the
ASM for intermediate storage of commands and results.
Use of command chaining and command buffering involves the following characteristics:
● Programming a function block becomes more complex.
● Optimum data throughput to and from the MDS.
This is particularly noticeable with large amounts of data ( 1 KB) and slower PROFIBUS
transmission rates.
The following diagram shows the procedure used for command and acknowledgment
communication between user (DP master) and MOBY-ASM when a chained command is
used.
7LPHD[LV
VW QG UG
FRPPDQG FRPPDQG FRPPDQG
'3PDVWHU 02%<$60
7UDQVIHURIVW 7UDQVIHURIQG 7UDQVIHURIUG

UHVXOW UHVXOW UHVXOW
&RPPXQLFD ([HFXWLRQRI
WLRQGLUHFWLRQ VWFRPPDQGLQ$60
([HFXWLRQRI ([HFXWLRQRI
QGFRPPDQG UGFRPPDQGLQ
7UDQVIHURIWKUHHFRPPDQGVLQ$60 LQ$60 $60
&KDQJHFRPPDQGFRXQWHU1HZVWDWXV ROGVWDWXVF\FOLFZRUG

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 transmission
speeds of PROFIBUS and the MOBY-MDS.
● If the PROFIBUS implementation on the DP master only provides limited resources
(buffer) for non-cyclic data transmission, the PROFIBUS data transmission may take
quite a while. This is particularly noticeable in extensive bus configurations with MOBY-
ASM.
● If the PROFIBUS master can be set to permit several non-cyclic telegrams between cyclic
data communication, PROFIBUS data transmission can be accelerated in a bus
configuration with many MOBY-ASMs. However, this has a negative effect on the cyclic
data communication of I/O modules which are also part of the same PROFIBUS branch.
The cycle time of PROFIBUS becomes irregular and sporadically may become very high.
FB 45
● When more commands are to be processed by the ASM than ASM buffer space, the user
must first fetch results from the ASM before new commands can be sent to the ASM.
● The ASM does not absolutely require 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 which is set in the command is returned by the ASM in the acknowledgment.
● The number of buffers on the ASM varies with the type of ASM. For more information,
see Section "Command repetition".
Command repetition
The procedure for command repetition and its advantages have already been described in
Section "Command repetition".
Programming of command repetition at the PROFIBUS level will now be discussed. The I/O
input or I/O output word controls command repetition (see Section "Cyclic control word
between master and MOBY-ASM").
The following diagram shows telegram communication between user (DP master) and
MOBY-ASM.
FB 45
7LPHD[LV
$60LV
SURJUDPPHGRQFH
DVGHVFULEHGHDUOLHU
'3PDVWHU LQWKLVVHFWLRQ 02%<$60
&RPPXQLFDWLRQGLUHFWLRQ
UHSHDWBFRPPDQGB
$60BEXV\B
$1=B0'6BSUHVHQWB
6ORZ0'6VHTXHQFH
$60BEXV\B
LPPHGLDWHO\LQGLFDWHVWKH )DVW0'6VHTXHQFH
SURJUDPPLQJRID H[HFXWLRQRIWKHQHZ0'6LV
FRPPDQG $IWHU
IDVWHUWKDQWKHWUDQVPLVVLRQ
$1=B0'6BSUHVHQWB
RIWKHGDWD
WKHFRPPDQGLVVWDUWHG
LPPHGLDWHO\
7KHFRPPDQGLV 7KHFRPPDQGLV
H[HFXWHG H[HFXWHG
WKHDFNQRZOHGJHPHQW WKHDFNQRZOHGJHPHQW
FRXQWHULVGHFUHPHQWHG FRXQWHULVGHFUHPHQWHG
DQGWKHUHVXOWLV DQGWKHUHVXOWLV
WUDQVIHUUHG WUDQVIHUUHG
&KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V
UHWDLQVWKHVDPHFRXQWHUYDOXH
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 MDS is entering the transmission
window (see figure below: Ⓐ).
● A new MDS is detected with the ANZ_MDS_present_ bit, and command repetition is then
started (see figure below: Ⓑ).
In this case, the command_repeat_active_ bit must be scanned to make sure the command
repetition was accepted.
FB 45
7LPHD[LV
$60LVSURJUDPPHG
RQFHDVGHVFULEHG
'3PDVWHU HDUOLHULQWKLVVHFWLRQ 02%<$60
&RPPXQLFDWLRQGLUHFWLRQ
$ %
UHSHDWBFRPPDQGB
FRPPDQGBUHSHDWBDFWLYHB
$60BEXV\B
$1=B0'6BSUHVHQWB
+DQGVKDNH $SSOLFDWLRQZDLWV 3URFHVVLQJVHTXHQFH

VHTXHQFHWRPDNH KHUHIRUQH[W0'6 IRUDQRWKHU0'6
VXUHFRPPDQGLV
SURFHVVHG
8VHUVWDUWVZLWK 7KHFRPPDQGLVH[HFXWHG 7KHFRPPDQGLVH[HFXWHG

UHSHDWBFRPPDQGB WKHDFNQRZOHGJHPHQW WKHDFNQRZOHGJHPHQW
FRXQWHULVLQFUHPHQWHGDQG FRXQWHULVLQFUHPHQWHGDQG
WKHUHVXOWLVWUDQVIHUUHG WKHUHVXOWLVWUDQVIHUUHG
7ULJJHUVLJQDOIRU
DFRPPDQGVWDUW
$1=B0'6BSUHVHQWBൺ
&KDQJHFRPPDQGFRXQWHU,IWKHFRPPDQGLVUHSHDWHGWKHFRPPDQGFRXQWHUDOZD\V
UHWDLQVWKHVDPHFRXQWHUYDOXH
Figure B-9 Focused command repetition
FB 45
B.4 Command and acknowledgement telegrams

Commands and results are sent and received with the non-cyclic telegram service of
PROFIBUS DP-V1. The telegrams are described in this section.
General telegram format

The telegram layout applies to both command telegrams to the MOBY-ASM and result
telegrams from the MOBY-ASM.
Special information on telegram expansions for the RF620R/RF630R readers can be found
in the Appendix of the "Configuration Manual RF620R/RF630R".
%\WH Q
$% &RP 6WDWXV &RPPDQGVSHFLILFGDWD

PDQG
7KHFRPPDQGVSHFLILFGDWDDUHGHVFULEHGLQGHWDLORQWHIROORZLQJSDJHV
7KHPLQOHQJWKLVWKHPD[GDWDOHQJWK
LV E\WHV
7KHVWDWXVE\WHDOZD\VKDVWKHYDOXHZKHQDFRPPDQGLVLVVXHG
,QWKHUHVXOWRUHUURUWHOHJUDPWKHE\WHKDVWKHIROORZLQJPHDQLQJ
%LW
%DWW %DWW (&& (UURUFRGH)
'HWDLOHGHUURUGHVFULSWLRQVHH&KDSWHU
(UURUPHVVDJHVDQGWURXEOHVKRRWLQJ
(&&FRUUHFWLRQZDVSHUIRUPHGWKHGDWDLQWKH
UHVXOWWHOHJUDPDUHRN
)RU0'6RQO\6WDWXVRIGLDORJEDWWHU\RQ0'6
಻ EDWWHU\EHORZWKUHVKROG಻
WKLVELWFDQEHRUZLWKRWKHU0'6W\SHV
%DWWHU\YROWDJHRQ0'6KDVGURSSHGEHORZWKUHVKROG
7KLVELWLVDOZD\VVHWRQ0'6W\SHVZLWK((3520PHPRU\
7KHLPSOHPHQWHGFRPPDQGVDUHGHVFULEHGRQWKHIROORZLQJSDJHV
*HQHUDOFRPPDQGIRUPDW

&RPPDQGFRGH)
FKDLQHGFRPPDQG
UHVHUYHGIRUV\VWHPIXQFWLRQVHJILUPZDUHXSGDWH
$PRXQWRIE\WHV
Q WRWDOQXPEHURIE\WHVLQWHOHJUDP$%E\WHLVQRWFRXQWHG
PLQLPXP$%
PD[LPXP$% PD[LPXPOHQJWKIRU352),%86'39LVE\WHV
7KHOHQJWKVSHFLILHGKHUHLVWKHPD[LPXPOHQJWKIRU352),%867KH$60
LVDQH[FHSWLRQZLWKDOHQJWKE\WHVKRUWHUPD[GDWDOHQJWK FRPPDQGVSHFLILFGDWD
Figure B-10 General telegram format
FB 45
Command table
Comma Comman Command Description

nd d
code code
chained
[hex] [hex]
0 – RESET ASM is reset. The active command is terminated.
(If an MDS command was terminated with RESET, the reset acknowledgment
reports error 1F.)
The RESET command can be used to switch the ASM to various operating modes.
1 41 Write Write data block to MDS
2 42 Read Read data block from MDS
3 43 Initialization This command is required when a new (not yet write-accessed) MDS is being used
or after failure/replacement of the battery or when MDS is to be run in ECC mode.
The MDS is already initialized for normal use.
MDS type INIT duration INIT Memory size +
(normal) duration 1
(with
ECC)
1KB VMDS (MOBY I) < 0.1 s – 00 05 00
2KB RAM (MOBY I) 0.4 s 5s 00 08 00
8KB FRAM (MOBY I) 0.8 s 20 s 00 20 00
8KB EEPROM (MOBY I) 18 s 54 s 00 20 00
32KB RAM (MOBY I) 3s 75 s 00 80 00
752 bytes EEPROM (MOBY E) 0.8 s – 00 02 F0
192 bytes MDS 4xx (MOBY F) 2.2 s – 00 00 C0
16 bytes MDS 2xx (MOBY F) 0.25 s – 00 00 10
2KB RAM (MOBY U) approx. 1 s – 00 08 00
32KB RAM (MOBY U) approx. 1.5 s – 00 80 00
44 bytes I-Code (MOBY D) approx. 0.4 s 00 00 2C
112 bytes I-Code SLI (MOBY D) approx. 0.5 s 00 00 70
256 bytes Tag-it HF-I (MOBY D) approx. 1 s 00 01 00
996 bytes my-d (MOBY D) approx. 3 s 00 04 00
2000 bytes FRAM (MOBY D) approx. 3 s -- 00 07 D0
20 bytes EEPROM (RF300) approx. 0.2 s – 00 00 14
8KB FRAM (RF300) 0.3 s – 00 20 00
32KB FRAM (RF300) 1.2 s – 00 80 00
64KB FRAM (RF300) 2.4 s – 00 FF 00
4 44 SLG status Returns as result the status byte, the selected reader and the ANZ_MDS_present_
bit. This command checks to determine whether a reader is connected to the ASM
and, if so, whether it is okay 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 following command(s) refer(s) to the next MDS. The user can immediately
start a command even though the old MDS is still in the field. The NEXT command
must only be programmed when MDS_control_ = 2 was set in the RESET
command.
A NEXT command must arrive between 2 MDS passes or an error message will
occur. Conclusion of an MDS pass with a NEXT command is also valid after the
MDS has already left the field or the next MDS is already in the field.
8 48 END Terminate communication with MDS
FB 45
Comma Comman Command Description

nd d
code code
chained
[hex] [hex]
A 4A Antenna Only MOBY F/U/D RF300 or RF600:
on/off This command turns the antenna field on the reader off and on again.
B 4B MDS status Returns the characteristics of the MDS in the result.
FB 45
Exact telegram format
&RPPDQG &RPPDQGWHOHJUDP 5HVXOWWHOHJUDPIURP

FRGH WR02%<$60 02%<$60

$60SRZHUXSLVRQO\
VLJQDOHGWRWKHXVHUYLDWKH
6WDUWXS F\FOLFZRUGVHH$SSHQGL[
%
5(6(7
W6&$1 3DUDP 237 6WDW 9HUV+ 9HUV/ 5HV
QRW
02%<8
RU )LUPZDUHYHUVLRQLQ$60YHUVLRQB02%<B
5) HJKH[KH[9
%LW
VFDQQLQJBWLPHB
VHH0'6GHVFULSWLRQ XQDVVLJQHG
%LW
XQDVVLJQHG
5HVHW(55/('
FRQWLQXRXVVFDQQLQJIRUSUHVHQFHFKHFN VWRSIODVKLQJ
YLDILHOGVFDQQLQJGHIDXOW 7LPHRXW
7LPHYDOXH)LVPXOWLSOLHGE\ $60UHVSRQGVZLWKHUURULIQR
WLPHEDVH 0'6SUHVHQW
7LPHEDVH 7LPHYDOXH PV
7LPHYDOXH PV 767B21IRU02%<,9RQO\
7LPHYDOXH V $60UHVSRQGVZLWKDQHUURULIILHOG
7LPHYDOXH V GLVWXUEDQFHVH[LVWRQWKHZULWHUHDG
GHYLFH
%LW
02%<BPRGHB
GHIDXOW
02%<,(
3UHVHQFHFKHFNDQG0'6FRQWURO 02%<,ZLWK0'6
0'6BFRQWUROB UHV
QRSUHVHQFHFKHFN UHV
QR0'6FRQWUROSUHVHQFHFKHFNYLD UHV
ILUPZDUHGHIDXOW 02%<,GLDORJ
0'6FRQWURODQGSUHVHQFHFKHFNYLDILUPZDUH 02%<9
$ 02%<)0'6[[
% 02%<)0'6[[
& 02%<)0'6[[
(&&GULYHUDFWLYDWHG
)XQFWLRQRIW6&$1LPSRUWDQWIRU0'6
,IWKHUHLVQR0'6ZLWKLQWKHILHOGWKH$60VFDQVWKHHQYLURQPHQWFRQWLQXRXVO\IRUDQ0'6,IDQ0'6ZDVGHWHFWHG
$1=B0'6BSUHVHQWB $1:/(' 21WKHHQYLURQPHQWLVQRZRQO\VFDQQHGDWWKHLQWHUYDOVVSHFLILHGLQW6&$1
,HWKH$1=B0'6BSUHVHQWBVLJQDOFDQRQO\EHFDQFHOHGZLWKLQWKHW6&$1WLPHLQWHUYDOV
:KHQ02%<BPRGHB DOOVHWWLQJVLQRSWLRQE\WHDQGW6&$1DUHLJQRUHG
FB 45
&RPPDQG &RPPDQGWHOHJUDP 5HVXOWWHOHJUDP

FRGH WR02%<$60 IURP02%<$60
5(6(7
RQO\ $ VWDQGE\ 3DUDP GLOL PXOWLWDJ IFRQ IWLP 6WDW 9HUV+ 9HUV/ 5HV
02%<8'
RU5)
)LUPZDUHYHUVLRQLQ$60YHUVLRQB02%<
02%<8 02%<8
ILHOGB21BFRQWUROVHHLQSXWSDUDPHWHU ILHOGB21BWLPHBVHHLQSXWSDUDPHWHUV
%(52RSHUDWLQJPRGH KH[ ZLWKRXW%(52V
KH[ ZLWKRXW%(52VQRZULWHUHDG KH[))KH[ V21GXUDWLRQ
GHYLFHV\QFKURQL]DWLRQ IRUWKHZULWHUHDGGHYLFHILHOG
02%<'
KH[ ILHOGB21BWLPHVZLWFKHVWKHILHOG 0'6W\SHVHHLQSXWSDUDPHWHUV
RII KH[ ,FRGHHJ0'6'
KH[ VW%(52VZLWFKHVWKHILHOGRQ
KH[ ,620'6
QG%(52VZLWFKHVWKHILHOGRII KH[ GXDOGULYHU,&RGHDQG,62
KH[ ZULWHUHDGGHYLFHV\QFKURQL]DWLRQ KH[ 0'6'RSWLPL]DWLRQRQO\IRUZULWHUHDG
YLDFDEOHFRQQHFWLRQDFWLYDWHGVHHPDQXDO GHYLFH'6
IRUFRQILJXULQJPRXQWLQJDQGVHUYLFHIRU KH[ 0'6'[[RSWLPL]DWLRQRQO\IRUZULWHUHDG
02%<8 GHYLFH'66
5)
02%<'5)QRWXVHGKH[ ILHOGB21BWLPHVHHLQSXWSDUDPHWHUV
KH[ 5)PRGHQR,62
KH[ 0DQXIDFWXUHULQGHSHQGHQWWDJ
KH[ ,62P\G,QILQHRQ65)93
KH[ ,62)XMLWVX0%5
KH[ ,62,&RGH6/,1;36/,&6
02%<8 KH[ ,627DJLW+),7H[DV,QVWUXPHQWV
GLVWDQFHBOLPLWLQJBVHHLQSXWSDUDPHWHUV KH[ ,6267/5,.
$)(KH[ P
$)($KH[ GLWWRZLWKUHGXFHGRXWSXWSRZHU
02%<'+)UDWLQJVHHLQSXWSDUDPHWHUV
5)
GLVWDQFHBOLPLWLQJRQO\IRU5)5FKDQJHRIRXWSXWSRZHU
KH[ : KH[ b:
KH[ : KH[ b:
KH[ b: KH[ :
KH[ b:
2SWLRQ02%<5)RQO\
%LW
XQDVVLJQHG XQDVVLJQHG
UHVHW(55/('RQWKHZULWHUHDGGHYLFH
GRQRWUHVHW(55/('RQWKHZULWHUHDGGHYLFH
%LW
02%<8'RU5)ದZLWKRXWPXOWLWDJ
UHV
3UHVHQFHFKHFNDQG0'6FRQWURO0'6BFRQWUROB
QRSUHVHQFHFKHFN
QR0'6FRQWUROSUHVHQFHFKHFNYLD
ILUPZDUHGHIDXOW
02%<8
VFDQQLQJBWLPHBVWDQGE\WLPHIRUWKH0'6VHHLQSXWSDUDPHWHUV
KH[ QRVWDQGE\PRGH
KH[&KH[ PVPVVWDQGE\WLPH
02%<'5)QRWXVHGKH[
FB 45
&RPPDQG &RPPDQGWHOHJUDP 5HVXOWWHOHJUDPIURP

FRGH WR02%<$60 02%<$60

$GGUHVV
ZULWH $% /1* ''Q
06% /6% &
$GGUHVV $GGUHVV

/1* $% /1* ''Q
UHDG 06% /6% & 06% /6%
)RU$60RQO\

$ ; == ''
&RXQWHULV
LQFUHPHQWHGZLWK
HDFKQHZ0'6
%LW $1=B0'6BSUHVHQWB
%LW +5 VHH$SSHQGL[$
SURFHVVLPDJHPRGH
(QGDGG

,1,7
LQLWLDOL
SDWWHUQ 06% /6% &
]H
7KLVPHDQV ''Q XVHUGDWDWRIRU$60WR

/1* /HQJWKRIWKHGDWDEORFN'WR'Q
5HPDUNV $GGUHVV/1*PXVWEHOHVVWKDQ
HQGDGGUHVVRIWKH0'6
$GGUHVV 6WDUWDGGUHVVRIWKHGDWDWREHSURFHVVHGRQWKH0'6
06% 0RVWVLJQLILFDQWDGGUHVVSRUWLRQ
/6% /HDVWVLJQLILFDQWDGGUHVVSRUWLRQ
$% 1XPEHURIFKDUDFWHUVLQWKHWHOHJUDP
$% /1*
5HPDUNV $%PD\QRWEHJUHDWHUWKDQWKHEXVFRQILJXUDWLRQ
,1,7SDWWHUQ 'XULQJLQLWLDOL]DWLRQWKH0'6LVZULWWHQZLWKWKHYDOXH
,1,7SDWWHUQ
(QGDGG 0HPRU\VL]HRIWKH0'6
,QWKHHYHQWRIDQHUURUWKHIRUPDWRIWKHUHVXOWWHOHJUDPLVDVIROORZV
7KH$%E\WHFDQVWRUHDYDOXH!IRUWKHUHDGFRPPDQG &RPPDQG (UURU
,QWKLVFDVHWKHGDWDDUHRQO\SDUWLDOO\FRUUHFWDQGPXVWEHUHMHFWHG
7KHVWDWXVE\WHLQWKHUHVXOWWHOHJUDPGHSHQGVRQWKH0'6W\SHEDWWHU\VWDWHV
7HOHJUDPZKHQUHDGLQJIL[HGFRGH0'602%<)7KH$60UHDGVHDFK0'6DXWRPDWLFDOO\
2QO\UHVXOWVDUHWUDQVPLWWHG
FB 45
&RPPDQG &RPPDQGWHOHJUDPWR 5HVXOWWHOHJUDPIURP

FRGH 02%<$60 02%<$60

PRGH UHV UHV UHV
:ULWHUHDG
GHYLFH :ULWHUHDG
VWDWXV PRGH :ULWHUHDGGHYLFHVWDWXV % 6WDW
GHYLFHVWDWXV
7KHPHDQLQJRIWKHZULWHUHDGGHYLFH
VWDWXVLVGHVFULEHGLQ8'7
PD[
02%<b8
VW QWK
PRGH :ULWHUHDGGHYLFH $% 6WDW Q FRPPDQG
FRPPDQG
GLDJQRVWLFV,
)XQFWLRQFDOOV
7HOHJUDPKHDGHUVRI
ODVWFRPPDQGV
H[HFXWHG
KH[KH[ PD[PHVVDJH
IUDPHVDUHWUDQVIHUUHG
PD[
02%<b8
VWHUURU
PRGH :ULWHUHDGGHYLFH $% 6WDW Q QWKHUURU
GLDJQRVWLFV,,HUURU
PHVVDJHV
,QGLFDWHVODVWHUURU
ZKLFKRFFXUUHG
KH[(%KH[ PD[HUURU
PHVVDJHV
PD[
02%<b8
PRGH :ULWHUHDGGHYLFH $% 6WDW Q 0'6 QWK0'6
GLDJQRVWLFV,,,LGHQWLILHG
0'6
,'VRIWKH0'6XQLWVODVW
GHWHFWHGLQWKHWUDQVPLV
VLRQZLQGRZ
KH[KH[ PD[0'6,'V
02%<b8
PRGH :ULWHUHDGGHYLFH $% 6WDW Q WREHGHILQHG
GLDJQRVWLFV,9
&RPPXQLFDWLRQTXDOLW\
PRGH ZULWHUHDGGHYLFH $% 6WDW 'LDJQRVWLFGDWD

GLDJQRVWLFV 7KHPHDQLQJVRIWKHGLDJQRVWLFVGDWDDUHGHVFULEHG
LQ8'7
FB 45

FRGH WR02%<$60 IURP02%<$60

1(;7 6WDW

(1' PRGH 6WDW

3URFHVVLQJZLWKWKLV0'6KDV
WHUPLQDWHG
3URFHVVLQJSDXVHZLWKWKH
0'67HUPLQDWHVFDQQLQJBWLPH
IRU02%<80'6LPPHGLDWHO\
$$
$ $
DQWHQQD PRGH 6WDW
212)) $ $
6ZLWFKRQDQWHQQD
6WDQGE\VZLWFKRIIDQWHQQD
0DWFKDQWHQQDWRHQYLURQPHQW
02%<)))7
FB 45

FRGH WR02%<$60 IURP02%<$60
%%
0'6 %
PRGH ZHHN \HDU
VWDWXV %
&XUUHQWGDWH

7DJ 'LDJQRVWLFGDWD
PRGH 02%<8 ZHHN FDOHQGDU % 6WDW 8,'
7\SH
ZHHN
KH[
KH[
E\WHWDJ,'QXPEHU 7KHPHDQLQJRIWKH
VWWR
QGZHHN GLDJQRVWLFVGDWDLV
\HDU \HDU GHVFULEHGLQ8'7

PRGH 5) ZHHN % 6WDW 8,' 'LDJQRVWLFGDWD

\HDU
1RWUHOHYDQW
E\WHWDJ,'QXPEHU 7KHPHDQLQJRIWKH
XQLTXHLGHQWLILHU GLDJQRVWLFVGDWDLV
GHVFULEHGLQ8'7

PRGH 5) ZHHN
\HDU % 6WDW 8,' 'LDJQRVWLFGDWD
1RWUHOHYDQW
7KHPHDQLQJRIWKH
GLDJQRVWLFVGDWDLV
GHVFULEHGLQ8'7
ZHHN

PRGH 5),62
02%<' \HDU % 6WDW 8,' 'LDJQRVHGDWHQ
1RWUHOHYDQW
7KHPHDQLQJRIWKH
GLDJQRVWLFVGDWDLV
GHVFULEHGLQ8'7
*7$%*7$%
FB 45
B.5 PROFIBUS implementation

PROFIBUS is implemented on the MOBY-ASM strictly in accordance with standard
IEC 61784-1:2002 Ed1 CP 3/1. Cyclic data communication (standard specified by EN 50170)
and optional non-cyclic data communication are used.
The following figure shows the communication interface to a MOBY-ASM. PAW and PEW
are exchanged cyclically between ASM and function block. PEW tells the function block
when commands and data may be transferred to the ASM. Commands and data are put into
data records.
02%<$60
,QWHUIDFHWRXVHU %XV $60b
$60BDGGUHVV
$60BFKDQQHO
6$31,/
0'6BFRQWURO 3$:[ 3$:[
(&&BPRGH 6HTXHQFH
02%<BPRGH 6$31,/ FRQWURO
3(:[ 3(:[
VFDQQLQJBWLPH
'6[ 6$3
)XQFWLRQ SDUDPHWHUV '6[
&RPPDQGV EORFN
02%<
'6[ 6$3 0'6
'6[Q GULYHU
GDWD GDWD
'DWD
DFNQRZO
'6[
HGJHPHQWV
'6[
[ FKDQQHO
Q 1RRIFRPPDQGLQ$60QPD[ QXPEHURIEXIIHUVLQ$60VHH6HFWLRQ&RPPDQGUHSHWLWLRQ
6,0$7,&6XVHV6$3DQG6$3IRUDF\FOLFFRPPXQLFDWLRQ
7KHWUDQVIHURIWKHFRQWUROZRUG3$:3(:WDNHVSODFHYLDWKHF\FOLFGDWDBH[FKDQJHVHUYLFH
RI352),%866$3 1,/
FB 45
The following figure shows the layout of a non-cyclic data record. SAP 51 is used to transmit
the data. The data unit (DU) indicates how the MOBY-ASM is addressed.
6' /( /(U 6' '$ 6$ )& '6$3 66$3 '8 )&6 ('
+ [ [ + [ [ [ + + [ [ +
%\WH

)XQFWLRQFRGHHJ'6B5HDGUHT
5HTXHVW5HVSRQVHRND\
5HVSRQVH(UURU)UDPH
%\WH
6ORWB1XPEHU$60
$60 WRWR
FRUUHVSRQGVWRWKHVORW
ZLWKLQDQ(70
(7;
%\WH
,QGH[ฬ GDWDUHFRUGQXPEHUIRUFKDQQHOV
WRVHHWDEOHEHORZ
%\WH
'DWDOHQJWK
FB 45
The following data records have been implemented on the MOBY-ASM for communication.
Table B- 1 Data record numbers (index)
Data record Present on MOBY-ASM Description

number
0 all Reserved
1 all Reserved
101 all Parameterization channel 1
102 ASM 452, 454, 475, 754, 854, 456, Parameterization channel 2
RF170C
103 ASM 454, 754, 854 Parameterization channel 3
104 ASM 454, 754, 854 Parameterization channel 4
111 all Data transmission channel 1
112 ASM 452, 454, 475, 754, 854, 456, Data transmission channel 2
RF170C
113 ASM 454, 754, 854 Data transmission channel 3
114 ASM 454, 754, 854 Data transmission channel 4
150 ASM 475, 473 Reserved (diagnosis of powerparameters)
151 ASM 475, 473 Reserved (diagnostic buffer)
231 RF170C I&M0 (module data)
232 RF170C I&M1 (maintenance data 1)
239 ASM 475, 473, 456, RF170C FW update (optional)
246 ASM 475, 473, 456 Reserved (read FW version)
248 ASM 475, 473, 456, RF170C Reserved (SZL list)
255 ASM 456 Reserved (I&M functions)
Data record 10x

Each of data records (DR) 101 to 104 parameterizes one MOBY channel. DR 10x must
contain a RESET command. After the module starts up, DR 10x must be sent to each MOBY
channel. The channel is not ready for operation until this is done.
A DR 10x is also accepted during normal operation. DS 10x interrupts a running command.
The user receives no further acknowledgment for the interrupted command.
Data record 11x

DRs 111 to 114 are used for sending the actual commands and related acknowledgments
(all commands except RESET).
FB 45
B.6 Example of a PROFIBUS Trace

The following trace shows all telegrams which were sent on the PROFIBUS interface during
an ASM start-up or a MOBY read command. The trace illustrates the information in Sections
"Cyclic control word between master and MOBY-ASM" to "PROFIBUS implementation". It
can also be used for orientation or for trouble-shooting of customer-specific MOBY-ASM
implementations.
Note
Using FB 45 on PROFINET
If the 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 telegrams are different.
Start-up of an ASM 754 and RESET sequence on 4th channel
68 0b 0b 68 03 02 5d 00 00 00 00 00 00 00 00 00 16 Start-up of ASM
68 0b 0b 68 02 03 08 80 00 80 00 80 00 80 00 00 16
68 0b 0b 68 03 02 7d 80 00 80 00 80 00 80 00 00 16 FB sets the start-up bit.
68 0b 0b 68 02 03 08 80 00 80 00 80 00 80 00 00 16
68 0b 0b 68 03 02 5d 80 00 80 00 80 00 80 00 00 16 ASM sets the command counter to one.
68 0b 0b 68 02 03 08 88 00 88 00 88 00 88 00 00 16
68 0b 0b 68 03 02 7d 00 00 00 00 00 00 00 00 00 16 FB resets the start-up bit.
68 0b 0b 68 02 03 08 88 00 88 00 88 00 88 00 00 16
68 0b 0b 68 03 02 5d 00 00 00 00 00 00 00 00 00 16 ASM also resets the start-up bit.
68 0b 0b 68 02 03 08 08 00 08 00 08 00 08 00 00 16
68 0f 0f 68 83 82 5c 33 36 5f 01 68 06 05 00 00 00 2b 02 00 16 RESET telegrams to 4th channel
E5
68 05 05 68 83 82 5c 33 36 00 16 PROFIBUS confirmation of the RESET
68 09 09 68 82 83 08 36 33 5f 01 68 06 00 16
68 0b 0b 68 03 02 7d 00 00 00 00 00 00 00 00 00 16 Command counter for 4th channel is incremented to
68 0b 0b 68 02 03 08 08 00 08 00 08 00 10 00 00 16 2.
68 0b 0b 68 03 02 7d 00 00 00 00 00 00 00 00 00 16 Acknowledgment counter for 4th channel is
68 0b 0b 68 02 03 08 08 00 08 00 08 00 30 00 00 16 incremented to one.
68 0b 0b 68 03 02 7d 00 00 00 00 00 00 00 00 00 16 Optional: Presence is set.
68 0b 0b 68 02 03 08 08 00 08 00 08 00 31 00 00 16
68 09 09 68 83 82 5c 33 36 5e 01 68 06 00 16 Request of FB for a non-cyclic telegram
E5
68 05 05 68 83 82 5c 33 36 00 16 Return acknowledgment telegram of the RESET to
68 0f 0f 68 82 83 08 36 33 5e 01 68 06 05 00 00 00 00 00 00 16 the FB
FB 45
RESET and read command to channel 1 of a MOBY-ASM

(only acyclic telegrams are recorded)
68 0f 0f 68 83 82 7c 33 36 5f 01 65 06 05 00 00 00 2b 02 00 16 RESET command
68 05 05 68 83 82 7c 33 36 00 16 Acknowledgment that RESET is being processed
68 09 09 68 82 83 08 36 33 5f 01 65 06 00 16
68 09 09 68 83 82 5c 33 36 5e 01 65 06 00 16 Request for an acknowledgment from ASM
68 05 05 68 83 82 5c 33 36 00 16 RESET acknowledgment
68 0f 0f 68 82 83 08 36 33 5e 01 65 06 05 00 00 00 00 00 00 16
68 0f 0f 68 83 82 7c 33 36 5f 01 6f 06 05 02 00 00 40 0c 00 16 Read command: MDS addr. = 0, length = 0c
68 05 05 68 83 82 7c 33 36 00 16 Acknowledgment that read is in progress
68 09 09 68 82 83 08 36 33 5f 01 6f 06 00 16
68 09 09 68 83 82 7c 33 36 5e 01 6f 12 00 16 Request for an acknowledgment from ASM
68 05 05 68 83 82 7c 33 36 00 16
68 1b 1b 68 82 83 08 36 33 5e 01 6f 12 11 02 00 00 40 0c aa aa Acknowledgment for read with the MDS data
bb bb cc cc dd dd ee ee ff ff 00 16
FB 45
FB 45
Service & Support C
Technical support
You can reach the technical support team for all A&D projects at:
● Telephone: +49 (0) 180 5050 222
● Fax: +49 (0) 180 5050 223
Internet
Visit our site on the Internet at:
http://www.siemens.com/automation/service&support
You can send a support query to:

http://www.siemens.com/automation/support-request
You can find the latest general information about our RFID systems on the Internet at:
http://www.siemens.com/simatic-sensors/rfid
You can find the catalog and online ordering systems at:
http://www.siemens.com/automation/mall
C.1 Contacts
If you have any further questions on the use of the products described in this manual, please
contact one of our representatives at your local Siemens office.
The addresses are found on the following pages:
● On the Internet at: http://www.siemens.com/automation/partner
● In catalog CA 01
● In Catalog FS 10 specially for factory automation sensors
FB 45
Service & Support
C.2 Training
C.2 Training
Training center
We offer appropriate courses to get you started. Please contact your regional training center
or the central training center in D-90327, Nuremberg, Germany.
Telephone: +49 (911) 895-3200
http://www.siemens.com/sitrain
FB 45

Manual FB45 PDF

Uploaded by

Copyright:

Available Formats

Manual FB45 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual FB45 PDF

Uploaded by

Copyright:

Available Formats

Introduction 1

Service & Support C

Siemens AG J31069-D0166-U001-A3-7618 Copyright © Siemens AG 2006,

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

$60 5)& 5)&

$60 $60 $60$60 $60

Figure 1-1 Interface modules for FB 45

Features of the interface

Position in the information landscape

Requirements for using FB 45

Purpose of this document

Scope of this documentation

1.3 Navigating in the Function Manual

Structure of contents Contents

Table 2- 1 Typical runtimes of FB 45 (cycle load of AS in ms)

S7-CPU Idle pass ASM Distributed ASM on PROFIBUS

n = Amount in bytes of processed user data per read or write command

Calculating MOBY data throughput

tk Communication time between ASM, write/read device

2.2 Configuration scheme

Table 2- 2 MOBY FB configuration scheme

Ladder logic Parameters Data type Permissible range Description

2.3 Data structures of FB 45

&DOOUHDGHU &DOOUHDGHU &DOOUHDGHU &DOOUHDGHU

3DUDPVB'% 3DUDPVB'% 3DUDPVB'% 3DUDPVB'%

Figure 2-1 Configuration scheme of FB 45

Each FB 45 call points to a separate parameter data block (Params_DB, Params_ADDR),

2.4 Number of MOBY channels which can be connected

Table 2- 3 Number of MOBY channels

2.5 Addressing of MOBY channels

Centralized configuration with ASM 475

Addressing via PROFIBUS

Figure 2-4 Example: Automatic address generation of a MOBY-ASM/communication module in ET

Figure 2-5 Setting the physical address assignment in UDT 10

Table 3- 1 UDT 10 "MOBY Param"

Address Name Type Initial Comment

3.1.1 INPUT parameters

Table 3- 2 INPUT parameters

00 hex = no standby time (default)

MOBY D: 00 hex (reserved)

distance_limiting MOBY U: Range limitation

3.1.2 Command and status word

Table 3- 3 Variables in command and status word

3.1.3 Further displays

([DPSOH '%% '%%

3.2 MOBY commands

Table 3- 5 UDT 20 "MOBY CMD"

3.2.1 Command parameters

Table 3- 6 Overview of commands

Command [hex] Command

Table 3- 7 Write MDS

Command sub_command length address_MDS DAT_DB Note

Table 3- 8 Read MDS

Command sub_command length address_MDS DAT_DB Note

**) Please refer to section for addressing individual transponder types.

Table 3- 9 Initialize MDS

Command sub_command length address_MDS DAT_DB Note

MDS type Memory size Init duration INIT duration

Table 3- 10 SLG status

$60 5)& 5)&

$60 $60 $60$60 $60

&DOOUHDGHU &DOOUHDGHU &DOOUHDGHU &DOOUHDGHU

([DPSOH '%% '%%

7KHXVHUVWDUWVKLVKHUFRPPDQG 7KH0'6VSDVVE\WKHZULWHUHDG 5HVXOWVDUH

$SSO\ 5(6(7 0'6HQWHUV 5HDGZULWH $60KDV 0'6 $FRPPDQG

$60LQ HJ$60LQ $60