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.

String: Buffer too small to hold the required number of characters

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.

String: Flash invalid

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(…).

String: Flash cannot be saved, SynqNet state must be SYNQ

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.

String: Flash write error

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.

String: Events lost

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.

String: SequenceCount is invalid

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.

String: MathBlockCount is invalid

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.

String: PreFilterDelayCount is invalid

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.

String: UserLimitCount is invalid

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.

String: TxTime is invalid

MPIControlMessageCANT_SET_SAMPLE_RATE
The controller sample rate can not be set in simulation mode. This message code is returned by mpiControlTimingConfigSet(…) if the controller type is SIMULATION.

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.

String: Could not open drive map file

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

String: Format error in drive map file

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

String: Node type not found in drives map files

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

String: Drive firmware version not found in drives map file (see drive vendor for .dm file update)

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

String: Drive parameter is read-only

Element

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

String: Element invalid

Event

MPIEventMessageEVENT_INVALID
The event type is not valid.

String: Event invalid

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.

String: Filter invalid

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(...).

String: Filter algorithm invalid

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.

String: DRate value out of range (0-7)

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.

String: Divide by zero in conversion

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

String: Specified postfilter section not 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).

String: Invalid filter form

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.

String:

License

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

String: Registers are bad or do not match serial number

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.

String: Requested runtime feature or package is not licensed

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.

String: Axis count exceeds the runtime license quantity

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.

String: Controller is unrestricted (legacy)

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.

String: Runtime license has expired

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.

String: Runtime license is not activated. Please return controller to the factory.

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.

String: Element not found

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.

String: Element invalid

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.

String: Name invalid

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.

String: Name not found

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.

String: Index invalid

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.

String: Symbol not found

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.

String: Symbol invalid

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.

String: Motion invalid

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.

String: Axis count invalid

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(...).

String: Axis frame count invalid

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.

String: Type invalid

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.

String: Attribute invalid

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.

String: MPIStateIDLE

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.

String: MPIStateMOVING

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.

String: MPIStateSTOPPING

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.

String: MPIStateSTOPPED

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.

String: MPIStateSTOPPING_ERROR

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.

String: MPIStateERROR

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.

String: Auto-start

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.

String: lllegal 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.

String: Profile error

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.

String: Profile not supported

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.

String: Path error

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.

String: Frame buffer low

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.

String: Frame buffer empty

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(…).

String: Frame buffer overrun

MPIMotionMessageRESERVED0
Reserved for specialized use.

MPIMotionMessageRESERVED1
Reserved for specialized use.

String: RESERVED1

MPIMotionMessageRESERVED2
Reserved for specialized use.

String: RESERVED2

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.

String: No axis mapped

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.

String: Bad path data

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.

String: Cannot map axis while 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.

String: Expected axis map does not match 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.

String: Motor invalid

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.

String: Motor type invalid

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.

String: Stepper motors are not available

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.

String: Motor not enabled

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.

String: Secondary feedback not available

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.

String: Hardware not found

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.

String: Cannot set motor type to STEPPER when disable action is CMD_EQ_ACT

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.

String: Cannot set disable action to CMD_EQ_ACT when motor type is STEPPER

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.

String: Stepper Pulse Width out of range (.00000006 < pulseWidth < .00100006)

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.

String: Unable to invert feedback for specified feedback type

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(…).

String: Motor phase finding failure

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.

String: Specified demand mode not supported by drive

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.

String: Unable to switch demand mode while the amplifier is enabled

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.

String: Position feedback offset storage not supported

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.

String: Position feedback offset set failed

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.

String: Position feedback offset data uninitialized or 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.

String: Wait in progress

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.

String: Address invalid

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.

String: Communication error

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.

String: Connection closed

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(...).

String: Platform invalid

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.

String: Device invalid

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.

String:

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.

String: Device map error

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.

String: Copy64 failure

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

String: No such file or directory

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.

String: The path 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.

String: The MPI install directory environment variable 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.

String: Incompatible driver version

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.

String: Invalid file type

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.

String: Incorrect file version

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(...).

String: No recorders available

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.

String: Not enabled

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

String: Cannot configure while 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.

String: Already started

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.

String: Already stopped

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(...).

String: Not configured

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.

String: Invalid record count set for recorder object

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.

String: Recorder is already reserved

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.

String: Recorder is not reserved

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.

String: Sequence invalid

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.

String: Command count invalid

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.

String: Command not found

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.

String: MPISequenceStateSTARTED

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.

String: MPISequenceStateSTOPPED

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.

String: Method invalid

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.

String: Header invalid

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.

String: Invalid

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(...).

String: Node invalid

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).

String: Network state error

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

String: Config file and network are different

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

String: Not in Config File

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.

String: Boot file not found or corrupt, kollmorgen_ember.a00 must be in path

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

String: Map and config files are different

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

String: Config file format invalid

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.

String: Service cmd response timeout

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

String: Service cmd ready timeout

MPISqNodeMessageSRVC_ERROR
There was an error in carrying out the service command issued.

String: Service cmd error

MPISqNodeMessageSRVC_UNSUPPORTED
The service command issued is either not supported or recognized by the drive.

String: Service cmd unsupported

MPISqNodeMessageCMD_NOT_SUPPORTED
The service command is not supported by the node.

String: Node module did not complete the specified operation

MPISqNodeMessageDISCOVERY_FAILURE
Unable to discover node rescources.

String: Node specific discovery failure

MPISqNodeMessageINIT_FAILURE
A node specific initialization routine was unable to successfully complete its routine. Verify that the node FPGA is the default version for your MPI version. See MPISqNodeInfoFpga.

String: Node specific initialization failure

MPISqNodeMessageFILE_NODE_MISMATCH
Node type does not match the file provided for download.

String: Node type does not match the file provided for download

MPISqNodeMessageFILE_INVALID
The file provided for download was not found or was corrupted.

String: The file provided for download was not found

MPISqNodeMessageINVALID_HEADER
The header information in the download image is invalid. Please verify firmware file to be correct and retry download. If firmware file is correct please contact firmware manufacturer.

String: The header information in the download image is invalid

MPISqNodeMessageDOWNLOAD_FAIL
Node firmware download failed. Verify that the firmware file is correct and retry the download.
NOTE: A network reset my be required.

String: Node firmware download failed

MPISqNodeMessageVERIFY_FAIL
The node FPGA firmware does not match the FPGA image file.

String: Node firmware verify failed

MPISqNodeMessageDOWNLOAD_NOT_SUPPORTED
The downloading of the node firmware (FPGA) image is not supported for this node.

String: Firmware download not supported

MPISqNodeMessageVERIFY_NOT_SUPPORTED
The Node specified for verification does not support the upload of the FPGA image. Therefore, the image cannot be verified.

String: Firmware verify not supported

MPISqNodeMessageBOOT_ROM_INVALID
The SqNode Boot Rom identification or version is not recognized by the MPI.

String: Boot rom not recognized

MPISqNodeMessageINVALID_TABLE
Invalid resource table in node module. This is a fatal error within the MPI. Please verify MPI and node FPGA versions to be correct and then contact MEI's Technical Support.

String: Invalid resource table in node module

MPISqNodeMessageINVALID_STR_LEN
An attempt to write information to the node has failed due to an invalid string length.

String: Invalid string length

MPISqNodeMessageFEEDBACK_MAP_INVALID
Returned from mpiSqNodeConfigSet(...) when the given secondary encoder (n) is not mappable to the motor on the node specified by MPISqNodeFeedbackSecondary[n].motorIndex. See MPISqNodeFeedbackSecondary.

String: Invalid feedback map attempt

MPISqNodeMessageNODE_FAILURE
An attempt was made to access a SynqNet node that has a node failure event active.

String: Node failure

MPISqNodeMessageEXCEEDED_MAXIMUM_SYNQNET_PACKET_LIMIT
When initializing the SynqNet network one of the node requires a SynqNet packet larger that what can be supported.

String: Exceeded maximum synqnet packet limit

MPISqNodeMessageIO_MODULE_INCOMPATIBILITY
Two modules attached to a SQID node are incompatible. This error message code is returned when initializing a SQID node. Different types of I/O module may be incompatible and will not work on the same SQID node.

String: I/O Module Incompatibility

MPISqNodeMessageIO_MODULE_EEPROM_NOT_PROGRAMMED
The EEPROM on one of the modules attached to a SQID node has not been programmed.

String: I/O Module EEPROM not programmed

MPISqNodeMessageIO_MODULE_COUNT_EXCEEDED
The maximum number of I/O that can be supported by a SQID node has been exceeded.

String: I/O Module Count Exceeded

MPISqNodeMessageIO_MODULE_LENGTH_CHECK_FAILED
When initializing an SQIO node, checks are performed to confirm that the node actually supports the correct number of I/O. This error is returned when one of these tests fails. An error will occur when the length of at least one of the inter module (SPI) buses did not match the length calculated from data held in the module EEPROMs. This error message can be returned by MPI functions that reset the SynqNet Network such as, mpiControlReset(...), mpiControlInit(...), mpiSynqNetInit(...). This error can ONLY be generated by SQIO nodes. This fault can also be caused by a poor electrical connection between the SQID and the I/O modules. If the modules are firmly connected and the error persists then you will need to contact your supplier of the I/O Modules to correct the hardware.

String: I/O Module length check failed

MPISqNodeMessageIO_MODULE_3_3V_BUS_CURRENT_EXCEEDED
During the initialization of the modules attached to a SQID node, the maximum current that can be drawn from the inter module 3.3V bus exceeds the allowable current.

String: I/O Module 3.3V bus current exceeded

MPISqNodeMessageIO_MODULE_24V_BUS_CURRENT_EXCEEDED
During the initialization of the modules attached to a SQID node, the maximum current that can be drawn from the inter module 5V bus exceeds the allowable current.

String: I/O Module 24V bus current exceeded

MPISqNodeMessageIO_SLICE_INITIALIZATION_FAULT
An error was encountered while initalizing the slice node.

String: I/O Slice initalization fault

MPISqNodeMessageIO_SLICE_INITIALIZATION_FAULT_TOO_MANY_SLICES
Slice I/O nodes can only support 32 slices attached to the network adapter. This error is returned when more than 32 slices are detected.

String: I/O Slice initalization fault too many slices

MPISqNodeMessageIO_SLICE_INITIALIZATION_TIMEOUT
The slice node did not initalize within the expected time.

String: I/O Slice initalization timeout

MPISqNodeMessageIO_SLICE_INITIALIZATION_FAULT_VENDOR_MISMATCH
A slice is attached to the node that is not supplied by MPI. You can only use slices supplied by MPI.

String: I/O Slice initalization timeout

MPISqNodeMessageIO_SLICE_TOPOLOGY_MISMATCH
When attempting to restore the slice parameters to the attached slices of a Slice I/O node, the arrangement of slices did not match the expected arrangement. If you wish to clear the previous slice parameters, you can stop this error by calling mpiSqNodeSegmentParamClear(...).

String: I/O Slice initalization timeout

MPISqNodeMessageIO_SLICE_SERVICE_RECEIVE_ERROR
When attempting to access data on Slice I/O, a communication fault was detected. The message received from the slice was badly formed, errors include CRC and missing start/stop bits.

String: I/O Slice service receive error

MPISqNodeMessageIO_SLICE_SERVICE_TOO_MANY_CHAR
When attempting to access data on Slice I/O, a communication fault was detected. The slice returned too many characters when responding to this request.

String: I/O Slice service too many char

MPISqNodeMessageIO_SLICE_SERVICE_BUS_ERROR_CODE
When attempting to access data on Slice I/O, a communication fault was detected. The slice returned an error code.

String: I/O Slice service bus error code

MPISqNodeMessageIO_SLICE_SERVICE_UNKNOWN_FAULT_CODE
When attempting to access data on Slice I/O, a communication fault was detected. An unknown fault was detected when accessing this slice.

String: I/O Slice service unknown fault code

MPISqNodeMessageIO_SLICE_SERVICE_RESOURCE_UNAVAILABLE
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the requested data.

String: I/O Slice service resource unavailable

MPISqNodeMessageIO_SLICE_SERVICE_NOT_SUPPORTED
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the action requested on this data. For example, a read or write.

String: I/O Slice service not supported

MPISqNodeMessageIO_SLICE_SERVICE_INVALID_ATTRIBUTE_VALUE
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the requested data.

String: I/O Slice service invalid attribute value

MPISqNodeMessageIO_SLICE_SERVICE_ALREADY_IN_MODE
When attempting to access data on Slice I/O, a communication fault was detected. The slice is already in the requested mode.

String: I/O Slice service already in mode

MPISqNodeMessageIO_SLICE_SERVICE_STATE_CONFLICT
When attempting to access data on Slice I/O, a communication fault was detected. The slice can not perform the requested action in its current state.

String: I/O Slice service state conflict

MPISqNodeMessageIO_SLICE_SERVICE_ATTRIBUTE_NOT_SETTABLE
When attempting to access data on Slice I/O, a communication fault was detected. You cannot modify the data on this slice.

String: I/O Slice service attribute not settable

MPISqNodeMessageIO_SLICE_SERVICE_NOT_ENOUGH_DATA
When attempting to access data on Slice I/O, a communication fault was detected. Not enough data was supplied to the slice for this operation.

String: I/O Slice service not enough data

MPISqNodeMessageIO_SLICE_SERVICE_ATTRIBUTE_NOT_SUPPORTED
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the requested data.

String: I/O Slice service attribute not supported

MPISqNodeMessageIO_SLICE_SERVICE_TOO_MUCH_DATA
When attempting to access data on Slice I/O, a communication fault was detected. Too much data was supplied to the slice for this operation.

String: I/O Slice service too much data

MPISqNodeMessageIO_SLICE_SERVICE_OBJECT_DOES_NOT_EXIST
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the requested data.

String: I/O Slice service object does not exist

MPISqNodeMessageIO_SLICE_SERVICE_INVALID_PARAMETER
When attempting to access data on Slice I/O, a communication fault was detected. The slice does not support the specified parameter.

String: I/O Slice service invalid parameter

MPISqNodeMessageIO_SLICE_SERVICE_STORE_OPERATION_FAILURE
When attempting to access data on Slice I/O, a communication fault was detected. The slice failed during a store operation.

String: I/O Slice service store operation failure

MPISqNodeMessageIO_SLICE_SERVICE_UNKNOWN_ERROR_CODE
When attempting to access data on Slice I/O, a communication fault was detected. The error code from the slice was not recognized.

String: I/O Slice service unknown error code

MPISqNodeMessageIO_SLICE_SERVICE_TIMEOUT
When attempting to access data on Slice I/O, a communication fault was detected. The operation on the slice exceeded the timeout threshold.

String: I/O Slice service timeout

MPISqNodeMessageIO_SLICE_SERVICE_RESPONSE_FORMAT
When attempting to access data on Slice I/O, a communication fault was detected. The response from the slice was not formatted correctly.

String: I/O Slice service response format

MPISqNodeMessageIO_SLICE_SERVICE_EEPROM_FORMAT
The data held on the EEPROM on the network adaptor was not formatted correctly.

String: I/O Slice eeprom format

MPISqNodeMessageIO_SLICE_SERVICE_TOO_MUCH_IO
When attempting to access data on Slice I/O, a communication fault was detected. You should remove some slices to stop this error message from being generated.

String: I/O Slice too much IO

MPISqNodeMessagePARAM_READ_ONLY
The drive parameter that the user is attempting to set is read only.

String: Parameter is read only

MPISqNodeMessagePARAM_LOCKED
The drive parameter that the user is attempting to set is not accessible. SelSFDParam must be set to 0, otherwise the SFD motor parameters will be used.

String: SFD motor selected, parameter is locked

MPISqNodeMessageMONITOR_INDEX
Drive does not support the configuring of Monitors through indexing.

String: Monitor config invalid, index not supported

MPISqNodeMessageMONITOR_ADDRESS
Drive does not support the configuring of Monitors through addressing.

String: Monitor config invalid, address not supported

MPISqNodeMessageMONITOR_NA
The node does not support monitors. This message code is returned by mpiSqNodeDriveMonitorInfo(…) if the node does not support drive monitors.

String: Monitor support is not available for this drive

MPISqNodeMessageCOMMUTATION_INIT_FAILURE
The drive communtation intialization failed. This is a drive specific message code returned by a drive specific communtation initialization function.

String: Commutation initialize failure

MPISqNodeMessagePOSITION_CLEAR_FAILURE
The drive position clear failed. This is a drive specific message code returned by a drive specific position clear function.

String: Position clear failure

MPISqNodeMessageNODE_EEPROM_SET
This is an internal error, caused by a failure to re-configure the node’s EEPROM.

String: Node identification invalid, EEPROM over written

MPISqNodeMessageDRIVE_FIRMWARE_FLASH_ERASE_FAILURE
The drive firmware flash erase failed. This is a drive specific message code returned by a drive specific firmware flash erase function.

String: Drive firmware flash erase failure

MPISqNodeMessageDRIVE_MULTITURN_POSITION_READ_FAILURE
The drive multi-turn position data initialization failed. This is a drive specific message code returned by a drive specific multi-turn position data initialization function.

String: Drive ABS multi-turn read failure

MPISqNodeMessagePOSITION_FEEDBACK_UNINITIALIZED
The feedback device position offset has not been initialized. This message code is returned by mpiMotorPositionFeedbackOffsetGet(…) if the feedback device position offset has not been initialized with mpiMotorPositionFeedbackOffsetSet(…).

String: Position feedback offset data uninitialized or corrupt

MPISqNodeMessageFIRMWARE_FILE_CRC_ERROR
The drive firmware file CRC did not match the expected CRC, the file is corrupt. This message code is returned by mpiSqNodeDownload(…) if the drive firmware file CRC fails.

String: File CRC error

MPISqNodeMessageFIRMWARE_DOWNLOAD_WARNING
The drive firmware download version string is not valid. This is a drive specific message code returned by a drive specific firmware download.

String: Firmware download warning