rf 180c application june 2013 - siemensit is the objective of this application to show you in a...

Applications & Tools

Answers for industry.

Operation of RFID Systems via Communication Module RF 180C (PROFINET RT) on Windows-based Systems RF 180C

Application June 2013

– Warranty and liability

2 Application: RFID via PNIO on Windows-based systems

V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Warranty and liability

Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications – e.g. Catalogs – the contents of the other documents have priority.

We do not accept any liability for the information contained in this document.

Any claims against us – based on whatever legal reason – resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of Siemens Industry Sector.

Siemens Industry Online Support This article is taken from the Siemens Industry Online Support. The following link takes you directly to the download page of this document: http://support.automation.siemens.com/WW/view/en/26608353 Caution The functions and solutions described in this article confine themselves to the realization of the automation task predominantly. Please take into account furthermore that corresponding protective measures have to be taken up in the context of Industrial Security when connecting your equipment to other parts of the plant, the enterprise network or the Internet. Further information can be found under the Item-ID 50203404.

http://support.automation.siemens.com/WW/view/en/26608353

– Table of contents

Application: RFID via PNIO on Windows-based systems V1.1, Item-ID: 26608353 3

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Table of contents Warranty and liability ................................................................................................... 2 1 Problem............................................................................................................... 4

2 Solution............................................................................................................... 5

2.1 Solution overview ................................................................................. 5 2.2 Required Hardware and Software Components .................................. 7

3 Function mechanisms of this application ..................................................... 11

3.1 Core functionality of the application PNIO_RFID.EXE ....................... 11 3.2 User interface of the application PNIO_RFID.EXE ............................ 11 3.3 Editing the ASM commands ............................................................... 13 3.3.1 Structure of the ASM command text file ............................................. 13 3.3.2 Activating the ASM command telegrams ........................................... 14 3.4 Structure of the ASM commands ....................................................... 15 3.5 Status byte in acknowledgement telegram ........................................ 20 3.6 Chained commands ........................................................................... 21

4 Installation of hardware and software ........................................................... 26

4.1 Installing the hardware ....................................................................... 26 4.2 Installing the software ......................................................................... 26 4.3 Testing the PROFINET IO system ..................................................... 28

5 Software configuration of the hardware configuration ............................... 30

5.1 Generating the hardware configuration in HW Config ....................... 30 5.2 Generating the PC configuration with the station manager ............... 34

6 Operating the Application ............................................................................... 37

6.1 First operating steps ........................................................................... 37 6.2 Additional operating information ......................................................... 38

7 Glossary ........................................................................................................... 39

8 Literature .......................................................................................................... 40

8.1 References on hardware and software of this application ................. 40 8.2 Further Literature ................................................................................ 41

9 History............................................................................................................... 41

1 Task


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

1 Task Introduction

In the logistics and distribution sector, RFID systems have for some years been setting new standards for control and management. As opposed to the common bar code systems, they do not only identify, but control and manage the logistic processes with rewritable electronic data memories, so-called transponders. The communication between RFID systems and automation devices has been described in some detail in the respective manuals and application descriptions (see /3/, /4/). The RFID system can be connected with the automation device via PROFIBUS and PROFINET via different interface modules. STEP7 functions and function blocks (e.g. FB45 “MOBY FB”) and prepared UDTs (e.g. UDT10 “MOBY Param_...” and UDT20 “MOBY CMD_...”) support the user in the configuration.

Description of the automation task However, direct communication of RFID systems with PCs is also possible. The application on hand shows how you can connect and operate different RFID systems with the Ethernet interface of your PC via PROFINET using a communication module.

2 Solution

2.1 Solution overview


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

2 Solution 2.1 Solution overview

Objective of this application It is the objective of this application to show you in a simple example how RFID systems (RF300, MOBY D, MOBY U) can exchange data with a computer, which runs on MS Windows, via PROFINET IO using a C++ user program and an RF 180C communication module. The open C++ source code is documented and can be changed and expanded at your discretion. This enables you to compile an RFID system according to your requirements.

Display The figure below shows a possible example configuration with the hardware components of this application example: Figure 2-1

Read-/Writedevice RF 310R

RF 180C RF 180C

IPC

PROFINET

Main contents of this application You will find out... • how to configure your computer as a “PC station” in the sense of PROFINET. • which hardware components and which material is needed for wiring, • which command telegram you use to control the RFID system and to write on

and read from transponders. • how you operate the C++ application.

Delimitation This application does not contain any description1 of... • the programming language C++

1 Description only where necessary for comprehension and setup of this application.

2 Solution

2.1 Solution overview


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

• the components on the SIMATIC NET CD, • the hardware components used, • of RFID in general. Previous knowledge in this field is assumed.

Language use For all explanations and step by step instructions referring to the software, the terms of an English installed or switched software are used, irrespective of the document language. This also applies to the pictures and screenshots.

2 Solution

2.2 Required Hardware and Software Components


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved


RFID components The following hardware-RFID-components are used in this application. Table 2-1: Used hardware components

element figure description

Communication module (ASM)

SIMATIC RF180C Communication module for direct connection to PROFINET IO. Two readers (SLGs) can be operated on this communication module. RF180C Order nr.: 6GT2 002-0JD00 Connection module Order nr.: 6GT2 002-1JD00

2 Solution



V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

element figure description

Write/Read device (SLG)

SIMATIC RF310R Write/Read device with integrated antenna and RS422 interface.

Mobile data storage unit (MDS)

SIMATIC RF320T Universal, compact tag (20 byte EEPROM) in button format.

SIMATIC RF340T Universal data memory (8 KB FRAM).

Hardware components General view over all hardware components.

Table 2-2: Hardware components

Component Note

PC Windows-based system with Ethernet interface

List of tested systems (all with SIMATIC NET V8.2): - Windows 7 Ultimate 32/64Bit - Windows 7 Professional 32/64Bit - Windows 7 Enterprise 32/64Bit

ASM RFID communication module RF 180C for PROFINET with PROFINET connection block.

In the chapters • 4 “Connecting“, • 10 “Connecting cable to

Reader/SLG“, • 11 “Ordering data“ of the operating instruction “SIMATIC Sensors - RFID Systems – Communication Module RF180C“ (/7/) you find all overleaf components, all pin assignments and all necessary ordering numbers. This takes into consideration systems RF300 and MOBY D/U.

PROFINET cables and connectors for connecting ASM ↔ PC;

(PROFINET cable, meter ware e.g. order no.: 6XV1870-2D)

Connection cable ASM↔SLG The SLGs of the various RFID systems use different plug-in connections. Cable/connector for ASM power supply

2 Solution



Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Component Note

SLG RFID write/read device of system RF300, MOBY D or MOBY U with RS422 interface (3964R)

If you wish to use the writing and reading of 8 kByte supported by the example application with chained commands, you must use an RFID system (as well as the respective transponder types), which also supports exchange of such large data volumes.

Example: System RF 300 SLG: SIMATIC RF310R Order nr: 6GT2801-1AA10 MDS: SIMATIC RF340T Order nr: 6GT2800-4BB00 For selecting a system consult the appropriate system manual (see /8/, /9/, /10/).

MDS Transponder of system RF 300, MOBY D or MOBY U.

Cable/connector for SLG power supply

SLGs of RF 300 and MOBY U are supplied via the ASM interface.

A MOBY D SLG requires a separate power supply. For the plug-in connection at the SLG you require a 4-pole M12 female connector.

Ordering number: 6GT2 390-1AB00

1. 4 Ground (0 V) 2. 3 + 24 V

View from above onto the connector in the SLG

Power supply for ASM and SLG

All involved components are supplied with 24 V DC. For the power consumption for ASM and SLG please refer to the documents /7/, /8/, /9/, /10/.

Standard software components Table 2-3: Standard software components

Component Ordering number Note IE SOFTNET PN IO Lizenz 6GK1704-1HW80-3AA0 IE SOFTNET PN IO V8.0

Windows 7 Professional//Ultimate, for CP1612

6GK1704-1HW71-3AA0 IE SOFTNET PN IO 2008 Windows XP Professional, Vista Business/Ultimate, Windows 2003/2008 Server for CP1612

6GK1704-1HW70-3AK0 IE SOFTNET PN IO 2007 Windows XP Professional forr CP1512/ CP1612

2 Solution



V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Component Ordering number Note

GSDML file for RF180C The files - GSDML-V1_0-SIEMENS-RF180C.xml - GSDML-RF180C_Pictogramm.bmp are contained in this application as a download. They are also contained • on the CD:

RFID SYSTEMS SOFTWARE & DOCUMENTATION ON CD, FB/FC FOR SIMATIC, MOBY PC LIBRARIES, MOBY TOOLS (Order no.: 6GT2080-2AA10, liable to charges) in the directory Daten\PROFI_GSD\RF180C

Application-specific files and projects Table 2-4: Application-specific files and projects

Component Note

The application contains the archive PNIO_RFID.zip (812 KB) for downloading. The archive contains the following folders/files: • GSD_RF180C (28 kB)

This folder contains the GSD file and the respective icon of the interface module RF180C.

• PNIO_RFID_C_Source (652 kB) This folder contains all source data required to modify or expand the application PNIO_RFID.EXE.

• S7Proj (5.34 MB) This folder contains the project files for the hardware configuration which you can open and edit with NCM PC or STEP7 HWConfig.

• PNIO_RFID.EXE (44 kB) This is the compiled application which you start with a double-click.

• SendTel.TXT and SendTel2.TXT (1 kB each) This text file contains the commands which are triggered with the ten buttons Tel.1 to Tel.10. In these text files you can edit the commands for each channel separately.

3 Function mechanisms of this application

3.1 Core functionality of the application PNIO_RFID.EXE


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

3 Function mechanisms of this application To build a solution for this automation task, a software application was developed, to control a RFID system with a pc.

3.1 Core functionality of the application PNIO_RFID.EXE

The core functionality of the application PNIO_RFID.EXE consists in … • addressing the used SLG with regards to the hardware configuration. • Triggering the communication module (ASM) to control the SLG for write/read

operations at the mobile data storage units. • visualizing the telegrams between software application and ASM of command

codes and acknowledgements with write/read data. • creating a log file for telegram traffic.

3.2 User interface of the application PNIO_RFID.EXE Figure 3-1: User interface of PNIO_RFID.EXE

The user interface of the application PNIO_RFID.EXE provides the following controls:

Configuration of the hardware

Command codes

System information

Visualization of

telegram traffic

Telegram informations

Controlling the software


3.2 User interface of the application PNIO_RFID.EXE


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Table 3-1: Elements of the user interface of PNIO_RFID.EXE

Element Explanation

Software Control PNIO START With this button you configurate the software

application and start the communication to the RFID system. When the communication between the software and the RFID system is active, the button label changes to “RELOAD”. By pressing the button again, you reload a changed configuration or restart the communication to the RFID system.

EXIT This button terminates the application. Hardware configuration Controller Slot Index (slot number) of the virtual module IE General

in HW Config. (configuration example: Controller Slot = 1)

Address Start address of the RF 180C. The address must be identical with the I/Q addresses in the Addresses tab in the Object Properties of Slot 1 (connecting two readers) of the PNIO device RF 180C in HW Config. (in the configuration example: Address = 512)

Channel 1 / Channel 2 Channel assigned by the SLG. Controlling only one SLG by the application at the same time is possible. For each channel there is a independent configuration file (SendTel.TXT and SendTel2.TXT) to define SLG specific telegrams.

MDS Shows the number of transponders located in the write/read area of the SLG, if supported by the SLG.

Command codes Tel.1 … Tel.10 With these buttons you can send ten user definable

commands to the ASM. The commands are edited in the text files SendTel.TXT or SendTel2.TXT separately for each channel.


3.3 Editing the ASM commands


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Element Explanation

Read 8k With this button you can read 8 kByte of data from the RFID Tag using a chained command code.

Write 8k With this button you can write 8 kByte of data to the RFID Tag using a chained command code.

Init/Re/Wri/Re With this button you activate chained commands for initialization, reading data, writing new data and reading the written data again.

Read/Write 8k With this button you activate a chained command for reading and writing 8 kByte of data.

System information / Visualization of telegram traffic Info: Displays possible information on program

processing and outputs errors which may occur during processing.

Exchange data Hex: Telegram traffic log. If the parameter Echo On/Off is not checked only the acknowledgements are logged.

Telegram information Send Tel. Counts the sent telegrams Read Tel. Counts the received telegrams. Reset Resets the telegram counter and deletes the

telegrams in the output window Exchange data Hex.

Log File At a Logfile rfid.log of the telegram traffic is created with time stamp for each telegram. The log file is saved to the directory which contains the executable file PNIO_RFID.EXE.

ECHO On/Off At the telegrams sent to the ASM are also logged in the Exchange data Hex window and the log file.

3.3 Editing the ASM commands The Buttons Tel.1 to Tel.10 can be assigned with ten user definable ASM commands. The commands and the button labels must be written to a text file. There is a separated text file for each channel of the ASM.

• Channel 1: Write the ASM commands to text file SendTel.TXT.

• Channel 2: Write the ASM commands to text file SendTel2.TXT. If this file does not exist the text file of channel 1 (SendTel.TXT) will be used.

The text files SendTel.TXT and SendTel2.TXT of this application example refer to the commands of the RF300 system. You could use these files as a template for your own application.

3.3.1 Structure of the ASM command text file

There is a separated text file for each channel of the ASM, which is based on the following structure:


3.3 Editing the ASM commands


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

• Identifier of the command, which is used as button label of the software application.

• Command telegram in Hex format, separated from Identifier by colon.

Note Between identifier and command string no blanks are allowed. Otherwise it is not possible to import the command string into the application.

Between the bytes of the command string there must be exactly one blank to separate the hexadecimal values.

The first ten lines represent the command telegrams of the buttons Tel.1 to Tel.10 of the application. The following lines could be used as telegram storage and will not be interpreted in the application. Figure 3-2: Structure of the text file SendTel.TXT

3.3.2 Activating the ASM command telegrams

By checking a channel and pressing the button PNIO_START respectively RELOAD the command telegrams of the text file SendTel.TXT or SendTel2.TXT are activated. If the command telegrams of the text file are active, the buttons of the software application will be labeled with the identifiers of the command telegrams in the text file.

The first ten lines represent the command telegrams of button Tel.1 to Tel.10 of the application.

The following lines are used as command storage.


3.4 Structure of the ASM commands


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Figure 3-3: Labeling of the software buttons by activating the command telegrams

Note To activate changes of the command telegrams in the text files SendTel.TXT respectively SendTel2.TXT, you have to press the button RELOAD to become the changes operative.


The commands for the connection module are also documented in • Chapter B.4 “Commands and acknowledgement telegrams” of the function

manual “SIMATIC Sensors - RFID systems – FB 45” (/5/) and in

• Chapter B.3 ”MOBY I call-compatible (version 2)” of the programming instruction ”MOBY C-library MOBY API” (/6/).

Using the example of the ASM commands from the SendTel.TXT text file, the telegram structure and the meaning of the individual bytes with regards to an RF300 system2 is explained below This is meant to facilitate comprehension of the general description in the programming instruction mentioned above. Following each command the structure of the acknowledgement telegram is given in the respective table. These must be considered as an example and may deviate from those of your configuration or from the history of the operation sequence respectively.

Reset ASM (Button Init_RF300) ASM is reset. The active command is cancelled.

2 Components from Table 2-2




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Table 3-2: Structure of RESET command

Reset (ResetT MOBY U/D, RF300)

0A Telegram length = 10 bytes 00 Command code RESET = 00 00 Always 00 00 Not relevant for MOBY D and RF 300

25

= 0 0 1 0 0 1 0 1 2

0 0 1 = no MDS controller; presence control via FW (default) 0 1 0 1 = MOBY U/D or RF300 – without Multitag

02 = 0 0 0 0 0 0 1 0 2

1 = Reset ERR-LED at SLG 00 Not to be used for RF300 00 For RESET always 00 01 For RESET always 01 00

Not to be used for RF300 00

Acknowledgement for Reset (Read MDS))

05 Telegram length = 5 bytes 00 For RESET always 00 00 Status byte: Acknowledgement without error (see page 20) 31 Firmware version in ASM [MSB] 31 Firmware version in ASM [LSB] 00 Not assigned (reserve)

Read data from MDS (Read button) Table 3-3: Structure of Read command

Read (Read MDS))

05 Telegram length = 5 bytes 02 Command code READ 00 Always 00 00 Address in MDS (from where it is read) [MSB] 00 Address in MDS (from where it is read) [LSB] 04 Number of bytes to be read

Acknowledgement for Read (Read MDS)

09 Telegram length = 9 bytes 02 Command code READ 00 Status byte: Acknowledgement without error (see page 20) 00 Address in MDS (from where it was read) [MSB] 00 Address in MDS (from where it was read) [LSB] 04 Number of read bytes 12 1. Data byte




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Read (Read MDS))

34 2. Data byte 56 2. Data byte 78 2. Data byte

Write data to MDS (Write button) Table 3-4: Structure of write command

Write (Write MDS)

09 Telegram length = 9 bytes 01 Command code WRITE 00 Always 00 00 Address in MDS (from where it is written) [MSB] 00 Address in MDS (from where it is written) [LSB] 04 Number of bytes to be written = 4 12 1. Data byte 34 2. Data byte 56 2. Data byte 78 2. Data byte

Acknowledgement for write (Write MDS)

02 Telegram length = 2 bytes 01 Command code WRITE 00 Status byte: Acknowledgement without error (see page 20);

Command repeat (buttons Repeat-on, Repeat-off) Using the REPEAT command automatically sends the last command (which is saved in the ASM) to the SLG again, as soon as the MDS in the SLG read field has left that area and another MDS has been recognized by the SLG. Table 3-5: Structure of Repeat command

Repeat (repeat last command)

03 Telegram length = 3 bytes 0D Command code REPEAT 00 Always 00

00 / 01 Switch on / off command repeat

Acknowledgement for repeat (repeat last command)

02 Telegram length = 2 bytes 0D Command code REPEAT 00 Status byte: Acknowledgement without error (see page 20)




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Note To verify this command you need at least two MDS. The follow up MDS is only read if he has a different UID (unique identifier) than the previous one.

Pleas note, that the command repetition is not available for all RFID systems (not available e.g. for MOBY D SLG D11S / SLG D12S).

Switch on/off antenna (buttons Ant-on, Ant-off) This command can be used to switch on/off the antenna field at the SLG. Table 3-6: Structure of command Antenna on/off

Ant-on/off (switch on/off SLG antenna)

03 Telegram length = 3 bytes 0A Command code Switch on/off antenna 00 Always 00

01 / 02 Switch on/off antenna

Acknowledgement Ant-on/off (switch on/off SLG antenna)

02 Telegram length = 2 bytes 0A Command code Switch on/off antenna 00 Status byte: Acknowledgement without error (see page 20)

Request SLG status (buttons SLG-Stat01, SLG-Stat06) As a result the response telegram returns the diagnostic data of the selected SLG. This command tests whether an SLG is connected at the ASM, functioning and ready for operation. For MOBY U various and additional diagnostic data can be fetched from the SLG using the different modes of this command. Table 3-7: Structure of Request SLG status command

SLG-Stat0x (Request SLG status)

06 Telegram length = 6 bytes 04 Command code SLG status 00 Always 00

01 / 06 Mode: SLG-Stat01 or SLG-Stat06 There are 6 modes. With these modes various and additional diagnostic data can be fetched from the SLG. Depending on the selected mode, the acknowledgement will be different.

00 Always 00 00

00

Acknowledgement for SLG-Stat01 (Request SLG status)

1B Telegram length = 27 bytes 04 Command code SLG status 00 Status byte: Acknowledgement without error (see page 20) 01 Mode: SLG-Stat01




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

SLG-Stat0x (Request SLG status)

… SLG status (length: 24 bytes) You will find a description of the SLG status in chapter B 3.2.2.2 “SLG-STATUS Acknowledgment (SLG Status)”of the programming instruction “MOBY – C-library MOBY API” (/6/).

Acknowledgement for SLG-Stat06 (Request SLG status)

1B Telegram length = 27 bytes 04 Command code SLG status 00 Status byte: Acknowledgement without error (see page 20) 06 Mode: SLG-Stat06 … SLG diagnostic status (length: 24 bytes)

You will find a description of the SLG diagnostic data in chapter 6.7 “UDTs of FB 45/ FC 45” of the Function Manual “SIMATIC Sensors - RFID systems – FB 45” (/5/)


3.5 Status byte in acknowledgement telegram


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Request MDS status With the acknowledgement the actual status and the properties of the MDS are sent back. Table 3-8: MDS status

MDS-Stat02 (Request MDS status)

05 Telegram length = 5 bytes 0B Command code MDS status 00 Always 00

02 Mode 02: Modes 01 and 02 say that the MDS status refers to an RF300 system. Both modes deliver different status data. A third mode (00) is for MOBY U.

00 Current date: week, 01H to 34H corresponds to 1st to 52nd week 00 Current date: Year, 01H corresponds to 2001 etc.

Acknowledgment for MDS-Stat02 (Request MDS status)

12 Telegram length = 18 bytes 0B Command code MDS status 00 Status byte: Acknowledgement without error (see page 20) 02 Mode 02 00

UID (unique identifier)

00 00 00 55 59 5B FF 01 Relationship between limit value power flux density and current measured value; 00 Error count, passive (errors during idle time); 03 Error count, active (error during communication); 05 Presence count 02 Interface error count for ASM; 00 … 00

Remaining bytes always 00;

The general description of the acknowledgement for requesting the MDS diagnostic data is available in chapter 6.7 “UDTs of FB 45/ FC 45” of the Function Manual “SIMATIC Sensors - RFID systems – FB 45” (/5/). UDT 270 contains the diagnostic data.

3.5 Status byte in acknowledgement telegram

For acknowledgement without error the byte takes the value 00 and the acknowledgements are represented as listed above. In case of an error, an error detection is written in the status byte. Generally an acknowledgement with error is represented as follows:


3.6 Chained commands


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Acknowledgement with error

023 Telegram length = 2 bytes; Cmd. Respective command code Flt. Status byte with error detection

The error detection in the status byte is available in chapter B.6 “Status byte status” of the programming instruction “MOBY – C-library MOBY API” (/6/).


On the user interface below the button for editable commands there are four keys for “chained” commands using fixed command strings.

Note The four keys trigger commands which transfer larger data volumes (8 kBytes).

If you wish to use the chained commands, please ensure that your RFID system or your used transponder support the data volume (Chained commands are not supported by MOBY D SLG D11S / SLG D12S).

What is a chained command? Using the chained commands enables faster processing of large and/or different address areas on the MDS. An SLG normally only contains one MDS command in the memory and processes it. This means, with one command a maximum of 248 bytes (without Multitag) or 244 bytes (with Multitag) can be written or read. A further command can only be transmitted after acknowledging the previous command. For faster reading or writing to more than 248 bytes (without Multitag), 244 bytes (with Multitag) and/or different address spaces, you may send several commands to the SLG in chained form where they will be contained. For processing larger and/or different data areas, various commands (Initialize MDS, Write, Read,…) may also be chained. Chained commands are characterized by bit 6 of the command byte being set to 1. A chained read command would be, for example “05 42 …” as opposed to the non-chained command “05 02 …”. A maximum of 150 commands could be chained. The end of a command chain is marked by its last command being a non-chained command (bit 6 of the command byte is 0).

Read 8K button The button Read 8k will start a sequence of 36 read commands. The first 35 read commands will read 233 bytes. The last read command (No. 36) will read the remaining 37 bytes.

3 If telegram length >2, the data are only partially correct and must be rejected.




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Figure 3-4: Read 8K telegram traffic

-->05 42 00 00 00 E9 -->05 42 00 00 E9 E9

-->05 42 00 1E 09 E9 -->05 42 00 1E F2 E9 -->05 02 00 1F DB 25

......

35 chained read commands per 233 bytes

1 read command per 37 bytes

35 re

spon

ses

per 2

33 b

ytes

use

r dat

a to

the

chai

ned

read

com

man

ds

<--2A 02 00 1F DB 25 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 1F 79 83

1 re

spon

se p

er 3

7 by

tes

user

da

te to

the

last

read

com

man

d

<--EE 42 00 00 00 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8

<--EE 42 00 1E F2 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Write 8K button The button Write 8k will start a sequence of 36 write commands. The first 35 write commands will write 233 bytes to the transponder. The last write command (No. 36) will write the remaining 34 bytes to the transponder. Figure 3-5: Write 8K telegram traffic

-->EE 41 00 00 00 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8

-->EE 41 00 1E F2 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 -->27 01 00 1F DB 22 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 <--02 41 00 <--02 41 00

......

<--02 41 00 <--02 01 00

35 responses to the chained write commands

1 response to the last write command

35 c

hain

ed w

rite

com

man

ds

per 2

33 b

ytes

use

r dat

a

1 w

rite

com

man

d w

ith

34 b

ytes

use

r dat

a




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Read/Write 8K button This chained command combines the functions of Write 8K and Read 8K. The read commands are directly chained to the write commands. The writing will immediately be read out again and they signal a “Verify function”. Figure 3-6: Read/Write 8K telegram traffic




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Button Init/Re/Wri/Re With this button the entire MDS is first initialized with (FF)H by means of chained commands, i.e. all 8 kbytes are preassigned with (FF)H, then the first 233 bytes are read out and these are then overwritten with a given bit pattern. Figure 3-7: Init/Re/Wri/Re telegram traffic

-->06 43 00 FF 00 20 00 -->05 42 00 00 00 E9 -->EE 41 00 00 00 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 -->05 02 00 00 00 E9 <--02 43 00 <--EE 42 00 00 00 E9 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF <--02 41 00 <--EE 02 00 00 00 E9 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8

cmd: initialize MDS with FF

1st cmd: read 233 bytes

cmd:

writ

e 23

3 by

tes

user

dat

a

2nd cmd: read 233 bytes

response to initialisation

resp

onse

to 1

st re

ad c

omm

and

with

233

byt

es u

ser d

ata

response to write command

resp

onse

to 2

nd re

ad c

omm

and

with

233

byt

es u

ser d

ata

pattern for initialisation

MDS size 8kB (=2000H)

4 Installation of hardware and software

4.1 Installing the hardware


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

4 Installation of hardware and software This chapter describes the hardware and software components to be installed and what the procedure is. The descriptions and manuals as well as delivery information included in the delivery of the respective products should be observed in any case.

4.1 Installing the hardware For setup, cabling and operating your RFID system please refer to the appropriate system manual (see /7/, /8/, /9/, /10/). Follow the installation and EMV guidelines that are given there. Perform the installation with no connected voltage for all components. For the hardware setup, proceed as follows:

Table 4-1

No. Workstep Remark

1. Connect the network connection of your PCs with connection PN1/X03 or PN2/X04 of the RF180C module. Detailed information is available in chapter 4 “Connecting“ the RF180C operating instruction /7/.

Since the RF180C supports “Autonegotiation“ and “Autocrossing“ it is of no importance whether you use a 1:1 cable or a crossover cable.

2. Wire the voltage supply of RF180C (7/8“ connector at X01). Detailed information is also available in chapter 4 “Connecting“ the RF180C operating instruction /7/.

The assumed current consumption for the RF180C is max. 500 mA.4

3. Connect the SLG with the RF180C. Which pre-assembled cable you use, or how to assemble the cable yourself, is described in chapter 10 “Connecting cable to Reader/SLG“ of the RF180C operating instruction (/7/).

4. Wire the separate voltage supply of the MOBY D SLGs. (For RF300 and MOBY U the SLG is supplied via the RF180C.)

Regarding current intake of the MOBY D SLG see chapt. 6.2 to 6.9 of the respective system manual (/9/).

5. Switch on the power supply.

4.2 Installing the software

Extract the application example After you downloaded PNIO_RFID.zip, extract the archive into a separate directory. The archive content is available in Table 2-4 (page 10).

Install the SIMATIC NET software During installation you follow the instructions of the installation wizzard. Read the readme file beforehand. For the software configuration of the hardware (hardware configuration) of the application example you either need NCM PC or STEP7.

4 If the SLG is supplied via the RF180C (for MOBY D), a maximum power intake of 1 A should be assumed.


4.2 Installing the software


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

If there is no STEP7 software on your PC, NCM PC will be automatically installed as well during the installation of SIMATIC NET. If STEP7 has already been installed, the hardware configuration is performed with HW Config of STEP7. The only difference for you as the user is that you either find an icon for NCM PC ore one for STEP7 on your desktop. Regarding the topics SIMATIC NET, PROFINET and PROFINET IO it is recommended to study the documents /11/, /12/ and /13/.

In stalling the GSD file of the RF180C Table 4-2: Installing the GSD file of the RF180C

No. Workstep Remark

1. Open NCM PC or STEP7 from the desktop of your PC. 2. Open the HW Config with . (It is only possible to open HW Config after creating a STEP7

project. Optionally you have to create a empty STEP7 project) 3. In the Options menu you select the menu

item Install GSD File…. In the Install GSD Files window you select from the directory from the top and with Browse … you navigate to the GSD file of the RFC180.

4. Select the GSD file and close the mask

with Install. The bitmap (BMP) in the directory of the GSD file, which in HW Config represents the PNIO device RF180C, is automatically installed as well, i.e. it is adopted into the project.


4.3 Testing the PROFINET IO system


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved


It is assumed that the previous work steps of this chapter (Installation of hardware and software) have already been performed.

Table 4-3: Testing the PROFINET IO system

No. Workstep

Test via Edit Ethernet Node

1. In the control panel you go to “Set PG/PC Interface”.

Select the access point of the application S7ONLINE (STEP7), the network ISO Ind. Ethernet and the network connection which is connected with your PNIO system.

2. In HW Config you go to PLC>Ethernet>Ethernet Node. Use Browse… to search the PNIO device

RF180C. 192.168.0.100 is the default IP address of the RF180C.5

Test via Command Prompt

3. On Windows level you change to Command Prompt via Start>Execute… by entering “cmd”. 4. Edit: “ping [IP-Adr.RF180C]” and close

with [RETURN]. If the ASM is recognized there will be a positive feedback (picture). If it is not recognized you receive a Request timed out.

5. Should the connection tests not yield any success, please check the configuration of your network card in the PC as well as the PROFINET line

5 If necessary you can also change the IP address of the RF 180C via the Edit Ethernet Node window.




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Note SIMATIC NET sets options of pc firewall on installation. Usually it works fine.

Sometimes firewall does not apply local options (e.g. Group Policy Management) and blocks the traffic.

In this case SOFTNET PN IO can not open the PROFINET connection to module and it is only possible by disabled firewall.

Please note: your computer is compromised by disabled firewall.

5 Software configuration of the hardware configuration

5.1 Generating the hardware configuration in HW Config


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

5 Software configuration of the hardware configuration The complete hardware configuration has already been stored in the application example. You can either use these or generate your own configuration. In the first case steps 1a, 2, 4, 5, 7, 8 and 9 of Table 5-1 apply to you.


Note In the following, only those property windows, tabs and submenus are mentioned which must be edited for the example on hand. In all other masks the default values can generally be kept.

Table 5-1: Generating the hardware configuration in HW Config

No. Workstep

1a.

Creating a new configuration Start STEP7 (SIMATIC Manager) or NCM PC respectively and create a new project with . In the right hand example the project named s7proj is created and filed in D:\PNIO_RFID.

1b.

Open example project Start STEP7 (SIMATIC Manager) or NCM PC respectively and open the example project s7proj with , which in the right hand screenshot is filed in D:\PNIO_RFID. If necessary, use the Browse… button to search the project.

or




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

No. Workstep

2.

Insert PC station (only if the project was generated new) Add a new PC station via Insert > Station > SIMATIC PC Station. If necessary change its name (in the example progam: PC_Station).

3. Call HW Config Your project now looks like the one on the right. Open the HW Config by double-clicking .

4. “Plugging” PROFINET IO Controller

Enter a dummy IE General ( SW V6.2 SP1) for the PROFINET IO Controller in slot 1. You will find it in the catalog at SIMATIC PC Station / CP Industrial Ethernet.

5. “Plugging” the application Enter the type of the application in slot 2. To do this you select the application SW V6.3 from the catalog at SIMATIC PC Station / User Application / Application.




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

No. Workstep

6. Configuring IE General • General tab

Open the network properties and make the settings according to the following screenshot or adopt the default settings.

The system only assigns free IP addresses. If the above one has already been assigned otherwise, the next free address, e.g. 192.168.0.2, will be preset. However, you may also enter a different IP address yourself.

• PROFINET tab Ensure the following settings:

For Assigned Application the name of the application of slot 2 must be selected (in this example also Application).

7. Configuring Application The application example on hand does not require any further configuration of this “plugin card“.

8. After “plugin card 1“ has been defined as PROFINET IO Controller, HW Config creates the Profinet-IO-System.




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

No. Workstep

9. Creating RF180C as PNIO device In PROFINET IO / Ident Systems / SIMATIC RFID you draw the interface module RF180C to the PNIO-IO-System.

From a software point of view the ASM consists of the PROFINET connection block and both virtual slots RF180C and connecting two readers.

10. Configuring RF180C – PROFINET connection block Double-click the RF180C icon. • General tab

The device-specific device name (here RF180C) is automatically assigned. However, it could be changed by you. Please take into account the DNS name conventions if necessary (see online help). The device number (here 1) is not relevant for the application on hand.

• General tab – Ethernet Interface RF180C window The Ethernet… button takes you to the appropriate window. There you enter the IP address of your PNIO device. In the example application it is 192.168.0.100.


5.2 Generating the PC configuration with the station manager


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

No. Workstep

11. Configuring RF180C – “Slot 0” At selected RF180C you double-click the top line in the table (Slot 0, Module RF180C). • Parameters tab

Adjust the baud rate to the connected RFID system. The remaining parameter can keep their default values according to the picture.

12. Configuring RF180C – “Slot 1”

At selected RF180C you double-click the second line down from the top in the table (Slot 1, Module connecting two readers). • Addresses tab

In the Start input fields always the next free addresses are entered, which are available for the configured module. These addresses can be kept.

13. Save & Compile

Save and compile the configuration with .


Editing the Station Component Editor The Station Component Editor gives you access to the component management of the station manager in the PC station. The Station Component Editor is the user interface of the station manager. In the terminology used here, components are... • modules and • applications …in the PC station which are involved in communication tasks. You require the Station Component Configurator for the initial configuration of your PC station. This application assumes, that no PC station has yet been configured on your PC.




Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Table 5-2: Editing the Station Component Editor

No. Workstep

1. Open the Station Configuration Editor by double-clicking the icon in the toolbar. It is located on the Windows desktop in the info section of the task bar.

The Component Station Configurator is always available and started on the PC on which you have installed the SIMATIC NET CD.

2. Press the Station Name… button and

enter the name you have specified for the PC station in HW Config (PC_Station).

3. Click the first “slot” (Index 1) and press

the Add.. button to enter the component IE General from the Type list box. In the Parameter assig. list box you select the used interface.

When exiting the input mask with OK the component is adopted in the first slot of the station manager.

Important! The slot (Index) must be the same as that in HW Config.

4. Click the second “slot” (Index 2) and

press the Add.. button to enter the component Application from the Type list box.

When exiting the input mask with OK the component is adopted in the second slot of the station manager.

Important! The slot (Index) must be the same as that in HW Config.

5. You can now close the input window of

the station component configurator with OK.




V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

Load the configuration data into the PC station You can now load the configuration created in HW Config into the PC station; proceed as follows:

Table 5-3: Load the configuration data into the PC station

No. Workstep

1. In the Windows control panel you go to “Set PG/PC Interface”.

Switch the interface to PC internal (local)

2. Go to HW Config and load the

configuration to the PC station with . In the Station Component Configurator the status of both entered components is displayed as illustrated overleaf.

6 Operating the Application

6.1 First operating steps


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

6 Operating the Application If you have successfully performed all steps from chapter 4 to 6, you are ready to work with the application example.

6.1 First operating steps Table 6-1: Operating the Application

No. Workstep

1. Call the application. Double-click the file

2.

In the Configuration input field you enter the following parameter:

• Controller Slot: slot number of IE General in HW Config.

• Address: IO addresses of the RF180C (= address configured in Table 5-1 (page 30))

• Channel: Select the channel (1, 2) via which your SLG is connected to the RF180C.

3. Start the application with

As a reaction you receive a message in the info field which states that the RF180C has not yet received a RESET command (code 02 00 0F). The designation of the start button changes to RELOAD.

4. Reset the RF180C with

PNIO_RFID.exe transmits the first command from the text file sendtel.txt to the ASM. If you have set a checkmark at ECHO On/Off, you will see the command telegram next and the response in the Exchange data Hex field.

5. According to point 4 of this table you can now trigger all ten of the commands defined in sendtel.txt as well as trigger the four chained commands and control the reactions.

6 Operating the Application

6.2 Additional operating information


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

6.2 Additional operating information

Logfile As soon as you checkmark Log File, a protocol file rfid.log will be created in the directory which contains PNIO_RFID.exe. It records all commands (only for ECHO On) and acknowledgements with data and time. Figure 6-1: Logfile

The file can be read as soon as you switch off the Log_Function (uncheck Log File) or terminate PNIO_RFID.exe. When switching on the log function (checkmark Log File) an already existing rfid.log is emptied.

Channel selection While the application is running, it may be switched between both channels of the RF180C without any problems. Depending on the selected channel, the right file of the command telegrams SendTel.TXT respectively SendTel2.TXT will be activated.

Editing SendTel.txt or SendTel2.TXT The commands specified in the text file SendTel.TXT or SendTel2.TXT are adopted during the start of the application (with PNIO START or RELOAD). While the application is running the text file may be changed and saved, however, the changes are not taken into account immediately. You have to use the button RELOAD to activate the changed telegrams.

7 Glossary


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

7 Glossary Table 7-1: Terms and abbreviations

Term Explanation

ASM Interface Module FB STEP 7 function block MDS Mobile Data Memory MLFB Machine-readable product designation. This is the SIEMENS order

number for the respective product. Multitag Ability/mode, to handle several transponders in the detection field of the

SLG simultaneously. PNIO PROFINET IO RFID Radio Frequency Identification SLG Write/Read Device SmartLabel Smartlabels or SmartTags are ultra-flat transponders, which are attached

to a foil including antenna (inlay). The foil will be laminated between paper layers or glue is added at one side. So it is easily possible to mark the transponders or to use the transponders as labels.

Tag Label, badge, name plate; in the context of RFID it is referred to as the mobile data carrier. In the WinCCflexible context “tags“ are the variables behind the display and control objects. The number of required (power) tags depends on the required license.

Transponder A transponder is a – mostly wireless – communication, display or control device, which records incoming signals and automatically responds to them. The term Transponder is a composite of the terms Transmitter and Responder. The term refers to the mobile data carrier.

UDT User defined data type; (data block) in STEP 7; UID Unique identifier of an MDS;

Note In the context of RFID and this application, the terms MDS, Tag and Transponder are synonymous and refer to a mobile data carrier, irrespective of its design and physical shape.

8 Literature


V1.1, Item-ID: 26608353

Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

8 Literature 8.1 References on hardware and software of this

application This list includes documents/entries referred to in this application.

Table 8-1: Literature for this application:

Title

/1/ Siemens A&D Customer Support http://www.ad.siemens.de/support

/2/ Reference to this entry http://support.automation.siemens.com/WW/view/en/26608353

/3/ Application example Identifying and Controlling material with MOBY D and SIMATIC S7-300 http://support.automation.siemens.com/WW/view/en/24621867

/4/ Application example: Connecting SIMATIC RF660R read / write device to SIMATIC S7 315-2PN/DP http://support.automation.siemens.com/WW/view/en/23626344

/5/ RFID Sytems, FB 45, Function Manual http://support.automation.siemens.com/WW/view/en/21738808

/6/ MOBY – C Library MOBY API (programming instruction) http://support.automation.siemens.com/WW/view/en/12412086

/7/ SIMATIC Sensors - RFID Systems – Communication Module RF180C, Operating Instruction http://support.automation.siemens.com/WW/view/en/24692269

/8/ SIMATIC RF 300, System Manual http://support.automation.siemens.com/WW/view/en/21738946

/9/ MOBY D System Manual http://support.automation.siemens.com/WW/view/en/13628689

/10/ MOBY U, Manual http://support.automation.siemens.com/WW/view/en/12443728

/11/ PROFINET System Description http://support.automation.siemens.com/WW/view/en/19292127

/12/ SIMATIC NET Commissioning PC Stations - Manual / Quick Start http://support.automation.siemens.com/WW/view/en/13542666

/13/ From PROFIBUS DP to PROFINET IO http://support.automation.siemens.com/WW/view/en/19289930

http://www.ad.siemens.de/support













9 History


Cop

yrig

ht

Sie

men

s AG

201

3 Al

l rig

hts

rese

rved

8.2 Further Literature

This list is by no means exhaustive and only gives a selection of appropriate sources. Table 8-2: Further Literature

Title

/14/ Pigan, Raimond; Metter, Mark

Automating with PROFINET

Publicis Corporate Publishing ISBN-10: 3-89578-256-4 ISBN-13: 978-3-89578-256-5

Book presentation: http://books.publicis-erlangen.de/en/produkte/techinhan /auto/index.cfm?bookid=5827

/15/ Klaus Finkenzeller

RFID Manual

Hanser Verlag ISBN-10: 3-446-40398-1 ISBN-13: 978-3-446-40398-7

Book presentation: http://www.hanser.de/buch.asp?isbn=978-3-446-40398-7&area=Computer

/16/ Christian Kern

Application of the RFID systems

Springer Verlag ISBN: 978-3-540-44477-0

Book presentation: http://www.springer.com/dal/home/generic/search/results?SGWID=1-40109-22-173708006-0

9 History Table 9-1 History

Version Date Modification

V 1.0 29.02.2008 First version V 1.1 13.06.2013 Tests with SIMATIC NET 8.2

http://books.publicis-erlangen.de/en/produkte/techinhan/auto/index.cfm?bookid=5827

http://books.publicis-erlangen.de/en/produkte/techinhan/auto/index.cfm?bookid=5827

http://www.hanser.de/buch.asp?isbn=978-3-446-40398-7&area=Computer

http://www.springer.com/dal/home/generic/search/results?SGWID=1-40109-22-173708006-0

http://www.springer.com/dal/home/generic/search/results?SGWID=1-40109-22-173708006-0

rf 180c application june 2013 - siemensit is the objective of this application to show you in a...

Documents