Norza D55 Developer Community Driver

Version specific info
RAMPS 1.7 RAMPS 1.6 RAMPS 1.5 RAMPS 1.4.4 RAMPS 1.4 RAMPS 1.3 RAMPS 1.2 (RAMPS 1.2 old) and older
RAMPS 1.4.4

Release status: Prototype

Description
RepRap Arduino Mega Pololu ShieldArduino MEGA based modular RepRap electronics.
License
Author
Contributors
Based-on
Categories
CAD Models
External Link


  • 1Summary
  • 2Files
  • 4Stepper driver Jumper settings
  • 5Motherboard/Controller board options
    • 5.1Arduino Mega
      • 5.1.1Firmware - Marlin
    • 5.2Arduino Due
    • 5.3Re-Arm
      • 5.3.4Connect SPI pins
    • 5.4Adafruit Grand Central M4

The RAMPS 1.4.4 shield is a RAMPS-1.4-pin-compatible shield that can be used with:

  • 8-bit or 32-bit controllers
  • a single 12V or 24V power supply.
  • TMC2130 drivers via SPI bus jumper selection.
  1. HP doesn't have Windows 7 drivers for the D530, the newest ones are for Vista. You could try doing to the individual sites of the video card for that model (intel, ati, nvidia), the network adapter, etc.
  2. Download firmware for Nikon digital products (firmware being the built-in software that controls cameras and other devices). To view descriptions, cautions, and download and installation instructions, click “View download page”.Note that a card reader or other equipment may be required for some firmware updates.

Stepper driver Jumper settings. Under each stepper driver is a set of jumper options. By setting the jumpers, it is possible to use the standard driver chips, like A4988 and DRV8825 chips (and others) or it is possible to connect the SPI bus signals, to TMC2130 stepper drivers.

And:

  • On-board 3V -> 5V buffer chip, for a higher Gate voltage control of all mosfets
  • Two additional Fan mosfets. For a total of 3 PWM controlled Fans. With 3x 2.54mm jumper pins for Fan connections (max 1A per fan)
  • Power selection for Fans:
    • Fan0: power from 24V or 12V rails
    • Fan1+2: power as Fan0, or from on-board optional 5V DC-DC switch mode power supply module
  • SMD mosfets. (datasheet numbers: 1.65 milli Ohm for Heated Bed, 3.3 milli Ohm for Hot-end) Max 1A for Fans.
  • 'on-board' 24V-to-12V DC-DC switch mode module
  • A 4-pin 7.62 mm (20A) Screw Terminal Power Connector, for Power Supply and Heat Bed connections
  • A 'blue' 5.08 (13A) Screw Terminal Connector for Heat-Bed connection
  • Jumper selection of 12V (or 8.5V) -> Vin on the Arduino. No soldering of D1 needed.

Further additions are:

  • 24V protection on Thermistor inputs
  • 100nF capacitors on end-stop pins.
  • 12V protection on end-stops
  • A high voltage (12V) Z-probe port. Connected to either Z-Min (default) or Z-Max end-stop pins
  • Hardware SPI port (at center of board) for use with the Arduino DUE controller
  • Includes all RAMPS familiar Aux ports - like: Aux-1, Aux-2, Aux-3 (with extensions), Aux-4, Servo, PS-on, I2C, 6x End-stops, 3x Thermistors
  • Jumper connection access to 5V, 8.5V, 12V, 24V rails. In addition to the usual +Voltage (Vcc pins) on the Aux ports.

And some extra options:

  • Easy use with a 5V PT100 sense amplifier - even on 3V controllers
  • An on-board Resistor option. For experimenting with Thermistor self heating issues
  • Lower voltage to Vin (to help prevent overheating of the Arduino Mega 5V volt regulator)
    • either via on-board diodes (lower the Vin Volt by about 1V per diode), or
    • via an on-board DC-DC 8.5V module
  • Optional on-board 24LS256 EEPROM. For use with controllers that have no built-in EEPROM.


  • Aux and Pins

  • Board

  • Test fitting an early version on a Re-ARM controller

Click any image for larger versions

How this board came into existence

While I was designing the RAMPS 1.7 shield, a friend said: Well, that is all good and dandy, but 10x10 cm is too big for my printer. I need a RAMPS shield that can do:

  • TMC2130 drivers (without SPI wires floating on-top),
  • can be used with a single 24V power supply,
  • and still only be the size of a standard RAMPS board - or it will not fit nicely on my printer.

And this RAMPS 1.4.4 shield is what we have ended up designing, over several experimental iterations.

Once we have a working prototype, we will share the design files.

For now, various files are available at GitHub

If you are interested in being a part of the early-adopters/testers team, then please send me an email to [email protected]

It is also possible to participate in the RepRap forum discussion here The first 4-5 pages of the forum thread are about the RAMPS 1.7 design, but after that, the focus is moved to this RAMPS 1.4.4 design.

Schematics

PDF version here

Do NOT reverse polarity on the power connector. There is NO PROTECTION DIODE for the mosfet's.

Reversing polarity is likely to fry your electronics.
Triple check to make sure the polarity on your power input is 100% correct!

Under each stepper driver is a set of jumper options.

By setting the jumpers, it is possible to use the standard driver chips, like A4988 and DRV8825 chips (and others) or it is possible to connect the SPI bus signals, to TMC2130 stepper drivers.

A4988 etc.

TMC2130 and TMC5160


Learn more about the TMC2130/TMC5160 stepper drivers at the Watterott FAQ and Watterott Comparison List (look for instance at the RDS-On column).


Please note that from Rev.C4 (and forward) the RAMPS 1.4.4 shield now have a diode connection (S18) from Vcc to Vmot, as well as a diode connection (S17) from 'Always-5V' to Vmot, so the 'USB power supply' and '3-5V internal logic' issues should not be a problem, when using the SilentStepStick TMC2130/TMC5160 stepper drivers with the RAMPS 1.4.4 shield.

Use the RAMPS 1.4.4 shield with one of the following controller boards:

Arduino Mega

Works as is. Just make sure that jumper J3 is used/shorted/mounted.

Otherwise the RAMPS 1.4.4 shield uses the same settings as the RAMPS 1.4 shield, with the following exceptions:

  • PS-on, is controlled by pin D39.
And is firmware 'Active High' (because of the additional 'open collector' mosfet used to actually do the pull-down of the 'Power On' pin of an ATX style power supply).
Where as the original RAMPS 1.4 PS_ON signal is firmware 'Active Low' (in order to turn on an ATX style power supply).
  • Fan 0 is still D9
  • Fan 1 is D7
  • Fan 2 is D12


CS pins for TMC2130/TMC5160 drivers are all connected to Aux-4, on pins that are NOT being used for the RRD Graphic LCD or 20x4 Text LCD displays. This leaves all pins on Aux-1, Aux-2, Aux-3 and Servo available for regular use.

The TMC2130/TMC5160 CS pins are as follows:

  • CsX = D47
  • CsY = D45
  • CsZ = D32
  • CsE0 = D22
  • CsE1 = D43

D22 is technically not an Aux-4 pin, but rather a J10 pin on the RAMPS 1.4.4 shield.


Firmware - Marlin

Marlin 2.0.x

For Marlin 2.0.x, in file 'configuration.h', select the following:

  • For the line MOTHERBOARD,
    • select (or type) '#define MOTHERBOARD BOARD_RAMPS_14_EFB'
  • For regular Z-Min use,
    • make sure that the line 'Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN' is uncommented (no // in front of the line)
    • possibly set : #define Z_MIN_PROBE_PIN 19
  • If controlling a power supply, set
    • #define PSU_ACTIVE_HIGH true


For Marlin 2.0.x, in file: 'configuration_adv.h' possibly do the following changes:

  • #define X_CS_PIN 47
  • #define Y_CS_PIN 45
  • #define Z_CS_PIN 32
  • #define E0_CS_PIN 22
  • #define E1_CS_PIN 42
  • #define E0_AUTO_FAN_PIN 7


For Marlin 2.0.x, in file src/pins/ramps/pins_RAMPS.h possibly do the following changes:

  • #define Z_MIN_PROBE_PIN 19
  • #define PS_ON_PIN 39

If not set in file configuration_adv.h, then change to the following lines

  • #define X_CS_PIN 47
  • #define Y_CS_PIN 45
  • #define Z_CS_PIN 32
  • #define E0_CS_PIN 22
  • #define E1_CS_PIN 42

Marlin 1.1.x

For Marlin 1.1.x, in file 'pins_RAMPS_14.h' possibly do the following changes:

- If using the PS_ON_PIN, change it from 12 to 39

- If using TMC2130/TMC5160 stepper driver, with SPI control, then set the corresponding numbers

  • For X change from 53 to 47
  • For Y change from 49 to 45
  • For Z change from 40 to 32
  • For E0 change from 42 to 22
  • For E1 change from 44 to 43

Arduino Due

Make sure that the jumper J3 is used/in place/mounted

Thermistor pins

Norza D55 Developer Community Driver

Thermistor pins are default on A13-A15. But for use with Arduino DUE it is necessary to physically connect the thermistor signal pins to A9-A11

On the RAMPS 1.4.4 board this can be done in one of several ways.

One way is:

  • Cut the pins connecting the 144-shield to the Arduino, on pins A13-A15, and
  • solder the three jumpers marked J22 on the bottom of the Shield.

This will connect the thermistor signals to the correct Arduino DUE analog pins. But it will not be possible to access the A13-A15 (D67-D69) pins, for other possible uses. And on a standard 3D printer, this is fine.


Another way is:

  • Cut the three pcb paths, at the letter 'Z' (for the Z stepper driver).
The cut path is shown with two lines on the silk screen
  • Solder wires (or pins) into the three holes marked as J23 (J23 is shown on the bottom of the shield)
  • use jumper wires to connect from J23, to AUX-2.
    • A9 (D63) connects to the Hot-End (previous A13)
    • A10 (D64) connects to the Bed (previous A14)
    • A11 (D65) connects to the Chamber (previous A15)

It is now possible to replace the A13-A15 pins with longer pins (or solder some pins directly on top), so one could get access to pins A13-A15 pins, for other purposes. On a standard 3D printer, this is not necessary - for the adventures hacker, it might be useful to have access to all un-used pins.


A third way is:

  • to select the RAMPS 1.4.5 PCB files.
The 1.4.5 PCB file is the same as the 1.4.4 PCB files - except for the analog pin connections.
And you can still use the 1.4.5 shield with the Arduino Mega or Adafruit Grand Central M4 controllers, without hardware modification, by just changing some numbers in the pins_.....h files.

A note about Pull-down resistors, DUE and Power-on pin state

As the DUE pins are internally pulled High, during power-up (and rest/being programmed) it is necessary to use some pull-down resistors to pins/functions that would otherwise be running wild, while not under firmware control.

For this reason, all mosfet signals on the RAMPS_1.4.4 have 10K pull-down resistors mounted.

All other functions are fine with being internally pulled High, during power-up of the Due.

Firmware - Marlin

Support for 32-bit controllers (like the DUE), is only available from Marlin 2.0.x and upwards.


In file 'configuration.h', select the following:

- For the line MOTHERBOARD, select (or type) '#define MOTHERBOARD BOARD_RAMPS4DUE_EFB '

- For regular Z-Min use, make sure that the line 'Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN' is uncommented (no // in front of the line)


In file: 'configuration_adv.h' possibly make the following changes

  • #define X_CS_PIN 47
  • #define Y_CS_PIN 45
  • #define Z_CS_PIN 32
  • #define E0_CS_PIN 22
  • #define E1_CS_PIN 42
  • #define E0_AUTO_FAN_PIN 7


In file 'src/pins/ramps/pins_RAMPS.h' possibly make the following changes:

- If using the PS_ON_PIN, change it from 12 to 39

- If using TMC2130 stepper driver, with SPI control, it could be useful to also then set the corresponding CS numbers. But if they have already been defined in configuration.adv it is not necessary to repeat in the pins_RAMPS.h file

  • For X change from 53 to 47
  • For Y change from 49 to 45
  • For Z change from 40 to 32
  • For E0 change from 42 to 22
  • For E1 change from 44 to 43

Connecting RRD LCD displays

As the DUE board primarily is a 3V board, the standard RRD LCD dispays, become quite dim, if operated on only 3V.

An easy way to fix this, is to use one of the LCD144 adapters that connect to the Aux-3 and Aux-4 ports, and provides 5V to the LCD's - without risk of damage to the 3V DUE pins.

As the DUE pins are also High, during power-up, the LCD beep will go off, during power-up - unless a pull-down resistor prevents this.
The LCD144 adapter boards all provide this pull-down resistor on the buzzer pin.


These LCD144 adapter boards:

  • provide the EXP-1 and EXP-2 sockets that the RRD LCD displays use.
  • they also repeat the AUX-4 port, so any pins, not used for controlling the LCD display, can be used for other purposes.
  • they also repeat the SPI pins, so other SPI controlled modules/chips can be connected.
  • they connect to the Always-5V-rail (as well as the Vcc rail), so 5V can be made available for the LCD backlight.
  • they have a pull-down resistor to stop the buzzer going off, during DUE power-up.
  • and there can be other functions as well, depending on the particular version of LCD144 adapter board.


PCB files 'LCD144-A' is a basics EXP-1 and EXP-2 sockets adapter board, as well as it repeats the Aux-3 port.


PCB files 'LCD144-B' offers the same as LCD144-A, but also has a 24LS256 EEPROM footprint. In case one does not want to use the EEPROM foot print provided on the underside of the RAMPS-144 and -145 shields.

Re-Arm

As the RAMPS 1.4.4 shield uses both 3V and 5V rails on the shield, it is necessary to do the following four things to get the shield working with a Re-ARM controller board.

  • Remove shield jumper J3
  • Power the shield Always-5V-rail with 5V from a Re-ARM Aux pin
  • Use shield J1 jumper to get 3V to the shield Vcc rail
  • Connect SPI pins

Remove J3

The Re-ARM controller board is a 3V only board, for all pins that go via the 'Arduino Mega' style connectors. For this reason shield jumper J3 needs to be removed. On other controllers, the jumper J3 takes 5V from the +pins next to D22 and D23. These +pins are however only 3V on the Re-ARM controller board. So for Re-ARM the J3 jumper needs to be removed, and 5V needs to be found else where.

-ToDo: picture of J3

Power the shield Always-5V-rail with 5V from a Re-ARM Aux pin

The Re-ARM board has +5V available on three pins, on the Re-ARM Aux ports (UART, J3, J12).
Connect one of these pins to one of the Always-5V-rail pins on the RAMPS_144 shield (like a pin at J7)

Re-ARM Aux ports (UART, J3 and J12) has 5V pins

-ToDo: picture of the 5V-rail pins on the RAMPS_144 shield

Use shield J1 jumper to get 3V to the shield Vcc rail

As the Re-ARM board has no I/O pin (at the power pins of Arduino Mega-style connectors), it is necessary to use a jumper to get 3V power to the Vcc-rail of the RAMPS_144 shield.

Shield jumper J1 can be used to do this.

  • Place a jumper on the 3V side of the J1 shield jumper.

-ToDo: picture of jumper at J1

Connect SPI pins

On the RAMPS_144 shield the pins D50-D52 (SPI pins) are (by default) only connected to J11. This works with other controller boards, because on the other boards, the SPI signals are also available on the central SPI connector.

On the Re-ARM board there are however no central SPI connector, so SPI is only available from the D50-D52 pins.

There are two options for connecting the D50-D52 pins to the rest of the SPI bus.

A) there are solder jumpers located right next to the D50-D52 pins.
B) use the LCD144-C LCD adapter board. It connects J11 pins to the rest of the SPI bus.


Solder jumpers

-ToDo: picture of the solder jumpers.

LCD144-C adapter board

-ToDo: picture of the adapter, and how the J11 pins can be connected to the rest of the SPI bus.

For TMC2130/YMC5160 stepper drivers

To use the TMC2130/TMC5160 stepper drivers with the Re-ARM controller board, some jumpers need to be put in place.

The CS pins of the TMC2130 stepper drivers are all brought to pins on Aux-4. Aux-4 pins that are Not being used for LCD control.

None of these non-LCD-pins on Aux-4 does however have any connections to the Re-ARM MCU (on the Re-ARM controller board itself - The MCU pins simply are not there).

So the CS pins on Aux-4 need to be re-routed/jumped to functional pins on the Re-ARM. There are several options of how to do this. The easiest way to do this, is however to use the LCD144-C adapter board.

  • Option A. -ToDo: introduce the LCD144 adapter boards.
  • Option B. Use jumper wires from one Aux-4 pin to another Aux-4 pin.
  • Option C. Use jumper wires from Aux-4 pins to the Re-ARM Aux port J12


The TMC2130 CS pins are brought to Aux-4 pins as follows:

  • CsX = D47
  • CsY = D45
  • CsZ = D32
  • CsE0 = D22
  • CsE1 = D43

D22 is technically not an Aux-4 pin, but rather a J10 pin on the Ramps_144 shield.

The LCD144-C adapter does however connect to all of Aux-3, Aux-4, J10 and I2C pins from the Ramps_144 shield. And thus it brings things together in a convenient package solution.

Adafruit Grand Central M4

Expected to works as is. Just make sure that jumper J3 is used/in-place/jumped/shorted.

Testing for use with the Adafruit Grand Central M4 (AGCM4) is to be done shortly.

What is know at this point is, that the ACGM4 board uses a different numbering scheme (for referring Digital numbers to the Analog pins) than the Mega and DUE does. See below for a conversion table.

Digital numbering of Analog pins of the AGCM4 board

RAMPS 144MEGAACGM4
X_STEPD54 (A0) D67 (A0)
X_DIRD55 (A1) D68 (A1)
Y_END56 (A2) D69 (A2)
Aux-1D57 (A3) D70 (A3)
Aux-1D58 (A4) D71 (A4)
Aux-2D59 (A5) D72 (A5)
Y_STEPD60 (A6) D73 (A6)
Y_DIRD61 (A7) D74 (A7)
Z_END62 (A8) D54 (A8)
Aux-2D63 (A9)D55 (A9)
Aux-2D64 (A10)D56 (A10)
Aux-2D65 (A11)D57 (A11)
Aux-2D66 (A12)D58 (A12)
Hot (T0)A13 (D67)A13 (D59)
Bed (T1)A14 (D68)A14 (D60)
Chamber (T2)A15 (D69)A15 (D61)
Retrieved from 'https://reprap.org/mediawiki/index.php?title=RAMPS_1.4.4&oldid=186403'
  • SOLUTIONS
    • DRIVE AV

This page provides access to software for developers using NVIDIA DRIVE™ AGX, DRIVE Hyperion and DRIVE PX 2 Developer Kits.


Borza D55 Developer Community Drivers

Developers using DRIVE AGX Developer Kits may choose between:

  • DRIVE OS 5.2.0 and DriveWorks 3.5 which includes more recent versions of CUDA and TensorRT. DRIVE OS and DriveWorks include the DRIVE OS and DriveWorks modules per diagram above.
  • DRIVE Software 10.0 which is intended for Hyperion Developers. DRIVE Software includes the DRIVE OS, DriveWorks, DRIVE IX and DRIVE AV modules above.
  • Please carefully choose the release that best meets your development needs.

Developers using DRIVE PX 2 Developer Kits have access to the legacy DRIVE OS 5.0 software.

See Automotive Software for more details.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Here’s what you need to know to update to DRIVE OS Linux 5.2.0:

  • Software is supported on the DRIVE AGX hardware:
    • NVIDIA DRIVE AGX Pegasus™
    • NVIDIA DRIVE AGX Xavier™
  • You must have DRIVE Software 10.0 or DRIVE OS 5.1.15 (from NVONLINE) flashed on your target DRIVE AGX System. Once updated to DRIVE OS 5.2.0, you may only downgrade to DRIVE OS 5.1.15 or DRIVE Software 10.0 with specified caveats, please see DRIVE OS Installation Guide for more info.
  • Install the most up to date version of the NVIDIA SDK Manager

    PLEASE NOTE: The NVIDIA Developer latest login and authentication system has been updated. The steps to login to the DRIVE Developer Programs when using SDK Manager have changed. Please see the SDK Manager User Guide for more details.

  • Documentation is publicly available at https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ OS and DriveWorks for DRIVE AGX.

  • After updating your software, be sure to review DRIVE OS 5.2.0 Installation Guide, Section 1.4 on how to Finalize your DRIVE AGX System Setup
Please Note: DriveWorks 3.5 is only compatible with DRIVE OS 5.2.0. Please install/flash DRIVE OS 5.2.0 (available above) before downloading and installing DriveWorks 3.5. To clarify, DriveWorks 3.5 will not work with DRIVE Software 9.0 or 10.0.

Here’s what you need to know to install DriveWorks 3.5 after you have updated to DRIVE OS 5.2.0:

  • DriveWorks 3.5 must be installed on top of DRIVE OS 5.2.0.
  • DriveWorks 3.5 SDK Reference Documentation is also available at https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ OS and DriveWorks for DRIVE AGX.
  • Download the DriveWorks 3.5 packages
    DriveWorks 3.5 for Host PC .tar DriveWorks 3.5 for DRIVE AGX .tar

Developer

Support:

For support, please post any queries or issues to the DRIVE Developer Forum.


Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Borza D55 Developer Community Driver License

Please Note: DRIVE Software 10.0 includes DRIVE OS 5.1.6.1 and DriveWorks 2.2, DRIVE IX and DRIVE AV. We recommend you develop using the latest DRIVE OS and DriveWorks available above. DRIVE Hyperion developers should continue to use DRIVE Software.

Here’s what you need to know to update to DRIVE Software 10.0:

  • Software is supported on the following hardware:
  • You must have DRIVE Software 9.0 (available below) or DRIVE OS 5.1.6 (from NVONLINE) flashed on your target DRIVE AGX System. Please see DRIVE Software Installation Guide and DRIVE AGX Developer Kit Flashing Technical Bulletin for DRIVE Software 10.0 for more info.
  • Install the most up to date version of the NVIDIA SDK Manager.
    NVIDIA SDK Manager

    PLEASE NOTE: The NVIDIA Developer latest login and authentication system has been updated. The steps to log in to the DRIVE Developer Programs when using SDK Manager have changed. Please see the SDK Manager User Guide for more details.

  • Documentation is available at DRIVE Documentation and https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ Software for DRIVE AGX.

Open Source:

DRIVE Software 10.0 Target Root Filesystem Open-Source Package (TAR.GZ)

DRIVE OS Open-Source Package installed by SDK Manager

Support:

For support, please post any queries or issues to the DRIVE Developer Forum.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Supported Hardware:

  • NVIDIA DRIVE AGX Pegasus™
  • NVIDIA DRIVE AGX Xavier™

Includes:

DRIVE OS version 5.1.0.2 (Linux)
  • CUDA
  • TensorRT
  • cuDNN

DriveWorks SDK v2.0 APIs
  • Sensor Abstraction
  • Recorder
  • Image/Point Cloud Processing

DRIVE IX SDK
  • Driver Monitoring System
  • DRIVE Hub

System requirements for the host machine

  • Software:
    • Ubuntu Linux 16.04 LTS x86_64
    • X11 enabled on the host system
  • Hardware:
    • Memory: 8GB of RAM
    • Hard disk: 120 GB of free disk space for the complete host and target deployed SDK version.
    • Graphics card: NVIDIA Pascal (or newer) GPU (required only for running the sample applications on the host machine).
    • A working Internet connection.

If you plan to run your sample applications on your development workstation, please ensure your system includes an NVIDIA Pascal based (or newer) GPU and that the latest NVIDIA GPU graphics driver is installed.

Setting up the development environment for DRIVE Software and DRIVE OS


1. REVIEW DOCUMENTATION

  • DRIVE AGX Developer Kit Flashing Technical Bulletin for DRIVE software 9.0 (PDF) (05/23/19)

2. DOWNLOAD

NVIDIA SDK Manager

3. UPDATE the PCIe SWITCH FIRMWARE

Before upgrading to a new release please verify and update the PCIe switch firmware on your DRIVE AGX System before proceeding. Refer to the documentation to identify your current firmware, if different from 0x40014001, download the restricted-pdk.run utility and follow the upgrade procedure.

4. INSTALL

From a terminal window, install the Debian package with the command: sudo apt install ./sdkmanager_0.9.12-4180_amd64.deb

5. LAUNCH

From a terminal window, launch SDK Manager with the command: sdkmanager

6. LOGIN & SETUP

  • From the SDK Manager launch screen, select the login tab for DEVELOPER ZONE developer.nvidia.com.
  • Enter the same credentials used to access the DRIVE Platform Download Center, and click Login.
  • Select the Software version you would like to install and follow the steps to complete the installation.
Developer
NVIDIA DRIVE™ OS 5.0.10.3 with NVIDIA DriveWorks SDK for NVIDIA DRIVE™ PX 2

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE PX 2

Includes:

DRIVE OS version 5.0.10.3 (Linux)
  • CUDA
  • TensorRT
  • cuDNN

DriveWorks SDK v1.2 APIs
  • Sensor Abstraction
  • Recorder
  • Image/Point Cloud Processing

System requirements for the development workstation

  • Software:
    • Ubuntu Linux 16.04 LTS x86_64
    • X11 enabled on the host system
  • Hardware:
    • Memory: 8GB of RAM
    • Hard disk: 120 GB of free disk space for the complete host and target deployed SDK version.
    • Graphics card: NVIDIA Pascal (or newer) GPU (required only for running the sample applications on the host machine).
    • A working Internet connection.

If you plan to run your sample applications on your development workstation, please ensure your system includes an NVIDIA Pascal based (or newer) GPU and that the latest NVIDIA GPU graphics driver is installed.

Setting up the development environment for DRIVE Software and DRIVE OS

    1. REVIEW DOCUMENTATION

    NOTE: For the most up to date documentation please refer to the documentation page as these are more frequently updated than the ones installed through the SDK Manager.

    2. DOWNLOAD

    NVIDIA SDK Manager

    3. INSTALL

    From a terminal window, install the Debian package with the command: sudo apt install ./sdkmanager_0.9.12-4180_amd64.deb

    4. LAUNCH

    From a terminal window, launch SDK Manager with the command: sdkmanager

    5. LOGIN & SETUP

    • From the SDK Manager launch screen, select the login tab for DEVELOPER ZONE developer.nvidia.com.
    • Enter the same credentials used to access the DRIVE Platform Download Center, and click Login.
    • Select the Software version you would like to install and follow the steps to complete the installation.

Additional Resources

  • Automotive Software uses third-party software
  • DriveWorks uses third-party software
  • SDK Manager uses open-source software

NVIDIA’s platforms and application frameworks enable developers to build a wide array of AI applications. Consider potential algorithmic bias when choosing or creating the models being deployed. Work with the model’s developer to ensure that it meets the requirements for the relevant industry and use case; that the necessary instruction and documentation are provided to understand error rates, confidence intervals, and results; and that the model is being used under the conditions and in the manner intended.

Comments are closed.