ThunderSync3-16 Page 12 of 41
5.1. Using without connecting to a host
When the Hub is switched on and is not connected to a local host computer it is automatically
configured to charge devices using its intelligent charging algorithm. Connect the devices to be
charged to any of the available ports (not the Host Port) using USB - compliant cables.
Once the devices are connected, the algorithm will detect the highest charge rate allowable for each
attached device. Charging at the optimum rate (up to 2.4)A specified by the manufacturer will
commence once profiling is complete. Depending on the state of charge of the device attached, this
may take tens of seconds.
During profiling, the LEDs will flash red. Charging at the optimum rate specified by the manufacturer
(up to 2.4 Amps) will commence once profiling is complete. At this point, the red LEDs will be
constantly illuminated. Depending on the state of charge of the device attached, profiling may take
tens of seconds. Once the device is nearly fully charged, and the current draw falls below a set limit
for a given period, the green LEDs will be illuminated.
5.2. Using when connected to a host
5.2.1 Connecting the Hub to a host computer
You can use either Thunderbolt™ host port on the rear of the hub to connect to your host system;
there are two ports on the rear, so you can use one port to connect the host and the other port to
daisy chain multiple hubs.
5.2.2 Authorising Thunderbolt™ hubs on Linux®
With Linux® systems, it is necessary to authorise/enrol the ThunderSync3-16 before it connects.
To do this, you will need to use "boltctl," which is used to control the Thunderbolt™ device manager.
"boltctl" is the command-line interface to interact with boltd, the system daemon that manages
Thunderbolt™ 3™ devices. Using "boltctl", input the following commands to authorise and enrol your
ThunderSync3-16.
Some useful information on this can be found at the following link.
https://manpages.ubuntu.com/manpages/focal/en/man1/boltctl.1.html
power [-t | --timeout seconds]
Power up the Thunderbolt™ controller. If the Thunderbolt™ controller is not in "native enumeration
mode", it can be completely powered down by the host firmware/BIOS. On supported systems, there
is an interface to "force" power the Thunderbolt™ controller. If supported, this command will request
the daemon to do so. The daemon will keep track of all client requests and will release the force
power override when the last request is released.
To Next Page
Loading...
Need help?
General