Industrial

Identification with
SIMATIC MV320 via
RF170C
Siemens
SIMATIC MV, PROFINET, PROFIBUS, STEP 7 V15 Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/109755705 Support
Legal information

Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several
components in the form of text, graphics and/or software modules. The application examples are
a free service by Siemens AG and/or a subsidiary of Siemens AG (“Siemens”). They are non-
binding and make no claim to completeness or functionality regarding configuration and
equipment. The application examples merely offer help with typical tasks; they do not constitute
customer-specific solutions. You yourself are responsible for the proper and safe operation of the
products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the
application examples used by technically trained personnel. Any change to the application
examples is your responsibility. Sharing the application examples with third parties or copying the
application examples or excerpts thereof is permitted only in combination with your own products.
The application examples are not required to undergo the customary tests and quality inspections
of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without
limitation, liability for the usability, availability, completeness and freedom from defects of the
application examples as well as for related information, configuration and performance data and
any damage caused thereby. This shall not apply in cases of mandatory liability, for example
under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of
life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent
non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for
damages arising from a breach of material contractual obligations shall however be limited to the
foreseeable damage typical of the type of agreement, unless liability arises from intent or gross
 Siemens AG 2018 All rights reserved

negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions
do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens
against existing or future claims of third parties in this connection except where Siemens is
mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any
damage beyond the liability provisions described.
Further notes
Siemens reserves the right to make changes to the application examples at any time without
notice. In case of discrepancies between the suggestions in the application examples and other
Siemens publications such as catalogs, the content of the other documentation shall have
precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with Industrial Security functions that support the secure
operation of plants, systems, machines and networks.
In order to secure plants, systems, machines and networks against cyber threats, it is necessary
to implement (and to maintain continuously) a holistic, state-of-the-art Industrial Security concept.
With this in mind, Siemens’ products and solutions are only part of such a concept.
It is the client’s responsibility to prevent unauthorized access to his plants, systems, machines
and networks. Systems, machines and components should only be connected with the company’s
network or the Internet, when and insofar as this is required and the appropriate protective
measures (for example, use of firewalls and network segmentation) have been taken.
In addition, the recommendations by Siemens regarding the respective protective measures have
to be observed. For additional information on industrial security measures that may be
implemented, please visit https://www.siemens.com/industrialsecurity.
Siemens' products and solutions undergo continuous development to make them more secure.
Siemens explicitly recommends to carry out updates as soon as the respective updates are
available and always only to use the current product versions. Use of product versions that are no
longer supported, and failure to apply latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
at: http://www.siemens.com/industrialsecurity.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 2
Table of Contents

Table of Contents
Legal information ......................................................................................................... 2
1 Introduction ........................................................................................................ 4
1.1 Overview............................................................................................... 4
1.2 Mode of operation ................................................................................ 6
1.3 Hardware and software components ................................................... 7
2 Engineering ........................................................................................................ 8
2.1 General overview ................................................................................. 8
2.2 Basics on using the Ident blocks ........................................................ 10
2.3 Explanation of HW_CONNECT .......................................................... 11
2.4 Explanation of the blocks ................................................................... 13
2.4.1 "MV3x0Control" (FB1) functionality .................................................... 13
Realized functions of the block .......................................................... 14
Note on the internal Ident block "Reset_Univ" ................................... 14
2.4.2 "freePortControl" (FB2) functionality .................................................. 14
Block interface .................................................................................... 14
Realized functions of the block .......................................................... 15
Note on initialization via the "Ident_Profile" block .............................. 15
2.5 Diagnostic and error messages ......................................................... 16
2.5.1 MOBY mode-specific error messages ............................................... 16
3 Configuration and Settings............................................................................. 17
 Siemens AG 2018 All rights reserved

3.1 Instructions for using "MOBY mode: MV3xx" ..................................... 17

3.2 Instructions for using "MOBY mode: Freeport protocol" .................... 17
4 Configuring the MV320 Optical Handheld Reader ....................................... 19
5 Installation and Commissioning .................................................................... 20
5.1 Installing the hardware ....................................................................... 20
5.2 Installing the software (download) ...................................................... 21
5.3 Commissioning the example project .................................................. 21
6 Tips and Tricks ................................................................................................ 22
7 Links & Literature ............................................................................................ 23
8 History............................................................................................................... 23

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 3
1 Introduction

1 Introduction
In order to implement automatic identification of goods, materials and workpiece
carriers for process and production plants, the SIMATIC Ident product portfolio
from Siemens offers customized modules.
This application example shows you what has to be observed for the configuration
of the SIMATIC MV320 optical handheld readers in combination with the SIMATIC
RF170C interface module. In addition, user blocks are provided to receive reading
results automatically using a SIMATIC S7-PLC.

1.1 Overview
The figure below provides an overview of the automation task.
Figure 1-1

PLC

RFID connection

Optical handheld reader

 Siemens AG 2018 All rights reserved

In order to integrate SIMATIC MV320 optical handheld readers into a SIMATIC

control system, the RF170C communication module is used.
Suitable function blocks for programming the SIMATIC RFID modules on SIMATIC
S7 controllers are available in TIA Portal.
Depending on the preferred transmission mode, the suitable ET200pro
communication module has to be selected.

Aim of this configuration help

In this application example, the MV320 optical handheld reader shall be connected
to the control system on a distributed basis using a SIMATIC ET200pro. For this,
the required communication module is the SIMATIC RF170C.
The application example supports you in commissioning your SIMATIC Ident
modules. It mainly focuses on the ready-to-use blocks of this application example.
In addition, the configuration and settings of the SIMATIC Ident modules is also
discussed.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 4
1 Introduction
1.1 Overview

Schematic layout
The figure below shows a schematic overview of the most important components of
the solution:
Figure 1-2

SIMATIC S7 controllers

PROFINET IE

PROFIBUS DP

Distributed I/O and

SIMATIC
communication module
 Siemens AG 2018 All rights reserved

RF170C

Serial connection / RS232

Optical handheld reader

MV320

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 5
1 Introduction
1.2 Mode of operation

Advantages
The application example offers the following advantages:
 The illustrations and explanations included in this application example save
you time and money in the commissioning of your own automation solution.
 You can expand the provided hardware configuration as desired or integrate it
in your project.
 By using the RF170C, the SIMATIC MV320 optical handheld reader is
integrated into a control system via PROFINET or PROFIBUS. This is a
frequent requirement in modern automation solutions.
 The ready-to-use blocks significantly simplify operating the SIMATIC MV320
optical handheld readers.

1.2 Mode of operation

Sequence of the core functionality
Figure 1-3

Trigger Display
reset job result
 Siemens AG 2018 All rights reserved

MV3x0 Trigger Data

Trigger read storage

Display
job result

Perform a reset (initialization) using the included user block to make the optical
handheld reader ready for operation. Once the reset has been performed, the user
can read 1D and 2D barcodes and further process the results in a PLC.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 6
1 Introduction
1.3 Hardware and software components

1.3 Hardware and software components

This application example was created with the following components:

Hardware components
Table 1-1
Component Qty. Article number Note
SIMATIC S7-1500 1 6ES7 516-3AN00- Alternatively, you can use a
CPU 1516-3 PN/DP 0AB0 different S7-CPU.
ET 200pro 1 6ES7154-1AA01- For PROFIBUS connection
IM 154-1 DP 0AB0
ET 200pro 1 6ES7153-4AB10- For PROFINET connection
IM 154-4 PN HF 0AB0
SIMATIC RF170C 1 6GT2002-0JD01 FW V2 or higher
SIMATIC MV320 1 6GF3320-0HT01 Alternatively, you can use a
different SIMATIC MV340
reader.
KAB_KONF_ V320_5M 1 6GT2191-0BH50 For MV340
6GT2191-0AH50
 Siemens AG 2018 All rights reserved

Software components
Table 1-2
Component Qty. Article number Note
STEP 7 TIA Portal V15 1 6ES7822-1..05-..

Example files and projects

The following list contains all files and projects that are used in this application
example.
Table 1-3
Component Note
109755705_SIMATIC_MV320_RF170C_PROJ_ This zip file contains the
V10.zip STEP 7 project for
SIMATIC S7-1500.
109755705_SIMATIC_MV320_RF170C_DOC_ This document
V10_en.pdf

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 7
2 Engineering
2.1 General overview

2 Engineering
The following chapters describe the PLC program of the configuration help.

2.1 General overview

The following figure schematically shows the interaction of the user program and
the SIMATIC hardware:
Figure 2-1

User program

User block Ident blocks

MV3x0 Reset
Control Read
Univ

Hardware
 Siemens AG 2018 All rights reserved

SIMATIC S7 controllers …

Interface modules …

SIMATIC MV320 …

The user block controls the operations of the optical handheld readers MV320
using the integrated Ident blocks. The command frames generated by the user
block are sent from the SIMATIC S7 controller to the SIMATIC MV320 readers via
the interface modules. The response frames of the MV320 readers take the same
path back to the user program and are provided to the user via the block outputs.
For the Ident blocks, it does not matter whether the interface modules are
connected to the control system via PROFIBUS, PROFINET or in a proprietary
manner.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 8
2 Engineering
2.1 General overview

Program overview
The following figure shows the call hierarchy of the user program in this application
example:
Figure 2-2

OB 1 cycle Ident blocks Data storage

Reset HW
Interface
Univ Connect

Read IdentData
OB 1
 Siemens AG 2018 All rights reserved

Ident profile
MV3x0
Control
Ident_
Profile

To show the use of the Ident blocks in a simplified manner, the application example
calls them all together directly in the "MV3x0Control" function block. Each Ident
block is responsible for a specific functionality.
The user data read are stored in the “IdentData” data block.
The “Interface” data block includes all tags of the application example that are to be
modified.
Internally, all Ident blocks call the basic block, “Ident Profile”. Therefore, the Ident
blocks are only an encapsulation of the complex “Ident Profile” block to make it
easier for you to implement the RFID functionalities.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 9
2 Engineering
2.2 Basics on using the Ident blocks

2.2 Basics on using the Ident blocks

To be able to use the Ident blocks, the following requirements must be met:

Working with multiple channels

If you are working with multiple channels, make sure that, for each channel, the
“Ident Profile” block is called with a separate instance DB.

Calling the blocks

If an Ident block is called in the TIA Portal, all required software components are
automatically generated for the block and added to your project. This includes
user-defined data types (UDTs), the basic “Ident_Profile” block and various system
function blocks (SFCs and SFBs). The Ident blocks can be found in the TIA Portal
in “Instructions” > “Optional packages” > “SIMATIC Ident”.

Addressing the block

All Ident blocks have an INOUT parameter called “HW_CONNECT”. Via this
interface, the blocks are provided with the address information of the configured
interface module/reader. For this purpose, the UDT “IID_HW_CONNECT” is
automatically generated when calling the Ident block and is stored in the TIA
project tree in “PLC data types”.
 Siemens AG 2018 All rights reserved

For more information about using the “IID_HW_CONNECT” UDT, please refer to
chapter 2.3.

Edge-controlled execution of the blocks

All Ident blocks have an input parameter called “EXECUTE”. The execution of the
respective RFID functionality of the blocks is started via this parameter. It has to be
observed that the “EXECUTE” input responds to positive edges only. This means
that the blocks with a logic 0 (“false”) have to be run on the EXECUTE parameter
before they can register the change to a 1 (“true”) in a later run of the CPU cycle.
This is why it is important to set the EXECUTE parameter to 0 (“false”) after
successful or unsuccessful processing of the Ident blocks in order to be able to
restart the block later on. Please observe also chapter 6.

Reset block
Before a SIMATIC MV320 reader can start, a reset has to be performed. For this,
the "Reset_Univ" block is available.
The RESET command is used for establishing the connection to the optical
handheld reader. You can read the firmware version of the RF170C in the instance
DB of the Ident profile or MOBY_DB.
A successfully established connection is signaled by a triple acoustic signal of the
optical handheld reader. The RESET command is made without any reader-
specific parameters and triggers the deletion of the buffer of the optical handheld
reader.
After the “Reset”, the handheld reader is ready for use.
If the connection is not established or in case of a faulty connection attempt, the FB
outputs the "0xE4FE03" error message.

Command buffer for user data

The user data of the MV320 are buffered on the SIMATIC RF170C. If no "Read"
has been added yet, the presence bit ("statReadPresence") signals that new data

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 10
2 Engineering
2.3 Explanation of HW_CONNECT

have been scanned and are available in the RF170C for being fetched via a “Read”
command.

2.3 Explanation of HW_CONNECT

The “hwConnect” input parameter of the “Ident Profile” block is used for addressing
the configured interface modules and requires the “IID_HW_CONNECT” UDT as
data type.

Details about “IID_HW_CONNECT”

The figure below shows the structure of the “IID_HW_CONNECT” UDT:
Figure 2-3

The following three fields are provided for the addressing of the interface modules:
 “HW_ID” (only for S7 1200 and S7 1500 PLC)
 Siemens AG 2018 All rights reserved

 “CM_CHANNEL”
 “LADDR”
The “CM_CHANNEL” is the slot of the optical handheld reader on communication
module 1 or 2. “LADDR” is the I/O address of the RFID communication channel.
“HW_ID” is the hardware identification number automatically assigned by TIA
Portal.

Using "IID_HW_CONNECT"
Proceed as follows to create the addressing tags:
1. Create a tag of type “IID_HW_CONNECT” in a global data block.
2. This is where you enter the correct address values in the tag (see bottom).
3. Connect this tag to the “hwConnect” input parameter of the “MV3x0Control”
block.

Note You have to create a separate address tag for each SIMATIC MV320 reader in
your project.

Reading correct address values

The figure below shows where you can read the correct values for addressing
interface modules:

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 11
2 Engineering
2.3 Explanation of HW_CONNECT

Figure 2-4

Proceed as follows to read the address values:

 Siemens AG 2018 All rights reserved

1. In TIA Portal, go to the hardware configuration.

2. Select your configured interface module.
3. In the “I address” and “Q address” fields of the Device overview of the selected
module, you will find the value for the “LADDR” field of the UDT (in this
application example: "0"). Make sure that the identical value is assigned to the
I and Q address.
4. Select this field and read the "Hardware ID" ("Hardware identifier"). Enter this
value in the “HW_ID” field (in this application example: 267 or 16#010B.)
5. In the “CM_CHANNEL” field, specify whether the reader is connected to port 1
or 2 of the interface module.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 12
2 Engineering
2.4 Explanation of the blocks

2.4 Explanation of the blocks

This chapter explains the most important blocks.

2.4.1 "MV3x0Control" (FB1) functionality

The “MV320Control” block is a complex block. It contains all functionalities required

for communication with the optical handheld reader MV320. The Ident blocks called
therein are a simplified interface to the “Ident Profile” block. Each Ident block
contains a single “Ident Profile” command.

Note For the connection of third-party optical readers, use the setting of the MOBY
Mode "Freeport protocol" in the HW Config. Instead of calling the
"MV320Control" function block, call the "freePortControl" function block included
in the project.

The Ident profile is based on the standardized “Proxy Ident Function Block”
protocol. For the specification of the protocol, please refer to the PROFIBUS User
Organization.
 Siemens AG 2018 All rights reserved

Block interface
Figure 2-5

The following table describes the interfaces of the block.

Table 2-1
Input parameter Description
reset “TRUE” = trigger a reset
hwConnect Physical addressing of communication module and reader
identDataArray Reference to global memory area for receive data.
identDataString Reference to string area for receive data.
done “TRUE” = job successfully completed.
busy “TRUE” = job active.
error “TRUE” = job completed with error
status Error message regarding an erroneous job (“ERROR” = “TRUE”)

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 13
2 Engineering
2.4 Explanation of the blocks

Realized functions of the block

The user block was created in SCL and offers the following functions:
 Reset of the communication module and the optical handheld reader MV320
 Automated reading of the result string after scanning a barcode
 Providing the reading result as string and as byte array (byte 0 and 1 specify
the length of the decoded result string)
 Output of the status and the error messages of the block

Note on the internal Ident block "Reset_Univ"

The "Reset_Univ" block is a universal reset block that can be used for resetting
identification systems. The parameters required for initialization are defined via the
"PARAM" input parameter.
The table below shows the parameters required for the optical handheld readers
MV320. The input parameter is defined as "Array [1..16] of Byte".
Table 2-2
Byte 1 2..5 6 7..10 11 12..16
Value 0x04 0x00 0x0A 0x00 0x02 0x00
 Siemens AG 2018 All rights reserved

2.4.2 "freePortControl" (FB2) functionality

The “freePortControl” block is a complex block. It contains all functionalities

required for communication with optical handheld readers via the Freeport protocol.

Block interface
Figure 2-6

The following table describes the interfaces of the block.

Table 2-3
Input parameter Description
reset “TRUE” = trigger a reset
hwConnect Physical addressing of communication module and reader
identDataArray Reference to global memory area for receive data.
identDataString Reference to string area for receive data.
done “TRUE” = job successfully completed.
busy “TRUE” = job active.
error “TRUE” = job completed with error
status Error message regarding an erroneous job (“ERROR” = “TRUE”)

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 14
2 Engineering
2.4 Explanation of the blocks

Realized functions of the block

The function block was created in SCL. Thus, the functions are easy to
comprehend and to extend.
 Reset of the communication module
 Automated reading of the result string after scanning a barcode
 Providing the reading result as string and as byte array (byte 0 and 1 specify
the length of the decoded result string)
 Output of the status and the error messages of the block

Note on initialization via the "Ident_Profile" block

The table below shows the structure of the reset frame for resetting the
communication module and the handheld reader which is transferred as "Array
[1..16] of Byte" to the "txref" input parameter of the “Ident_Profile” block.
Table 2-4
Byte 1 2..5 6 7..10 11 12..16
Value 0x04 0x00 0x0A 0x00 0x02 0x00

Note The "FreePortControl" user block resets only the RF170C communication
module. If your connected reader requires a “Reset” function, additionally send
 Siemens AG 2018 All rights reserved

the reset frame mentioned above to the end device using the Ident command
"PHYSICAL_WRITE" (command code 71hex).

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 15
2 Engineering
2.5 Diagnostic and error messages

2.5 Diagnostic and error messages

If an error has occurred, the “STATUS” output parameter of the Ident blocks
provides different hex codes. The meaning of the codes can be found in the
manual “SIMATIC Ident RFID systems Ident profile and Ident blocks, standard
function for Ident systems” (\3\) in chapter 4 “Error Messages”.
2.5.1 MOBY mode-specific error messages

The table below gives an overview of the error messages specific for the MOBY
mode "MV3xx”.
Table 2-5
Error ID Meaning
0xE4FE03 Connection error to the reader
0xE2FE01 Negative acknowledgment or faulty frame from the reader
0xE6FE01 Unknown command, wrong command parameters or inadmissible
command chain (wrong length specification)
0xE1FE03 Address error in the command (≠ "0x0000", "0x0002", "0xFFFF)
0xE4FE8D Internal communication error
0xE4FE04 New data were received before available data have been fetched.
• Scan mode: Latest data are lost.
 Siemens AG 2018 All rights reserved

For the “Write” command, the oldest acknowledgments are lost

without an error message being generated.
0xE6FE05 "Reset_Reader" required
0xE5FE08 The command has not been executed.
Possible causes:
• Previous command still active.
• Data from the reader are available ("Reader_Status").
0xE5FE04 Invalid data block number (DBN) in the reader / communication
module

ATTENTION Connection error to the reader

If for the MV320 the trigger button of the reader is pressed for more than
30 seconds, a message is displayed in the controller indicating that an optical
handheld reader is not connected. As soon as the trigger button is released,
the error will not be signaled anymore.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 16
3 Configuration and Settings
3.1 Instructions for using "MOBY mode: MV3xx"

3 Configuration and Settings

3.1 Instructions for using "MOBY mode: MV3xx"
This chapter shows the configuration steps required to create a project with the
SIMATIC S7 CPU, SIMATIC RF170C and SIMATIC MV320 optical handheld
readers.
1. Configure the hardware.
2. For this purpose, go to “Devices & networks” and select the RF170C interface
module.
3. Go to "Device view" > "Properties" > "Module parameters" and set the module
parameters as shown in the figure below.
Figure 3-1
 Siemens AG 2018 All rights reserved

4. Determine the correct values for HW_ID, LADDR and CM_CHANNEL as

described in chapter 3.3 and enter the values in the DB "HWConnect".
5. Load the user program and the hardware configuration into your S7 CPU.

3.2 Instructions for using "MOBY mode: Freeport

protocol"
This chapter shows the configuration steps required to create a project with the
SIMATIC S7 CPU, SIMATIC RF170C and other serial devices.
1. Configure the hardware.
2. For this purpose, go to “Devices & networks” and select the RF170C interface
module.
3. Go to "Device view" > "Properties" > "Module parameters" and set the module
parameters according to the technical data of the serial device. As an example,
set the values as shown in the figure below.

ATTENTION Changing over to the RS232 interface

By selecting the "MV3xx" option, the communication module automatically
switches over to the RS232 interface. For selecting the Freeport protocol, you
have to change over the interface manually to RS232 and configure the
interface parameters.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 17
3 Configuration and Settings
3.2 Instructions for using "MOBY mode: Freeport protocol"

Figure 3-2
 Siemens AG 2018 All rights reserved

4. Determine the correct values for HW_ID, LADDR and CM_CHANNEL as

described in chapter 2.3 and enter the values in the DB "HWConnect".
5. Load the user program and the hardware configuration into your S7 CPU.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 18
4 Configuring the MV320 Optical Handheld Reader
3.2 Instructions for using "MOBY mode: Freeport protocol"

4 Configuring the MV320 Optical Handheld

Reader
To enable operation of the optical handheld reader via the RS232 interface with the
RF170C RS422/RS232, the handheld readers must be configured correspondingly.
This configuration can be made quickly and easily by scanning the corresponding
code.
Figure 4-1

Scanning of the corresponding code sets all relevant parameters for

communication between the RF170C RS422/RS232 communication module
and the optical handheld reader:
• Interface: RS232
 Siemens AG 2018 All rights reserved

• Transmission speed: 115.2 kBaud

• Data bits: 8
• Parity: None
• Stop bits: 1
• Protocol format: Packet mode (not supported by MV325)

See also: https://support.industry.siemens.com/cs/ww/en/view/32622825

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 19
5 Installation and Commissioning
5.1 Installing the hardware

5 Installation and Commissioning

This chapter shows the steps required to install and start up the application
example using the code from the sample program and the components from the
hardware list.

5.1 Installing the hardware

The following figure shows the hardware configuration of the application.
Figure 6-5-1

L+ (24V)

M (0V)

SIMATIC S7-1500
 Siemens AG 2018 All rights reserved

PROFIBUS DP
PROFINET / IE

ET200pro + RF170C SIMATIC MV320

Reader cable

Note Follow the installation guidelines for SIMATIC S7-1500 (\6\), SIMATIC RF170C
(\5\), SIMATIC MV320 (\10\).

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 20
5 Installation and Commissioning
5.2 Installing the software (download)

5.2 Installing the software (download)

This chapter describes the steps for installing the sample code.
1. Install TIA Portal V15.
2. The TIA Portal project is available on the HTML page from which you
downloaded this document (\2\). Save the project to your hard disk.
3. Unzip the file.
4. Open the just unzipped project in the TIA Portal:
“File > Open > Browse”.
5. The project is now available to you.

5.3 Commissioning the example project

This chapter describes the steps to start up the sample code.
1. Wire your hardware.
2. Open the application example in the TIA Portal.
3. If you are using alternative hardware, perform the configurations described in
chapter 3.
 Siemens AG 2018 All rights reserved

4. Assign an IP address from the IP band of the configured S7 CPU to your

programming device. Alternatively, customize the CPU’s IP address to your
preferences.
5. Download the user program into your S7 CPU. To do this, select the S7 CPU
in your project tree and then click “Download”.

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 21
6 Tips and Tricks

6 Tips and Tricks

Visit our guide on the topic SIMATIC Ident
The “Industrial Identification with SIMATIC Ident in the Siemens Industry Online
Support” guide provides you with more information about SIMATIC Ident and
related application examples.
https://support.industry.siemens.com/cs/ww/en/view/109477926
 Siemens AG 2018 All rights reserved

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 22
7 Links & Literature

7 Links & Literature

Table 8-1
Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Download page of the entry
https://support.industry.siemens.com/cs/ww/en/view/109755705

\3\ SIMATIC Ident RFID systems Ident profile and Ident blocks, standard function for
Ident systems
https://support.industry.siemens.com/cs/ww/en/view/106368029
\4\ SIMATIC Ident RFID Systems SIMATIC RF200
https://support.industry.siemens.com/cs/de/en/view/47189592

\5\ SIMATIC Ident RFID systems RF170C communication module

https://support.industry.siemens.com/cs/de/en/view/109743487

\6\ SIMATIC S7-1500, ET 200MP Automation system

https://support.industry.siemens.com/cs/ww/en/view/59191792

\7\ SIMATIC S7 S7-1200 Programmable controller

https://support.industry.siemens.com/cs/ww/en/view/109478121

\8\ SIMATIC S7-300 CPU 31xC and CPU 31x: Installation

 Siemens AG 2018 All rights reserved

https://support.industry.siemens.com/cs/ww/en/view/13008499

\9\ Industrial Identification with SIMATIC Ident in the Siemens Industry Online Support
https://support.industry.siemens.com/cs/ww/en/view/109477926

\10\ SIMATIC MV320 / SIMATIC MV325

https://support.industry.siemens.com/cs/de/en/view/85219368
\11\ SIMATIC IDENT Machine Vision Systems SIMATIC MV340 System Manual 2012
https://support.industry.siemens.com/cs/de/en/view/61909865
\12\ Homepage of the PROFIBUS user organization
http://www.profibus.com/

8 History
Table 9-1
Version Date Modifications
V1.0 02/2018 First version

MV320 via RF170C

Entry ID: 109755705, V1.1, 04/2018 23