Up to TwinCAT Version 3.1 Build 4024
The modules can be attached to the API (Application Profile Interface). Open by right-clicking on Add New Item
The order of the modules in the tree always corresponds to the populated slot, starting at 0.
The DAP (DeviceAccessPoint) is added directly with the device. If, according to GSMDL, this is not plugged into slot 0, empty placeholder modules are inserted before it. The DAP is a special module that comes with device properties from the GSDML. The PDEV properties are attached to it in the form of submodules (interface and port). In addition, the DAP can also contain normal submodules with process and record data. It is always fixed and cannot be deleted.
Each additional module is assigned to a specific API. The information regarding its identity comes from the GSDML. By default this is always the API 0. Alternatively, an API e.g. for the PROFIDRIVE profile or a fieldbus API is also conceivable.
If the modules (described in GSDML) support it, the submodules can be projected below them. The subslots are also simply numbered continuously, starting at 1 (modules at 0). The PDEV submodules (interface and port) are exceptions; these are plugged into a fixed subslot specified via the GSDML.
The current slot or subslot can be checked via the associated object.
