Home · Products · OEM components
Products

Assemblies for vehicle builders

Not everyone building an unmanned vehicle wants to develop the running gear themselves. We supply the assemblies individually — and say which responsibilities come with them.

First of all

What you can source

What we build is the mechanics and drive technology of the PALLAS.75 — derived from the ZELOS range already in production, with documented spare parts availability. Those are exactly the assemblies available individually.

Quantities, prices and delivery times depend on volume and are therefore not listed here. What we can commit to, we commit to in conversation.

Scope

What is available individually

Tracked running gear

Drive sprockets as milled aluminium parts, rollers, tracks and running gear mounts. On the PALLAS.75 that means 60 mm wide tracks and two rollers per side — designed for low ground pressure and traction on soft ground.

Manufacturing: our own Deggendorf site

Drive module

Motor and gearbox unit with the matching control, connected over CANopen. Matched as an assembly rather than assembled from individual parts — which saves the design work that in-house developments usually get stuck on.

Interface: CANopen

Payload interface

The mechanical mount with four latches, plus the power and data interface. Whoever adopts it can use superstructures built for the PALLAS.75 — and the other way round.

See also: Payload modules

Autonomy retrofit

Putting control, sensors and the operating side onto an existing vehicle. The most demanding case — and the one where the question of responsibility has to be put most sharply, see below.

First: assessment required
Roles

What passes to you with the assembly

An assembly that does not perform a specific function on its own is partly completed machinery. It comes with a declaration of incorporation and assembly instructions setting out the conditions under which it can be assembled into complete machinery without impairing safety and health. We supply both.

That makes the division of roles unambiguous: we are liable for the risks arising from our component, and for the declaration of incorporation and the assembly instructions. As the final integrator, you are responsible for safe integration and for the CE marking of the finished vehicle.

That is not passing the buck but the division the law makes — and the reason we assess before we build in a retrofit. Sorting that out belongs to engineering and conformity.

From December 2026

Product liability is changing — software included

The new EU Product Liability Directive (EU) 2024/2853 entered into force on 8 December 2024 and has to be transposed into national law by 9 December 2026. For anyone supplying or fitting components, three points matter:

  • Software becomes a product. Software, AI systems and digital manufacturing files count expressly as products in future — updates included. Faulty code is therefore subject to the same rules as a defective part.
  • No fault required, no ceiling. Liability applies without proof of fault, the burden of proof is eased for injured parties, and the previous upper limit on liability falls away. The circle of economic operators who can be held liable is widened.
  • The cut-off date counts. The Directive applies to products placed on the market or put into service after 9 December 2026 (Article 2(1)). For anything before that, the previous law continues to apply.

We raise this here because it shapes how we work together: anyone fitting one of our assemblies into their vehicle and taking on the CE marking should know how the liability position changes from that date. Contractual demarcation and documentation are worth more from then on than they were before.

Limits

What we say openly

  • We are not a catalogue supplier. No web shop, no shelf stock, no delivery from store. OEM supply runs through a project with an agreed specification — in return you get access to the people who designed the assembly.
  • Today there is one size. The assemblies come from the PALLAS.75. For larger vehicles the technology only comes into being with the sizes that are still prototypes or on the roadmap.
  • Autonomy retrofits carry a caveat. Putting a control system onto an existing vehicle can amount to a substantial modification — in which case whoever carries it out becomes the manufacturer. We do not do it without an assessment first.
  • Third-party vehicles need documentation. Without solid information on frame, drive, brakes and safety chain, a retrofit cannot be designed responsibly. That is the precondition, not a bureaucratic surcharge.
Discuss a project All products