Upload a FANUC backup. Understand the whole cell without opening a file.

Integrators and plant teams

One backup. Better documented decisions.

Bring Maatron into your engineering reviews using the backups you supply. Start with a concrete task, then share the result with your team.

• FANUC integrators

  Take over a cell, find where a register is used and explore program calls. Compare backups before and after an intervention, then prepare handover documentation with the reports.

• Maintenance and controls teams

  Find the available configuration in a fleet organized by site, cell and controller. Support a change review with recorded differences and their sources.

• Plant and project managers

  Evaluate Maatron on one cell with your engineering team. Review the results, reading limits and reports before extending its use across your fleet.

Discuss your plant or integration workflow

Your engineering process

What changes for the plant

A shared review between the integrator, maintenance team and project lead, based on the same files and reports.

Example workflow: a cell modification

1. Before the intervention

   The team keeps its reference backup and uploads it to Maatron. It can locate the programs, I/O and frames present in the files to prepare its review.

2. At handover

   The integrator uploads the backup after the intervention. The A → B comparison shows changes and their before/after values, including the limits of what the files can reveal.

3. During the team review

   Maintenance and the project lead review the differences and FR/EN reports. They have a shared record for asking questions and documenting their decision.

This scenario illustrates a workflow, not a measured customer outcome. Machine validation and authorization to return to service remain part of your procedures.

What the engine does

Unreadable files become a queryable model

Programs, I/O and frames brought together in one view. Missing and undecoded sections are identified so you can judge what the result supports.

User Frame
  130.0  -2590.0  -2356.0     0.0     0.0  -180.0
  863.0  -2080.0  -2356.0     0.0     0.0     0.0

[*SYSTEM*]$CELL_SETUP.$DI_INISTY_T  Access: RW: INTEGER = 20
[*SYSTEM*]$CELL_SETUP.$DO_STYSTR_T  Access: RW: INTEGER = 2

/PROG  MAIN_CYCLE
   1:  WAIT DI[18:INITIATE STYLE]=ON  ;
   2:  CALL PICK_PART                 ;
   3:  DO[2:STYLE ACK]=ON             ;
/END

Example produced by the engine from the repository's demonstration backup — no customer data.

Three moves

Nothing to install on the controller

1. 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 — the ASCII .VA exports when the backup carries them, and failing that the .VR/.SV binaries from the teach pendant.

2. 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.

3. 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 and frames appear there only as binary .VR/.SV files: the engine decodes them, and the analysis states which file was used and with what confidence. The ASCII .VA export, produced by an FTP export or a RoboGuide simulation, still takes precedence when present — it is a controller export, where the binary is a reconstruction. DCS is read from its verification listing, and controller mastering from the binary system-variable file that every teach-pendant backup carries. Whatever still awaits a decoder is named section by section in the analysis. Nothing is guessed either way: the engine names the sections it could not read, and states which of the two causes it met — file absent from the backup, or file right there that it cannot yet read. Either way it connects to nothing — you supply the file.

Security

The robot never knows Maatron exists

Your team uploads a backup to the SaaS. Maatron analyzes its files without an agent or a connection on the industrial network. Have your organization approve the use of the service and the upload of your data.

Read the “Security and trust” page

• 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

  Cookies keep your session and your language and theme preferences. No advertising trackers.

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.

What Maatron does not do: replace a scheduled backup, a version vault or a controller restore. Those tools exist and do their job well.

Before you start

Your technical questions