The property does not exist in the configuration file. It is not displayed for properties that have been excluded using a filter.
Missing object: object
The object does not exist in the configuration file. It is not displayed for objects that have been excluded using a filter.
Invalid firmware address: property
The firmware address cannot be interpreted by the MEIMap module.
The following elements will be excluded: element list
Elements specified to be excluded will be displayed.
The following elements will be included: element list
Elements specified to be included will be displayed.
Undefined enum value for element
The element is an enum and has a value that cannot be interpreted. Indicative of an internal error.
Undefined enum value for bits in element
The same as above, but applied to a bit mask.
WARNING: Drive firmware version not found in drives map files: (Drive Model, Drive FPGA Version)
A match could not be found for the drive in the set of drive map files (*.dm) in the MEI bin directory. Contact the drive vendor for an appropriate drive map file.
SqNode: service cmd error ::
Node # : Value entered is out of range
The value specified for a drive param is less than the minimum or greater than the maximum allowable value. For some drives, such as the Kollmorgen PicoDAD, the default value for some params are actually invalid. This forces the user to set the params to legal values.
Warning Messages When Getting Configuration
Invalid firmware address group
The firmware address cannot be saved because the address group is invalid.
Invalid enum for element
The element value is set to an enum that does not exist.
The following elements will be excluded: element list
Elements specified to be excluded will be displayed.
The following elements will be included: element list
Elements specified to be included will be displayed.
Error Messages When Setting Configuration
Cannot translate firmware address "address"
Internal error indicating that the address was translated to the wrong firmware address.
Topology mismatch: details
The SynqNet topology saved in the file does not match that of the current physical network. Details indicate the differences in the two topologies.
Invalid input: details
An error occurred while parsing the input. Details indicate the problem.
Invalid input: Could not convert attribute
The value of a property could not be converted. This can happen if the value attribute type is incorrect (a letter instead of a digit, for example), or if the value attribute is missing altogether.
Object type Object does not contain objects of type ObjectType
An object of type Object contained a sub-object with an invalid nodeType ObjectType.
Parser error at line #: details
The input is not valid XML.
Missing MPI Version element (MeiXmlConfig.MPI_INTERFACE_VERSION)
The MPI version is saved in the configuration file. It is a required element.
Errors that Occur when DLL Files are Missing
Missing DLL files are handled differently depending on the version of meiConfig.
In all cases, if a DLL is missing simply contact our technical support team at support@moteiong.com and ask for the correct DLL file. The DLL file should be placed in the same directory as meiConfig.exe.
Below is a description of how missing DLL files are handled for different MPI releases.
MPI 03.03.00
In the 03.03.00 MPI versions, if a necessary DLL is missing, the following message will appear:
This application has failed to start because {SOME_DLL} was not found.
Re-installing the application may fix this problem.
After you click OK, the application will crash and display the following error message:
Traceback (most recent call last):
File "meiConfig.py", line 21, in ?
File "mpy\__init__.pyo", line 1, in ?
File "mpy\mpy.pyo", line 230, in ?
File "mpy\stdmei.pyo", line 4, in ?
File "mpy\_stdmei.pyo", line 9, in ?
File "mpy\_stdmei.pyo", line 7, in __load
ImportError: DLL load failed: The specified module could not be found.
NOTE: Re-installing the application will not solve this problem. Ask our technical support team to provide you with the correct DLL. support@motioneng.com
MPI 03.04.00
In the 03.04.00 and patch versions, up until MPI 03.04.04 (meiConfig version 03.04.18), if mpivc60.dll is missing, the following error message is printed:
meiConfig has failed to load a necessary module.
Be sure that the file mpivc60.dll is accessible.
It was not found in any of these directories:
{List of directories in the PATH environment variable}
Unfortunately, if any DLL is missing other than mpivc60.dll, the following message is printed:
Traceback (most recent call last):
File "meiConfig.py", line 21, in ?
File "zipextimporter.pyo", line 78, in load_module
File "mpy\__init__.pyo", line 1, in ?
File "zipextimporter.pyo", line 78, in load_module
File "mpy\mpy.pyo", line 230, in ?
File "zipextimporter.pyo", line 78, in load_module
File "mpy\stdmei.pyo", line 4, in ?
File "zipextimporter.pyo", line 91, in load_module
ImportError: MemoryLoadLibrary failed loading mpy\_stdmei.pyd
meiConfig has failed to load a necessary module.The traceback information
above may be helpful in determining which module could not be loaded.
The traceback information is usually not very helpful. It is likely that the missing DLL is msvcp71.dll. This DLL became necessary as of MPI 03.04.00. See the Release Notes for more information.
As of MPI 03.04.05 (meiConfig version 03.04.19), the error message for any missing DLL file is:
meiConfig has failed to load a necessary module.
One or more of the following files may be missing:
{List of missing DLL files}
Not found in any of these directories:
{List of directories in the PATH environment variable}
