How to Configure RevPi Gate for PROFINET

Setting Station Name

Since names are easier to handle than complex IP addresses in most cases, you can assign a station name to the gateway component.

You set the station name using the software of your PROFINET controller.

According to the definition RFC 5890, attention must be paid to the name assignment rules in this regard:

• Data should be specified in the Octet string type
• Restriction to a total of 240 characters (letters “a” to “z”, numbers “0” to “9”, hyphen or dot)
• A name element of the device name must be separated with a dot and can have a maximum of 63 characters.
• No special characters such as umlauts, brackets, underscore, blank etc.
• The hyphen is the only special character allowed.
• The device name must not begin or end with a dot.
• The device name must not begin with numbers.
• The device name must not have the form n.n.n.n ( n = 0…999 ).
• The device name must not begin with the character string “port-xyz-” ( x,y,z = 0…9 ).
• The device name may only begin with “xn-” if the original character string contains values other than “0” to “9” and “a” to “z”.
• The field “NameOfStationValue” must not end with 0.

Examples of valid names:

“device -1.machine- 1.plant- 1.vendor” “mühle1.ölmühle1.plant.com” is coded as ” xn–mhle1-kva.xn–lmhle1 -vxa4c.plant.com”

Exchanging Data cyclically

To configure the gateway component, you have to perform the appropriate settings with the configuration software of your PROFINET -Controller.

The gateway component is equipped with virtual slots (installation positions). PROFINET controllers use these slots to address selected process data. Each slot contains one module. You can assign process data to these modules that are to be exchanged.

Info!The gateway component supports only a submodule with data per module.

In the following tables you will find a detailed overview of all modules.
DAP (Device Acess Point)

Submodule for Record Access

Submodule that represents the entire Profinet Device

Submodule that represents Port 1

Submodule that represents Port 2

Input 16 Byte

Input 32 Byte 

Input 64 Byte

Output 16 Byte

Output 32 Byte

Output 64 Byte

Exchanging Data acyclically

The gateway component supports records. This access type is useful for all events that do not have to be repeated regularly (e.g. sending parameter data in the start-up phase).

Another benefit of records is due to the fact that you can write continuously ascending areas at once.

Example:. Index 0x1005 writes byte 10 to byte 19 with 10 bytes of data in the output process mapping.

You can use all 512 bytes of the input and output area to read or write records.

Addressing

All records are addressed via API 0, Slot 0, Subslot 1. The data is transferred in Little Endian format. In the case of Big-Endian format, the higher-value bytes are first transmitted and stored at the memory locations with the lowest addresses.

2 bytes are always addressed per index:

Offset 0 + Offset 1 → Record 0

Offset 510 + Offset 511 → Record 255 (0x00ff)

Index 0x0000 – 0x00ff contains the input data sent from the partner gateway component.

Index 0x1000 – 0x10ff contains the output data sent to the partner gateway component.

State of the Partner Gateway

You can read information on the state of the partner gateway component via API 0, Slot 0, Subslot 1, Index 0x2000: