Introduction
I often hear competitors say, ‘You keep changing things, look at all the different versions of PROFINET.’ Yes, we release new versions of the PROFINET specification and tester annually. This is a normal process when new requirements arise, new technological possibilities emerge, and feedback for improvements is received.
We compile this feedback and, in close coordination with customers, technology manufacturers, and experts, create new specification and tester versions. This approach is not unusual; standardization organizations like IEEE and IEC, as well as device manufacturers and system developers, have version management to introduce new features.
In summary: PROFINET is a dynamic standard driven by an active community. I would be more concerned if our customers or community ran out of ideas for further development.
By the way: of course, our advancements are compatible. I know of setups with the latest PROFINET controllers and very old PROFINET devices (evident from their somewhat aged housings): it works! PROFINET communication does not age – unlike my face and body. 😉
New Versions of the PROFINET Specification
In April, the latest version of the PROFINET specification was released, featuring significant extensions for Security Class 2/3. These were developed in close coordination between the PROFINET-IO Working Group and the Security Working Group. While earlier versions primarily focused on hardware-related details, the emphasis is now on security integration in systems and engineering. Years ago, the specifications for Security Class 1 were introduced, and now we see the first concrete implementations in devices and engineering systems.
PI has also contributed to this: with the infrastructure for signing GSD files and the certification of Security Class 1. Such an important and extensive topic as security cannot be defined all at once –the elephant must be eaten in pieces.
As usual, the new PROFINET tester version is now available. In addition to tests for Security Class 1, PROFINET controller tests are now automated. This provides both a required functionality extension and a simplification of the testing process. Another important extension is the testing of virtual PLCs. As mentioned above, we expand our (test) specifications in close coordination with emerging new technologies and are once again leading the way. The tester is increasingly integrated into the regular testing cycle at manufacturers and not just used for official certification tests. And let’s not forget: the tester also includes a new GSD checker.
The many active members in the respective working groups bring a lot of commitment, and PI invests a significant budget to set the quality benchmark here. Many thanks to those involved at this point!
The best result and praise is when we have satisfied users who rely on interoperable devices, and developers who find clear testing environments. (Note: praise usually manifests itself in the form of silence, it just works.)
Outlook and Summary
Of course, we also have a well-filled backlog list for our further development. As usual, there is a prioritization process – even PI does not have unlimited resources – and then there will be an upcoming version next year. To specifically support new topics, there are now also mid-year innovation and test bundles outside the annual major development cycle. Test partners are always welcome.
The PI community continuously develops PROFINET in close coordination with users and manufacturers and ensures the highest quality through professional testing environments. This is the foundation of PROFINET’s success, now and in the future.
Xaver Schmidt