FANUC 0i-F automatic backup diagnosis 1016: completion is not recovery readiness
Separate AEX, ACM, ANG and DT1–DT3, check the scope of FROM program backup and establish the snapshot time before treating an execution indication as evidence of recoverability.
Contents
Does an automatic-backup screen without an error justify replacing hardware? A single status bit cannot answer that. Record execution, coverage, data timing and recovery preparation separately. This article concerns evidence from automatic backup, not IPL batch-backup instructions or a restoration tutorial.
Scope and mechanism
The reference is the FANUC Series 0i-MODEL F Maintenance Manual B-64605EN/01, §5.3, printed pages 352–356. This applies only to 0i-F configurations matching that edition; 0i-D, F Plus and other software editions require separate documentation. The function stores backups in battery-independent FROM. SRAM data such as parameters and offsets must be distinguished from NC programs and directory information in FROM. Parameter 10340#2 (AAP) controls inclusion of the latter: 0 excludes them and 1 includes them. These meanings support interpretation, not parameter changes.
Read diagnosis 1016 as separate indications
Section 5.3, printed pages 353 and 356, supplies the definitions below. The last column is our interpretation boundary, not an additional manufacturer alarm definition.
| Entry | Meaning of 1 | What it does not establish |
|---|---|---|
| #0 AEX | Automatic backup is running | Backup has finished |
| #6 ACM | Automatic backup has executed; p. 353 describes completion | Every currently needed item is in that copy |
| #7 ANG | An automatic-backup error occurred | Which component failed |
| #1 DT1, #2 DT2, #3 DT3 | The corresponding data set was updated in the previous backup | Every set must update, or an unchanged set is lost |
Preserve the entire diagnosis screen and observation time, not just ACM. If AEX is active, do not record completion. If ANG is active, retain the error context and stop treating that attempt as success evidence. AEX=0 only means execution is not currently underway; alone it cannot prove past success. Use ACM within the manual’s execution/completion meaning, without extending it to successful restoration or accepted machine accuracy.
Update flags are not snapshot ages
DT1–DT3 identify which set the previous backup updated, not its date or a per-file inventory. The same section describes an overwrite-protected backup set, so a zero DT bit alone is not a fault verdict. A handover should separately list confirmed snapshot times, machine identity, protection policy and update indications. Write “unconfirmed” for missing evidence rather than inventing a date from a bit.
Consider an illustration, not a workshop repair case: a machine has newly adjusted parameters, but the next technician receives only a screenshot showing ACM=1. It does not prove that the backup followed the adjustment. Correlate snapshot timing with the change record. If that relationship is unknown, record “execution indication observed; inclusion of the latest adjustment unconfirmed” rather than approving restoration.
Coverage and consistency need their own checks
Even with normal execution indications, record the current AAP value separately from the known configuration at backup time. Today’s setting cannot prove that an old copy included NC programs. Nor should “SRAM backup” become a synonym for all stored content. For each kind of data needed for recovery, establish its source, timing and machine association.
Section 5.3, printed page 353, warns that changing data while it is being backed up can produce a mismatch between original and backup. Thus “operation ended” and “data represents one confirmed state” are different questions. We recommend keeping relevant editing or adjustment records beside backup records. This is an editorial handover method, not an additional manufacturer procedure.
Safety boundaries and handover
Do not change parameters, trigger emergency stop, restart or attempt restoration simply to make status bits change. CNC power must not be cut during backup or restoration (§5.3, printed p. 356); an immediate danger to people still requires the machine’s emergency procedures. Qualified personnel must separately plan hardware replacement, restoration and motion acceptance under the applicable machine procedures.
Separate the handover into “status recorded,” “coverage checked,” “timing confirmed” and “recovery preparation awaiting approval.” Confirm only work actually completed. No specific machine or backup was tested for recoverability here. No protection bypass, parameter-writing or cross-machine restoration method is provided.
Source
FANUC Series 0i-MODEL F Maintenance Manual B-64605EN/01: §5.3, printed pp. 352–356 (coverage and AAP: 352, 355; execution and consistency: 353; protection: 353–354; diagnosis and cautions: 356). This is a third-party public mirror of a FANUC-authored manual, not an official FANUC download site.