M12 Connector Coding

New automation products hit the market every day and each device requires the correct cable to operate. Even in standard cables sizes, there are a variety of connector types that correspond with different applications.

When choosing a cable, it is essential to choose the correct size, length, number of connectors, pinout, and codes for your application. This post will review cable codes, which signify different capabilities and uses for a cable. Cables that are coded differently will have different specifications and electrical features, corresponding to their intended uses. To distinguish between the different styles of cable, each connector has a different keyway, as shown in Figure 1.  This is to prevent a cable from being used in an incorrect application.

Cable Codes-01

There are a wide variety of cable codings used for different purposes. Below are the five most common M12 cable codes and their uses. They are as follows:

  • A-coded connectors are the most common style of connector. These are used for sensors, actuators, motors, and most other standard devices. A-coded connectors can vary in its number of pins, anywhere between two pins and 12 pins.
  • B-coded connectors are mostly used in network cables for fieldbus connections. Most notably, this includes systems that operate with Profibus. B-coded connectors typically have between three and five pins.
  • C-coded connectors are less common than the others. These connectors are primarily used with AC sensors and actuators. They also have a dual keyway for added security, ensuring that this connector will not be accidentally used in the place of another cable. C-coded connectors have between three and six pins.
  • D-coded connectors are typically used in network cables for Ethernet and ProfiNet systems. D-coded connectors transfer data up to 100 Mb. These connectors typically provide three to five pins.
  • X-coded connectors are a more recent advancement of the cables. They are growing in popularity due to their ability to transfer large amounts of data at high speeds. X-coded cables transfer data up to 1 Gb. These are ideal for high-speed data transfer in industrial applications. While the other coded cables typically vary in number of connectors, X-coded cables will always have eight pins.

IO-Link Makes Improving OEE in Format Change Easier than Ever

One of the primary applications in Packaging, Food & Beverage that is a huge area for improving overall equipment efficiency (OEE) is format change.  Buyers respond well to specialized or individualized packaging, meaning manufacturers need to find ways to implement those format changes and machine builders must make those flexible machines available.

IO-Link Makes Improving OEE in Format Change Easier than Ever_2

Today, thanks to IO-Link devices, including master blocks, hubs and linear position sensors, improving OEE on format change is more possible today than ever before. IO-Link offers capabilities that make it ideal for format change. It communicates:

  • Process data (control, cyclical communication of process status)
  • Parameter data (configuration, messaging data with configuration information)
  • Event data (diagnostics, communication from device to master including diagnostics/errors)

What is format change and how does it impact OEE?

Format change is the physical adjustments necessary to make to a machine when the product is altered in some way.  It could be a change in carton size, package size, package design, case size or a number of other modifications to the product or packaging.  The time to adjust the machine itself or the sensors on the machine can take anywhere from 30 minutes to an entire eight- hour shift.

Types of format changes to consider when seeking to improve your OEE:

Guided format change is when the operator is assisted or guided in making the change.  For example, having to move or slide a guide rail into a new position.  IO-Link linear position sensors can help guide the operator, so the position is exact every time. This reduces time by eliminating the need to go back and look at an HMI or cheat sheet to determine if everything is in the right position.

Change parts is when a part needs to be swapped out on the machine for the next production run.  An example of this is when the bag size on a bagger or vertical form fill and seal (VFFS) machine changes and the forming tube needs to be changed.  Having an RFID tag on the forming tube and a RFID reader on the machine allows for easy verification that the correct forming tube was put on the machine and only takes seconds.

Color Change is when the color of a pouch, package or container changes for the next production run like when a yogurt pouch changes color or design while the size and shape remain the same as previous production runs. Smart color photo electric sensors can change the parameters on the photo eye to detect the correct color of the new pouch occurs instantly upon changing the recipe on the machine.

Developing semi-automated or fully automated solutions can improve OEE in regard to format change by helping reduce the time needed to make the change and providing consistent and accurate positioning with the ability to automatically change parameters in the sensor.

Being smart, easy and universal, IO-Link helps simplify format change and provides the ability to change sensor parameters quickly and easily.

IO-Link Makes Improving OEE in Format Change Easier than Ever_1

How TSN boosts efficiency by setting priorities for network bandwidth

As manufacturers move toward Industry 4.0 and the Industrial Internet of Things (IIoT), common communication platforms are needed to achieve the next level of efficiency boost. Using common communication platforms, like Time-Sensitive Networking (TSN), significantly reduces the burden of separate networks for IT and OT without compromising the separate requirements from both areas of the plant/enterprise.

TSN is the mother of all network protocols. It makes it possible to share the network bandwidth wisely by allocating rules of time sensitivity. For example, industrial motion control related communication, safety communication, general automation control communication (I/O), IT software communications, video surveillance communication, or Industrial vision system communication would need to be configured based on their time sensitivity priority so that the network of switches and communication gateways can effectively manage all the traffic without compromising service offerings.

If you are unfamiliar with TSN, you aren’t alone. Manufacturers are currently in the early adopter phase. User groups of all major industrial networking protocols such as ODVA (CIP and EtherNet/IP), PNO (for PROFINET and PROFISAFE), and CLPA (for CC-Link IE) are working toward incorporating TSN abilities in their respective network protocols. CC-Link IE Field has already released some of the products related to CC-Link IE Field TSN.

With TSN implementation, the current set of industrial protocols do not go away. If a machine uses today’s industrial protocols, it can continue to use that. TSN implementation has some gateway modules that would allow communicating the standard protocols while adding TSN to the facility.

While it would be optimal to have one universal protocol of communication across the plant floor, that is an unlikely scenario. Instead, we will continue to see TSN flavors of different protocols as each protocol has its own benefits of things it does the best. TSN allows for this co-existence of protocols on the same network.

 

Power & Force Limiting Cobots for Dull, Dirty and Dangerous Applications

Collaborative robots, or cobots, is currently one of the most exciting topics in automation. But what do people mean when they say “collaborative robot”? Generally, they are talking about robots which can safely work near and together with humans. The goal of a collaborative robot system is to optimize the use of humans and robots, building on the capabilities of each.

There are four modes of robot collaborative operation defined by the global standard ISO/TS 15066. We discussed these modes in a previous blog, Robot Collaborative Operation.

This post will go more deeply into the most commonly used mode: power & force limiting. Robots in this category include ones made by Universal Robots, as well as FANUC’s green robots and ABB’s Yumi.

What is power & force limiting?

Power & force limiting robots are designed with limited power and force, along with physical features to avoid or reduce injury or damage in case of contact. These robots are generally smaller, slower and less powerful than traditional robots but also more flexible and able to work near or with humans — assuming a risk assessment determines it is safe to do so.

The standards define the creation of a shared or collaborative work space for the robot and human, and define how they may interact in this space. In a power & force limiting application, the robot and operator can be in the shared/collaborative work space at the same time and there may be contact or collision between the operator and the collaborative robot system (which includes the robot, gripper/tool and work piece). Under the proper conditions the features built into the power & force limiting robot allow this close interaction and contact to occur without danger to the operator.

What technologies allow these robots to work closely with humans?

The limiting of the robot’s force can be implemented in several ways. Internal torque/feedback sensors in the joints, external sensors or “skins” and/or elastic joints are some of the methods robot suppliers use to assure low force or low impact. They also design possible contact areas to avoid injury or damage by using rounded edges, padding, large surface areas, etc. to soften contact. Grippers, tools and work pieces also need to be considered and designed to avoid injury or damage to people and equipment.

Peripherally, additional sensors in the robots, grippers, tools, work holders and surrounding work stations are critical parts of high performance robot applications. Connecting these sensors through protocols such as IO-Link and PROFISafe Over IO-Link allows more tightly integrated, better performing, and safer collaborative robot systems.

Where are power & force limiting robots typically applied?

Similar to traditional robots, power & force limiting robots are best applied in applications which are dull, dirty and/or dangerous (the 3 Ds of robotics). They are especially well suited to applications where the danger is ergonomic — repetitive tasks which cause strain on an operator. In many cases, power & force limiting robots are being applied to cooperate closely with people: the robots take on the repetitive tasks, while the humans take on the tasks which require more cognitive skills.

A large number of the customers for power & force limiting robots are small or medium-sized enterprises which can not afford the investment and time to implement a traditional robot, but find that power & force limiting robots fit within their budget and technical capabilities.

What are some of the benefits and drawbacks to power & force limiting robots?

Benefits:

  • Low cost
  • Fast, simple programming and set up; often does not require special knowledge or training
  • Small and lightweight
  • Easy to deploy and redeploy
  • Can be fenceless
  • Low power usage
  • Close human-robot interaction

Drawbacks:

  • Slow
  • Small payload
  • Low force
  • Low precision (not always the case, and improving)

Final Thoughts

Buying a power & force limiting robot does not necessarily mean that fences or other safeguards can be removed; a risk assessment must be completed in order to ensure the application is appropriately safeguarded. The benefits, however, can be significant, especially for smaller firms with limited resources. These firms will find that power & force limiting robots are very good at cost-effectively solving many of their dull, dirty and dangerous applications.

IO-Link devices deliver data specific to your manufacturing operations needs

IO-Link is a point-to-point communication standard [IEC61131-9]. It is basically a protocol for communicating information from end devices to the controller and back. The beauty of this protocol is that it does not require any specialized cabling. It uses the standard 3-pin sensor cable to communicate. Before IO-Link, each device needed a different cable and communication protocol. For example, measurement devices needed analog signals for communication and shielded cables; digital devices such as proximity sensors or photo eyes needed 2-pin/3-pin cables to communicate ON/OFF state; and any type of smart devices such as laser sensors needed both interfaces requiring multi-conductor cables. All of these requirements and communication was limited to signals.

Shishir1

With IO-Link all the devices communicate over a standard 3-pin (some devices would require 4/5 pin depending if they need separate power for actuation). And, instead of communicating signals, all these devices are communicating data. This provides a tremendous amount of flexibility in designing the controls architectures for the next generation machines.

IO-Link data communication can be divided into 3 parts:

  1. Process data: This is the basic functionality of the sensor communicated over cyclical messages. For example, a measurement device communicating measurement values, not 4-20mA signals, but the engineering units of measurement.
  2. Parameter data: This is a cyclic messaging data communication and where IO-Link really shines. Manufacturers can add significant value to their sensors in this area. Parameter data is communicated only when the controller wants to make changes to the sensor. Examples of this include changing the engineering units of measurement from inches to millimeters or feet, or changing the operational mode of a photoelectric sensor from through-beam to retro-reflective, or even collecting capacitance value from a capacitive sensor. There is no specific parameter data governed by the consortium — consortium only focuses on how this data is communicated.
  3. Event data: This is where IO-Link helps out by troubleshooting and debugging issues. Event messages are generated by the sensor to inform the controller that something has changed or to convey critical information about the sensor itself. A good example would be when a photoeye lens gets cloudy or knocked out of alignment causing a significant decrease in the re-emitted light value and the sensor triggers an event indicating the probable failure. The other example is the sensor triggering an event to alert the control system of a high amperage spike or critical ambient temperatures. When to trigger these events can be scheduled through parameter data for that sensor.

Shishir2

Each and every IO-Link device on the market offers different configurations and are ideally suited for various purposes in the plant. If inventory optimization is the goal of the plant, the buyer should look for features in the IO-Link device that can function in different modes of operation such as a photo eye that can operate as through-beam or retro-reflective. On the other hand, if machine condition monitoring is the objective, then he should opt for sensors that can offer vibration and ambient temperature information along with the primary function.

In short, IO-Link communication offers tremendous benefits to operations. With options like auto-parameterization and cable standardization, IO-Link is a maintenance-friendly standard delivering major benefits across manufacturing.

Shishir3

Three Ways to Configure a Splitter and Harness the Power of Pin 2

Based on the increasing popularity of machine mounted I/O utilizing readily available IP67 components, it’s more important than ever to utilize every I/O point.  I/O density has increased over the years and the types of I/O have become more diversified, yet in many systems pin 2 is left unused by the end user.  Sensors tend to come in twos, for example, a pneumatic cylinder may require a sensor for the extended position and one for the retracted position.  Running each individual sensor back to the interface block utilizes pins 1,3 and 4 (for power, ground and signal) but wastes pin 2 on each port.

Figure 1
Fig. 1 Bad I/O configuration: neglecting pin 2 is inefficient and costly

Rather than using a separate port on the I/O block for each sensor, a splitter can collect the outputs of two sensors and deliver the input to a single port.  With a splitter, one sensor output goes to pin 4, the other goes to pin 2.

By putting two signals into one and utilizing both pins 2 and 4, the overall I/O point cost decreases.

There are multiple ways to configure a splitter to utilize pin 2. We will review three methods — good, better and best:

1. T-splitter on the I/O block:

Figure 3
Fig. 3 Good basic method for utilizing the additional I/O point, pin-2

A T-splitter is a good way to utilize pin 2.  However, the “T” covers the I/O module port eliminating the benefit of the high-value diagnostic LEDs on the block. Also, individual cables must run all the way from the block to the sensors at the installation point, creating clutter and cable bulk.  In addition, when Ts are used on a vertically mounted block, the extra cable bulk can weigh down the T-splitter and threaten its integrity.

2. V-type splitter on the I/O block:

Figure 4
Fig. 4 Better way of utilizing pin 2 while also allowing visibility of diagnostic LEDs

The use of a V-type configuration allows better visibility of the diagnostic LEDs and eliminates the need to purchase a separate part. However, individual cables must still be run from the block to the sensors, creating clutter and cable bulk.

3. Ytype configuration:

Figure 5
Fig. 5 Best way to utilize pin 2

In the Y-type splitter configuration, all aspects of usability are improved. One cable runs from the I/O block to the installation point. The split of pins 2 and 4 is done as close to the sensors as possible. This significantly cleans up cable clutter, provides a completely unrestricted view of the diagnostic LEDs and allows for easy installation of multiple connectors to the I/O block.

How IO-Link is Revolutionizing Overall Equipment Efficiency

Zero downtime.  This is the mantra of the food and beverage manufacturer today.  The need to operate machinery at its fullest potential and then increase the machines’ capability is where the demands of food and beverage manufacturers is at today.  This demand is being driven by smaller purchase orders and production runs due to e-commerce ordering, package size variations and the need for manufacturers to be more competitive by being flexible.

Using the latest technology, like IO-Link, allows manufacturers to meet those demands and improve their Overall Equipment Efficiency (OEE) or the percentage of manufacturing time that is truly productive.  OEE has three components:

  1. Availability Loss
    1. Unplanned Stops/Downtime – Machine Failure
    2. Planned Downtime – Set up and AdjustmentsS
  2. Performance Loss
    1. Small Stops – Idling and Minor Stops
    2. Slow Cycles – Reduced Speed
  3. Quality Loss
    1. Production Rejects – Process Defects
    2. Startup Rejects – Reduced Yield

IO-Link is a smart, easy and universal way to connect devices into your controls network.

The advantage of IO-Link is that it allows you to connect to EtherNet/IP, CC-Link & CC-LinkIE Field, Profinet & Profibus and EtherCAT & TCP/IP regardless of the brand of PLC.  IO-Link also allows you to connect analog devices by eliminating traditional analog wiring and provides values in actual engineering units without scaling back at the PLC processor.

Being smart, easy and universal, IO-Link helps simplify controls architecture and provides visibility down to the sensor and device.

IO-Link communicates the following:

  • Process data (Control, cyclical communication of process status)
  • Parameter data (Configuration, messaging data with configuration information)
  • Event data (Diagnostics, Communication from device to master (diagnostics/errors )

This makes it the backbone of the Smart Factory as shown in the graphic below.

 

IO-Link Simplifies the Controls Architecture

IO-Link OEE1

IO-Link OEE2

The Emergence of Device-level Safety Communications in Manufacturing

Manufacturing is rapidly changing, driven by trends such as low volume/high mix, shorter lifecycles, changing labor dynamics and other global factors. One way industry is responding to these trends is by changing the way humans and machines safely work together, enabled by updated standards and new technologies including safety communications.

In the past, safety systems utilized hard-wired connections, often resulting in long cable runs, large wire bundles, difficult troubleshooting and inflexible designs. The more recent shift to safety networks addresses these issues and allows fast, secure and reliable communications between the various components in a safety control system. Another benefit of these communications systems is that they are key elements in implementing the Industrial Internet of Things (IIoT) and Industry 4.0 solutions.

Within a typical factory, there are three or more communications levels, including an Enterprise level (Ethernet), a Control level (Ethernet based industrial protocol) and a Device/sensor level (various technologies). The popularity of control and device level industrial communications for standard control systems has led to strong demand for similar safety communications solutions.

Safety architectures based on the most popular control level protocols are now common and often reside on the same physical media, thereby simplifying wiring and control schemes. The table, below, includes a list of the most common safety control level protocols with their Ethernet-based industrial “parent” protocols and the governing organizations:

Ethernet Based Safety Protocol Ethernet Based Control Protocol Governing Organization
CIP Safety Ethernet IP Open DeviceNet Vendor Association (ODVA)
PROFISafe PROFINET PROFIBUS and PROFINET International (PI)
Fail Safe over EtherCAT (FSoE) EtherCAT EtherCAT Technology Group
CC-Link IE Safety CC-Link IE CC-Link Partner Association
openSAFETY Ethernet POWERLINK Ethernet POWERLINK Standardization Group (EPSG)

 

These Ethernet-based safety protocols are high speed, can carry fairly large amounts of information and are excellent for exchanging data between higher level devices such as safety PLCs, drives, CNCs, HMIs, motion controllers, remote safety I/O and advanced safety devices. Ethernet is familiar to most customers, and these protocols are open and supported by many vendors and device suppliers – customers can create systems utilizing products from multiple suppliers. One drawback, however, is that devices compatible with one protocol are not compatible with other protocols, requiring vendors to offer multiple communication connection options for their devices. Other drawbacks include the high cost to connect, the need to use one IP address per connected device and strong influence by a single supplier over some protocols.

Device level safety protocols are fairly new and less common, and realize many of the same benefits as the Ethernet-based safety protocols while addressing some of the drawbacks. As with Ethernet protocols, a wide variety of safety devices can be connected (often from a range of suppliers), wiring and troubleshooting are simplified, and more data can be gathered than with hard wiring. The disadvantages are that they are usually slower, carry much less data and cover shorter distances than Ethernet protocols. On the other hand, device connections are physically smaller, much less expensive and do not use up IP addresses, allowing the integration into small, low cost devices including E-stops, safety switches, inductive safety sensors and simple safety light curtains.

Device level Safety Protocol Device level Standard Protocol Open or Proprietary Governing Organization
Safety Over IO-Link/IO-Link Safety* IO-Link Semi-open/Open Balluff/IO-Link Consortium
AS-Interface Safety at Work (ASISafe) AS-Interface (AS-I) Open AS-International
Flexi Loop Proprietary Sick GmbH
GuardLink Proprietary Rockwell Automation

* Safety Over IO-Link is the first implementation of safety and IO-Link. The specification for IO-Link Safety was released recently and devices are not yet available.

The awareness of, and the need for, device level safety communications will increase with the desire to more tightly integrate safety and standard sensors into control systems. This will be driven by the need to:

  • Reduce and simplify wiring
  • Add flexibility to scale up, down or change solutions
  • Improve troubleshooting
  • Mix of best-in-class components from a variety of suppliers to optimize solutions
  • Gather and distribute IIoT data upwards to higher level systems

Many users are realizing that neither an Ethernet-based safety protocol, nor a device level safety protocol can meet all their needs, especially if they are trying to implement a cost-effective, comprehensive safety solution which can also support their IIoT needs. This is where a safety communications master (or bridge) comes in – it can connect a device level safety protocol to a control level safety protocol, allowing low cost sensor connection and data gathering at the device level, and transmission of this data to the higher-level communications and control system.

An example of this architecture is Safety Over IO-Link on PROFISafe/PROFINET. Devices such as safety light curtains, E-stops and safety switches are connected to a “Safety Hub” which has implemented the Safety Over IO-Link protocol. This hub communicates via a “black channel” over a PROFINET/IO-Link Master to a PROFISafe PLC. The safety device connections are very simple and inexpensive (off the shelf cables & standard M12 connectors), and the more expensive (and more capable) Ethernet (PROFINET/PROFISafe) connections are only made where they are needed: at the masters, PLCs and other control level devices. And an added benefit is that standard and safety sensors can both connect through the PROFINET/IO-Link Master, simplifying the device level architecture.

Safety

Combining device level and control level protocols helps users optimize their safety communications solutions, balancing cost, data and speed requirements, and allows IIoT data to be gathered and distributed upwards to control and MES systems.

 

Connecting Safety Devices to a Safety Hub

Safety device users face a dilemma when selecting safety components: They want to create a high-performance system, using best-in-class parts, but this often means buying from multiple suppliers. Connecting these devices to the safety control system to create an integrated system can be complicated and may require different cabling/wiring configurations, communications interfaces and/or long, hardwired cables.

Device-Level Protocols

One solution, discussed in a previous blog on industrial safety protocols, is to connect devices to an open, device-level protocol such as Safety Over IO-Link or AS-i Safety At Work. These protocols offer a simple way to connect devices from various suppliers using non-proprietary technologies. Both Safety Over IO-Link and AS-i Safe offer modules to which many third party devices can be connected.

Connecting to a Safety HubSafety-Arch_012518

The simplest way to connect to a safety hub/module is to buy compatible products from the hub supplier. Many safety block/hub suppliers also offer products such as E-stops, safety light curtains, door switches, inductive safety sensors and guard locking switches which may provide plug & plug solutions. There are, however, also many third party devices which can also be easily connected to some of these hubs. Hubs which are AIDA (Automation Initiative of German Domestic Automobile manufacturers) compliant allow connection of devices which are compatible with this standard. Generally, these devices have M12 connectors with 4, 5 or 8 pins, and the power, signal and ground pins are defined in the AIDA specifications. Most major safety device manufacturers offer at least one variant of their main products lines, which are AIDA pin-compatible.

AIDA/Safety Hub Compatible Devices

Some suppliers have lists of devices which meet the M12 pin/connector AIDA specification and may be connected to AIDA compatible modules. Note that not all the listed safety devices may have been tested with the safety blocks/hubs, but their specifications match the requirements. AIDA compatible devices have been identified from all major safety suppliers including Balluff, Rockwell, Sick, Schmersal, Banner, Euchner and Omron STI; and range from safety light curtains to door switches to E-stop devices.

Easy Connection

While some manufacturers prefer to focus on locking customers into a single supplier solution, many users want to combine devices from multiple suppliers in a best-in-class solution. Selecting a safety I/O block or hub which supports AIDA compatible devices makes it fast and easy to connect a wide range of these devices to create the safety system that is the best solution for your application.

Why IO-Link is the Best Suited Technology for Smart Manufacturing

While fieldbus solutions utilize sensors and devices with networking ability, they come with limitations. IO-Link provides one standard device level communication that is smart in nature and network independent. That enables interoperability throughout the controls pyramid, making it the most suitable choice for smart manufacturing.

IO-Link offers a cost effective solution to the problems. Here is how:

  • IO-Link uses data communication rather than signal communication. That means the communication is digital with 24V signal with high resistance to the electrical noise signals.
  • IO-Link offers three different communication modes: Process communication, Diagnostic communication (also known as configuration or parameter communication), and Events.
    • Process communication offers the measurement data for which the device or sensor is primarily selected. This communication is cyclical and continuous in nature similar to discrete I/O or analog communication.
    • Diagnostic communication is a messaging (acyclic) communication that is used to set up configuration parameters, receive error codes and diagnostic messages.
    • Event communication is also acyclic in nature and is how the device informs the controller about some significant event that the sensor or that device experienced.
  • IO-Link is point-to-point communication, so the devices communicate to the IO-Link master module, which acts as a gateway to the fieldbus or network systems or even standard TCP/IP communication system. So, depending on the field-bus/network used, the IO-Link master may change but all the IO-Link devices enjoy the freedom from the choice of network. Power is part of the IO-Link communication, so it does not require separate power port/drop on the devices.
  • Every open IO-Link master port offers expansion possibilities for future integration. For example, you could host an IO-Link RFID device or a barcode reader for machine access control as a part of a traceability improvement program.

For more information, visit www.balluff.com/io-link.