Where can I find the Azure Kinect wiring diagram?

Zack Allen 0 Reputation points
2023-11-02T17:05:49.9633333+00:00

I have been doing some testing with an Azure Kinect. I've noticed it pulls .18-.19 A by USB. If I plug in the barrel connector, the USB line changes to .29 A. Then, I disconnect the barrel connector and the USB line changes to .36 A. I would really like to understand what is going on inside the sensor without having to open it.

Azure Kinect DK
Azure Kinect DK
A Microsoft developer kit and peripheral device with advanced artificial intelligence sensors for sophisticated computer vision and speech models.
287 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Vishnu A 0 Reputation points
    2023-11-02T17:36:25.8733333+00:00

    he behavior you're observing with the Azure Kinect's power consumption when connecting and disconnecting the barrel connector is related to how the device manages its power sources and how it adapts to different power levels.

    Here's a general explanation of what might be happening:

    USB Power: When you initially connect the Azure Kinect via USB, it likely draws around 0.18-0.19 A from the USB port, which is a standard USB power draw for data transfer and basic functionality.

    Barrel Connector: When you plug in the barrel connector (an external power source), it provides more power to the device. The Azure Kinect, in response to the additional power, might adapt its power consumption to handle more intensive operations or to maintain optimal performance, which could result in a higher power draw.

    Disconnecting Barrel Connector: When you disconnect the barrel connector, the Azure Kinect might continue to draw more power from the USB port as it maintains the settings or power profile it adapted to when the barrel connector was connected. This could explain the increased power consumption you're seeing after disconnecting the barrel connector.

    Please note that the exact behavior might depend on the device's internal power management system, and the device's behavior could vary between different versions or models of the Azure Kinect.

    If you're interested in understanding the device's behavior in more detail, you might consider contacting Microsoft's support or Azure Kinect's technical support for specific technical insights. They may be able to provide more information on how the device manages power and what's happening internally without the need to open it.

    0 comments No comments

  2. LeelaRajeshSayana-MSFT 13,621 Reputation points
    2023-11-02T22:45:20.3866667+00:00

    Hi @Zack Allen Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

    There is no open documentation available on how the Azure Kinect DK device is wired internally. However, there is hint given in the documentation to imply the cause of this behavior. Please refer the below note provided in the Hardware Specifications document.

    User's image

    The difference in current draw that you are observing when using the barrel connector versus not using it is likely due to the power management features of the Azure Kinect sensor. When the barrel connector is plugged in, the sensor is able to draw more power from the external power supply, which can allow it to operate at a higher power level. This can result in higher performance or more accurate measurements, but it also increases power consumption.

    When the barrel connector is not plugged in, the sensor is limited to drawing power from the USB port, which can limit its performance or accuracy. However, this also reduces power consumption, which can be beneficial for battery-powered devices or other low-power applications.

    There could also be other factors that influence the difference in current drawn, such as the operating mode of the sensor or the specific USB port that it is connected to.

    Hope this answers your question. Let us know if you need anything further clarification in the comments below.


    If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.

    0 comments No comments