MC14-2.4A
Page 15 of 20
This can be due to the host system in question needing to be trusted on the device. This can be
done on the device itself on initial connection.
This could also be due to an insufficient number of endpoints available on the USB controller in
the host system. This is a limitation within the USB controller and can only be resolved if you
connect fewer USB devices to the controller in question.
Cannot connect any more devices
Sometimes you may reach the endpoint limit of your USB controller and this may stop you from
being able to attach any more devices to your host system.
One way you can create more space is to change connections from USB3 to USB2. You can
change the connection by disabling USB3 in the BIOS on startup.
A much simpler way is to use USB2 cables instead of USB3 cables and this will limit the
connection to USB2
6.3. Hub connection issues
If you are having issues with the hub and connecting to your host system please see below
toubleshooting solutions.
Hub not connecting to host
If you are seeing that the MC14-2.4A is not connecting to the host system, one of the issues
may be caused by the USB drivers on your host system not being up to date. It is good practice
to ensure you have the latest drivers and updates installed on your host system, which is
usually handled by the OS, but sometimes may require an update directly from the USB host
controllers manufacturer, which will be found on their website.
USB drivers required are FTDI drivers which can be found from the site
https://ftdichip.com/drivers/
Cannot access COM port
You may get an error message stating "COM (and then a number) could not be opened (Access
is denied.)"
