We will not try to sell you anything on the call.

VNTA Robotics tests what a robot or fleet system can actually do through its interface. Before we point it at a real system, we want to know whether the checks are the right ones.

Five questions:

1. How did you find out what the robot could and could not do through its interface?
2. How long did interface testing take, and who did it?
3. What went wrong after go-live that a test would have caught?
4. Did vendor certification cover it? What did it miss?
5. What would it have been worth to have a report like this on day one?

In return we will show you the report from our first external test, and you can tell us which lines are useful and which are noise.

Write to us at vnta.xyz/contact, or reply wherever you are reading this.

Three are simulators we wrote ourselves. Each speaks a different invented interface, and each has faults we planted on purpose. One has no pause. One acts on the same order twice. One goes quiet after a restart.

The suite finds every planted fault and no others. That proves the tester works. It proves nothing about robots.

The fourth is the one that matters: an open-source VDA 5050 virtual vehicle that somebody else wrote. We ran it unmodified, in its own process, and judged its messages against the official schemas.

32 of 37 checks passed. Every behavioural check passed: orders, pause, resume, cancel, duplicates, charging, recovery after a restart.

The next step is a real system. That needs a partner who has one.

It is easy to show the first and call it the second.

VNTA Robotics keeps three things apart, for every function of every machine:

Declared: what the interface is documented to offer.
Discovered: what the system says when you ask it.
Verified: what a test run actually saw work, and when.

The picture is a real result from our console. One virtual vehicle, 14 capabilities, all of them declared. 13 verified. One failed: asked to describe its own functions, it answered, but named none.

It is a virtual vehicle, not a real one. The point is the shape of the answer.

That question is harder to answer than it should be.

A robot’s interface says it supports pause. The fleet manager says it speaks the standard. Then you get on site, and pause does something slightly different from what the manual said.

We are building software that answers the question properly. It connects to a robot or fleet system, runs the same set of checks against it, and keeps the evidence: every call, every answer, every raw message.

It is called VNTA Robotics. It is in development. So far it has run against simulated robots and one virtual vehicle that we did not write. It has not met a real machine yet.

Over the next few weeks we will post what we have built, what it found, and what is not done.

If you commission mobile robots for a living, we would like to hear how you do this today.