ThunderSync3-C10
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.
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-C10 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-C10.
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.
authorize DEVICE
Authorize a currently unauthorized device identified via its unique id (uuid) DEVICE. If a
key is stored in the database, it will be used, given the security level of the domain
supports secure device connection. Use boltctl list to find out the uuid of a device.
enrol [--policy default] DEVICE
Authorize and record the device with the unique id DEVICE in the database. If the domain
supports a secure connection a new key will be generated and stored in the database
alongside the device and vendor name. The key, if created, will be used in the future
to authorize the device securely.
