
TS3-16 Page 12 of 33
enroll [--policy default] DEVICE
Authorize and record the device with the unique id DEVICE in the database. If the domain
supports secure connection a new key will be generated and stored in the database
alongside the device name and vendor name. The key, if created, will be used in the future
to securely authorize the device.
5.2.3 Charging
When the Host Port is connected to a local computer, the hub defaults to Sync mode and
charge currents are determined according to USB Implementers Forum (USBIF) Super-Speed
USB3 specifications. If the attached device complies with USB-IF Battery Charging
specification BC1.2 and supports Charging Downstream Port (CDP), the hub can provide
high-speed charging at up to 2.4A. If the connected device does not comply with BC1.2, the
charge current will be limited to 900 mA in compliance with USB specifications.
5.2.4 Data Transfer
If you wish to transfer data, install applications, restore or update attached mobile devices, a
data connection to a local host computer is required. The hub works independently to the
Operating System (OS) and data transfer can be performed on all common operating systems,
such as iOS™, Android™, Chromebook™ and Microsoft Windows™. Many versions of Linux® are
also supported.
In order to transfer data, connect the Thunderbolt™ port of your local (host) computer to one
of the Thunderbolt™ ports on the back of the hub using a Thunderbolt™ 3 compliant cable. A
Thunderbolt™ 2 cable with a Thunderbolt™ 2-3 adaptor can also be used with consequently
reduced data speeds. Any devices connected to the hub will now appear as if they were
connected to the host computer’s USB port. The hub is fully compliant with SuperSpeed USB3.2
and can provide up to 5Gbps data transfer speeds per port. A yellow LED above each port will
illuminate when Syncing. You can use the program of your choice to transfer data to and from
your device. If the attached device has a BC1.2 compliant CDP port, the device can draw up to
1.5A while transferring data.
5.2.5 Communication Interface and Protocol
TheTS3-16 appears as a virtual serial port (also called a UART or VCP). On Microsoft Windows,
the system will appear as a COM port. On macOS, a device file is created in the / directory. This
is of the form /dev/tty.usbserial S where S is an alpha-numeric serial string unique to each
device.