Software Requirements
Generally, no additional network support code needs to be written to support the Anybus CompactCom 40 PROFINET IRT IIoT Secure, however due to the nature of the PROFINET networking system certain things must be taken into account:
Up to 32767 ADIs can be represented on PROFINET.
ADI names, types and similar attributes cannot be accessed via PROFINET. They are however represented on the network through the built in web server.
Up to 5 diagnostic instances can be created by the host application. An additional 6th instance may be created in event of a major fault.
For conformance reasons, the host application must implement support for network reset types 00h (Power-on) and 02h (Power-on + Factory Default) in the Application Object (FFh).
PROFINET in itself does not impose any particular timing demands when it comes to acyclic requests (i.e. requests towards instances in the Application Data Object), however it is generally recommended to process and respond to such requests within a reasonable time period (exactly what this means in practice depends on the implementation and the actual installation).
The order in which ADIs are mapped to Process Data is significant and must be replicated in the IO Controller when setting up the network communication (i.e. modules must be set up in the same order, size and direction, as the mapped ADIs). In case of a configuration mismatch, see Configuration Mismatch for more information.
See also ...
Diagnostic Object, Anybus Module Objects
Anybus CompactCom 40 Software Design Guide, Application Data Object (FEh)