Mail
All-embracing Plugfest of the PROFINET community
 
20.06.2016
Germany
Around 80 participants attended this year's PI Plugfest.

Around 80 participants attended this year's PI Plugfest.

Open and straightforward testing and exchange of experience are the main highlights of the Plugfest events held by PI (PROFIBUS & PROFINET International). The two-day Plugfest of the PROFINET community at the beginning of June proved to be no different. This focus of this year's event was on PROFIdrive and PROFIsafe based on PROFINET communication.

The Plugfest event took place this time at the Siemens Erlangen facility. Most notably, this site produces motion control and drive technology and is thus a suitable environment for tackling all related developer issues. Around 80 participants brought their newly developed technology, thus enabling many interesting configuration variations to be tested. During the event, basic technology, devices, controllers, systems, engineering tools, and diagnostic tools were tested both with pilot devices as well as with devices just introduced on the market.

Testing was carried out in a proven fashion in various systems ranging from small groups up to larger shared networks. Participants particularly appreciated the open exchange of experience among specification experts, device developers, and certification bodies.

"It is simply very helpful and above all effective to test the many different integration possibilities in direct contact with my developer colleagues. Of course, we also actively participate in specification and test definition work, but the additional experience at Plugfest helps us to optimize our specific implementations. There are always new devices and advances that give us new ideas," said Benjamin Meyer, Group Leader for PROFINET protocol stack development at Hilscher.

The event also included tests and issues related to certification, both for PROFINET communication and for the profile testers of PROFIsafe and PROFIdrive. The findings from the Plugfest not only flow into the respective device implementations but are also the basis for further development of documentation and certification.

By: Weber