|
MX Foundation 4
|
|
MX Foundation 4
|
This section lists all the return codes that can be returned by MXF API.
The function API mxfSystemErrorStringGet() can be used for returning from a return code a message string that is a short form of the messages in the following sections.
| Error Code | Description |
|---|---|
| MAXT_SUCCESS (0x00000000) | This error code means the success (no error) of the function call. In the case where the function only have [in] parameters, this means that the function was performed properly. For a function having [out] parameters, this means that the output information requested was returned. |
| MAXT_ERROR_MODEL (0x20000000) | The detected device is not supported or the embedded code to burn into non-volatile memory does not match the device. |
| MAXT_ERROR_LOG_CHANNEL (0x20000001) | This returned code means that no channel matching the selection was found (not detected). |
| MAXT_ERROR_TIMEOUT (0x20000002) | A timeout condition was detected. This often means that the device is not responding and needs to be reset. |
| MAXT_ERROR_COUNT (0x20000003) | This error is returned if a function received a 'count' parameter that is invalid: - a zero count was specified. - an out of range count was specified. - a string length was too small or too big. |
| MAXT_ERROR_OVERRUN (0x20000004) | The records transmitted cannot fit in the vritual link queue. The buffer queue size defined for the virtual link/subvl maxbuffs parameter may be too small. |
| MAXT_ERROR_LABEL_NOT_RECEIVED (0x20000005) | This error occurs when a call to mxfRxSamplingSingleRead() function for a label that has not been received. |
| MAXT_ERROR_WRONG_FIRMWARE (0x20000006) | The following conditions can return this error: - The firmware version does not match the library version - The signature of the firmware is bad. - The firmware file size is invalid |
| MAXT_ERROR_DEVICE_NOT_DETECTED (0x20000007) | No device has been found at MX Foundation library initialization. |
| MAXT_ERROR_OPEN_DRIVER (0x20000008) | Error opening an MXF4 driver at initialization. The software was likely not installed properly and the driver is missing. |
| MAXT_ERROR_DEVICE_ALREADY_SET (0x20000009) | Device already initialized. |
| MAXT_ERROR_INTERNAL_LOCK (0x2000000A) | An internal error occurred during the programming of a device and the verification failed or an error occurred when locking an internal resource. |
| MAXT_ERROR_INTERNAL_UNLOCK (0x2000000B) | An internal error occurred during the programming of a device or an error occurred when unlocking an internal resource. |
| MAXT_ERROR_NULLPTR (0x2000000C) | At least one parameter of the function is specifying a NULL pointer but needs to be set to a valid memory location. |
| MAXT_ERROR_PARAM (0x2000000D) | At least one parameter of the function has an invalid value. Can occur if a reserved parameter in a function or structure is not set to zero. |
| MAXT_ERROR_MEM (0x2000000E) | Stack based or heap memory allocation from the operating system failed or not enough memory. |
| MAXT_ERROR_CHANNEL (0x2000000F) | This error occurs if a function call specifies an operation that cannot be performed by the channel. For example, if an operation that can be performed only by an ARINC 429 channel is specified for another channel class, this error can be returned. |
| MAXT_ERROR_CMD (0x20000010) | An invalid command has been sent to the firmware by the library. |
| MAXT_ERROR_BUFFER_FULL (0x20000011) | Error detected in client / server mode when an excess of data was detected and the Tx/Rx buffer allocated is full. |
| MAXT_ERROR_FILENAME (0x20000012) | The filename specified is invalid or the file cannot be found. |
| MAXT_ERROR_EOF (0x20000013) | EOF character not detected in one of the MXF4 configuration file. |
| MAXT_ERROR_VER (0x20000014) | Error reading version info. |
| MAXT_ERROR_DATA (0x20000015) | Discrete data or mask is invalid. |
| MAXT_ERROR_FILEREADONLY (0x20000016) | File is read-only. |
| MAXT_ERROR_NORESPONSE (0x20000017) | No response while reading a temperature or voltage sensor. |
| MAXT_ERROR_HANDLE (0x20000018) | An invalid handle or a wrong type of handle was passed to the function. |
| MAXT_ERROR_BUFFLETNULL (0x20000019) | Internal Error. No resources available to complete the operation. |
| MAXT_ERROR_FUNCTION_NOT_IMPLEMENTED (0x2000001A) | Function not implemented or not supported for this channel. |
| MAXT_ERROR_BAD_DEVICE_ID (0x2000001C) | The device required to perform the operation does not respond or was not found. |
| MAXT_ERROR_EVENTLIST (0x2000001D) | Invalid event list handle. |
| MAXT_ERROR_EVENT_IS_SCHEDULED (0x2000001E) | The operation is not allowed when the schedule is running. |
| MAXT_ERROR_SCHED_NOT_FOUND (0x2000001F) | The schedule at the specified index does not exist. |
| MAXT_ERROR_OUT_OF_EVENT (0x20000020) | No more periodic events available. |
| MAXT_ERROR_OUT_OF_BUFFLET (0x20000021) | Out of internal buffers for performing the operation. |
| MAXT_ERROR_SIZE_FIELD (0x20000022) | The size of a field is invalid. |
| MAXT_ERROR_DEVICE_NOT_READY (0x20000023) | The device is not ready. The initialization of the device is not done. |
| MAXT_ERROR_ACK_FIRMWARE (0x20000024) | The firmware has been downloaded on the device but does not respond. |
| MAXT_ERROR_INCOMPLETE_FRAME (0x20000025) | The major frame is empty (ARINC 629). |
| MAXT_ERROR_NOT_FOUND (0x20000026) | The resource cannot be found. |
| MAXT_ERROR_NOT_INIT (0x20000027) | The device DMA is not initialized. |
| MAXT_ERROR_OUT_OF_RESOURCES (0x20000028) | Not enough resources available to complete the operation. An out-resource condition can be defined as follows: - The device has not enough memory available - An internal thread creation failed. |
| MAXT_ERROR_TOO_MANY_CONDITIONS (0x20000029) | The number of conditions defined is greater than the maximum. |
| MAXT_ERROR_TOO_MANY_ACTIONS (0x2000002A) | The number of actions for a trigger is greater than the maximum. |
| MAXT_ERROR_SEM_RESERVED (0x2000002B) | The firmware is trying to free a reserved semaphore. |
| MAXT_ERROR_NOT_SUPPORTED (0x2000002C) | General error message that specify that the operation is not supported: - by the module / device - not defined for the channel class - not supported by the current software version - not supported for the hardware port (like an attribute) |
| MAXT_ERROR_MODULE_UNKNOWN (0x2000002D) | The module specified by the calling function does not exist. |
| MAXT_ERROR_VALUE_OOR (0x2000002E) | At least one of the parameters specified by the function has a value out of range. |
| MAXT_ERROR_WRONG_VERSION (0x2000002F) | Wrong software version detected during a client / server connection or while executing a command. |
| MAXT_ERROR_ALREADY_CREATED (0x20000030) | The function call requested an operation that was already performed. For example a request for creating a bridge was already performed with the same source / destination channels and a handle was returned. |
| MAXT_ERROR_TOO_MANY_BRIDGES (0x20000031) | The number of bridges exceeds the limit of 8192. |
| MAXT_ERROR_SCHED_STARTED (0x20000032) | The operation cannot be executed because a schedule is started. This error code is returned when: - starting a schedule that is already started - adding a message to a running schedule - adding a record list to a running schedule |
| MAXT_ERROR_MON_STARTED (0x20000033) | The operation cannot be executed because the monitoring is started. |
| MAXT_ERROR_SERVICES_STARTED (0x20000034) | The operation cannot be executed because at least one service (acquisition, sampling, scheduling, ...) is started. |
| MAXT_ERROR_BAD_TERM_MODE (0x20000035) | The operation cannot be executed because the device is not configured for this mode. - For MIL-1553 SF, it can be because the operation needs to be in BC mode, but the device is in BM or RT mode. - For ARINC 629, it can be because the operation needs to transmit, but the device is in RX only mode. |
| MAXT_ERROR_INVALID_REGION (0x20000036) | The device region to read from or write to is invalid. |
| MAXT_ERROR_WRONG_DRIVER (0x20000037) | The driver version does not match the library version. |
| MAXT_ERROR_MANY_MASTER (0x20000038) | At least two devices in the same system are not synchronized. This error is a non-fatal error, meaning that the application can ignore the error and continue its execution, but the timestamps on unsynchronized device will not be in sync. Typically this error is returned when more than one device is the master. The device sync-in/sync-out should be used to daisy chain the device in a master/slave configuration. deviceinfo utility returns master/slave information for each device. You can refer to Synchronization signal chaining for more information. |
| MAXT_ERROR_DEVICE_REBOOT (0x20000039) | The device is rebooting. |
| MAXT_ERROR_NO_MODULE (0x2000003A) | There is no module at the specified index on the device. |
| MAXT_ERROR_FRAME_LABEL_NOT_FOUND (0x2000003B) | Frame label not found for the ARINC 629 protocol. |
| MAXT_ERROR_BAD_OWNER (0x2000003C) | Bad asynchronous event condition owner. |
| MAXT_ERROR_ATTACH (0x2000003D) | A function call requires that an asynchronous event handler is attached using mxfAsyncEventHandlerInit()). |
| MAXT_ERROR_BACKUPBUS_CLOCK_EN (0x2000003E) | In ASCB the backup bus is already used by the clock. |
| MAXT_ERROR_INVALID_MSGADDRESS (0x2000003F) | Invalid message address. |
| MAXT_ERROR_INVALID_MSGEXTENSION (0x20000040) | Invalid message address extension. |
| MAXT_ERROR_CHANNEL_DISABLED (0x20000041) | The channel must be enabled in order to perform the operation. |
| MAXT_ERROR_MXLIBRARY_NOT_LOADED (0x20000042) | The library was not loaded before executing the operation. |
| MAXT_ERROR_DEVICE_RESET (0x20000043) | The device has been reset. This error usually happens when another process has reset the device. |
| MAXT_ERROR_IRIGB_SLAVE_DEVICE (0x20000044) | The device must be master to perform the operation. |
| MAXT_ERROR_IRIGB_INPUT_NOT_FOUND (0x20000045) | No IRIG-B input found on the device. |
| MAXT_ERROR_IRIGB_INPUT_DISABLED (0x20000046) | The IRIG-B input must be set before performing the operation. |
| MAXT_ERROR_IRIGB_WAITING_SIGNAL (0x20000047) | The IRIG-B signal must be locked before performing the operation. |
| MAXT_ERROR_IRIGB_NO_SIGNAL (0x20000048) | No IRIG-B signal has been detected on the IRIG-B input. |
| MAXT_ERROR_INVALID_ERR_INJ_ID (0x20000049) | Error injection ID is invalid. |
| MAXT_ERROR_READ_ONLY_ATTRIB (0x2000004A) | The operation is trying to change a read-only attribute value. |
| MAXT_ERROR_CONDBRANCH_DEST_NOT_FOUND (0x2000004C) | Conditional branch does not branch to a valid destination. |
| MAXT_ERROR_BAD_HEADER_VERSION (0x2000004D) | Software internal error detected with the header versions. |
| MAXT_ERROR_INVALID_COMPUTER_TIME (0x2000004E) | The computer system time is invalid. |
| MAXT_ERROR_WRONG_BOOT (0x2000004F) | Invalid device boot version. Usually occurs when a new version of the software has been installed and needs a newer version of the boot software for the device installed. Program the device with the correct boot version. |
| MAXT_ERROR_TRIG_NOT_OCCURRED (0x20000050) | The function mxfRxAcqTrigTimeGet() was called but no event was triggered yet and the trigger time cannot be returned. |
| MAXT_ERROR_MODULE_OPT_NOT_SUPPORTED (0x20000051) | This error code is returned when the API wants to perform a function not supported on the device. |
| MAXT_ERROR_DEVICE_OPT_NOT_SUPPORTED (0x20000052) | Device option not supported. |
| MAXT_ERROR_DEVICE_TYPE_NOT_SUPPORTED (0x20000053) | Device type not supported. |
| MAXT_ERROR_SLAVE_DEVICE (0x20000054) | The function call tries to perform on a slave device something that requires a master device. |
| MAXT_ERROR_CHN_CLASS_NOT_SUPPORTED (0x20000055) | The specified channel class is not supported. |
| MAXT_ERROR_EMPTY_SCHEDULE (0x20000056) | The function call is trying to start an empty schedule. |
| MAXT_ERROR_SCHED_NOT_STARTED (0x20000057) | The function call is trying to suspend or resume a schedule that was not started. |
| MAXT_ERROR_EMPTY_MSG (0x20000058) | The function call is trying to start a schedule but the message has no record. |
| MAXT_ERROR_INVALID_RECSIZE (0x20000059) | The record size is invalid. |
| MAXT_ERROR_MSG_OVERLOAD (0x2000005A) | The time it takes to transmit the message is longer than the period. |
| MAXT_ERROR_EMPTY_REC_LIST (0x2000005B) | The operation cannot update the record list because the list is empty. |
| MAXT_ERROR_MANY_HSCHED_FOUND (0x2000005C) | The operation is trying to start a scheduler already started. |
| MAXT_ERROR_SCHED_SUSPENDED (0x2000005D) | The operation is trying to suspend a scheduler that is already suspended. |
| MAXT_ERROR_SCHED_NOT_SUSPENDED (0x2000005E) | The operation is trying to resume a scheduler that is not suspended. |
| MAXT_ERROR_MSG_SUSPENDED (0x2000005F) | The operation is trying to suspend a message that is already suspended. |
| MAXT_ERROR_MSG_NOT_SUSPENDED (0x20000060) | The operation is trying to resume a message that is not suspended. |
| MAXT_ERROR_DUPLICATED_CHANNEL (0x20000061) | The operation is trying to start twice a schedule based on the same channel. |
| MAXT_ERROR_INVALID_MODULE_VERSION (0x20000062) | The module has not the version needed to perform the operation. Usually occurs when a new version of the software has been installed and needs a newer version of the embedded software for the module installed. Program the module with the correct embedded software version. |
| MAXT_ERROR_INVALID_DATA_INDEX (0x20000063) | The data index is invalid. |
| MAXT_ERROR_CLOCK_PORT_NOT_FOUND (0x20000064) | No Tx & Rx clock port found. |
| MAXT_ERROR_CLOCK_ALREADY_USED (0x20000065) | Legacy error code because MXF_CLASS clock is not supported in MXF4. |
| MAXT_ERROR_TRANSMITTER_ENABLED (0x20000066) | The transmitter should not be enabled. |
| MAXT_ERROR_SERVICE_DISABLED_SF (0x20000067) | A required service is disabled (single function module). |
| MAXT_ERROR_EMBEDDED_CODE_SIZE (0x20000068) | The embedded code size is invalid. The MX-Embedded code size is bigger than the maximum code size allowed or the embedded application code size is bigger than 8MiB. |
| MAXT_ERROR_EMBEDDED_DATA_SIZE (0x20000069) | The embedded data size is invalid. The MX-Embedded data size is bigger than the maximum data size allowed or is 0. |
| MAXT_ERROR_INVALID_OFFSET (0x2000006A) | The offset is invalid. The offset is bigger than the MX-Embedded shared data size. |
| MAXT_ERROR_INVALID_TIMETAG (0x2000006B) | Invalid time tag error in the request. The probable causes are: - Based on the options specified for the function call, the time tag value must be zero. - Based on the options specified for the function call, the time tag value should be in the future (greater than current time). - The time tags in the array must be in chronological order. - The time tag should not be more than 30 seconds in the future (from the current time). |
(0x2000006C) | Invalid trigger option for the IPM-ADC module. |
| MAXT_ERROR_IRIGB_NOT_LOCKED (0x2000006D) | An IRIG-B signal is detected but the signal is not locked. |
| MAXT_ERROR_INVALID_INDEX (0x2000006E) | One of the parameters specifies an invalid index. |
| MAXT_ERROR_BM_STARTED (0x20000070) | The operation cannot be performed because MIL-1553 bus monitor is started. |
| MAXT_ERROR_RT_STARTED (0x20000071) | The operation cannot be performed because MIL-1553 remote terminal is started. |
| MAXT_ERROR_BC_STARTED (0x20000072) | The operation cannot be performed because MIL-1553 bus controller is started. |
| MAXT_ERROR_NO_MASTER (0x20000073) | No device in the system is master. |
| MAXT_ERROR_INVALID_CONVERSION_PERIOD (0x20000074) | Invalid conversion period for the IPM-ADC module. |
| MAXT_ERROR_HANDSHAKE_PORT_NOT_FOUND (0x20000075) | Handshake port not found. Needed to perform ASYNC flow-control operation. |
| MAXT_ERROR_HANDSHAKE_ALREADY_USED (0x20000076) | HANDSHAKE mode already enabled. |
| MAXT_ERROR_ANOTHER_PROCESS_RUNNING (0x20000077) | Another process is running and prevent this action. |
| MAXT_ERROR_SOCKET_INIT_FAILED (0x20000078) | The function used for initializing the operating system protocol stack failed. |
| MAXT_ERROR_SOCKET_NOT_FOUND (0x20000079) | While establishing a client / server communication, a communication endpoint socket was not allocated by the socket network service. |
| MAXT_ERROR_SOCKET_IOCTL_NOT_FOUND (0x2000007A) | Internal software error: an IOCTL request failed. |
| MAXT_ERROR_SOCKET_OPTION_NOT_FOUND (0x2000007B) | Internal software error: invalid socket option. |
| MAXT_ERROR_SOCKET_BIND_FAILED (0x2000007C) | Internal software error: socket bind failed. |
| MAXT_ERROR_SOCKET_LISTEN_FAILED (0x2000007D) | Internal software error: socket listen failed. |
| MAXT_ERROR_SOCKET_SEND_FAILED (0x2000007E) | Client / Server transmission error detected: likely a network problem occurred. |
| MAXT_ERROR_SOCKET_RCV_FAILED (0x2000007F) | Client / Server reception error detected: likely a network problem occurred. |
| MAXT_ERROR_SOCKET_CONN_ABORTED (0x20000080) | The communication between the client and the server was aborted. |
| MAXT_ERROR_HOSTNAME_INVALID (0x20000081) | The host name is invalid. Either the hostname refer to a non-existent host on the network or the hostname itself is invalid (empty string or greater than 128 characters). |
| MAXT_ERROR_SERVER_TOO_MANY_CONNECTIONS (0x20000082) | Maximum number of client connections allowed on a server has been reached. |
| MAXT_ERROR_CLIENT_ALREADY_CONNECTED (0x20000083) | A client tried to reconnect to a server with the same connection or tried to connect more than once locally or an exclusive client already connected on the server. |
| MAXT_ERROR_CLIENTSERVER_CMD (0x20000084) | Client / Server command not supported. |
| MAXT_ERROR_CLIENTSERVER_CMD_SIGNATURE (0x20000085) | The command received by the server has an invalid signature. |
| MAXT_ERROR_CLIENTSERVER_CMD_SIZE (0x20000086) | The command received by the server was smaller than the minimum expected. |
| MAXT_ERROR_FILE_READING (0x20000087) | An error occurred when reading a file. |
| MAXT_ERROR_FILE_WRITING (0x20000088) | An error occurred when writing a file. |
| MAXT_ERROR_FILE_CRC (0x20000089) | The CRC value of the file is invalid. The file may be corrupted. |
| MAXT_ERROR_FILE_FORMAT (0x2000008A) | The file format is invalid. This error can occur when: - the file signature is invalid - the file is empty - the file size is invalid |
| MAXT_ERROR_FILE_OPEN (0x2000008B) | Error opening a file. Probably the file (filename) does not exist. |
| MAXT_ERROR_FILE_SAVE (0x2000008C) | Error saving a file on the disk. Likely no enough room on the operating system or directory security protection. |
| MAXT_ERROR_FILE_NOT_FOUND (0x2000008D) | - The file cannot be flashed because the file is not found. - The EPROM programming failed because the file was not found. - When a standalone file is generated the file was not found. - A file to be downloaded to the server (MXF_DEVICE_FILE_UPLOAD) was not found. |
| MAXT_ERROR_USERNAME (0x2000008E) | The username is invalid. For remote connection, verify that the username is defined in the server configuration file mxf_server_passwd.conf. |
| MAXT_ERROR_PASSWORD (0x2000008F) | The password is invalid. For remote connection, verify that the password defined in the server configuration file mxf_server_passwd.conf matches the username. |
| MAXT_ERROR_NVSTORAGE_NOT_FOUND (0x20000090) | No non-volatile storage auto-detected on the board. |
| MAXT_ERROR_NVSTORAGE_INIT (0x20000091) | Error with initialization of non-volatile storage. |
| MAXT_ERROR_NVSTORAGE_OUT_OF_SECTORS (0x20000092) | This error can occur during a file creation if there is not enough room to allocated the file. |
| MAXT_ERROR_NVSTORAGE_OUT_OF_FILES (0x20000093) | This error can occur during a file creation if more than 64 files are allocated. |
| MAXT_ERROR_NVSTORAGE_MOUNT (0x20000094) | Cannot mount the flash storage device. |
| MAXT_ERROR_NVSTORAGE_IOREQ (0x20000095) | Flash IO request failed: operation not performed. |
| MAXT_ERROR_NVSTORAGE_READ (0x20000096) | Error reading sectors on the flash storage. |
| MAXT_ERROR_NVSTORAGE_WRITE (0x20000097) | Error writing data to the flash storage. |
| MAXT_ERROR_NVSTORAGE_FORMAT (0x20000098) | The flash format failed: likely bad chip fitted. |
| MAXT_ERROR_NVSTORAGE_HEADER_SIGNATURE (0x20000099) | The file system first sector does not have the right signature. The flash is probably not formatted. |
| MAXT_ERROR_NVSTORAGE_HEADER_VERSION (0x2000009A) | Invalid flash header version: - The flash header can be corrupted and the flash needs to be reformatted. - A new version of the MXF software was installed and the flash need to be reformatted. |
| MAXT_ERROR_NVSTORAGE_HEADER_CRC (0x2000009B) | Flash CRC error detected: flash not formatted or corrupted. |
| MAXT_ERROR_NVSTORAGE_NOT_FORMATTED (0x2000009C) | Non-volatile storage (flash) not formatted. The flash must be formatted before allocating file and writing to the files. |
| MAXT_ERROR_NVSTORAGE_MSGFILE_NOT_EMPTY (0x2000009D) | The application is trying to assign a message type to a file that is not empty (not a new file). |
| MAXT_ERROR_NVSTORAGE_MSGFILE_INVALID_INDEX (0x2000009E) | The file specified by the index does not exist. |
| MAXT_ERROR_NVSTORAGE_MSGFILE_OVERFLOW (0x2000009F) | The service cannot allocate another flash sector for writing to the file: the file is full. If more room is required reallocate the file with a bigger size if necessary. |
| MAXT_ERROR_NVSTORAGE_MSGTYPE_INVALID (0x200000A0) | The application cannot assign this message type to the flash file: the type value is invalid. |
| MAXT_ERROR_NVSTORAGE_MSGFILE_STARTED (0x200000A1) | The application is trying to format the file but some files are still opened. |
| MAXT_ERROR_DMA_D2H_FAILED (0x200000A2) | This error occurs when a transmission on a DMA channel failed: likely an hardware error. |
| MAXT_ERROR_DMA_H2D_FAILED (0x200000A3) | This error occurs when a transmission on a DMA channel failed: likely an hardware error. |
| MAXT_ERROR_SENSOR_NOT_FOUND (0x200000A4) | The sensor(s) specified by the function call is not defined. |
| MAXT_ERROR_IP_ADDRESS_INVALID (0x200000A5) | The IPv4 network address is invalid. |
| MAXT_ERROR_IP_NETMASK_INVALID (0x200000A6) | The IPv4 network mask is invalid. |
| MAXT_ERROR_TIMEBASE_INVALID (0x200000A7) | The parameter timebase has an invalid value. |
| MAXT_ERROR_EVENT_EMPTY (0x200000A8) | The event list is empty. At least one record must be added to the event. |
| MAXT_ERROR_STARTTIME_INVALID (0x200000A9) | Invalid start time for a write function call. |
| MAXT_ERROR_FLAGS_INVALID (0x200000AA) | Invalid flags bits value in the flag parameter. |
| MAXT_ERROR_BUFFER_ALLOCATED (0x200000AB) | The buffer is already allocated. |
| MAXT_ERROR_BUFFER_NOT_ALLOCATED (0x200000AC) | The buffer is not allocated and must be allocated for the operation to be executed. |
| MAXT_ERROR_BUFFER_NOT_EMPTY (0x200000AD) | The buffer must be empty for the operation to be executed. |
| MAXT_ERROR_WAITONCOND_INVALID (0x200000AE) | The wait on condition option specified for mxfTxPeriodicMajorFrameSet() is invalid. |
| MAXT_ERROR_RESET_NEEDED (0x200000AF) | The device needs to be reset. |
| MAXT_ERROR_PARAM_SIZE (0x200000B0) | The parameter size of the network command is bigger than the network transaction buffer. |
| MAXT_ERROR_NIC_NOT_FOUND (0x200000B1) | No network interface detected on the device. |
| MAXT_ERROR_TOO_MANY_MSG (0x200000B3) | The maximum number of messages has been reached. |
| MAXT_ERROR_EMBEDDED_STARTED (0x200000B4) | The function call failed because an embedded application is running. Many host functions are not allowed when an embedded application is running. |
| MAXT_ERROR_EMBEDDED_APP (0x200000B5) | The embedded application did not start or did not load MX Foundation library in a timely fashion. Maybe the embedded application is corrupted. |
| MAXT_ERROR_MANY_LIB_LOADED (0x200000B6) | More than one host application is running when uploading an embedded application. |
| MAXT_ERROR_OPT_NOT_ENABLED (0x200000B7) | The operation failed because it needed an option to be enabled. For example, the KMXF_DEVICE_IRIGB_YEAR_RANGE_MIN attribute needs the KMXF_DEVICE_IRIGB_YEAR_DECODING_ENABLE attribute to be enabled. |
| MAXT_ERROR_RELOAD_NEEDED (0x200000B8) | The library needs to reloaded. |
| MAXT_ERROR_LIB_LOADED (0x200000B9) | The library must not be loaded to call this function. |
| MAXT_ERROR_CTRL (0x200000BA) | The control field of the data record is invalid. |
| MAXT_ERROR_SERVER_NOT_FOUND (0x200000BB) | The connection failed with the specified network server address. Verify the network configuration. |
| MAXT_ERROR_TOO_MANY_HANDLES (0x200000BC) | This error occurs when the server cannot allocate more handles to an application. |
| MAXT_ERROR_ALREADY_ATTACHED (0x200000BD) | An asynchronous event handler has already been attached. |
| MAXT_ERROR_MAC_ADDRESS_INVALID (0x200000BE) | This problem occurs when setting the MAC address: the LSB = 0 or LSB > 65535. |
| MAXT_ERROR_USER_PRIVILEGE (0x200000BF) | The user privilege is invalid or the user does not have the privileges to perform the operation. |
| MAXT_ERROR_USER_CONN_EXCLUSIVE (0x200000C0) | During a client / server connection, three conditions can return this error: - a client with user privileges did not connect with exclusive parameter set to TRUE. - a client with advanced privileges and exclusive parameter set to TRUE cannot connect because another client is already connected. - the exclusive parameter is invalid (neither TRUE or FALSE). |
| MAXT_ERROR_TYPE_INVALID (0x200000C1) | The specified type is invalid. |
| MAXT_ERROR_NETWORK_TIMEOUT (0x200000C2) | A command was sent to the server applications but no response was received. The application should reconnect to the server. |
| MAXT_ERROR_REPEAT_COUNT (0x200000C3) | The repeat count field of the data record is invalid. |
| MAXT_ERROR_ADDRESS_OOR (0x200000C4) | The address is out of range. |
| MAXT_ERROR_NOT_CONNECTED (0x200000C5) | The client application is not connected. mxfServerConnect() function should be called first. An invalid server handle can also return this condition. |
| MAXT_ERROR_MXF_NOT_FOUND (0x200000C6) | Problem loading a system file at initialization. The firmware file was not found or the file is empty. You probably need to reinstall the software. |
| MAXT_ERROR_NETWORK_CONNECTION (0x200000C7) | Server connection could not be established. Network configuration could cause this condition (ex: firewall does not allow the connection). |
| MAXT_ERROR_INVALID_MAJORFRAME (0x200000C8) | The major frame is invalid. Usually, this means that the major frame index is invalid and not set to zero. |
| MAXT_ERROR_INVALID_MINORFRAME (0x200000C9) | The minor frame is invalid. Usually, this means that the minor frame index is invalid (bigger than the maximum number of minor frames allowed) or that the branch index points to an invalid minor frame index. |
| MAXT_ERROR_INVALID_MODULO (0x200000CA) | Invalid modulo value. |
| MAXT_ERROR_NOT_SINGLE_MSG (0x200000CB) | The mxfTxPeriodicScheduleSingleMsgUpdate() function has been called for a message that has more than one record. |
| MAXT_ERROR_INVALID_DELAY (0x200000CC) | The delay is invalid (MXF_MIL1553_DATAREC.service.txAperiodic.delay). |
| MAXT_ERROR_EMBEDDED_HANDLER_NOT_FOUND (0x200000CD) | At least one of the mandatory MX Embedded handler has not been found in the MX Embedded application. Make sure the following callbacks are implemented in the MX Embedded application: - mxfEmbeddedCommandHandler() - mxfEmbeddedDataDownloadHandler() - mxfEmbeddedRxIntHandler() - mxfEmbeddedTxPeriodicUpdateMsgIntHandler() - mxfEmbeddedTimerHandler() |
| MAXT_ERROR_EMBEDDED_CODE_NOT_DOWNLOADED (0x200000CE) | The operation cannot be executed because no MX-Embedded application has been downloaded on the device. |
| MAXT_ERROR_DATA_INDEX_NOT_SUPPORTED (0x200000CF) | The operation cannot be executed because the buffer has never been assigned. |
| MAXT_ERROR_PORT_NOT_FOUND (0x200000D0) | The self-test port index is invalid. No port exists at that port index. |
| MAXT_ERROR_LEVEL_NOT_SUPPORTED (0x200000D1) | The self-test level is invalid. |
| MAXT_ERROR_ZONE (0x200000D2) | The self-test zone is invalid. |
| MAXT_ERROR_LOOPBACK_NOT_SUPPORTED (0x200000D3) | The self-test internal loopback is not supported. |
| MAXT_ERROR_INVALID_FILE (0x200000D4) | MX Embedded application is invalid. |
| MAXT_ERROR_TOO_MANY_DEVICES (0x200000D5) | The maximum of 16 devices locally installed has been exceeded. |
| MAXT_ERROR_OPT_DISABLED (0x200000D6) | Options is disabled. Usually means that an attribute depends on another attribute which is currently disabled. |
| MAXT_ERROR_INVALID_MODE (0x200000D7) | Pulse mode is invalid. |
| MAXT_ERROR_INVALID_DURATION (0x200000D8) | Pulse duration is invalid. |
| MAXT_ERROR_BUFFER_TOO_SMALL (0x200000D9) | The buffer is too small. Can happen if the buffer size to contain a string is smaller than the string to copy. |
| MAXT_ERROR_INVALID_BIT_INDEX (0x200000DA) | The bit index is invalid. In A708, verify MXF_A708_DATAREC.manchesterBitErr field value. |
| MAXT_ERROR_RESOURCE_BUSY (0x200000DB) | Resource busy. |
| MAXT_ERROR_PERMISSIONS (0x200000DC) | Access denied (insufficient permissions). |
| MAXT_ERROR_INTERRUPT (0x200000DD) | System call interrupted (perhaps due to signal). |
| MAXT_ERROR_PIPE (0x200000DE) | Pipe error. |
| MAXT_ERROR_IO (0x200000DF) | Input/output error. |
| MAXT_ERROR_CLOSE (0x200000E0) | The file is not yet closed. |
| MAXT_ERROR_ALREADY_INSTALLED (0x200000E1) | Already installed. |
| MAXT_ERROR_PACKAGE_SIZE (0x200000E2) | The package size is invalid. |
| MAXT_ERROR_SHARED_EVENT (0x200000E3) | Error with shared event. |
| MAXT_ERROR_BUFFER_EMPTY (0x200000E4) | The buffer is empty. |
| MAXT_ERROR_DISK_SPACE (0x200000E5) | Low Disk Space. |
| MAXT_ERROR_NVSTORAGE_UMOUNT (0x200000E6) | Non-Volatile Storage unmount failed. |
| MAXT_ERROR_NVSTORAGE_FSCHK (0x200000E7) | Non-Volatile Storage file system error found. |
| MAXT_ERROR_INFO (0x200000E8) | Invalid INFO Field. |
| MAXT_ERROR_ID (0x200000E9) | Invalid ID Field |
| MAXT_ERROR_DLC (0x200000EA) | Invalid DLC Field. |
| MAXT_ERROR_DOMAIN (0x200000EB) | Invalid domain. |
| MAXT_ERROR_SOCKET_TYPE (0x200000EC) | Invalid socket type. |
| MAXT_ERROR_PROTOCOL (0x200000ED) | Invalid socket protocol. |
| MAXT_ERROR_ADDRESS_IN_USE (0x200000EE) | Address already in use. |
| MAXT_ERROR_STACK (0x200000EF) | Internal logic error. |
| MAXT_ERROR_SUBVL (0x200000F0) | Invalid subvl. |
| MAXT_ERROR_VL_IN_USE (0x200000F1) | Virtual link already created. |
| MAXT_ERROR_BAG (0x200000F2) | Invalid 'bag' value. |
| MAXT_ERROR_MESSAGE_SIZE (0x200000F3) | Invalid message size: - MAX_UDP_PAYLOAD > 8192. - Payload UDP exceeds the maximum defined for an ARINC frame or EDE frame. - The data PDU is likely bigger than the buffer size allocated. - The TX fragmentation is disabled and a frame needs to be segmented. |
| MAXT_ERROR_LMAX (0x200000F4) | Lmax value > Ethernet frame size. |
| MAXT_ERROR_LMIN (0x200000F5) | Lmin value < minimum Ethernet frame size. |
| MAXT_ERROR_BUFFER_SIZE (0x200000F6) | Invalid buffer size. |
| MAXT_ERROR_PORT (0x200000F7) | Invalid port/interface number. |
| MAXT_ERROR_NOT_BINDED (0x200000F8) | VL/SubVL not binded (closed and available). |
| MAXT_ERROR_PATH_DOWN (0x200000F9) | VL TX/RX path disabled: frame discarded. |
| MAXT_ERROR_THREAD_FAILED (0x200000FA) | Thread startup failed. |
| MAXT_ERROR_SKEW_MAX (0x200000FB) | Invalid skewmax 'value'. |
| MAXT_ERROR_VL_FULL (0x200000FC) | Number of VL greater than 1024. |
| MAXT_ERROR_NOT_RUNNING (0x200000FD) | The protocol stack entity is not initialized. |
| MAXT_ERROR_SN_RANGE (0x200000FE) | Sequence Number Range Error. |
| MAXT_ERROR_MODE (0x200000FF) | Invalid mode value. |
| MAXT_ERROR_PORT_ACTIVE (0x20000100) | Port is active. In A664, a receive port is active for the VL. You are probably trying to create a COM/SAP port with an address (ip,port) already registered for another port. |
| MAXT_ERROR_PRIORITY (0x20000101) | Invalid queue specified. |
| MAXT_ERROR_NO_HANDLER (0x20000102) | No handler was defined. |
| MAXT_ERROR_VLID (0x20000103) | VLID parameter error. |
| MAXT_ERROR_FRAME_TYPE (0x20000104) | Invalid frame type value. |
| MAXT_ERROR_DIRECTION (0x20000105) | Invalid direction value. |
| MAXT_ERROR_SN_LAG (0x20000106) | EDE: Invalid SN lag value. |
| MAXT_ERROR_SID (0x20000107) | Invalid Source ID. |
| MAXT_ERROR_PORT_FULL (0x20000108) | COM/SAP port table full. |
| MAXT_ERROR_BUFNUM (0x20000109) | Invalid number of buffers specified. |
| MAXT_ERROR_COND_ALREADY_SET (0x2000010A) | Error condition already set. |
| MAXT_ERROR_SAMPLING_RATE (0x2000010B) | Sampling rate value error. |
| MAXT_ERROR_PORT_TYPE (0x2000010C) | Invalid port type value. |
| MAXT_ERROR_PROTOCOL_FAMILY (0x2000010D) | Invalid protocol family value. |
| MAXT_ERROR_NETSELECT (0x2000010E) | Invalid Net Selection. |
| MAXT_ERROR_OPTION (0x2000010F) | Invalid Option. |
| MAXT_ERROR_FRAGMENTATION (0x20000110) | Invalid Fragmentation/Reassembly parameter. |
| MAXT_ERROR_FILTERS_NOT_SUPPORTED (0x20000111) | Filter not supported. |
| MAXT_ERROR_JUMPER_DETECTED (0x20000112) | A jumper has been detected and prevents the modification. |
| Warning Code | Description |
|---|---|
| MAXT_WARNING_MANY_MASTER (0x30000000) | At least two devices in the same system are not synchronized. The timetags on un-synchronized device will not be in sync. Typically this warning is returned when more than one device is master. The device sync-in/sync-out should be used to daisy chain the device in a master/slave configuration. deviceinfo utility return master/slave information for each device. |
| MAXT_WARNING_NO_MODULE (0x30000001) | During the software initialization no module was auto-detected. |
| MAXT_WARNING_DEVICES_NOT_SYNCHRONIZED (0x30000002) | In a system with more than one device, the timer of at least one device is not synchronized with the others. |
| MAXT_WARNING_NEWER_BOOT (0x30000003) | A newer boot is available but the library does not require it. |
| MAXT_WARNING_MANY_BOOT_VERSION (0x30000004) | In a system with more than one devices, the devices of the same series do not all run with the same boot version. |
