Red X on My Mapped NI Motion Device After Rebooting RT Primary Software: Driver Software>>NI-Motion/FlexMotionPrimary Software Version: 7.2 Primary Software Fixed Version: N/A Secondary Software: LabVIEW Modules>>Real-Time Module
Problem: I get a red X on my mapped NI motion device after I reboot the RT Controller. I have tried refreshing MAX, unmapping and remapping, and restarting MAX. None of them seem to work. How do I fix this? Solution: A red X on a motion controller in MAX, whether it is a mapped board or not, means that the driver is reporting an error when trying to comunicate with the board from MAX. This is usually caused by an unreachable PXI chassis because it is turned off, unplugged from the network, or currently rebooting. The solution would be to turn it back on, plug it back in, or wait for it to finish rebooting to remove the red X. For more information about configuring an RT System, see the related link below. In this case, the driver is unable to communicate with the remote motion board and although the PXI chassis is reachable the red X won't go away. We have only seen this particular issue when using a crossover cable. There are a number of workarounds for this issue:
Related Links: KnowledgeBase 2CGF3OKN: Configuring RT Series PXI Controllers in LabVIEW Real-Time 6.0 (or higher) KnowledgeBase 46IE5IFL: MAX is Slow When a Mapped Motion Board is not Reachable Attachments:
Report Date: 02/16/2007 Last Updated: 06/18/2007 Document ID: 46FGCRFL |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
