Best Practices for Structuring Virtual Submodules in a Simple PROFINET Device

sbsprofi
Posts: 4
Joined: 28 May 2025, 17:46

Best Practices for Structuring Virtual Submodules in a Simple PROFINET Device

Post

I am currently working on defining the I/O submodules of a Profinet IO device. From what I understand, modules typically correspond to physically pluggable components, while the definition of submodules within a module is generally left to the device manufacturer's discretion.

Source: https://reference.opcfoundation.org/PRO ... docs/4.1.3

With that being said, what are some common paradigms used in separating virtual submodules for a given module? The I/O device I am working on is a very mechanically simple single-port device targeting Conformance Class A. No other modules can be attached to it, so my GSDML will only include a single module with at least one virtual submodule.

Right now, I have defined a single virtual submodule that handles all I/O data. However, I could just as easily split it into multiple virtual submodules based on logical functionality — for example:
  • Spindle RPM Submodule
  • Acoustic Signal Submodule
  • Current State Submodule
  • Status Flags Submodule
Are there any commonly accepted guidelines or best practices for structuring virtual submodules in a case like this? Does breaking them up improve clarity or interoperability from the perspective of the engineering tool or PLC programmer, or can it act as a hinderance if broken up too finely?