F07082 — Macro: Execution not possible

F07082 is raised when a macro — a stored macro file that the drive executes and which sets a series of parameters — is started and cannot be executed. The macro is started via a trigger parameter; the manual's cross-reference for this fault names the macro parameters p0015 (Macro drive unit), p0700 (Macro BI), p1000 (Macro CI n_set) and p1500 (Macro CI M_set). When execution fails, the drive stores which parameter it was working on and why the file check or the parameter write failed; the fault value in r0949 decodes this information.

• The macro cannot be executed. The cause lies either in the trigger parameter itself — the file called for it is not valid, or a TAG in the file has an incorrect data type — or in one of the parameters the macro wants to set.
• Errors on the parameters to be set range from an undefined error level or mode, through writes the drive refuses (a read-only or unavailable parameter, an impermissible write via macro, a BICO interconnection whose source parameter cannot be determined, wrong or missing index usage, an invalid bit operation), to a factory setting for DEVICE executed somewhere other than the DEVICE and a value setting that failed. The numbered list in the fault value identifies the exact cause.

1. Read the fault value in r0949 as a hexadecimal number: cccc gives the preliminary parameter number — the parameter the macro was processing when it failed — bb the supplementary information and aa the fault cause.
2. Look up the fault cause (aa) in the decoding below; it shows whether the problem is in the trigger parameter itself or in a parameter the macro wanted to set.
3. Check the parameter involved.
4. Check the macro file and the BICO interconnection.
5. Check the macro parameters p0015, p0700, p1000 and p1500 that the remedy cross-references.

The message value consists of three placeholders: the fault cause, the supplementary information and the preliminary parameter number. The same information is stored in the fault value r0949; interpreted hexadecimal, it has the layout ccccbbaa:

• cccc = preliminary parameter number
• bb = supplementary information
• aa = fault cause

Fault causes for the trigger parameter itself:

• 19: Called file is not valid for the trigger parameter.
• 20: Called file is not valid for parameter 15.
• 21: Called file is not valid for parameter 700.
• 22: Called file is not valid for parameter 1000.
• 23: Called file is not valid for parameter 1500.
• 24: Data type of a TAG is incorrect (e.g. Index, number or bit is not U16).

Fault causes for the parameters to be set:

• 25: Error level has an undefined value.
• 26: Mode has an undefined value.
• 27: A value was entered as string in the tag value that is not "DEFAULT".
• 31: Entered drive object type unknown.
• 32: A device was not able to be found for the determined drive object number.
• 34: A trigger parameter was recursively called.
• 35: It is not permissible to write to the parameter via macro.
• 36: Check, writing to a parameter unsuccessful, parameter can only be read, not available, incorrect data type, value range or assignment incorrect.
• 37: Source parameter for a BICO interconnection was not able to be determined.
• 38: An index was set for a non-indexed (or CDS-dependent) parameter.
• 39: No index was set for an indexed parameter.
• 41: A bit operation is only permissible for parameters with the parameter format DISPLAY_BIN.
• 42: A value not equal to 0 or 1 was set for a BitOperation.
• 43: Reading the parameter to be changed by the BitOperation was unsuccessful.
• 51: Factory setting for DEVICE may only be executed on the DEVICE.
• 61: The setting of a value was unsuccessful.

• r0949 (Fault value): read the fault value here and interpret it hexadecimal — its layout ccccbbaa holds the preliminary parameter number, the supplementary information and the fault cause of the failed macro.
• p0015 (Macro drive unit): macro trigger parameter — check it when the fault cause states that the called file is not valid for parameter 15.
• p0700 (Macro Binector Input (BI)): macro trigger parameter — check it when the fault cause states that the called file is not valid for parameter 700.
• p1000 (Macro Connector Inputs (CI) for speed setpoints): macro trigger parameter — check it when the fault cause states that the called file is not valid for parameter 1000.
• p1500 (Macro Connector Inputs (CI) for torque setpoints): macro trigger parameter — check it when the fault cause states that the called file is not valid for parameter 1500.

The fault can be acknowledged immediately — an acknowledgement is the only reset action, since the drive does not take any automatic reaction to this fault. Correct the parameter or the macro file identified by the fault value before triggering the macro again.