Using when connected to a host

Connecting the Hub to a host computer

Connect the OEM-U16S Spade to your host system using a Type-B cable. Using an incorrect host cable may result in the hub and all subsequent ports not being recognised by your host. You can use an optical cable to connect to your host as the OEM-U16S Spade is self powered.

The OEM-U16S Spade must be connected physically to a host in order to communicate with the hub and devices. If you wish to connect to a hub remotely (not on the physical host it is connected to) it will still need to be connected to a host and have access to the Cambrionix Hub API which can then be connected to if the relevant steps have been taken, more information on remote access can be seen in the Cambrionix Hub API user manual, which can be viewed from the website. https://www.cambrionix.com/cambrionix-api

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 1.5A. If the connected device does not comply with BC1.2, the charge current will be limited to Standard Downstream Port (SDP) which is 0.5A in compliance with USB specifications. Information on the different charging levels can be found in the Port Specifications section.

The OEM-U16S Spade also has an 'ALT Sync Charge' mode which is on by default, having this option selected will allow the OEM-U16S Spade to charge devices up to 2.1A whilst syncing data.

If you wish to limit the charging to your devices whilst connected to your host system then you can disable CDP. You can disable CDP through Internal hub settings either by going through the advanced settings and turning "Sync charge" off or through the API and disabling it via code. For example, the instructions would be below using the command line.

The CLI commands for turning off the sync charge options, with a 1 or 0 per port.

settings_unlock 
settings_reset 
settings_set sync_chrg 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
settings_set alt_sync_chrg 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
reboot

This can also be done via the API if this is easier. Just supply that string (joined with \n) like:

cbrxapi.cbrx_connection_set(handle, "Settings", "settings_unlock\nsettings_reset\nsettings_set sync_chrg 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0\nsettings_set alt_sync_chrg 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0\nreboot")

Note that settings_reset clears any previous settings, so if you need to retain something else, it would be better to issue settings_display first, which gives you the entire settings which you can then modify and re-issue in entirety.

For more information on this please see the internal hub settings section of CLI manual, which can be viewed from the following link. www.cambrionix.com/cambrionix-cli

Data Transfer

If you wish to transfer data, change applications, restore or update your mobile device, a data connection to a local host computer is required. The Cambrionix Hub API and software is compatible with macOS®, Windows™ and Linux® operating systems and can transfer data between these operating systems and many mobile operating systems such as iOS™ and Android™.

In order to transfer data, connect the host port to your local (host) computer using a Type-B compliant cable. Any devices connected to the hub will now appear as if they were connected to the host computer’s USB port.

Communication Interface and Protocol

The OEM-U16S Spade appears as a virtual COM port (VCP). On Microsoft Windows™, the system will appear as a COM port, the COM port number can be found in device manager. On macOS®, a device file is created in the / directory. S is an alpha-numeric serial string unique to each device

Devices incorporate a USB to UART converter IC from FTDI International. On Windows 7 or later, a driver may automatically be installed (if Windows is configured to download drivers from the internet automatically). If this is not the case, or if a Mac® or Linux® platform is used, the driver may be downloaded from www.ftdichip.com. The VCP drivers are required. For Linux® or Mac computers, the default OS drivers should be used.

The default communications settings are as below, ANSI terminal emulation should be selected.