PROFINET Addressing
In PROFINET, the bus coupler is a modular field device. In the PROFINET environment, the system is constructed as a combination of modules and sub-modules defined in a General Station Description (GSD) file, and are assigned to the slots and sub-slots of the system.
PROFINET communications addresses modular field devices using slot and sub-slot addressing. It divides the slot addressing space into two regions, one for avatars and one for devices. Slot 0 is used for the bus coupler and System Avatar. Within each slot, sub-slot values are used to access the different datasets.
The TeSys island PROFINET interface represents the system as one module with multiple slots and sub-slots as follows:
-
One Device Access Point (DAP), the bus coupler-This DAP is located in slot 0.
-
A set of slots representing the avatars-Sub-slots for datasets associated with each avatar.
-
A set of slots representing the devices-Sub-slots for the datasets associated with each device
NOTE: Empty slots also should be filled with empty slot.
After importing the General Station Description Markup Language (GSDML) file into your programming environment, add a TeSys island instance from the hardware catalog. The TeSys island is created with a System Avatar but no other modules.
Follow the instructions for your programming environment to populate the empty slots with avatars and devices using the information in PROFINET Slot Ranges below. For example:
-
In CoDeSys v3.5, right click on an empty slot and choose Plug Device.
-
Select the appropriate avatar or device from the catalog.
-
When the island is fully defined, start creating tags for the data you need to access for each avatar.
TeSys island applies the following slot ranges for physical and virtual modularity:
PROFINET Slot Ranges
| Item | Slot | Comment |
|---|---|---|
|
Bus Coupler / System Avatar |
0 | — |
|
Avatars |
1–21 |
Device, Load, and Application avatars |
|
Bus Devices |
101–121 |
Digital I/O Module (DIOM) Analog I/O Module (AIOM) Starters SIL* Starters Power Interface Module (PIM) SIL Interface Module (SIM) Voltage Interface Module (VIM) |
| Not Applicable | 22–100, 122–254 |
These slots are not used with TeSys island. |
Example of Avatar Numbering
|
Order of Avatar in Digital Tool |
PROFINET Avatar Slot |
Description |
Physical Order in island |
||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |||
| 1 | 0 |
System |
BC |
— |
— |
VIM |
— |
— |
SIM |
— |
— |
| 2 | 1 |
AIOM |
— |
AIOM |
— |
— |
— |
— |
— |
— |
— |
| 3 | 2 |
Motor Two Directions – SIL Stop, W. Cat 1/2* |
— |
— |
— |
— |
SIL Starter |
SIL Starter |
— |
— |
— |
| 4 | 3 |
Motor One Direction |
— |
— |
— |
— |
— |
— |
— |
Starter |
— |
| 5 | 4 |
Power Interface with I/O (Control) |
— |
— |
DIOM |
— |
— |
— |
— |
— |
PIM |
Example of PROFINET Physical Device Slots
| Physical Order in island | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| PROFINET Physical Device Slot | 0 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 |
A typical PROFINET IO-Controller is a PLC. It provides and consumes I/O (cyclic) data as well as configuration (acyclic) data and is comparable to a PROFIBUS Class 1 client. A PROFINET IO-Supervisor is used for diagnostic purposes and can be a programming device, personal computer, or an HMI device. The IO-Supervisor is comparable to a PROFIBUS Class 2 client.
Write arbitration between multiple clients is specified in PROFINET standard. The IO-Controller (the main client) has the exclusive write access by default. Other clients (by default only) have read access. If not restricted, the other clients (that is, the IO-Supervisor) can request write access on a per module (per avatar) basis. If the IO-Controller allows write access, the write access is transferred to the requesting client until it is released again.
The TeSys island limits the IO-Supervisor application relation (AR) to an IO-Supervisor Device Access AR. This means that only acyclic parameters can be accessed from the IO-Supervisor. Access to the cyclic data is not possible. However, it is possible to view the state of the cyclic process data values in an additional acyclic parameter (for read-only access).