Upload a FANUC backup. Understand the whole cell without opening a file.
Maatron rebuilds a cell's engineering state from its backup files — programs, I/O, registers, frames, DCS — and states what is missing, what breaks, what drifted. Without ever connecting to the robot.
MediumAnd a finding that nothing hides, the most severe first: BACKUP_INCOMPLETE.
Example produced by the engine from the repository's demonstration backup — no customer data.
Three moves
Nothing to install on the controller
01 Drop
A FANUC backup ZIP archive. Nothing to install on the controller, nothing to open on the industrial network.
The engine reads the .LS, .DG, DIOCFGSV.IO and eipcfg.xml files it contains — plus the ASCII .VA exports when the backup carries them.
02 Analyze
The engine produces a validated model, then applies deterministic rules.
Same files, same findings — the model produced is identical from one analysis to the next.
03 Decide
Findings sorted by severity, exportable report, comparison against the robot's designated reference backup.
3 report formats, in French and in English.
Two paths, two contents. A backup taken from the teach pendant to an SD card or a USB stick carries the programs, the diagnostic listings and the I/O assignment config — the engine reads those. Registers, frames, mastering and DCS appear there only as binary .VR/.SV files, which the engine does not decode; their readable form is the ASCII .VA export, produced by an FTP export from the controller or by a RoboGuide simulation. Without those .VA files, nothing is guessed: the engine emits BACKUP_INCOMPLETE and names the sections it could not read. Either way it connects to nothing — you supply the file.
Security
The robot never knows Maatron exists
No connection to the controller, no agent, no port opened on the industrial network. An engineer drops a file; the engine works on bytes. That is what makes the tool admissible in a plant where the smallest write to a controller is a documented event.
Offline by construction
The engine is not allowed to open a connection: an architecture test rejects networking libraries, including through indirect dependencies.
Refuses to start
The application does not start if a route fails to declare who may enter it. The omission cannot be shipped.
Strict isolation
Each organization is a boundary, enforced by the database itself. Without a scope, a query returns no rows.
Short links, opaque keys
Download links expire in minutes, and no storage key is derived from a file name.
No trackers
One session cookie, one language cookie. Nothing else — so there is no banner to click.
What Maatron adds
The layer a backup tool does not give you
Backing up and versioning are trades well served elsewhere. Maatron does not replace them: it reads what comes out of them.
Maatron
Canonical cell model
A backup becomes a queryable relational model, not a folder of files.
Impact analysis
What is connected to what, and what a change touches downstream.
Deterministic findings
Named rules, sorted by severity, replayable identically.
What Maatron does not do: replace a scheduled backup, a version vault or a controller restore. Those tools exist and do their job well.
The product, as it is
What you will see, on a demonstration cell
This is not a screenshot: it is the product's screen, rendered from a demonstration analysis overview.
Analyzed on
Feb 3, 2026, 8:15 a.m.
Source
backup_dir
Engine version
1.0
Findings
HighMISSING_CALL_TARGET
CALL target(s) not found: neither a known TP program, nor a KAREL from the catalog, nor a builtin — subprogram not exported in the backup, typo, or external dependency.
PICK -> GRIP_OPEN
MediumBACKUP_INCOMPLETE
PARTIAL backup: the following sections are present but carry NO values (dcs.safe_io_connect, motion.payload). Those values/configs come from binary .vr/.sv files or from ASCII .va exports (numreg.va, posreg.va, strreg.va, diocfgsv.va, system.va, symotn.va, sysmast.va, dcsioc.va) that are missing from the backup provided — the analysis is therefore incomplete for these sections.
dcs.safe_io_connect
motion.payload
What this backup does not contain
Warning — Partial coverage
The items below could not be analyzed. Their absence from this screen means "not provided", not "none".
Expected files that could not be used
File
State
DIOCFGSV.VA
unreadable
numreg.va
missing from the backup
Sections without values
dcs.safe_io_connect
motion.payload
1 other file was read.
Cell contents
Identity3
F number
F123456
Robot model
R-2000iC/165F
System version
V9.30P/17
Software options2
J518 EtherNet/IP
J567 DCS Position
Inputs / Outputs3
DI
1
DO
2
I/O configuration (rack / slot)1
Numeric registers2
R[2]
R[10] — Compteur pièces
Position registers1
PR[1,3] — Prise
String registers1
SR[1] — Recette
Frames3
Tool frames (UTOOL)
1
User frames (UFRAME)
2
DCS — safety1
Position zones
1
TP programs3
MAIN
PICK
PLACE
1. Severity carries three signs
A hue, a shape and a label. A colour-blind reader gets the same hierarchy; so does a black-and-white print.
2. The rule is named
MISSING_CALL_TARGET is not a slogan: it is an engine rule, quotable in a ticket and replayable.
3. An absence stays an absence
An empty section is never rendered as a default value. The product says it did not look.