A frequently expressed concern of PROFINET users is bandwidth. Is there enough? How can I be sure? This is a legitimate concern, prompting a reminder that there’s never a substitute for doing the engineering. Architect the system with bandwidth usage in mind.

For most folks jumping in to a PROFINET development project, there’s one only goal that they have in mind: exchange cyclic real-time data with a PLC. That’s the same task that every fieldbus in history has been designed around, and it comes with well-known drawbacks: devices that can only exchange data cyclically force developers to pack all sorts of data in to the real-time channel that don’t belong there.

Communication issues are often encountered on PROFIBUS networks, due to various factors such as reflections or electromagnetic interference (EMI). Malfunctions caused by these problems can easily be avoided if the main causes can be identified. Here is how to avoid them.

A previous edition of PROFINEWS carried a PROFINET quiz drawn from new and old questions. This month there are all new questions! Challenge your PROFINET knowledge today...

Did you know that there’s a new IO-Link Design Guideline? A new Design Guideline from the IO-Link Community offers all interested users support during the planning of automation systems with IO-Link devices. In an action-oriented approach, the tasks required during planning are described step by step.

Did you know that IO-Link can be integrated into any fieldbus system? One of the most important features of IO-Link is its fieldbus neutrality. It allows the IO-Link functionality to be connected to nearly any fieldbus. Either the standardized mappings in fieldbuses, e.g. for PROFIBUS, PROFINET, EtherCat, and Sercos, or manufacturer-specific mappings for EtherNet/IP, CANopen, Modbus, CC-Link, and AS-Interface can be used for this.

Should you use a managed switch or an unmanaged switch with PROFINET? YES! Yes, you should use either a managed or an unmanaged Ethernet switch with PROFINET.