Did you know that new options for diagnostics are available?
IO-Link now makes it possible to transfer larger data volumes.
Articles with category TECH TIPS
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.
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.
In the early days of Ethernet, collisions on the network prevented its use in deterministic industrial applications. If two stations tried to transmit at the same time, a collision would result. The collision was detected and each station “backed off” a random time and tried again. This approach was fine for web browsing and email but prevented determinism. The advent of switched Ethernet networks did away will collisions allowing Ethernet to be applied in industrial automation where determinism was a must.