| MEISqNodeMessageINVALID |
| |
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. |
| MEISqNodeMessageNODE_INVALID |
| |
The SynqNet Node number is out of range. This message code is returned if the given node number is less than zero, or greater than or equal to MEISynqNetMaxNODE_COUNT. |
| MEISqNodeMessageSTATE_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).
|
| MEISqNodeMessageCONFIG_NETWORK_MISMATCH |
| |
The type of map file specified in meiSqNodeDriveMapParamFileSet(...) does not match the type of drive found on the network. |
| MEISqNodeMessageMAP_CONFIG_MISMATCH |
| |
The parameter name or number specified in meiSqNodeDriveMapParamFileSet(...) was not valid for the specified drive. |
| MEISqNodeMessageNOT_IN_CONFIG_FILE |
| |
The parameter name or number specified in meiSqNodeDriveMapParamFileSet(...) was not found. |
| MEISqNodeMessageCONFIG_FILE_FORMAT_INVALID |
| |
A file with an incorrect format was used in meiSqNodeDriveMapParamFileSet(...).
|
| MEISqNodeMessageRESPONSE_TIMEOUT |
| |
The drive/node did not respond to the service command issued in a reasonable amount of time.
|
| MEISqNodeMessageREADY_TIMEOUT |
| |
The node/drive did not complete the hand shaking for the service command.
|
| MEISqNodeMessageSRVC_ERROR |
| |
There was an error in carrying out the service command issued.
|
| MEISqNodeMessageSRVC_UNSUPPORTED |
| |
The service command issued is either not supported or recognized by the drive.
|
| MEISqNodeMessageSRVC_CHANNEL_INVALID |
| |
Invalid service channel specified. See MEISqNodeCmdHeader.
|
| MEISqNodeMessageCMD_NOT_SUPPORTED |
| |
The service command is not supported by the node.
|
| MEISqNodeMessageDISCOVERY_FAILURE |
| |
Unable to discover node rescources.
|
| MEISqNodeMessageDISPATCH_ERROR |
| |
Is the default error code returned when a node specific routine has failed. Check the node FPGA version to verify whether or not it is correct. |
| MEISqNodeMessageINIT_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 MEISqNodeInfoFpga. |
| MEISqNodeMessageINTERFACE_ERROR1 |
| |
This is an outdated node, which does not support the current discovery routine.
|
| MEISqNodeMessageFILE_NODE_MISMATCH |
| |
Node type does not match the file provided for download.
|
| MEISqNodeMessageFILE_INVALID |
| |
The file provided for download was not found or was corrupted.
|
| MEISqNodeMessageINVALID_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. |
| MEISqNodeMessageDOWNLOAD_FAIL |
| |
Node firmware download failed. Verify that the firmware file is correct and retry the download.
NOTE: A network reset my be required. |
| MEISqNodeMessageVERIFY_FAIL |
| |
The node FPGA firmware does not match the FPGA image file. |
| MEISqNodeMessageDOWNLOAD_NOT_SUPPORTED |
| |
The downloading of the node firmware (FPGA) image is not supported for this node.
|
| MEISqNodeMessageVERIFY_NOT_SUPPORTED |
| |
The Node specified for verification does not support the upload of the FPGA image. Therefore, the image cannot be verified. |
| MEISqNodeMessageBOOT_ROM_INVALID |
| |
The SqNode Boot Rom identification or version is not recognized by the MPI. |
| MEISqNodeMessageINVALID_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. |
| MEISqNodeMessageINVALID_STR_LEN |
| |
An attempt to write information to the node has failed due to an invalid string length.
|
| MEISqNodeMessageFEEDBACK_MAP_INVAILD |
| |
Returned from meiSqNodeConfigSet(...) when the given secondary encoder (n) is not mappable to the motor on the node specified by MEISqNodeFeedbackSecondary[n].motorIndex. |
| MEISqNodeMessageNODE_FAILURE |
| |
An attempt was made to access a SynqNet node that has a node failure event active.
SynqNet Node Failure describes the details.
|
| MEISqNodeMessageEXCEEDED_MAXIMUM_SYNQNET_PACKET_LIMIT |
| |
When initializing the SynqNet network one of the node requires a SynqNet packet larger that what can be supported.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_MODULE_EEPROM_NOT_PROGRAMMED |
| |
The EEPROM on one of the modules attached to a SQID node has not been programmed.
|
| MEISqNodeMessageIO_MODULE_COUNT_EXCEEDED |
| |
The maximum number of I/O that can be supported by a SQID node has been exceeded.
|
| MEISqNodeMessageIO_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(...), meiSynqNetInit(...). 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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_SLICE_INITIALIZATION_FAULT |
| |
An error was encountered while initalizing the Slice I/O node.
|
| MEISqNodeMessageIO_SLICE_INITIALIZATION_FAULT_TOO_MAY_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.
|
| MEISqNodeMessageIO_SLICE_INITIALIZATION_FAULT_VENDOR_MISMATCH |
| |
A slice is attached to the node that is not supplied by MEI. You can only use slices supplied by MEI.
|
| MEISqNodeMessageIO_SLICE_INITIALIZATION_TIMEOUT |
| |
When initializing a Slice I/O node the initialization routine failed to complete within the expected time.
|
| MEISqNodeMessageIO_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 meiSqNodeSegmentParamClear(...).
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_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.
|
| MEISqNodeMessageIO_SLICE_SERVICE_EEPROM_FORMAT |
| |
The data held on the EEPROM on the network adaptor was not formatted correctly.
|
| MEISqNodeMessageIO_SLICE_SERVICE_TOO_MUCH_IO |
| |
When starting the slice node, too many I/O slices were found. You should remove some slices to stop this error message from being generated.
|
| MEISqNodeMessageBOOT_FILE_NOT_FOUND |
| |
The boot file "kollmorgen_ember.a00" was not found. When downloading drive images to Kollmorgen CD, DASA, and PicoDAD drives, a boot file is downloaded to the drive prior to the actual drive image. This boot file needs to be located in the same directory as the drive's image file that is provided for download.
|
| MEISqNodeMessagePARAM_READ_ONLY |
| |
The drive parameter that the user is attempting to set is read only.
|
| MEISqNodeMessagePARAM_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. |
| MEISqNodeMessageMONITOR_INDEX |
| |
Drive does not support the configuring of Monitors through indexing.
|
| MEISqNodeMessageMONITOR_ADDRESS |
| |
Drive does not support the configuring of Monitors through addressing. |
| MEISqNodeMessageMONITOR_NA |
| |
The hardware support for SynqNet node monitors is not available. This message is returned by meiSqNodeDriveMonitorInfo(…), if the node/drive hardware does not support monitor fields. To avoid this problem, do not use the monitor methods if the SynqNet node hardware does not support it. The monitor field data is SynqNet drive-specific. All drives do not support monitors. SynqNet RMBs (Remote Motion Blocks) or I/O nodes do not support monitors.
|
| MEISqNodeMessageCOMMUTATION_INIT_FAILURE |
| |
Motor commutation initialization failed. This message is returned from sgdsCommutationInit(…) or sgdzBsCommutationInit(…) if the commutation initialization fails.
|
| MEISqNodeMessagePOSITION_CLEAR_FAILURE |
| |
SynqNet drive did not clear the position as requested. This message is returned from sgdsEncoderPositionClear(…) or sgdzBsEncoderPositionClear(…) if the SynqNet drive does not respond to the service command request to clear the feedback position.
|
| MEISqNodeMessageNODE_EEPROM_SET |
| |
SynqNet node EERPOM was modified by the MPI. This message is returned from mpiControlInit(…) or meiSynqNetInit(…) if the Kollmorgen S300, S600 or S1800 drive’s EEPROM was not properly configured at the factory. The MPI will attempt to discover the drive’s configuration and set the appropriate option number in the node’s EEPROM.
|
