Modules
A module represents a logical or physical function of your device. PROFINET controllers reads the modules to understand the device structure.
What a module represents:
A container for submodules
Required to contain at least one submodule
Shown as a selectable, pluggable component in engineering tools
A functional block such as digital I/O, analog I/O, or configuration/parameter access
A module defines what the device does. Its submodules define how the device exchanges data.
Modular devices with multiple instances of a module dynamically added by the controller are not currently supported.
Device Access Point (DAP)
The Device Access Point (DAP) is a mandatory PROFINET module. It is always present and acts as the entry point for all PROFINET communication.
What the DAP does:
Identifies your device on the PROFINET network
Always occupies slot 0x0000
Is managed by the device firmware and can only be partially modified by the user
Contains the network interface and ports of the PROFINET device
The DAP structure is currently read‑only. It is fixed to comply with the PROFINET specification and to match the capabilities of the Anybus ONE hardware and firmware.
Submodules can currently not be added, removed or reordered.
Module design best practices
To create a clear and maintainable device structure:
Use descriptive module names that clearly reflect their purpose.
Align modules with the physical layout of the device.
Example: One module per I/O card or functional block.
Group related I/O signals within the same module.
Avoid overly granular modules that makes the structure hard to read.
Avoid mixed‑purpose modules that combine unrelated functions.
Keep module patterns consistent across similar device families or variants.