F01082 — Parameter error when powering up from data backup

F01082 reports that the drive found a parameterizing error while it was powering up from the data backup — typically an incorrect parameter value. The message itself names the affected parameter, its index and the fault cause; the same three values are coded in the fault value the drive stores in r0949. Because parameter limits can depend on other parameters, the real reason a stored value is rejected is only visible there.

• A parameterizing error was detected during power-up from the data backup, for example a parameter value that is incorrect for the current configuration.
• Parameter limits can depend on other parameters, so a value stored in the backup may fall outside the limits that apply at power-up, even though it was accepted when it was saved.

1. Read the fault value in r0949, interpreting it as a hexadecimal number, and decode the parameter number, the index and the fault cause from it.
2. Open the indicated parameter and enter the correct value in it.
3. If the value is rejected because of its limits, identify the parameter that restricts the limits of the specified parameter and correct that one first.
4. Alternatively, correct the parameterization in the commissioning tool and download the project to the drive again.

Read r0949 as a hexadecimal value in the layout ccbbaaaa hex: aaaa is the parameter number, bb the index and cc the cause of the parameter error. The causes that matter most after restoring a data backup are:

• cc = 0: parameter number illegal; cc = 25: the drive object does not exist.
• cc = 2: lower or upper value limit exceeded; cc = 200/201: value below or above the valid values.
• cc = 1, 6 or 7: the value, a setting (6: only resetting) or a descriptive element cannot be changed.
• cc = 5, 22 or 23: data type, parameter address or format incorrect.
• cc = 107: write access not permitted while the controller is enabled.
• cc = 109 to 118: write access only in a particular commissioning state of p0010, e.g. 112 — quick commissioning (p0010 = 1) or 114 — parameter reset (p0010 = 30).
• cc = 120 to 127: the same restriction at device level via p0009, e.g. 123 — device configuration (p0009 = 1).
• cc = 119 or 129: the parameter may not be written in a download.
• cc = 130 to 132: transfer of the master control inhibited via binector input p0806, a required BICO interconnection not possible, or free BICO interconnections inhibited via p0922.
• cc = 202/203: no access or no read access from the Basic Operator Panel (BOP); cc = 204: write access not permitted.

The manual lists further, rarer causes in the same scheme.

• r0949 — holds the fault value for this fault; interpreted hexadecimal it yields the parameter number (aaaa), the index (bb) and the fault cause (cc) in the layout ccbbaaaa hex.
• p0010 — for causes 109 to 118 the indicated parameter can only be written with this drive parameter filter in the required commissioning state, for example quick commissioning (p0010 = 1).
• p0009 — for causes 120 to 127 the value can only be entered with this device parameter filter in the required state.
• p0806 — fault cause 130: transfer of the master control is inhibited via this binector input, so check its interconnection before writing the value again.
• p0922 — fault cause 132: free BICO interconnections are inhibited via this telegram selection.

Enter the correct value in the parameter named by the fault value — or correct the parameterization in the commissioning tool and download the project again — then acknowledge the fault so the drive can restart. If the write is refused once more, decode the new fault cause in r0949 first: many causes only permit write access in a specific commissioning state of p0010 or p0009.