Drive AGX Xavier Pegasus Electrical Integration (Power, Ethernet, Fakra)

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version

Target Operating System

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

SDK Manager Version

Host Machine Version
native Ubuntu 18.04

Hi everyone,

We are currently in the process of designing/installing the electrical interface for our Nvidia.

We had a couple of questions pertaining to the peculiarities of the AGX Pegasus 2x dGPU (TU100) system. Please let me know if the post should be split up into multiple posts.

I have included some relevant forum posts and documents that I have tried to comprehend to the best of my ability prior to posting:

a) DRIVE AGX Xavier vehicle installation and wiring

b) What is the nominal current of AGX

c) Power consumption estimations & hardware (regulator) recommendations

d) NVIDIA DRIVE Documentation | NVIDIA Developer

e) DRIVE AGX: Out of specification power input may damage the system

f) DRIVE AGX: Wait time required between system power cycles

g) Power requirements Pegasus with dGPU

  1. Is it safe to say that there is NO COM Express modules installed on the E3550 Unit with PN# 940-63550-2200-100? Therefore, is there no need for an isolated power supply? (Such as the CALEX solution discussed in the documentation.

  2. Provided we are currently using a DriveWorks OS Linux 5.2.6 and Driveworks 4.0, are the protections for low voltage discussed in FAQ (e) in place within Driveworks 4.0 as well as Driveworks software 9.0.? If not what kind of active low voltage protection do you recommend?

  3. For the sensor suite that uses Fakra (Cameras etc) we intend to extend the provided cables. It is our understanding that it is imperative to match the impedance of interconnections. Do you know of any panel mount options that are male-female? Or is it preferable to use male-female extension cables rather than cable-panelmount-cable.

  4. Nvidia no longer sells the ED3579 (Dual GbE Dongle) ethernet adapter. It is our understanding that sensors should be attached to the Fakra connectors, and ideally not all on the same ethernet port. Is it OK to put a multitude of sensors (Inertial GPS, LiDars (x3), Radar etc) on a single ED3579 as long as the data rate is below the port maximum? Or are there any replacements for the ED3579 available should sensors have their own ethernet ports?

  5. For the electrical integration, is the following simplified setup acceptable?

Battery->Master Inline Switch->Busbar->Relay (Connected to switch on/off Nvidia Power)->120ABreaker->Nvidia Anderson Connector.

  1. While running some basic computations our Nvidia seems to pull approximately 20Amps. The EDP in the documentation is stated as being 95A. Can the EDP value be assumed to be an average current draw, or is it more of a maximum limit?

Our usage does not have a large alternator, therefore, to properly size our battery capacity for a day of testing I need to estimate the average current draw. Example: with 3 Lidars, 4 cameras and a radar can one expect to pull around 50A? Or is 95A truly the average current draw?

Q1, no need for an isolated power supply but need Battery Isolator.
Q2, Driveworks software 9.0 could use same 7V for <10ms low threshold.
Q3, Quad Camera Connector, TE Connectivity MATE-AX 0-2304168-9, cable LEONI Dacar® 302, silimar one can be used.
Q4, E3579 Dual Ethernet Dongle dongle is designed to allow the automotive 1000BASE-T1 port on the HSD connectors of the NVIDIA DRIVE AGX system to communicate with other systems through the standard RJ45 Ethernet connectors and Ethernet cables.
Sensors attached should be within 1000BASE-T bandwidth.
Q5, Input power should within spec and provide enough current with protect function.
Q6, System EDP Current define as (200ms moving average) @ 12V, 95A.
Inrush Current (Magnitude / Duration) @ 12V, 130A / 200us.
EDP is not average current.

Thank-you for the reply Jim.

If possible could you re-clarify some of the points.

Q1: We already have a battery isolator between our Vehicle Battery and our “Secondary” battery. Is this what you are referencing?

Q2: In your FAQ it states “DRIVE Software 9.0 contains a software patch that prevents this damage from occurring” in reference to the 7V for <10ms threshhold. My question is if this “software patch” is also included in “DRIVE OS Linux 5.2.6 and DriveWorks 4.0”. As you make a distinction between the two in the “Software version” above all forum questions.

Q3: The MATE-AX 0-230416-9 is for a PCB-Panel mount, however we are looking for a Box-Panel mount. An example of the connector we are looking for but in SMA form follows. Do you know of any Fakra options similar to this?

Q4: Is it safe to assume that we can therefore put all our sensors (4 total) into a ethernet switch such as below, and then onto a single port on the E3579?

Q5: That is understood thank-you.

Q6: Thank-you for clarifying that EDP is not average current. We therefore understand that the EDP and Inrush are both “Peak” currents that will not necessarily be seen “Continuously”. However, if possible we would like to know a ballpark range that we can assume to be using “Continuously”, in order to size our battery. Example: In the hyperion setup during heavy GPU/CPU usage does the Nvidia pull 30A? 60A? 80A?. A ball park +/- 20A range is a sufficient response for our needs. But I would like to avoid assuming that the Nvidia pulls 95A continuously. I will end up with oversized batteries and wires.

Thank-you in advance.


I’d also like to know the answer of Q6. Say the Nvidia is running at “steady state”, but while having the maximum number of sensors plugged in : what would be the “continuous” current?