Descriptions of Error Messages / Return Values

A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z

General Return Values

MPIMessageOK
The operation was successful. This message code is returned by a method when the operation completed successfully. If a message code other than MPIMessageOK is returned by a method, then an error occurred or operation status information is being reported. Check return values from ALL method calls. The only exceptions are methods that return object handles. For example, the mpiObjectCreate(...) methods return a handle to an object.

MPIMessageARG_INVALID
An argument is not valid. This message code is returned by a method when one or more arguments fail an integrity check. The following integrity checks are made, depending on the argument types:
- Pointers and addresses are not NULL.
- Memory addresses are within a valid range.
- Object maps have a valid number of members.

MPIMessagePARAM_INVALID
A parameter is not valid. Parameters are the data inside an argument. This message code is returned by a method when one or more parameters fail an integrity check. The following integrity checks are made, depending on the parameter types:
- Pointers and addresses in structures are not NULL.
- Memory addresses in structures are within a valid range.
- Object numbers are within a valid range.
- Values in structures are within a valid range.

MPIMessageHANDLE_INVALID
An object handle is not valid. This message code is returned by a method when the object handle argument is NULL. To correct this problem, create an object using an object create method. For example, to create an axis object use mpiAxisCreate(...).

MPIMessageNO_MEMORY
Memory is not available. This message code is returned by a method when an object, thread or buffer is not created due to a memory allocation failure. All host memory allocation occurs through mpiPlatformAlloc(...). To correct this problem, check your host computer resources and remove unused components or add more memory.
NOTE: Some methods may make several memory allocations or may call other methods that allocate memory. If a memory allocation fails, the previous allocations will not be freed.

MPIMessageOBJECT_FREED
The object has been freed. This message code is set within the object when the object is deleted. This message code is used internally. This message code is returned by an object delete method if the object has already been deleted. To prevent this problem, make sure to delete objects only one time.

MPIMessageOBJECT_NOT_ENABLED
The object is not active in the controller. This message code is returned by a method if real-time data or a handshake is required between the MPI and the controller, and the specified object is not enabled in the controller. To correct this problem, use mpiControlConfigSet(...) to enable the object, by setting the object count to greater than the specified object number. For example, to enable motor objects 0 to 3, set motorCount to 4.

MPIMessageOBJECT_NOT_FOUND
The object is not found on an object list. This message code is returned by a method when an object does not exist on the specified list or the object list does not exist. This message code can be returned from methods that insert or remove objects from a list. To correct this problem, specify an object that exists on the list or specify a different object list containing the object. To prevent object creation/deletion problems, delete objects in the reverse order they were created.

MPIMessageOBJECT_ON_LIST
The object is a member of a list. This message code is returned when a method tries to add an object to a list and the object already exists on the list. It is also returned when a method tries to delete an object when the object exists on a list. For example, if an axis object is a member of a list of axis objects or an axis object is associated with a motion object, calling mpiAxisDelete(...) will return the object on list message code. To correct this problem when adding an object to a list, check to make sure the object is not already a member. To correct this problem when deleting an object, remove the object from the list and delete the parent object. To prevent object creation/deletion problems, delete objects in the reverse order they were created.

MPIMessageOBJECT_IN_USE
This message is returned when an operation cannot be completed because the object is currently in use. For example, when threadDelete(…) from the apputil library attempts to delete a thread that is currently running, MPIMessageOBJECT_IN_USE will be returned. To correct this problem, make sure the object is not in use before you attempt the operation.

MPIMessageTIMEOUT
The wait time has expired. This message code is returned by a method waiting for a response from the controller, a hardware resource, or a semaphore lock and the maximum wait time value expired. The library uses timeout values to prevent lock-up conditions when unexpected behavior occurs. To correct this problem, check the hardware health, power, and network connections.

MPIMessageUNSUPPORTED
The software or controller does not support a feature. This message code is returned by a method if the MPI library, controller, or network device does not support a feature.

MPIMessageFATAL_ERROR
The software or hardware failed. This message code is returned by a method when an inexplicable data value is read from the controller or host memory. This message code indicates a serious problem with the host computer, memory, or controller. Contact an MEI applications engineer if you receive this message code.

MPIMessageFILE_CLOSE_ERROR
An error occurred when closing a file. This message code is returned by a method that fails to close a file. Internally, files are closed using mpiPlatformClose(...) which makes a platform specific call. File closing errors indicate a missing file, bad file, or other file system problems.

MPIMessageFILE_OPEN_ERROR
An error occurred when opening a file. This message code is returned by a method that fails to open a file. Internally, files are opened using mpiPlatformOpen(...) which makes a platform specific call. File opening errors indicate a missing file, bad file, or other file system problems.

MPIMessageFILE_READ_ERROR
An error occurred when reading from a file. This message code is returned by a method that fails to read from a file. Internally, files are read using mpiPlatformFileRead(...) which makes a platform specific call. File reading errors indicate a bad file or other file system problems.

MPIMessageFILE_WRITE_ERROR
An error occurred when writing to a file. This message code is returned by a method that fails to write to a file. Internally, files are written using mpiPlatformFileWrite(...) which makes a platform specific call. File writing errors indicate a bad file or other file system problems.

MPIMessageFILE_MISMATCH
The file being downloaded does not match the installed hardware. For example, if a user attempts to download an XMP file to a ZMP controller or a ZMP file to an XMP controller, the MPI will return error code MPIMessageFILE_MISMATCH.

MPIMessageASSERT_FAILURE
An assertion check internal to the library failed. This message code is used internally by the MPI. Contact MEI if you receive this message code.

Axis

MPIAxisMessageAXIS_INVALID
The axis number is out of range. This message code is returned by mpiAxisCreate(...) if the axis number is less than zero or greater than or equal to the allocated axisCount on the controller. Use mpiControlConfigGet(…) and mpiControlConfigSet(…) to allocate more objects if needed.

MPIAxisMessageCOMMAND_NOT_SET
The axis command position did not get set. This message code is returned by mpiAxisCommandPositionSet(...) if the controller's command position does not match the specified value. Internally, the mpiAxisCommandPositionSet(...) method requests the controller to change the command position, waits for the controller to process the request, and reads back the controller's command position. There are several cases where the controller will calculate a new command position to replace the requested command position. For example, if motion is in progress, stopped, or if the amp enable is disabled (when the motor's disableAction is configured for command equals actual), the controller will calculate a new command position every sample. To prevent this problem, set the command position when the motion is in an IDLE state and the motor's disableAction is configured for no action. It may also indicate that the motor associated to this axis is configured to mode MPIMotorDisableActionCMD_EQ_ACT and the motor is disabled. When the motor is disabled and in the MPIMotorDisableActionCMD_EQ_ACT mode, the command position is continually set to the actual position. To set the command position, enable the motor or take the motor out of the MPIMotorDisableActionCMD_EQ_ACT mode. Alternatively, setting the origin for the motor can often perform an equivalent result in this situation, as the command position will be set to the actual position the next sample.

MPIAxisMessageNOT_MAPPED_TO_MS
An axis is not mapped to the motion supervisor. This message code is returned by move or event methods when there are no axes associated with a motion supervisor. To correct this problem, map the axes to the motion supervisor in the controller with mpiMotionAxisMapGet(…) and mpiMotionAxisMapSet(…).

Capture

MPICaptureMessageMOTOR_INVALID
The capture motor number is not valid. This message code is returned by mpiCaptureConfigSet(...) if the captureMotorNumber does not have node hardware or the value is MPICaptureNOT_MAPPED.

MPICaptureMessageCAPTURE_TYPE_INVALID
The capture type is not valid. This message code is returned by mpiCaptureConfigSet(...) if the type is not one of the values defined by the enum MPICaptureType.

MPICaptureMessageCAPTURE_INVALID
The capture number is out of range. This message code is returned by mpiCaptureCreate(...) if the capture number is less than zero or greater than or equal to the enabled captureCount on the controller. Use mpiControlConfigGet(...) and mpiCaptureConfigSet(…) to allocate or enable more objects if needed.

MPICaptureMessageFEEDBACK_INVALID
The feedback number is out of range. This message code is returned by mpiCaptureConfigSet(…) if the feedback number is neither MPIMotorFeedbackInputPRIMARY or MPIMotorFeedbackInputSECONDARY. See MPIMotorFeedbackInput.

MPICaptureMessageINVALID_EDGE
The edge trigger type is not valid. This message code is returned by mpiCaptureConfigSet(...) if the capture edge type is not a member of the MPICaptureEdge enumeration.

MPICaptureMessageCAPTURE_NOT_ENABLED
The capture object in the controller is not enabled. This message code is returned by mpiCaptureCreate(…) if the capture number is less than zero or greater than or equal to the enabled captureCount on the controller. Use mpiControlConfigGet(...) and mpiControlConfigSet(…) to enable more objects if needed.

MPICaptureMessageCAPTURE_STATE_INVALID
This value is returned by mpiCaptureStatus(...) when the communication between the controller and the capture logic on the node fails resulting in an invalid capture state. See MPICaptureState.

MPICaptureMessageUNSUPPORTED_PRIMARY
The capture hardware does not support the primary feedback. This message code is returned by mpiCaptureConfigSet(...) if the node hardware's primary feedback does not support the specified capture. To correct this problem, select a different motor, feedback, or capture number.

MPICaptureMessageUNSUPPORTED_SECONDARY
The capture hardware does not support the secondary feedback. This message code is returned by mpiCaptureCreate(...) if the node hardware's secondary feedback does not support the specified capture. To correct this problem, select a different motor, feedback, or capture number.

MPICaptureMessageCAPTURE_ARMED
The Capture resource being configured is already armed and cannot be reconfigured until it is disabled or triggered. See mpiCaptureConfigSet(...).

Client

MPIClientMessageMETHOD_INVALID
The client method is out of range. This message code is returned by mpiClientMethod(...) if the method number is not a member of the MPIRemoteMethod enumeration.

MPIClientMessageHEADER_INVALID
The client packet header is not valid. This message code is returned by mpiClientMethod(...) if the packet header is corrupted. This indicates a problem with the message transmission. Check your network hardware.

MPIClientMessageMPI_INCOMPATIBLE
The server side MPI version is not compatible with the client side MPI version. This message code is returned by any MPI function that requires a specific version (or higher). To correct the problem, upgrade either the server or client side with the same MPI version.

MPIClientMessageSERVER_INCOMPATIBLE
The server side checksum did not match the client side checksum, indicating an incompatibility between the server and client. This message code is returned by any MPI function that fails a client/server transaction due to a checksum mismatch. To correct the problem, upgrade either the server or client side with the same MPI version.

MPIClientMessageSERVER_INACCESSIBLE
The server is not accessible. This message code is returned by mpiControlCreate(…) if a client connection could not be established with the server. To correct the problem, make sure the server is running properly, the specified TCP/IP address is correct, and the network hardware is working properly.

Command

First message in list of messages, placeholder only.

MPICommandMessageTYPE_INVALID
The command type is not valid. This message code is returned by mpiCommandCreate(...) if the command type is not a member of the MPICommandType enumeration.

Compensator

MPICompensatorMessageCOMPENSATOR_INVALID
The compensator number is not valid. This message code is returned by mpiCompensatorCreate(...) if the compensator number is less than 0 or greater than the allocated compensatorCount on the controller. Use mpiControlConfigGet/Set(…) to allocate more objects if needed.

MPICompensatorMessageNOT_CONFIGURED
MPI Compensator object must be configured before calling mpiCompensatorTableGet/ Set.

MPICompensatorMessageNOT_ENABLED
The compensator is not available on the controller. This message code is returned by mpiCompensatorValidate(…) if the compensator number is not within the range of enabled compensators on the controller. To correct the problem, use MPIControlConfig to configure the compensatorCount to be greater than the required compensator number.

MPICompensatorMessageAXIS_NOT_ENABLED
The axis is not available on the controller. This message coder is returned by mpiCompensatorConfigSet(...) if the axisOutNumber or any of the inputAxis[n].axisNumbers are not within the range of enabled axes on the controller. To correct the problem, use MPIControlConfig to configure the axisCount to be greater than the required axis number.

MPICompensatorMessageTABLE_SIZE_ERROR
The host compenstation table will not fit within the controller's configured compensation table. See Determining Required Compensator Table Size.

MPICompensatorMessagePOSITION_DELTA_INVALID
The positionDelta is either out of range or is not a multiple of the range. This message code is returned by mpiCompensatorConfigSet(…). To correct the problem, check the valid range values for MPICompensatorInputAxis.

MPICompensatorMessageDIMENSION_NOT_SUPPORTED
The dimensionCount is out of range. This message code is returned by mpiCompensatorConfigSet(…). To correct the problem, check the valid range values for MPICompensatorConfig.

Control

MPIControlMessageLIBRARY_VERSION
The MPI Library does not match the application. This message code is returned by mpiControlInit(...) if the MPI's library (DLL) version does not match the MPI header files that were compiled with the application. To correct this problem, the application must be recompiled using the same MPI software installation version that the application uses at run-time.

MPIControlMessageCONTROL_INVALID
The controller model is not supported. This message code is returned by mpiControlCreate(…) if the controller hardware is not supported by the MPI library.

MPIControlMessageCONTROL_NUMBER_INVALID
The controller number is out of range. This message code is returned by mpiControlCreate(...) if the controller number is less than zero or greater than or equal to MaxBoards(8).

MPIControlMessageTYPE_INVALID
The controller type is not valid. This message code is returned by mpiControlCreate(...) if the controller type is not a member of the MPIControlType enumeration.

MPIControlMessageINTERRUPTS_DISABLED
The controller interrupt is disabled. This message code is returned by mpiControlInterruptWait(...) if the controller's interrupt is not enabled. This prevents an application from waiting for an interrupt that will never be generated. To correct this problem, enable controller interrupts with mpiControlInterruptEnable(...) before waiting for an interrupt.

MPIControlMessageINTERNAL_MEMORY_OVERFLOW
The controller's internal memory will overflow. This message code is returned by mpiControlConfigSet(...) if the dynamic memory allocation exceeds the internal memory available on the controller. To correct the problem, reduce the number/size of control configuration resources or use a controller model with a larger static memory component.

MPIControlMessageEXTERNAL_MEMORY_OVERFLOW
The controller's external memory will overflow. This message code is returned by mpiControlConfigSet(...) if the dynamic memory allocation exceeds the external memory available on the controller. To correct the problem, reduce the number/size of control configuration resources or use a controller model with a larger static memory component.

MPIControlMessageAXIS_COUNT_INVALID
The axis count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of axes is greater than MPIControlMAX_OBJECTS.

MPIControlMessageAXIS_FRAME_COUNT_INVALID
This message is returned from mpiControlConfigSet() if the value for MPIControlConfig.axisFrameCount is not a power of two or if axisFrameCount is less than MPIControlMIN_AXIS_FRAME_COUNT.

MPIControlMessageCAPTURE_COUNT_INVALID
The capture count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of captures is greater than MPIControlMAX_OBJECTS.

MPIControlMessageFILTER_COUNT_INVALID
The filter count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of filters is greater than MPIControlMAX_OBJECTS.

MPIControlMessageMOTION_COUNT_INVALID
The motion count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of motions is greater than MPIControlMAX_OBJECTS.

MPIControlMessageMOTOR_COUNT_INVALID
The motor count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of motors is greater than MPIControlMAX_OBJECTS.

MPIControlMessageSAMPLE_RATE_TO_LOW
The controller sample rate is too small. This message code is returned by mpiControlConfigSet(…) if the sample rate is less than MPIControlMIN_SAMPLE_RATE (1kHz). SynqNet does not support cyclic data rates below 1kHz. The controller's sample rate specifies the SynqNet cyclic rate.

MPIControlMessageSAMPLE_RATE_TO_HIGH
The controller sample rate is too big. This message code is returned by mpiControlConfigSet(…) if the sample rate is greater than MPIControlMAX_SAMPLE_RATE (100kHz).

MPIControlMessageRECORDER_COUNT_INVALID
The recorder count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of recorders is greater than MPIControlMAX_OBJECTS.

MPIControlMessageCOMPENSATOR_COUNT_INVALID
The compensator count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of compensators is greater than MPIControlMAX_OBJECTS.

MPIControlMessageAXIS_RUNNING
Attempting to configure the control object while axes are running. It is recommended that all configuration of the control object occur prior to commanding motion.

MPIControlMessageRECORDER_RUNNING
Attempting to configure the control object while a recorder is running. It is recommended that all configuration of the control object occur prior to operation of any recorder objects.

MPIControlMessagePACK_ALIGNMENT
The application was compiled with a packing alignment that is different from the MPI library. For Windows, use the MSVC “/Zp8” compiler option or surround the MPI header files with the following #pragma pack statements:

#pragma pack(push, 8)
#include "stdmpi.h"
#include "stdmpi.h"
#include "apputil.h"
#pragma pack(pop)

For Linux, use the “-malign-double” compiler option.

MPIControlMessageFIRMWARE_INVALID
The controller firmware is not valid. This message code is returned by mpiControlCreate(...) if the MPI library does not recognize the controller signature. After power-up or reset, the controller loads the firmware from flash memory. When the firmware executes, it writes a signature value into external memory. If mpiControlCreate(...) does not recognize the signature, then the firmware did not execute properly. To correct this problem, download firmware and verify the controller hardware is working properly.

MPIControlMessageFIRMWARE_VERSION_NONE
The controller firmware version is zero. This message code is returned by control methods do not find a firmware version. This indicates the firmware did not execute at controller power-up or reset. To correct this problem, download firmware and verify the controller hardware is working properly.

MPIControlMessageFIRMWARE_VERSION
The controller firmware version does not match the software version. This message code is returned by control methods if the firmware version is not compatible with the MPI library. To correct this problem, either download compatible firmware or install a compatible MPI run-time library.

MPIControlMessageNO_FPGA_SOCKET
The FPGA socket type does not exist. This message code is returned by mpiControlFlashLoadFromFile(...) if the controller does not support the FPGA type that was specified in the FPGA image file. To correct this problem, use a different FPGA image that is compatible with the controller.

MPIControlMessageSYNQNET_STATE
The controller's SynqNet state is not expected. This message code is returned by mpiControlCreate(...), mpiControlReset(...) and mpiControlConfigSet(...) if the SynqNet network initialization fails to reach the SYNQ state. To correct this problem, check your node hardware and network connections.

MPIControlMessageIO_BIT_INVALID
The controller I/O bit is not valid. This message code is returned by mpiControlIoGet(...) or mpiControlIoSet(...) if the controller I/O bit is not a member of the MPIControlIoBit enumeration.

MPIControlMessageOBJECT_INVALID
The object type is not valid. This message code is returned by mpiControlObjectCount(...) or mpiControlObjectPtr(...) if the objectType argument is not a value defined by the MPIControlObjectType enumeration.

MPIControlMessageOBJECT_INDEX_INVALID
The object number is not valid. This message code is returned by mpiControlObjectPtr(...), if the objectIndex argument is beyond the range of objects allocated in the controller's memory. To allocate additional objects in the controller, see mpiControlConfigGet(...) and mpiControlConfigSet(...).

MPIControlMessageBUFFER_TOO_SMALL
The size of the file path buffer is smaller than required. This message code is returned by mpiControlDefaultFile(...) if the specified filePathBufferSize is smaller than the required size specified by pRequiredSize.

MPIControlMessageFILE_INACCESSIBLE
The specified path to the file is not accessible. This message code is returned by mpiControlDefaultFile(...) if the installation path environment variable (MEI_MDK_DIR_xx_xx_xx) is not valid. To fix the installation path variable, either re-install the software or manually configure the environment variable.

MPIControlMessageFLASH_INVALID The Flash object is not valid. This message code is returned by the control flash functions if the internal Flash object failed to be created. This message indicates an internal MPI library problem.

MPIControlMessageFLASH_VERIFY_ERROR
The flash memory does not match the flash file. This message code is returned by mpiControlFlashVerify(...) if the controller's flash memory does not match the specified flash file.

MPIControlMessageFLASH_SYNQNET_STATE_INVALID
The controller's SynqNet state is not expected. This message code is returned by mpiControlFlashSaveAll(…) if the SynqNet network is not in the SYNQ state. To correct this problem, initialize the SynqNet network with mpiSyqnNetInit(…).

MPIControlMessageFLASH_WRITE_ERROR
The value written to flash memory does not match the value read from flash memory. This message code is returned by any function that writes to controller flash memory if the flash memory fails. This message code indicates a controller flash memory failure.

MPIControlMessageEVENTS_LOST
The event message was lost. This message code is retevent messages were lost. To correct this problem, increase the priority of the control event service handler or purned by mpiControlProcessEvents(…) if the circular event message buffer rollover occurred and oll mpiControlProcessEvents(…) more frequently.

MPIControlMessageSEQUENCE_COUNT_INVALID
The math block count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of math blocks is greater than MPIControlMAX_OBJECTS.

MPIControlMessageMATH_BLOCK_COUNT_INVALID
The math block count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of math blocks is greater than MPIControlMAX_OBJECTS.

MPIControlMessagePRE_FILTER_DELAY_COUNT_INVALID
The pre-filter delay count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of pre-filter delay is greater than MPIControlMAX_OBJECTS.

MPIControlMessageLIMIT_BLOCK_COUNT_INVALID
The user limit count is not valid. This message code is returned by mpiControlConfigSet(...) if the number of user limits is greater than MPIUserLimitCOUNT_MAX.

MPIControlMessageTX_TIME_INVALID
The Tx Time is not valid. This message code is returned by mpiControlTimingConfigSet if the TxTime is less than zero or greater than 100.

DriveMap

MPIDriveMapMessageMAP_FILE_OPEN_ERROR
The drive map file could not be opened. Either it doesn't exist or the user does not have permission to access it.

MPIDriveMapMessageMAP_FILE_FORMAT_INVALID
The contents of the drive map file does not match the format of a drive map file.

MPIDriveMapMessageNODE_NOT_FOUND_IN_MAP
The node type, specified by the "nodeName" parameter, was not found in the drive map file.

MPIDriveMapMessageVERSION_NOT_FOUND_IN_MAP
The drive firmware version, specified by the "firmwareVersion" parameter, was not found in the drive map file.

MPIDriveMapMessageDRIVE_PARAM_READ_ONLY
An attempt was made to modify a read-only drive parameter.

Element

MPIElementMessageELEMENT_INVALID
The element is not valid. This message code is used internally to guarantee an element module and element number are valid.

Event

MPIEventMessageEVENT_INVALID
The event type is not valid. This message code is returned by mpiEventStatusSet(...) if the event type is not a member of the MPIEventType enumerations.

Filter

MPIFilterMessageFILTER_INVALID
The filter number is out of range. This message code is returned by mpiFilterCreate(...) if the filter number is less than zero or greater than or equal to MPIControlMAX_OBJECTS.

MPIFilterMessageINVALID_ALGORITHM
The filter algorithm is not valid. This message code is returned by mpiFilterIntegratorReset(...) if the filter algorithm is not a member of the MPIFilterAlgorithm enumeration (does not support integrators). This problem occurs if the filter type is set to user or an unknown type with mpiFilterConfigSet(...).

MPIFilterMessageINVALID_DRATE
The filter derivative rate is not valid. This message code is returned by mpiFilterConfigSet(...) if the filter derivative rate is less than 0 or greater than 7.
NOTE: The derivative rate for all gain tables must be in the range [0,7], not just the derivative rate for the current gain table.

MPIFilterMessageCONVERSION_DIV_BY_0
Returned when mpiFilterPostfilterGet(...) or mpiFilterPostfilterSectionGet(...) cannot convert digital coefficients to analog coefficients. When this error occurs, the offending section(s) will report its type as MPIPostFilterTypeUNKNOWN and will not contain any analog data.

MPIFilterMessageSECTION_NOT_ENABLED
Returned when mpiFilterPostfilterGet(...) or mpiFilterPostfilterSectionGet(...) attempt to read postfilter data when no postfilter sections are enabled.

MPIFilterMessageINVALID_FILTER_FORM
Returned when mpiFilterPostfilterGet(...) or mpiFilterPostfilterSectionGet(...) cannot interpret the current postfilter's form (when the form is something other than NONE, IIR, or BIQUAD).

MPIFilterMessageINVALID_SMOOTHING
The filter smoothing value is not valid. This message code is returned by mpiFilterConfigSet(...) if the filter smoothing value is less than 0 or greater than or equal to .999999 for the PIV algorithm.

License

MPILicenseMessageNOT_VALID
The license registers are not valid. This message code is returned if the hardware license register has been corrupted.

MPILicenseMessageNOFEATURE
The feature does not have a runtime license. The message code is returned if an unlicensed feature is accessed. To correct the problem, contact MEI to purchase a runtime license for the feature.

MPILicenseMessageNOAXIS
The axis does not have a runtime license. The message code is returned if an unlicensed axis is accessed. To correct the problem, contact MEI to purchase a runtime license for the axis.

MPILicenseMessageLEGACY
The controller does not require licenses. The message code is for legacy controllers that do not have licenses. There are no feature restrictions for legacy controllers.

MPILicenseMessageEXPIRED
The license has expired. The message code is returned when a runtime license expires. To correct the problem, contact MEI to renew a runtime license.

MPILicenseMessageUNLICENSED
The runtime license has not been activated. The message code is returned when a feature or axis is accessed with an unlicensed controller (default from factory). To correct the problem, contact MEI to install the runtime licenses.

List

MPIListMessageELEMENT_NOT_FOUND
The element is not a member of the list. This message code is returned by mpiListElement(...) if the index to the list is greater than or equal to the list count. This message code is used by the MPI internally to check object list handling.

MPIListMessageELEMENT_INVALID
The element is not valid. This message code is returned by mpiListInsertNow(...) or mpiListRemoveNow(...) if the element cannot be inserted or removed from the list. This message code is used by the MPI internally to check object list handling.

Map

MPIMapMessageNAME_INVALID
The map name is not valid. This message code is returned by mpiMapNameToParams(...) if the name is not a member of a map.

MPIMapMessageNAME_NOT_FOUND
The map name is not found. This message code is returned by mpiMapCreate(...), mpiMapNameToParams(...), or mpiMapNameParse(...) if the name is not found in the map.

MPIMapMessageINDEX_INVALID
The map index is not valid. This message code is returned by mpiMapNameToParams(...) if the map index is less than 0 or greater than or equal to the maximum instance count.

MPIMapMessageSYMBOL_INVALID
The map file is not valid. This message code is returned by mpiMapNameParse(...) if the map file cannot be parsed.

MPIMapMessageSYMBOL_NOT_FOUND
The map symbol is not found. This message code is returned by mpiMapSymbolToPtr(…) if the symbol type is not a member of the MPIMapSymbolType enumeration.

MPIMapMessageFILE_INVALID
The map symbol is not valid. This message code is returned by mpiMapSymbolIndexCount(…) if the symbol type is not a member of the MPIMapSymbolType enumeration.

Motion

MPIMotionMessageMOTION_INVALID
The motion supervisor number is out of range. This message code is returned by mpiMotionCreate(...) if the motion supervisor number is less than zero or greater than or equal to the enabled motionSupervisorCount on the controller. Use mpiControlConfigGet(...) and mpiControlConfigSet(…) to allocate more objects if needed.

MPIMotionMessageAXIS_COUNT
The number of axes is out of range. This message is returned from mpiMotionConfigSet(...), if there are no axes associated with the motion object or if the axis count exceeds MPIMotionMAX_AXES.

MPIMotionMessageAXIS_FRAME_COUNT
The axis frame count invalid on this Motion object. All axes appended to a Motion object must have the same frame buffer size. The axis frame buffer sizes are configured with the low-level controller configuration routine mpiControlConfigSet(...).

MPIMotionMessageTYPE_INVALID
The motion type is not valid. This message code is returned by any move function if the motion type is not a member of the MPIMotionType enumeration.

MPIMotionMessageATTRIBUTE_INVALID
The motion attribute is not valid. This message code is returned by any move function if the motion attribute mask is not compatible with the specified motion type. To correct the problem, do not use the motion attribute mask with the specified motion type or select a different motion type.

MPIMotionMessageIDLE
All motion supervisor axes are not moving and are ready to move. This message code is returned by any move function attempting to modify a non-existent move (motion supervisor is in the IDLE state). A move cannot be modified if no motion is in progress. To correct the problem, use the AUTO_START attribute for the behavior type. This message code is also returned from mpiMotionAction(...) when a STOP or RESUME is commanded when the motion supervisor is in the IDLE state. A motion cannot be stopped if there is no motion in progress and a motion cannot be resumed if there is no motion profile pending.

MPIMotionMessageMOVING
At least one motion supervisor axis is moving. This message code is returned by any move function attempting to command a move when the motion supervisor is in the MOVING state. A move cannot be started if a motion is in progress. To correct the problem, use the MODIFY attribute for the behavior type. This message code is also returned from mpiMotionAction(...) when a RESUME or RESET is commanded when the motion supervisor is in the MOVING state. A motion cannot be resumed or reset while a motion is in progress.

MPIMotionMessageSTOPPING
Motion supervisor axes are stopping due to a STOP action. This message code is returned by any move function attempting to command a move when the motion supervisor is in the STOPPING state. A move cannot be commanded when a stop is in progress. This message code is also returned from mpiMotionAction(...) when a RESUME or RESET is commanded when the motion supervisor is in the STOPPING state. A motion cannot be resumed or reset while a stop is in progress.

MPIMotionMessageSTOPPED
Motion supervisor axes are stopped due to a STOP action. This message code is returned from mpiMotionAction(...) when a STOP action is commanded while the motion supervisor is already in the STOPPED state.

MPIMotionMessageSTOPPING_ERROR
Motion supervisor axes are stopping due to an E_STOP or ABORT action. This message code is returned by any move function attempting to command a move when the motion supervisor is in the STOPPING_ERROR state. A move cannot be commanded when a stopping on error action is in progress. This message code is also returned from mpiMotionAction(...) when a RESUME or RESET is commanded when the motion supervisor is in the STOPPING state. A motion cannot be resumed or reset while a stopping on error action is in progress.

MPIMotionMessageERROR
Motion supervisor axes are in an error state due to an E_STOP or ABORT action. This message code is returned by any move function attempting to command a move when the motion supervisor is in the ERROR state. A motion cannot be commanded when the motion supervisor is in an error state. This message code is also returned from mpiMotionAction(...) when a STOP or RESUME is commanded when the motion supervisor is in the ERROR state. To correct the problem, fix the condition that caused the E_STOP or ABORT action and then clear the ERROR state using mpiMotionAction(...) with a RESET.

MPIMotionMessageAUTO_START
The commanded move with the MODIFY attribute was automatically converted to a move start. This message code is returned from any move function when the AUTO_START attribute for the behavior type was specified and the move was commanded while the motion supervisor is in the IDLE state. This message code is useful for notifying an application of an auto-start, it is not an error condition.

MPIMotionMessageILLEGAL_DELAY
Move is commanded to be modified with a non-zero delay value. To avoid this message code, do not modify a move with a non-zero delay.

MPIMotionMessagePROFILE_ERROR
The move profile is not possible within the specified constraints. This message code is returned by a move function if the profile is not physically possible and cannot be calculated by the controller firmware.

MPIMotionMessagePROFILE_NOT_SUPPORTED
The controller firmware does not support the specified motion profile type. This message code is returned by an mpiMotionXxxxxSCurveJerkMove function if the feature is not supported by the controller firmware. To correct the problem, use the mpiMotionXxxxxSCurveJerkPercentMove motion type instead.

MPIMotionMessagePATH_ERROR
The specified multi-point motion path is not valid. This message code is returned by mpiMotionStart(...) when the final point is not specified or the time slice is less than one controller sample. The following motion types must have the motion parameter “final” set to 1.
Spline
Bessel
BSpline
BSpline2

Setting the motion parameter “final” set to a value other than 1 for Spline will result in a MPIMotionMessagePATH_ERROR error message.

Specifying a point count of < 0 for (Bessel, BSpline, or BSpline2) will result in a MPIMotionMessagePATH_ERROR error message.

MPIMotionMessageFRAMES_LOW
The controller's frame buffer is low. This message code is returned by mpiMotionFramesLow(...). This is an internal message code used by the library to manage the frame buffering.

MPIMotionMessageFRAMES_EMPTY
The controller's frame buffer is empty. This message code is returned by mpiMotionFramesLow(...). This is an internal message code used by the library to manage the frame buffering.

MPIMotionMessageFRAMES_BUFFER_OVERRUN
The controller's frame buffer has overflowed. This message code is returned by a move function, if the move exceeds the frame buffer space. To correct this problem, increase the size of the frame buffer using mpiControlConfigSet(…).

MPIMotionMessageRESERVED0
Reserved for specialized use.

MPIMotionMessageRESERVED1
Reserved for specialized use.

MPIMotionMessageRESERVED2
Reserved for specialized use.

MPIMotionMessageNO_AXES_MAPPED
The motion supervisor has no axes. This message code is returned by a move function or mpiMotionAction(...) if there are no axes mapped to the motion supervisor. To correct this problem, make sure there is at least one axis object associated with the motion supervisor before commanding any motion or motion actions.

MPIMotionMessageBAD_PATH_DATA
If any of the motion parameters passed to the MPI for path motion are infinite or NAN, the MPI will return MPIMotionMessageBAD_PATH_DATA and will not load the move to the controller.

MPIMotionMessageAXIS_MOVING
An axis cannot be mapped to a motion supervisor while it is moving. This message code is returned by mpiMotionAxisMapSet(…) if a specified axis is moving.

MPIMotionMessageAXIS_MAP_MISMATCH
The expected motion supervisor to axis map does not match the specified axis map. This message code is returned by a move function when the EXPECTED_AXES attribute is specified and the expected axis map does not match the actual axis map.

Motor

MPIMotorMessageMOTOR_INVALID
The motor number is out of range. This message code is returned by mpiMotorCreate(...) if the motor number is less than zero or greater than or equal to the allocated motorCount on the controller. Use mpiControlConfigGet/Set(…) to allocate more objects if needed.

MPIMotorMessageTYPE_INVALID
The motor type is not valid. This message code is returned by mpiMotorConfigGet/ Set if the motor type is not a value defined in the enumeration MPIMotorType. To avoid this error, use one of the defined motor types in MPIMotorType.

MPIMotorMessageSTEPPER_NA
The hardware does not support the Stepper motor type. This message code is returned by mpiMotorConfigSet(...) if the motor type is configured for MPIMotorTypeSTEPPER when the node hardware does not support steppers. To correct the problem, do not select the stepper motor type.

MPIMotorMessageMOTOR_NOT_ENABLED
The motor number is not active in the controller. This message code is returned byby mpiMotorFeedback(…) or mpiMotorEventReset(…) if the specified motor is not enabled in the controller. To correct the problem, use mpiControlConfigSet(...) to enable the motor object, by setting the motorCount to greater than the motor number. For example, to enable motor 0 to 3, set motorCount to 4.

MPIMotorMessageSECONDARY_FEEDBACK_NA
The motor's secondary feedback is not available. This message code is returned by mpiMotorLimitConfigSet(...)if the feedback fault trigger is configured for a secondary feedbackwhen the hardware does not support a secondary feedback. To correct the problem, do not select the secondary encoder when configuring the feedback fault conditions.

MPIMotorMessageHARDWARE_NOT_FOUND
The motor object's hardware resource is not available. This message code is returned by mpiMotorConfigGet/ Set. if the node hardware for the motor is not found. During controller and network initialization the nodes and motor count for each node is discovered and mapped to the controller's motor objects. An application should not configure a motor object if there is no mapped hardware to receive the service commands. To correct this problem, verify that all expected nodes were found. Use mpiSynqNetInfo(...) and mpiSqNodeInfo(...) to determine the node topology and motor count per node. Check the node hardware power and network connections.

MPIMotorMessageDISABLE_ACTION_INVALID
The motor object stepper configuration is not valid. These message codes are returned by mpiMotorConfigGet(...) if the motor type is configured for stepper while the disable action is configured for command position equals actual position. The disable action feature sets the command position equal to the actual position when the amp enable signal is set to disable. Stepper motor types are driven by a digital pulse, which is triggered by the controller's command position. Do not use disable action set to command equals actual with stepper motor types.

MPIMotorMessageSTEPPER_INVALID
The motor object stepper configuration is not valid. These message codes are returned by mpiMotorConfigGet(...) if the motor type is configured for stepper while the disable action is configured for command position equals actual position. The disable action feature sets the command position equal to the actual position when the amp enable signal is set to disable. Stepper motor types are driven by a digital pulse, which is triggered by the controller's command position. Do not use disable action set to command equals actual with stepper motor types.

MPIMotorMessagePULSE_WIDTH_INVALID
The motor stepper pulse width is not valid. This message code is returned by mpiMotorConfigSet(...) if the pulseWidth is out of range. To correct the problem, specify the the pulse width value between 100 nanoseconds and 1 millisecond.

MPIMotorMessageFEEDBACK_REVERSAL_NA
The feedback reversal is not applicable for the feedback type specified. This message code is returned by mpiMotorConfigSet(...) if the feedback type is not MPIMotorEncoderTypeQUAD_AB and the encoderPhase is set to TRUE. To correct the problem, set encoderPhase to FALSE. Some drives may support feedback reversal via drive parameters. Please consult the drive manufacturer's documentation for details.

MPIMotorMessagePHASE_FINDING_FAILED
The drive failed to complete the phase finding procedure. This message code is returned by mpiMotorPhaseFindStart(…) if the drive failed to successfully initailized commutation. To determine the cause of the failure, check the fault and warning codes from the drive with mpiMotorAmpFault(…) and mpiMotorAmpWarning(…).

MPIMotorMessageDEMAND_MODE_UNSUPPORTED
The motor does not support the specified demand mode. This message is returned by mpiMotorDemandModeSet(…) if the demand mode is configured for a mode that the node/drive does not support. To correct this problem, use the default demand mode or specify a different demand mode.

MPIMotorMessageDEMAND_MODE_NOT_SET
The demand mode cannot be changed while the amplifier is enabled. This message is returned by mpiMotorConfigSet(…) if the demand mode is changed while the motor’s amplifier is enabled. To avoid this error message, disable the motor’s amp enable with mpiMotorAmpEnableSet(…) before changing the demand mode.

MPIMotorMessagePOSITION_FEEDBACK_OFFSET_UNSUPPORTED
The specified motor does not support the position feedback offset storage feature, either because the FPGA on the drive to which the motor is connected does not implement the feature, or because there is no storage available in the encoder's EEPROM. This message will also occur if the drive is not configured to talk to the encoder using the EnDat 2.1 protocol.

MPIMotorMessagePOSITION_FEEDBACK_OFFSET_SET_FAILED
The specified motor failed to store the position feedback offset. The exact cause of the failure may vary, but it indicates a problem with the service channel mechanism used to communicate to the motor.

MPIMotorMessagePOSITION_FEEDBACK_OFFSET_UNINITIALIZED
The motor object was able to retrieve the stored position feedback offset, but the internal checksum indicated that the data was unintialized. The returned position may not be valid. This error will also occur if the encoder memory used to store the offset becomes corrupted.

Notify

MPINotifyMessageWAIT_IN_PROGRESS
The notify object is waiting for an event. This message code is returned by mpiNotifyEventWait(...) if the notify object is already waiting for an event in another thread. To prevent this problem, make sure a thread does not share notify objects with other threads.

Packet

MPIPacketMessageADDRESS_INVALID
The server socket address is not valid. This message code is returned by mpiControlCreate(...) or mpiControlReset(...) if the server name is not specified or the server address is not valid. This message code comes from a lower level routine, mpiPacketClient(...). To correct the problem, make sure the server is operational and the server name or address is valid.

MPIPacketMessageCOMM_ERROR
The socket communication failed. This message code is returned by a packet method that fails to send or receive data correctly. This usually indicates a hardware problem. To correct this problem, make sure your network hardware is functioning properly and all network connections are reliable.

MPIPacketMessageCONNECTION_CLOSED
The socket communication connection is closed. This message code is returned by mpiPacketRecv(...) or mpiPacketSend(...) if zero bytes of data are sent or received. This usually means the socket communication was not opened or was closed. To correct this problem, make sure mpiPacketCreate(...) was successful and that another thread did not close the socket connection.

Geometric Path

MPIGeometricPathMessageILLEGAL_DIMENSION
The path dimensions are not valid. This message code is returned by mpiGeometricPathParamsSet(...) or mpiGeometricPathToPTPoint(...) or mpiGeometricPathToPVTPoint(…) if the path dimension is less than one or greater than or equal to MPIGeometricPathPointDIMENSION_MAX. Also, this message code is returned if specific path element types have dimension restrictions. For example, the ARC type is limited to 2 dimensions and the ARC_END_POINT type is limited to 3 dimensions. To correct this problem, select an appropriate dimension for the path element type.

MPIGeometricPathMessageILLEGAL_ELEMENT
The path element type is not valid. This message code is returned by mpiGeometricPathAppend(...) if the specified path element type is not a member of the MPIGeometricPathElementType enumeration.

MPIGeometricPathMessageARC_ILLEGAL_DIMENSION
Illegal arc dimension (too many axes in arc). Arc dimension is out of range. This message code occurs when the specified dimension is out of range. An arc element dimension must be 2.

MPIGeometricPathMessageILLEGAL_RADIUS
The path element arc radius is not valid. This message code is returned by mpiGeometricPathAppend(...) if the ARC element radius is less than or equal to zero. To correct this problem, set the arc radius to a value greater than zero.

MPIGeometricPathMessagePATH_TOO_LONG
There is not enough memory available for the specified path length. This message code is returned by mpiGeometricPathToPTPoint(…) or mpiGeometricPathToPVTPoint(…) if the path length is greater than the available memory for the host buffer dynamic allocation. To correct the problem, specify a path with fewer points or add memory.

MPIGeometricPathMessageUNSUPPORTED_TYPE
The path interpolation type is not supported. This message code is returned by mpiGeometricPathToPTPoint(…) or mpiGeometricPathToPVTPoint(…) if the path interpolation type is not a member of the MPIGeometricPathInterpolationType enumeration.

MPIGeometricPathMessageILLEGAL_VELOCITY
The path element velocity is not valid. This message code is returned by mpiGeometricPathAppend(...) if the specified velocity is less than or equal to zero. To correct this problem, set the element velocity to a value greater than zero.

MPIGeometricPathMessageILLEGAL_ACCELERATION
The path element velocity is not valid. This message code is returned by mpiGeometricPathAppend(...) if the specified velocity is less than or equal to zero. To correct this problem, set the element velocity to a value greater than zero.

MPIGeometricPathMessageILLEGAL_TIMESLICE
The path element time slice is not valid. This message code is returned by mpiGeometricPathAppend(...) if the specified time slice is less than or equal to zero. To correct this problem, set the element time slice to a value greater than zero.

Platform

MPIPlatformMessagePLATFORM_INVALID
The platform object is not valid. This message code is returned by a platform method if the platform object handle is not valid. Most applications do not use the platform module. The MPI library uses the platform module internally. If an application needs a platform handle, use mpiControlPlatform(...). Do NOT create your own platform object with mpiPlatformCreate(...).

MPIPlatformMessageDEVICE_INVALID
The platform device driver is not valid. This message code is returned by mpiControlCreate(...) or mpiControlReset(...) if the platform device handle is not valid. This message code comes from the lower level routines, mpiPlatformInit(...) or mpiPlatformDeviceClose(...). To correct the problem, make sure the device driver is installed and operational.

MPIPlatformMessageDEVICE_ERROR
The platform device failed. This message code is returned by the platform methods that fail to access a controller via a device driver. It occurs if the specified board type is not a member of the MPIPlatformBoardType enumeration. It also occurs if the device driver fails to read/write controller memory or there is an interrupt handling failure. To correct the problem, verify the platform has support for your controller and the device drive is installed and operational. Check for any resource conflicts (memory range, I/O port range, and interrupts) with other devices.

MPIPlatformMessageDEVICE_MAP_ERROR
The platform device memory mapping failed. This message code is returned by mpiControlCreate(...) or mpiControlReset(...) if the controller memory could not be mapped to the operating system's memory space. To correct this problem, verify there are no memory resource conflicts. Also, make sure the host computer and operating system have enough free memory for the controller.

MPIPlatformMessageCOPY64_FAILURE
The 64-bit read failed. This message is returned by mpiPlatformMemoryGet64(…), mpiAxisCommandPositionGet(…), or mpiAxisActualPositionGet(…), if the 64-bit position data cannot be read atomically. Internally, the MPI uses an algorithm to construct the 64-bit position data via multiple 32-bit reads. If the 64-bit position value is not valid after multiple attempts, this error will be returned. If your application experiences this error message, if possible, use the equivalent 32-bit methods, mpiAxisCommandPositionGet32(…), mpiAxisActualPositionGet32(…), or contact MEI.

MPIPlatformMessagePATH_DOES_NOT_EXIST
The file path is not valid. This message code is returned by mpiLibraryInstallPath(…) if the directory path does not exist.

MPIPlatformMessagePATH_IS_NOT_A_DIRECTORY
The file path is not actually a directory. This message code is returned by mpiLibraryInstallPath(…) if the path exists, but is not a directory.

MPIPlatformMessageINSTALL_VARIABLE_NOT_SET
The installation environment variable is not valid. This message code is returned by mpiLibraryInstallPath(…) if the install environment variable (MEI_MDK_DIR) is not set.

MPIPlatformMessageDRIVER_VERSION_INCOMPATIBLE
The device driver version is not compatible with the MPI library. This message code is returned by mpiControlCreate(...) if the device driver version is not compatible. To correct the problem, use the installer package to install the device driver and library.

MPIPlatformMessageFILE_TYPE_INVALID
The controller memory dump file is not valid. This message code is returned by mpiControlCreate(...) if the controller memory dump file format is not recognized by the MPI library.

MPIPlatformMessageFILE_VERSION
The controller memory dump file version is not compatible with the MPI library. This message code is returned by mpiControlCreate(...) if the controller memory dump file version is not compatible with the MPI library.

Recorder

MPIRecorderMessageNO_RECORDERS_AVAIL
This message code is returned when there are no more recorders available to create. If the mpiRecorderCreate(control, -1) is called to create the next available recorder object and either all recorders have already been allocated or there are not enough recorders enabled on the controller, this error message will be returned. Check to make sure that enough recorders are enabled on the controller. To enable more recorders, use mpiControlConfigSet(...).

MPIRecorderMessageNOT_ENABLED
This message code is returned by a recorder method when a specific recorder is not enabled on the controller. When a recorder number is explicitly requested when creating a recorder such as mpiRecorderCreate(control, 3) and the corresponding recorder is not enabled on the controller, this message will be returned.

MPIRecorderMessageRUNNING
This message is returned by mpiRecorderConfigSet(...) and mpiRecorderConfigGet(...) when an application attempts to configure a recorder that is currently running.

MPIRecorderMessageSTARTED
The data recorder is already running. This message code is returned by mpiRecorderStart(...) if the data recorder has already been started. If this is a problem, call mpiRecorderStop(...) to stop the data recorder or wait for the recorder to collect the number of specified records and stop.

MPIRecorderMessageSTOPPED
The data recorder is not running. This message code is returned by mpiRecorderStop(...) if the data recorder has already been stopped. If this is a problem, call mpiRecorderStart(...) to start the data recorder.

MPIRecorderMessageNOT_CONFIGURED
The data recorder has not been configured. This message code is returned by mpiRecorderRecordGet(...) if the data address count has not been configured. To correct this problem, configure the data recorder with mpiRecorderConfigSet(...).

MPIRecorderMessageRECORD_COUNT_INVALID
This message code is returned by mpiRecorderStart(...) and mpiRecorderRecordConfig(...) when the specified recorder object has no records allocated to it. The recorder record count is configured by calling mpiControlConfigSet(...) with MPIControlConfig.recordCount[recorderNumber] set to a non-zero value. The recorder itself is enabled by setting MPIControlConfig.recorderCount. See MPIControlConfig.

MPIRecorderMessageRESERVED
The data recorder cannot be created because it is already in use. This message code is returned by mpiRecorderValidate(...) if the requested data recorder is already in use. To correct this problem, call mpiRecorderCreate(...) with a recorder index for a recorder that is not already in use.

MPIRecorderMessageNOT_RESERVED
The data recorder is not reserved. This message code is returned by mpiControlRecorderCancel(...) if the requested data recorder is not already in use. To correct this problem, do not call mpiControlRecorderCancel(...) with a recorder index for a recorder that is not already in use.

Sequence

MPISequenceMessageSEQUENCE_INVALID
The sequence number is out of range. This message code is returned by mpiSequenceCreate(...) if the sequence number is less than zero or greater than or equal to MPIXmpMAX_PSs. This message code is also returned if the specified sequence number is not active in the controller. To correct this problem, use mpiControlConfigSet(...) to enable the sequence object, by setting the sequenceCount to greater than the sequence number. For example, to enable sequence 0 to 3, set sequenceCount to 4. This message code is returned by mpiSequenceLoad(...) if the sequence buffer size and the sequence page size are not equal. This indicates an internal MPI Library problem.

MPISequenceMessageCOMMAND_COUNT
The sequence command count is out of range. This message code is returned by mpiSequenceStart(...), or mpiSequenceCompile(...) if the sequence command count is less than or equal to zero. To correct this problem, set the command count to a value greater than zero.

MPISequenceMessageCOMMAND_NOT_FOUND
The sequence command is not found. This message code is returned by mpiSequenceLoad(...), mpiSequenceStart(...), or mpiSequenceCompile(...) if the specified command is not a member of the sequence. To correct this problem, specify a command that is a member of the sequence.

MPISequenceMessageSTARTED
The program sequencer is already running. This message code is returned by mpiSequenceResume(...), mpiSequenceStart(...), or mpiSequenceStep(...) if the program sequencer has already been started. If this is a problem, call mpiSequenceStop(...) to stop the program sequencer or monitor the sequence status and wait for the state to equal STOPPED.

MPISequenceMessageSTOPPED
The program sequencer is not running. This message code is returned by mpiSequenceStop(...) if the program sequencer has already been stopped. If this is a problem, call mpiSequenceStart(...) to start the program sequencer.

Server

MPIServerMessageMETHOD_INVALID
The server method is out of range. This message code is returned by mpiServerMethod(...) if the method number is not a member of the MPIRemoteMethod enumeration.

MPIServerMessageHEADER_INVALID
The server packet header is not valid. This message code is returned by mpiServerMethod(...) if the packet header is corrupted. This indicates a problem with the message transmission. Check your network hardware. This message code can also be returned when there is an MPI version mismatch between the server.exe utility and the connecting client application.

SqNode

MPISqNodeMessageINVALID
The SqNode type is out of range. This message code is returned by SynqNet node methods if the node type is not a member of the SQNodeLibNodeType enumeration.

MPISqNodeMessageNODE_INVALID
The node number is not available on the network. This message code is returned by MPI methods that fail a service command transaction due to the specified node number is greater than or equal to the total number of nodes discovered during network initialization. To correct this problem, check the discovered node count with mpiSynqNetInfo(...). If the node count is not what you expected check your network wiring, node condition, and re-initialize the network with mpiControlReset(...).

MPISqNodeMessageSTATE_ERROR
Some methods can only be executed in SYNQ state. This message will be returned when the network is not in the expected network state (i.e ASYNQ state).

MPISqNodeMessageCONFIG_NETWORK_MISMATCH
The type of map file specified in mpiSqNodeDriveMapParamFileSet(...) does not match the type of drive found on the network.

MPISqNodeMessageNOT_IN_CONFIG_FILE
The parameter name or number specified in mpiSqNodeDriveMapParamFileSet(...) was not valid for the specified drive.

MPISqNodeMessageBOOT_FILE_NOT_FOUND
The drive firmware boot file was not found. This message code is returned by mpiSqNodeDownload(…) if the drive specific firmware boot file was not found in the path.

MPISqNodeMessageMAP_CONFIG_MISMATCH
The parameter name or number specified in mpiSqNodeDriveMapParamFileSet(...) was not valid for the specified drive.

MPISqNodeMessageCONFIG_FILE_FORMAT_INVALID
A file with an incorrect format was used in mpiSqNodeDriveMapParamFileSet(...).

MPISqNodeMessageRESPONSE_TIMEOUT
The drive/node did not respond to the service command issued in a reasonable amount of time. It's possible that this error was caused by the node losing communication to the SynqNet network. To correct this problem, check your node hardware. See mpiSqNodeInfo or MPISynqNetMessage.

MPISqNodeMessageREADY_TIMEOUT
The node/drive did not complete the hand shaking for the service command.

MPISqNodeMessageSRVC_ERROR