Skip to content

From design to machine

Your site is in the cab within seconds

No stick, no email, no operator hunting for a folder. You load your design, tick the machine and press send. The tablet in the cab picks it up and puts it where the control system looks.

Unicontrol and Trimble. This route works today for Unicontrol in the cab and for Trimble Access and Siteworks on the field controller. Topcon, Leica and CHCnav follow — converting to those formats already works; only sending straight there is still to come.

1

Pair once

You add the machine in the portal and get an eight-digit code. The operator types it once on the tablet — with gloves on, facing the sun, so eight digits and no letters. After that it goes quiet: the code stays valid, and a tablet in a cab does not get set up again every month.

The eight-digit pairing code in the customer portal

2

Load your design

Drop your design into the workbench — DXF, DWG, LandXML, TP3, a Pythagoras file. Surface, linework and points each land in their own bin, and you see what is in it in 3D straight away. The coordinate system is derived from the coordinates; if that is wrong, you pick it yourself.

The workbench with a design loaded in 3D

3

See where it lands

Put the official aerial photo underneath and you see at a glance whether your design falls in the right place. Belgium, the Netherlands, France and Luxembourg, each from its own service. A plan a hundred metres off shows here — not when the excavator is already waiting.

The design on the official aerial photo

4

Tick the machine and send

Choose the machine, name the site and press send. The dot tells you whether the tablet has reported in the last two minutes. More than one machine? They all go at once, and each gets the format its control system reads.

The block for sending a site to the machine

5

And it is waiting

The package is built and queued for that machine. The portal counts what is still on the way until nothing is left waiting. The tablet picks it up on its next round — within seconds.

Confirmation that the site is ready for the machine, with the number of files

Or straight from the program

The Converter on your own PC does the same, without a browser. Your licence key already says who you are, so your company and your machines are right there — no second sign-in.

Your site, your machines, one window

On the left what you load, in the middle what it became, on the right where it goes. Your company name sits top right; one click takes you to your customer portal.

The MV3D Converter with a design loaded and the machine column on the right

You pick the brand once

Every control system has its own format, and behind each brand is what it produces. What your file does not allow is greyed out with the reason — so you can see the brand exists and that it is down to the file.

The brand list with their logos

Tick and send

Your machines are listed with their control system and a green dot if the tablet has just reported in. Tick several and they go together: the design goes up once, and each machine gets the format it reads. Adding a machine works here too, with the pairing code straight away in large type.

The machine column in the Converter, pairing code masked

The pairing code shows as dots on these images. That is not styling: the code is a working key, and it does not belong on a public page.

Or the other way round: the code is on the device

Open the MV3D app on the tablet, or MV3D Veld on the field controller. As long as the device is not paired, an eight-digit code is shown on its screen. You type that under Add device, and brand, model and software come along automatically. That is the shortest route when the operator is already on site and you have not created the device yet.

This is not only about the tablet in the cab: on a TSC7 or TSC5, MV3D Veld does the same, with the project folder of Trimble Access or Siteworks.

Giving a site without a position a location

A site that only holds linework does not know where it is: no pin on the map, and the coordinate system has to be guessed. You set that location yourself on the map and pick the system with it. The program then sets that system as soon as you open the site, and sends it along when you publish.

Own, rented or from a subcontractor

Not every machine on your site is yours. For each device you mark how it stands; it shows in the list and in the tree, and it decides what happens when the rental ends.

Own
Your own machines and field controllers. They get the sites as always.
Rented
With the hire company and the end date. After that date the program first asks whether it should send anyway — a rental that was extended but not yet entered must not hold up the work.
From a subcontractor
Someone else’s machine working on your site. It gets the designs like your own devices, and you see at a glance that it is theirs.

And back: see what is on your devices

The road runs both ways. Every device reports what it holds, and that lands in the same overview as your own projects — with a light that says whether the machine is talking right now or standing still.

Open
Fetch a site from the machine and open it. If there is something newer on the device, that is fetched first.
Rename
The folder on the device takes the new name, so office and cab give the same site the same name.
Delete
Only after you have retyped the name. On a field controller there is no recycle bin.
Waiting is part of it
The device carries it out on its next round. If the machine is switched off, the request stays until it makes contact again — it does not expire.

Everything on one page Your own projects and the sites on your devices sit together on the projects page: on the map, in a tree per customer, site and work order with their own numbers, and with a filter by device, software, content, period or location.

What exactly gets sent

Not one file, but the whole project the way Unicontrol expects it — in the folder tree the control system looks in.

site.xml
The terrain model as LandXML: the triangles the machine works to.
site.dxf
The linework: manhole edges, kerbs, slopes and alignments, each on its own layer.
Project.yml
The project itself, so Unicontrol sees a site instead of loose files.
system.wkt
Your country’s coordinate system, placed twice where the control system looks.
geoid
The height reference — and only one that is actually on that tablet, because a name that is not there gets refused.

How long does it take? The tablet checks in every five seconds. An ordinary site is therefore in the cab within ten seconds; a two-hundred-megabyte linework plan takes as long as your connection needs. If the tablet is out of range, the site keeps waiting until it reports back.

Fourteen days to try everything, with your own designs and your own machine.