Hi.
During DP's autoconfiguration process, the MA host is a) queried for robotics b) queried for drive serial numbers associated with these robotics c) queried for drives, and their serial numbers. After this, all drives whose serial numbers match that reported by a robotic controller are linked to form a library. For drives where no match can be found, standalone drives are reported. I suspect that is what is happening in your case. To verify this, run this command on your MA host - devbra -dev. Count the number of drive serial numbers reported by the robotic controller. If that number is 19, then the problem is in the device discovery process. If that number is 20, then it's probably an issue with the GUI.
For the first case, there could be driver issues at play. Please ensure that you only have the minimum required drivers in the picture. Since you seem to be using a VLS, please check if all drives are linked to the library at the VLS level, and that any port mappings etc are taken care of.
In case you can't find anything, or if the GUI appears to be a culprit, it might be time to engage DP support.
Regards,
Shishir