No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-how to solve the problem that there is no association between machine arm and driver in NBU6.5.4

Publication Date:  2012-10-15 Views:  122 Downloads:  0

Issue Description

We can find the machine arm and driver mapped from VTL in Windows system, and it shows the driver has installed. But we can find these devices in NBU6.5.4, and there is no association between machine arm and driver. There is no association between Robot 0 and IBM ULTRIUM-TD3’s driver, this leads the driver recognize as Standalone Drivers, it shows in picture 1.

Alarm Information


Handling Process

On common sense, Windows system can recognize the machine arm and install driver correctly. But in some sense there will be as the situation we have introduced. On this sense, we can uninstall the machine arm driver and scan the hardware again to let the system install device diver automatically. If there is still no association in NBU, we can reboot the system.

Root Cause

The machine arm driver hasn’t installed correctly.