Transfer Drive Dock (Classic)

    (CDX-62102-2)

    Storage Media Compatibility

    The Transfer Drive Dock (Classic) is compatible with CODEX Transfer Drives: CDX-37002, CDX-37003 and CDX-37004.

    Operating System

    The Transfer Drive Dock (Classic) is compatible with macOS only.

    OS Versions

    The Transfer Drive Dock (Classic) is compatible with macOS 10.13 or higher.

    We would recommend macOS 10.15 or above to support the most recent version of Device Manager.

    Apple Silicon M1:  macOS 11.4 or above is required to use the Transfer Drive Dock (Classic) with an Apple Silicon M1 Mac.

    Drivers and Licences

    Device Manager for macOS is required to use the Transfer Drive Dock (Classic).

    You can download Device Manager from the CODEX Software Downloads page.

    Device Manager and HDE

    The Transfer Drive (Classic) and Dock requires Device Manager for macOS. (Device Manager is not available on Windows). 

    HDE can only be applied when offloading from original camera media (such as the Compact Drive or SXR Capture Drive). You cannot apply HDE to clips already offloaded from the original camera media. If using an HDE workflow, you will need to apply HDE before offloading to the Transfer Drive. See our HDE section for more information.

    Connection Speeds

    The connection speed of the Transfer Drive Dock (Classic) depends on the type of Thunderbolt connection. With Thunderbolt 3 the Dock can transfer up to 20 GB/sec.

    We recommend connecting the Dock directly to a Thunderbolt 3 port that is not shared to obtain throughput. The Transfer Drive Dock will then provide a connection speed of 20 GB/s. If shared with other Thunderbolt devices on the same system, the connection speed will be reduced.

    Connecting the Transfer Drive Dock (Classic)

    Connect the Transfer Drive Dock (Classic) to the Mac host with a Thunderbolt 3 cable before booting the Mac, or if the Mac is already booted, connect the Thunderbolt 3 cable to the Transfer Drive Dock first and then to the Mac host.

    Connecting on Mac with either of the above methods will result in the Transfer Drive Dock providing the best performance.

    Please note that, although USB-C cables look like Thunderbolt cables, they are different. Make sure the Thunderbolt cable is properly rated for use as they can vary depending on the manufacturer. If you experience reliability issues then try another cable, or a cable from another supplier.

    Compatible Cabling

    The following cable types have been tested and are known to work with the Transfer Drive Dock (Classic):

    • 0.5m Thunderbolt 3 cable (passive type)
    • 1-2m Thunderbolt 3 cable (active type)

    Use with the Compact or SXR Capture Drive Dock

    You can daisy chain the Compact or SXR Capture Drive Dock to the open Thunderbolt 3 port on the Transfer Drive Dock (Classic).

    Please note that when daisy chaining Thunderbolt devices, you will be sharing the bandwidth of a single Thunderbolt bus across all daisy chained devices. This may reduce the maximum read / write speed achieved by an individual device.

    For optimum performance, connect each device to a separate Thunderbolt bus.

    Using a Thunderbolt 2 > Thunderbolt 3 Adapter

    Thunderbolt 2 > Thunderbolt 3 adapters may limit throughput. Ideally the dock should be connected directly to a Thunderbolt 3 port.

    Use with a Mac Pro 2013 model?

    You can connect the Transfer Drive Dock (Classic) to a Mac Pro 2013 model using the Thunderbolt 2 > Thunderbolt 3 adaptor.

    Technical Specifications

    Interface/PowerDual Thunderbolt 3 Interface
    Single or Dual Link Operation Modes
    Operating SystemmacOS and Windows
    Capacities8TB, 16TB, or 32TB capacities
    Dimensions150 x 214 x 58mm
    Operating Temperature0°C ~ 40°C (32°F ~ 104°F)
    Power160W Power Supply, Host Charging 85W (60W while Transfer Drive loaded)
    Storage Humidityto 95% [non-condensing]
    Insertion/removable durability10,000 actions
    Connection SpeedUp to 3GB/s write | 4.5GB/s read (Dual Link Mode)
    Warranty3 year limited warranty
    CertificationCE, FCC
    Product CodeCX.0001005

    Formatting the Transfer Drive (Classic) for use on macOS

    Device Manager (version 6.1 and above) allows you to format a Transfer Drive (Classic) with either an HFS+, ExFAT or CodexFS file system.

    Note: It is not recommended to use Disk Utility for formatting of Transfer Drive as Device Manager will have no awareness of volumes created in this way, and will show the Transfer Drive as unformatted.

    Redundancy Options:

    The table below shows the RAID level of the volumes created when choosing Striped or Parity when you format the volume.

    Redundancy
    		                 File System / RAID-Level
            HFS+        
    		       ExFAT         
    		    CodexFS        
    Striped
    		RAID-0RAID-0RAID-0
    Parity
    		RAID-5RAID-5RAID-3

    You can check how the Transfer Drive is formatted by going to Device Manager > Transfer Drive Rack TB and checking the Type. 

    Go to Device Manager > Transfer Drive - Rack TB and choose the Format option.

    A pop-up window titled Create new volume on Transfer Drive - Rack TB will appear asking you to choose options for three properties. 

    Choose the following options to create a RAID-5 HFS+ volume with read / write access on macOS:

    • Volume Name: Any name you would like to give the volume up to 11 characters.
    • File system: HFS+
    • Redundancy: Parity


    Ensuring Data Safety on Disk Failure

    When your Transfer Drive is formatted with an HFS+ or exFAT filesystem, for best data security, ensure you format the Transfer Drive with the Redundancy option set to Parity. This will create a RAID 5 volume. 

    In this case your data will still be accessible if a single disk fails inside the Transfer Drive. In this case, the status of your Transfer Drive volume will be set to At Risk. If your volume is marked as At Risk, then please backup your data as soon as possible and contact Codex Support.

    If you have formatted the Transfer Drive with the Redundancy option set to Striped, this will create a RAID 0 volume. If a single disk fails inside the Transfer Drive, all data will be lost.

    Updating Firmware

    For information on updating firmware on any CODEX Media Station, please see the Updating Firmware on CODEX Media Stations section of the Device Manager help page.

    “At Risk” or “Failed” status

    If your Transfer Drive volume status is “At Risk”, we would recommend to back up any data on the Transfer Drive and contact Codex Support.

    If your Transfer Drive volume status is “Failed”, please contact Codex Support.
    Our support team is available to answer any questions:

    Telephone and email support is available 8am to 5pm GMT | 8:30am to 5:30pm PDT through our teams in London and Los Angeles.

    Support Email: support@codex.online
    US Support: +1 323 283 8929
    UK Support: +44 203 7000 999
    HOLIDAY SEASON HOURS
    Saturday 23rd 9am - 5pm GMT
    Sunday 24th 9am - 5pm GMT
    Monday 25th CLOSED - Merry Christmas!
    Tuesday 26th 8:30am - 5:30pm PST
    Wednesday 27th 9am - 5pm GMT | 8:30am - 5:30pm PST
    Thursday 28th 9am - 5pm GMT | 8:30am - 5:30pm PST
    Friday 29th 9am - 5pm GMT | 8:30am - 5:30pm PST
    Saturday 30th 9am - 5pm GMT
    Sunday 31st 9am - 5pm GMT
    Monday 1st CLOSED - Happy New Year!
    Tuesday 2nd Normal hours resume

    Cookies improve your experience

    X2X, the company (X2X II LLC represents the CODEX brand), collect device and browser information and store them in cookies - some of which are essential for the website to function properly e.g. security, shopping cart features, sign in. Selecting Accept all you'll get all the benefits of a personalised experience across all our platforms. Choose Manage preferences if you'd like to select individual cookies that X2X can use to personalise your experience. Choose Only essential if you're ok to reject cookies that provide you with an optimized experience. Some of the data is shared with third parties outside the EU such as Google. For more information, see our Privacy Agreement.

    Privacy Policy

    Effective date: May 25, 2018
    Last updated: November 9, 2020