added content

Author: Teresa-Motiv

articles/kinect-dk/media/multicam-sync-daisychain.png

@@ -13,7 +13,7 @@ keywords: azure, kinect, specs, hardware, DK, capabilities, depth, color, RGB, I
 
 In this article, we will explore the benefits of multi device synchronization and its details.
 
-Before you start, make sure to review [Azure Kinect DK Hardware specification](hardware-specification.md) and the [the multi-camera hardware set up](https://support.microsoft.com/help/4494429). 
+Before you start, make sure to review [Azure Kinect DK Hardware specification](hardware-specification.md). 
 
 There are a few important things to consider before starting your multi-camera setup. 
 
@@ -25,13 +25,13 @@ There are a few important things to consider before starting your multi-camera s
 - Do set the exposure when needed, just call the API once.
 
 
-## Why to use multiple Azure Kinect DK devices?
+## Why use multiple Azure Kinect DK devices?
 
 There are many reasons to use multiple Azure Kinect DK devices. Some examples are
 - Fill in occlusions
 - 3D object scanning 
 - Increase the effective frame rate to something larger than the 30 FPS
-- Multiple 4K color images capture of the same scene, all aligned at the start of exposure within 100 us
+- Multiple 4K color images capture of the same scene, all aligned at the start of exposure within 100 microseconds.
 - Increase camera coverage within the space
 
 ### Solve for occlusion
@@ -45,7 +45,64 @@ Using additional Azure Kinect DK devices will solve this issue and fill out an o
 
 ## Set up multiple Azure Kinect DK devices
 
-Make sure to review [the multi-camera hardware setup article](https://support.microsoft.com/help/4494429) that describes different options for hardware setup. 
+### Before you start 
+
+You might need additional hardware before you can begin syncing devices:
+
+- Additional Azure Kinect devices with the latest firmware. For more info about updating your devices, go to [Update Azure Kinect DK](). 
+- Host PC for each Azure Kinect DK. A dedicated host controller can be used, but it depends on how you're using the device and the amount of data being transferred over USB. 
+- Azure Kinect Sensor SDK installed on each host PC. For more info on installing Sensor SDK, go to [Set up Azure Kinect DK](). 
+- 3.5mm audio cables less than 10m in length (not included). Mono or stereo cables can be used. 
+- One headphone splitter (star configuration only). 
+
+### Set up your devices
+
+Once you have all the hardware to sync your devices, you’ll need to connect the devices and configure syncing. There are two different ways to connect your hardware.
+
+[Make sure to remove the Azure Kinect DK cover to reveal the sync ports!]()
+
+#### Daisy chain configuration 
+
+Sync up to 9 additional devices with the daisy chain configuration. 
+
+![Diagram that shows how to connect Azure Kinect DK devices in a daisy chain configuration.](./media/multicam-sync-daisychain.png)
+
+1. Connect each Azure Kinect DK to power, then connect one device to one host PC. 
+1. Connect the Azure Kinect DK devices to each other using a 3.5mm audio cable. Here's how: 
+   - **On the master device**   
+   Plug in one end of a 3.5mm cable into the sync out port on the first Azure Kinect DK—this is the master device. 
+   - **On the subordinate device**   
+   Plug the other end of the 3.5mm cable into the sync in port of the second Azure Kinect DK—this is a subordinate device. 
+
+To connect more subordinate devices, do the following: 
+
+1. Take another 3.5mm cable and plug one end into the sync out port of the subordinate device. 
+1. Plug the other end of the cable into the sync in port of the next Azure Kinect DK. 
+1. Continue using 3.5mm audio cables to connect Azure Kinect DK devices until you have one device left. The last Azure Kinect DK should only have one 3.5mm cable plugged into the sync in port. 
+
+#### Star configuration 
+
+Sync up to 3 devices with the star configuration. 
+
+![Diagram that shows how to set up multiple Azure DK devices in a star configuration.](./media/multicam-sync-star.png)
+
+1. Connect each Azure Kinect DK to power, then connect one device to one host PC. 
+1. Connect the devices using the headphone splitter and 3.5mm cables. Here’s how: 
+   - **On the master device**   
+   Plug in the headphone splitter into the sync out port on the first Azure Kinect DK—this is the master device. 
+   - **On the subordinate device** 
+   Plug one end of a 3.5mm cable into the sync in port of the second Azure Kinect DK, then the other end into the headphone splitter—this is a subordinate device. 
+
+To connect more subordinate devices, do the following: 
+
+1. Take another 3.5mm cable and plug one end into the sync out port of the subordinate device. 
+1. Plug the other end of the cable into the headphone splitter connected to the master device. 
+
+### Set up synchronized triggering 
+
+Once you've set up your hardware for synchronized triggering, you'll need to set up the software. For more info on setting this up, go to the [Azure Kinect developer documentation]()(English only). 
+
+## Synchronize multiple Azure Kinect DK devices
 
 ### Synchronization cables
 
@@ -59,12 +116,12 @@ Cable requirements:
 
 When using multiple depth cameras in synchronized captures, depth camera captures should be offset from one another by 160μs or more to avoid depth cameras interference.
 
-> [!NOTE]
+> [!NOTE]  
 > Make sure to remove the cover in order to reveal the sync ports.
 
 ### Cross-device calibration
 
-In a single device depth and RGB cameras factory calibrated. However, when multiple devices are used, new calibration requirements need to be considered to determine how to transform an image from the domain of the camera it was captured in, to the domain of the camera you want to process images in.
+In a single device depth and RGB cameras are factory calibrated. However, when multiple devices are used, new calibration requirements need to be considered to determine how to transform an image from the domain of the camera it was captured in, to the domain of the camera you want to process images in.
 There are multiple options for cross-calibrating devices, but in the GitHub green screen code sample we are using OpenCV methods
 There are multiple options for cross-calibrating devices, but in the [GitHub green screen code sample](https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/green_screen) we are using OpenCV method.
 
@@ -80,26 +137,25 @@ If you are setting up multi-camera synchronization on Linux, by default the USB
 
 After setting up the hardware and connecting the sync out port of the master to sync in of the subordinate, we can use the [Azure Kinect Viewer](azure-kinect-viewer.md) to validate the devices setup. It also can be done for more than two devices.
 
-> [!NOTE]
-> The Subordinate device is the one that connected to "Sync In" pin.
+> [!NOTE]  
+> The Subordinate device is the one that connected to "Sync In" pin.  
+>  
 > The master is the one connected "Synch Out".
 
 1. Get the serial number for each device.
 2. Open two instances of [Azure Kinect Viewer](azure-kinect-viewer.md)
 3. Open subordinate Azure Kinect DK device first. Navigate to Azure Kinect viewer, and in the Open Device section choose subordinate device:
 
-
       ![Open device](./media/open-devices.png)
 
 4. In the section "External Sync", choose option "Sub" and start the device. Images will not be sent to the subordinate after hitting start due to the device waiting for the sync pulse from the master device.
 
-
       ![Subordinate camera start](./media/sub-device-start.png)
 
 5. Navigate to another instance of the Azure Kinect viewer and open the master Azure Kinect DK device.
 6. In the section "External Sync", choose option "Master" and start the device.
 
-> [!NOTE]
+> [!NOTE]  
 > The master device must always be started last the get precise image capture alignment between all devices.
 
 When the master Azure Kinect Device is started, the synchronized image from both of the Azure Kinect devices should appear.
@@ -113,8 +169,8 @@ Due to the differences in the clock used by the firmware and the clock used by t
 
 Using the [depth sensor raw timing table](hardware-specification.md) the exposure time can be calculated as:
 
-> [!NOTE]
-> Exposure Time = (IR Pulses * Pulse Width) + (Idle Periods * Idle Time)
+> [!NOTE]  
+> *Exposure Time* = (*IR Pulses* × *Pulse Width*) + (*Idle Periods* × *Idle Time*)
 
 ## Triggering with custom source
 
@@ -133,4 +189,11 @@ A custom sync source can be used to replace the master Azure Kinect DK. It is he
 - [Capture Azure Kinect device synchronization](capture-device-synchronization.md)
 - [Set up hardware](set-up-azure-kinect-dk.md)
 
+## Related topics
 
+- [Meet Azure Kinect DK]() 
+- [Set up Azure Kinect DK]() 
+- [Update Azure Kinect DK]() 
+- [Where to use Azure Kinect DK]() 
+- [Reset Azure Kinect DK](reset-azure-kinect-dk.md) 
+- [Use Azure Kinect Viewer]()