Select a Step ......................................................... Command Line Syntax Examples Firmware/ Library Upgrades Configuration File Format Configuration File Editors Configuration File Transformation Filter Files SynqNet Topology Issues Warning and Error Messages Appendix A: Supported MPI Objects Appendix B: MPI Version Independence Appendix C: FAQs for meiConfig and meiConfigGui Appendix D: Firmware Address Configuration Elements Version History

SynqNet Topology Issues

When meiConfig creates a configuration file, the SynqNet network topology is saved in the file. Before setting the controller configuration from a file, meiConfig compares the current physical network with the previously saved topology in the file. If the two topologies are not equivalent, then meiConfig will exit and an error message will appear. It is possible to override this behavior with the -noTopoCheck command line option.

Network Topology Criteria

The following criteria are used to detect network topology mismatch:

MPISynqNetInfo.nodeCount
MPISynqNetInfo.nodeOffset
MPISynqNetInfo.networkType
MPISqNodeInfo.driveCount
MPISqNodeInfo.motorCount
MPISqNodeInfo.motorOffset
MPISqNodeInfo.id.nodeType
MPISqNodeInfo.id.option
MPISqNodeInfo.fpga.vendorDevice
MPISqNodeInfo.id.switchId
MPISqNodeInfo.fpga.type == MPISqNodeFpgaTypeRUN_TIME
MPISqNodeDriveInfo.firmwareVersion

For more information, see: MPISynqNetInfo | MPISqNodeInfo | MPISqNodeDriveInfo

Previous | Next