Material Handling

How does a material handling conveyor control integration engagement work?

We engineer the controls and networking layer of material-handling systems.

This is for the system integrators and equipment builders whose floor it is, and the work is conveyor control integration, AS/RS and AGV control design, and the industrial Ethernet and safety networking underneath them. The layer is a specific one:

• The network design.
• The control structure.
• The device and gateway layer.
• The safety communication that rides with it.

Installation, site commissioning and the end customer stay with the integrator. Where the design has to be integrated and tested, our team works with your engineers, onshore during integration and test and remotely for the rest.

Intralogistics is an integration discipline more than a machinery one. The conveyor works, the crane works, the vehicles work; the engineering question is whether they hand a load to each other reliably at throughput, and whether the network can prove they did. That question is answered in the design, which is why it is the part that gets outsourced.

What sets the network budget in a material-handling system?

Node count and topology set it, not the fastest device on the floor.

A sorter diverting at speed needs its decision inside a fixed window, and every zone added to the segment eats into it. We design the segments and the traffic split up front so that extending the system later adds nodes without pushing the existing zones out of their cycle budget, which is the difference between a spur being a week’s work and a re-commissioning. A multi-tier conveyor and lift our team built faced exactly this: 18 lanes merging across two levels, held in step on a 2 ms POWERLINK cycle.

How is a load handed between fixed equipment and mobile robots?

The handover point is the harder part of an AGV deployment; navigation rarely is.

A vehicle and a fixed conveyor have to agree on state there. We design the interface at the fleet-manager level and model the handover explicitly (requested, granted, occupied, cleared) so the transfer is interlocked instead of being driven by a timer, which is what stops a load being placed onto a station that has not finished releasing the last one. Our work is the interface and the logic above it. Fleet-management software itself is a different business, and the vendors who build it are the people we work alongside. What varies between projects is the interface; the handover model stays the same. Our team has built the vehicle side as well, including the control system for a line-following AGV that reads its route from markers in the floor.

Where the fleet manager speaks VDA 5050, the interface is at least a published specification, which makes the handover modelling a bounded piece of work from the start. Note that VDA 5050 remains an industry-association specification and is not yet a European standard, so it is a common agreed interface without a conformance requirement, and plenty of fleet managers do not implement it. Where one does not, the handover is built against that vendor’s own API, usually REST or MQTT, and the state model above it is unchanged. The work that adds is an adapter and its test, without a redesign.

Where does safety communication sit?

On the same wire, in most modern builds.

A safety protocol carries its own integrity checks end to end, so the network beneath it does not have to be trusted and a separate safety network is no longer the default answer. openSAFETY (IEC 61784-3-13) is the clearest example, because it is bus-independent. Our team has ported it onto a customer’s own board and taken it through SIL2 pre-certification testing, and later worked on a fire-safety system where it ran across both POWERLINK and PROFINET segments. That was not intralogistics work, but it is the same discipline a conveyor or AS/RS safety layer needs. Two boundaries apply here:

• Pre-certification testing is not certification. The assessment belongs to an accredited body.
• On driverless vehicles the personnel-safety stop is a certified duty under ISO 3691-4 in Europe and ANSI/ITSDF B56.5 in North America, which is a separate question from obstacle detection using ultrasonic, lidar or vision sensors.

Does floor-level tracking change any of this?

It is starting to change what the fleet layer knows, but not what the safety layer may conclude.

Wireless location tracking over 5G and Wi-Fi is being demonstrated for floor-level material handling. The interlock at the handover point still has to be provable on its own terms. We treat a location feed as useful context for traffic management and not as a substitute for the interlock.

How do you design for a system that keeps growing?

We keep the control structure per zone, identical and parameterised.

Material-handling systems are commissioned in phases and then extended for years.

• What an extension represents. Adding an aisle or a spur is a configuration and a network-budget check, with no new one-off logic, and the safety validation stays limited to the zone that changed instead of covering the whole floor.
• When it is accounted for. At the design step, while the first phase is still on paper, and not after the extension is needed during operation.

The same reasoning drove an EtherCAT motion platform our team built to be configured into several machine geometries instead of rebuilding per machine.