Possible CoLa errors.
Enumerator |
---|
NETWORK_ERROR | Network error (not sent with messages).
|
OK | No error.
|
METHOD_IN_ACCESS_DENIED | Wrong userlevel, access to method not allowed.
|
METHOD_IN_UNKNOWN_INDEX | Trying to access a method with an unknown Sopas index.
|
VARIABLE_UNKNOWN_INDEX | Trying to access a variable with an unknown Sopas index.
|
LOCAL_CONDITION_FAILED | Local condition violated, e.g. giving a value that exceeds the minimum or maximum allowed value for this variable.
|
INVALID_DATA | Invalid data given for variable, this errorcode is deprecated (is not used anymore)
|
UNKNOWN_ERROR | An error with unknown reason occurred, this errorcode is deprecated.
|
BUFFER_OVERFLOW | The communication buffer was too small for the amount of data that should be serialised.
|
BUFFER_UNDERFLOW | More data was expected, the allocated buffer could not be filled.
|
ERROR_UNKNOWN_TYPE | The variable that shall be serialised has an unknown type. This can only happen when there are variables in the firmware of the device that do not exist in the released description of the device. This should never happen.
|
VARIABLE_WRITE_ACCESS_DENIED | It is not allowed to write values to this variable. Probably the variable is defined as read-only.
|
UNKNOWN_CMD_FOR_NAMESERVER | When using names instead of indices, a command was issued that the nameserver does not understand.
|
UNKNOWN_COLA_COMMAND | The CoLa protocol specification does not define the given command, command is unknown.
|
METHOD_IN_SERVER_BUSY | It is not possible to issue more than one command at a time to an SRT device.
|
FLEX_OUT_OF_BOUNDS | An array was accessed over its maximum length (the famous 0xE)
|
EVENT_REG_UNKNOWN_INDEX | The event you wanted to register for does not exist, the index is unknown.
|
COLA_VALUE_UNDERFLOW | The value does not fit into the value field, it is too large.
|
COLA_A_INVALID_CHARACTER | Character is unknown, probably not alphanumeric (CoLaA only).
|
OSAI_NO_MESSAGE | Only when using SRTOS in the firmware and distributed variables this error can occur. It is an indication that no operating system message could be created. This happens when trying to GET a variable
|
OSAI_NO_ANSWER_MESSAGE | This is the same as OsaiNoMessage with the difference that it is thrown when trying to PUT a variable.
|
INTERNAL | Internal error in the firmware, probably a pointer to a parameter was null.
|
HUB_ADDRESS_CORRUPTED | The Sopas Hubaddress is either too short or too long.
|
HUB_ADDRESS_DECODING | The Sopas Hubaddress is invalid, it can not be decoded (Syntax).
|
HUB_ADDRESS_ADDRESS_EXCEEDED | Too many hubs in the address.
|
HUB_ADDRESS_BLANK_EXPECTED | When parsing a HubAddress an expected blank was not found. The HubAddress is not valid.
|
ASYNC_METHODS_ARE_SUPPRESSED | An asynchronous method call was made although the device was built with "AsyncMethodsSuppressed". This is an internal error that should never happen in a released device.
|
COMPLEX_ARRAYS_NOT_SUPPORTED | Device was built with "ComplexArraysSuppressed" because the compiler does not allow recursions. But now a complex array was found. This is an internal error that should never happen in a released device.
|
SESSION_NO_RESOURCES | CoLa2 session can not be created, no more sessions available.
|
SESSION_UNKNOWN_ID | The CoLa2 session id is not valid, either it timed out or it never existed.
|
CANNOT_CONNECT | Requested connection (probably to a Hub Device) could not be established.
|
INVALID_PORT | The given PortId (for routing a CoLa2 telegram) does not exist.
|
SCAN_ALREADY_ACTIVE | A UDP Scan is already running.
|
OUT_OF_TIMERS | There are no more timer objects available (for SOPAS Scan).
|
WRITE_MODE_NOT_ENABLED | It is currently not allowed to write to the device, it is in RUN mode.
|
SET_PORT_FAILED | Internal error with SOPAS Scan.
|
IO_LINK_FUNC_TEMP_NOT_AVAILABLE | IoLink error: function temporarily not available.
|
UNKNOWN | Unknown error, internally thrown if SOPAS Scan received an unknown command.
|