Getting Started


Before operating the Nova Carter robot, read all of the following safety guidelines carefully. You must follow all of these guidelines during operation of the robot.

Robot Operator Safety

The Nova Carter robot is small and lightweight, weighing less than 100 kg even with its full payload. The main hazard is impact from the robot itself, where moderate harm could result from a worst-case direct collision. Robot operators must take the following precautions:

  • Familiarize yourself with the Nova Carter controls and dynamics in an open area away from bystanders.

  • Be aware of the speed at which Nova Carter can accelerate, decelerate, and turn.

  • Be aware that stopping Nova Carter quickly while it’s moving forward can cause it to overshoot and move backwards.

In the event of a safety incident, inspect the Nova Carter for the following:

  • Damage to the robot chassis (including dents and punctures to the housing or drivetrain).

  • Damage to the sensors that emit IR (including scratches and pits on the optical window).

  • If there is damage, do not power on Nova Carter. Use the tow handle to move the robot and contact your Segway representative immediately. Nova Carter has a tow handle for manual transport located above the caster wheels.

A red emergency stop (ESTOP) button is located above the caster wheels below the tow handle. Pushing the ESTOP button disconnects power to the motors, but the Carter robot can continue to coast in the direction it was previously moving. It can also roll if placed on a sloped surface while the ESTOP is pressed.

Do not open or remove any panels from the robot, and do not loosen or remove any sensors.

Unboxing Nova Carter

After receiving your Nova Carter robot from Segway, follow the guide below to unpack and power on the robot.

Make sure you are familiar with or have completed the following:

  1. Remove Nova Carter from its packaging.

  2. Remove the protective Lidar cover (colored red) using a 2.5 mm hex driver, and re-install any bolts which were removed.

  3. Familiarize yourself with the following parts of Nova Carter:

    1. Wall charger and its connection to the robot. You can connect Nova Carter to its charger when it is powered on or off.


    The robot does not respond to movement commands while plugged into the wall charger.

    1. E-Stop button at the rear of the robot and its operation. Press to engage, twist clockwise to disengage.

    2. IO panel at rear of robot with USB-C, DisplayPort, and Ethernet connections. These connect directly to the Jetson, and can be used for development, rapid data transfer, or to re-flash the Jetson AGX Orin.

    3. Status indicator LED bar at the front. This shows yellow on boot, green when Jetson is actively communicating with the wheelbase, and red if there is an error or E-Stop button is pressed.

  4. Power on the robot using the button at its front. The LED panels at each corner of the robot flash white. After Jetson has finished booting, they transition to green. If the status indicator light flashes red, disengage the E-Stop.

Connecting the Robot to your WiFi Network

Follow these steps to connect the Nova Carter to the local WiFi network:

  1. Connect the robot to a display using the DisplayPort on the rear IO panel.


A recommended best practice is to engage the E-Stop button any time you connect external cables to the robot, to prevent it from responding to any movement commands.

  1. Connect the keyboard with touchpad to the USB-C port on the rear IO panel.

  2. Log in to the robot (contact the NVIDIA Solutions team for the robot password).

  3. Follow the WiFi instructions for Ubuntu.

  4. After connecting to the internet it is required to reboot the system. Press the power button or run:

    sudo reboot

Connecting the PC to the Robot

To control, deploy, launch, and debug applications, you have to connect your PC to the robot.

First, you must get the IP address of the robot. Assuming you have the robot connected to a display and a keyboard with touchpad from the previous section, follow these instructions:

  1. Use CTRL+ALT+t to open a terminal.

  2. Find the IP address of the WiFi by running ifconfig wlan0. You should see an output similar to the screenshot below. The IP address is highlighted with a red rectangle.

ifconfig console screenshot
  1. Record the IP address (in the above case it is This IP address will be used for connecting in all further tutorials and may need to be retrieved again if it changes.

  2. From your PC run the following command to SSH into the robot. Make sure to use a PC that is connected to the same WiFi network as your robot. Enter the robot password when asked for it.

    $ ssh <USER>@<ROBOT_IP>


Make sure to replace <USER> and <ROBOT_IP> with the values for your robot. In the above case, it would be ssh nvidia@


The login will timeout for security reasons. Also, the DisplayPort will turn off after a while due to inactivity, so retry if the screen goes black.

Nova Orin Initialization

  1. Verify if Nova Orin software is the latest version by comparing the installed package with the candidate:

    $ apt policy nova-orin-init
      Installed: 1.3.1
      Candidate: 1.3.1
      Version table:
     *** 1.3.1 600
            600 jammy/main arm64 Packages
  2. If the installed version is lower than the candidate, please follow the nova init upgrade process here. Otherwise proceed to the next step.

  3. Verify that sensors are functioning by running:

    nova_preflight_checker -v

    It is expected for all tests to pass. Refer to the Nova PFC documentation for more details.

Pairing the Joystick Controller

  1. A PS5 joystick controller is shipped with the robot. To connect the joystick with the robot, put the controller in pairing mode, by pressing and holding down the two buttons shown in the image below until the controller lights start blinking:

  1. SSH into the robot and pair the controller to the robot.


# This should list the available devices
$ sudo bluetoothctl
**[bluetooth]#** scan on
Discovery started
[CHG] Controller 90:E8:68:84:35:24 Discovering: yes
[NEW] Device D4:20:B0:42:66:4F D4-20-B0-42-66-4F
[NEW] Device D4:20: B0:42:5C:CC D4-20-B0-42-5C-CC
[NEW] Device D4:20:B0:42:64:1A D4-20-B0-42-64-1A
[NEW] Device 7C:66:EF:5D:36:B1 Wireless Controller
[NEW] Device D4:20:B0:42:C6:80 D4-20-B0-42-C6-80
[NEW] Device D4:20:B0:42:5B:37 D4-20-B0-42-5B-37

# The mac address used should match the one named Wireless Controller, in
# this case it is.
**[bluetooth]#** scan off

# Upon successful pairing, it should ask you to type yes/no to trust the
# device. Type "yes".
**[bluetooth]#** pair 7C:66:EF:5D:36:B1
**[bluetooth]#** trust 7C:66:EF:5D:36:B1
**[bluetooth]#** exit


Once the controller is connected, the LEDs on the controller should stay solid blue; flashing blue LEDs indicate the controller is trying to connect.


In the terminal run ls /dev/input/js0. If the connection was successful it prints out /dev/input/js0. If the connection was not successful the command prints out \ ls: cannot access '/dev/input/js0': No such file or directory\.

  1. The controller should now be connected. You should not need to pair again. If you want to connect again after the controller turns off press the PS button as shown below.

PS5 Controller

Docker Configuration

To run applications on Nova Carter, you shall configure docker as below.

  1. Add the nvidia user to the docker group to enable using docker without sudo:

    # Add your user to the docke group
    sudo usermod -aG docker $USER
    # Verify that command succeeded
    id nvidia | grep docker
    # Log out and log in for the changes to take effect
    newgrp docker
  2. Stop the Docker service.

    sudo systemctl stop docker
  3. Move the existing Docker folder.

    sudo du -csh /var/lib/docker/ && \
        sudo mkdir /mnt/nova_ssd/docker && \
        sudo rsync -axPS /var/lib/docker/ /mnt/nova_ssd/docker/ && \
        sudo du -csh  /mnt/nova_ssd/docker/
  4. Use a text editor (e.g. Vi) to edit /etc/docker/daemon.json

    sudo vi /etc/docker/daemon.json

    Insert "data-root" line similar to the following:

        "runtimes": {
            "nvidia": {
                "path": "nvidia-container-runtime",
                "runtimeArgs": []
        "default-runtime": "nvidia",
        "data-root": "/mnt/nova_ssd/docker"
  5. Rename the old Docker data directory.

    sudo mv /var/lib/docker /var/lib/docker.old
  6. Restart the Docker daemon.

    sudo systemctl daemon-reload && \
        sudo systemctl restart docker && \
        sudo journalctl -u docker

Checking the Battery Status

Before using the robot check the battery level. Run:

$ nova_battery_status
host version build date: [23-09-19]
host version build time: [14:21:54]
Communication interface adding CAN_INTERFACE
Please guarantee the '' file has been taken into the
'/home/sdcard/firmware' directory, if can register has not been configed HAL
CANBUS init success!
Scheduler Num 0 Start. Task Num = 1. Period = 100000
Scheduler Num 1 Start. Task Num = 1. Period = 50000
Scheduler Num 2 Start. Task Num = 1. Period = 20000

battery: 54%


If you consider using Nova Carter only through the pre-built docker image, continue to Visualization Setup. Otherwise, you should complete Isaac ROS Development Environment, repositories, and visualization setup before proceeding to run the applications.

Isaac ROS Development Environment Setup (Optional)

  1. Set up your development environment by following the instructions in getting started.

  2. Clone isaac_ros_common under ${ISAAC_ROS_WS}/src.

    cd ${ISAAC_ROS_WS}/src && \
       git clone
  3. (Optional) Install dependencies for any sensors you want to use by following the sensor-specific guides.


    We strongly recommend installing all sensor dependencies before starting any quickstarts. Some sensor dependencies require restarting the Isaac ROS Dev container during installation, which will interrupt the quickstart process.


Ensure you have set up the SSD and migrated the Docker directory to SSD. Instructions can be found here.


We recommend that you connect the Nova Carter through Ethernet in this step. Building a Docker image for the development environment takes longer time in the first time you run it. Expect faster spin-up of the development environment after the first cached build.

Repositories Setup (Optional)

  1. Clone nova_carter repository under ${ISAAC_ROS_WS}/src:

    cd ${ISAAC_ROS_WS}/src && \
      git clone --recursive
  2. Create a file called .isaac_ros_common-config with the following context:

    cd ${ISAAC_ROS_WS}/src/isaac_ros_common/scripts
    echo -e "CONFIG_IMAGE_KEY=ros2_humble.nova_carter\nCONFIG_DOCKER_SEARCH_DIRS=(../../nova_carter/docker ../docker)" > .isaac_ros_common-config
  3. Create a file called .isaac_ros_dev-dockerargs with the following context:

    cd ${ISAAC_ROS_WS}/src/isaac_ros_common/scripts && \
      echo -e "-v /etc/nova/:/etc/nova/\n-v /opt/nvidia/nova/:/opt/nvidia/nova/" > .isaac_ros_dev-dockerargs
  4. Launch the Docker container using the script:

    cd ${ISAAC_ROS_WS}/src/isaac_ros_common && \
  5. Clone the dependency repositories using the vcstool file in the nova_carter repository:

    cd /workspaces/isaac_ros-dev
    vcs import --recursive src < src/nova_carter/nova_carter.repos

Visualization Setup

To visualize and evaluate outputs from running applications, you should follow these steps on your remote machine.

  1. Complete the Foxglove setup guide. Make sure to follow the instructions of installing additional Nvblox Foxglove extension.

  2. Download all Foxglove layout configurations available in nova_carter repository.