Skip to main content

VDA 5050 Documentation

The J1600 has full VDA 5050 support. This page covers what that means in practice for a deployment: what the interface enables, what it requires, and how a VDA 5050 fleet setup is delivered. For the standard itself, see VDA 5050 explained.

What VDA 5050 enables on the J1600​

VDA 5050 is the interoperability interface that lets mobile robots from different vendors work together in the same space under a compatible fleet-management layer. With VDA 5050 enabled, the J1600 can:

  • operate as part of a fleet coordinated by a VDA 5050 fleet manager;
  • coexist with robots from other vendors under the same fleet layer;
  • scale from a single teach-and-repeat unit into an orchestrated multi-robot deployment without changing hardware.

The Mobile Robot Company works with established VDA 5050 fleet-management providers.

Requirements​

VDA 5050 support is part of the Advanced software package (€14,500 end-user list), which also includes the REST API, Fleet Manager, and advanced mission planning. The upgrade is easiest to install at the factory when the robot is ordered; a partner can install it later, but customers cannot install it themselves.

Connected fleet operation requires a network. Basic standalone use of the J1600 does not — Wi-Fi is optional out of the box.

Planning a VDA 5050 deployment​

  1. Order the robots with Advanced software, or have a partner upgrade existing units.
  2. Confirm interface specifics — including the supported VDA 5050 version and the fleet-management products validated for your project — with The Mobile Robot Company or your partner during scoping.
  3. Include Fleet Management System setup in the commissioning scope. It is an add-on to the installation and commissioning package.
  4. Validate tasks and safety on site as part of commissioning before handover.

When VDA 5050 is the wrong tool​

A single J1600 serving one flow needs no fleet layer: teach and repeat on the Standard software covers it. For direct point integrations with site software or equipment rather than fleet coordination, use the REST API.