ERROR#060
This error occurs when the user has attempted to utilize more variable DSP resources 
than are available. This may occur if too many matrix crosspoints are unmuted or too 
many parametric EQ filters are enabled. The 
DSPLOAD command can query the 
current percentage utilization of DSP resources. 
ERROR#070
This error occurs as a result of a macro or preset execution command (
PRESETX, 
PRESETQ, MACROX, MACROQ). It indicates that the macro or preset requested was 
empty. 
ERROR#071
This error occurs as a result of a 
PRESETW or PRESETK command. In the case of 
PRESETW it indicates that an attempt was made to write to a factory preset, which is 
not allowed. In the case of 
PRESETK, it indicates that an attempt was made to delete 
a factory preset, which is not allowed. 
ERROR#072
This error occurs as a result of a 
PRESETQ command. It indicates that one or more 
commands in the preset had errors during execution. 
ERROR#073
This error occurs as a result of a 
MACROA command when there are already too many 
commands in the macro. The limit is 256 commands per macro. 
ERROR#074
This error occurs in response to a 
MACROA or a logic pin (LIA, LIH, etc.) command. 
If the command written to the macro or logic pin is illegal, then this error occurs. 
ERROR#075
This error occurs when a command attempts to write non-volatile memory, but non-
volatile memory is password protected via 
NVLOCK. 
ERROR#076
This error occurs when attempting to add a macro command (either during an upload 
or while writing a single macro) and the Vortex runs out of room in non-volatile 
memory. As a result, the entire macro is discarded. If this occurs during an upload, 
all previous macros (before the one that caused the error) are written successfully. 
ERROR#077
This error occurs when attempting to add a command to a macro, but the Vortex is 
not in the process of writing a macro. This may happen if you forget to do a MACROS 
or UMACROS command, or if you had an ERROR#076 and continued trying to add 
commands. 
ERROR#090
This error indicates an EF Bus hardware handshaking error. This could happen if 
bussed units are not powered on simultaneously. Powering the units up 
simultaneously should remove the error. 
ERROR#091
This error indicates an EF Bus software handshaking error. This could happen if 
bussed units are not powered on simultaneously. Powering the units up 
simultaneously should remove the error. 
ERROR#092
This error indicates an EF Bus ID conflict. See the Vortex user manual for information 
on valid device IDs. 
This command is a boolean command. See 
Section 6.1 for more information on this type of command. 
This command is saved to global non-volatile memory and is not part of a preset. Its value is saved 
each time it is changed. It will retain its value after power-down. Since this command writes to non-
volatile memory, there will be a delay before an acknowledgment is returned. 
Example Description Status Message
T01ERROR1
Enable error messages.
T01ERROR1