English
English
English
  • SWARM Documentation
  • What's new?
    • Version 2024.2
    • Version 2024.1
    • Version 2023.3
      • Update 1
  • SWARM in a nutshell
    • SWARM Perception Platform Overview
  • Quick start guide
    • P101, P401 or OP101
      • P101 - Perception Box
      • P401 - Perception Box
      • OP101AC - Outdoor Perception Box
      • OP101DC - Outdoor Perception Box
    • Virtual Perception Box
      • System requirements
      • Install VPX Agent on NVIDIA Jetson (Jetpack 4.6)
      • Install VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)
      • Install VPX Agent on X86/NVIDIA Server
  • Solution areas
    • Traffic Insights
      • Set-up Traffic Counting
      • Set-up Traffic Counting with speed estimates
      • Set-up Intersection Insights
    • Parking Insights
      • Set-up Barrierless Parking
      • Set-up Barrierless Parking with ANPR
        • Set-up guide and recommendations - ANPR
      • Set-up Single Space/Multi Space Parking
        • Standard examples
    • Advanced Traffic Insights
      • Set-up Adaptive Traffic Control
      • Set-up Journey Time & Traffic Flow
        • Set-up guide - Installation
        • Technical concept
      • Set-up Queue Length Detection
    • People Entry/Exit counting
  • SWARM Control Center
    • Devices
      • Camera & Device Monitoring
      • Camera Configuration
        • Scenario Configuration
          • Models
          • Calibration support
          • Camera settings
        • Rule Engine
          • Use Case Examples for Rule Engine
      • Device Health
    • Data Analytics
      • Creation and organization of dashboards
      • Dashboard overview & Widget creation
        • Traffic Scenario
        • Parking Scenario
        • Generic Scenario
    • Data Integration
      • Data Analytics API (REST API)
      • Raw event data with Custom MQTT server
      • SCC API
    • Administration
      • Monitoring Alerts
      • License Management
      • User Management
  • Test & Performance measurements
    • Benchmarks
      • How do we measure Performance?
    • White paper for use cases
      • Traffic Counting
      • Barrierless Parking and ANRP
  • Useful knowledge
    • 🚒Troubleshooting Guidelines
    • Network Requirements
    • Browser Compatibility SCC
    • Our Object Classes
    • Number Plate Area Code
  • Guidelines
    • How to access the debug output?
    • How to use Azure IotHub as Custom Broker
    • VPX
      • Upgrade IotEdge from 1.1 to 1.4
      • Upgrade Jetpack from 4.4.1 to 4.6.0
  • Getting Support
    • Get in touch
    • FAQs
Powered by GitBook
On this page
  • Install JetPack 5.1.2
  • Installation size
  • Install VPX Agent

Was this helpful?

Export as PDF
  1. Quick start guide
  2. Virtual Perception Box

Install VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)

PreviousInstall VPX Agent on NVIDIA Jetson (Jetpack 4.6)NextInstall VPX Agent on X86/NVIDIA Server

Last updated 1 year ago

Was this helpful?

Install JetPack 5.1.2

Flash the system image JetPack 5.1.2 (L4T 35.4.1) onto your Jetson device. Follow the . Depending on your hardware capability, you have the option to use an SSD or internal storage.

Make sure the NVIDIA docker engine is installed (apt package nvidia-docker2)

Installation size

Jetpack 5.1.2 requires at least 32GB or more of storage. In order to free up more storage for additional software, either use a bigger storage device or .

Install VPX Agent

With our installer script, installing the VPX agent is easy. Make sure to get the serial(s) from us in advance.

sudo apt update && sudo apt install curl -y
curl http://get-vpx.swarm-analytics.com/install-2.0.sh > install.sh  && chmod +x install.sh 
./install.sh

After the installation script is complete, the IoT Edge runtime will pull four docker containers as outlined below.

The device type needs to be set in SWARM Control Center. Currently, only our support team can do that.

Make sure that the container curiosity-arm64-jetpack5 is used.

swarm@VPX:~$ sudo docker ps -a
CONTAINER ID        IMAGE                                             COMMAND                   CREATED             STATUS              PORTS                                                                  NAMES
57eec104e917        swarm.azurecr.io/curiosity-arm64-jetpack5:7.1.0   "./curiosity"             2 weeks ago         Up 5 minutes                                                                               curiosity
82b106f9d3d7        swarm.azurecr.io/azure-module-arm64:1.11.1         "java -jar app.jar"       6 weeks ago         Up 10 days                                                                                 azure-module
27ffd61ab021        mcr.microsoft.com/azureiotedge-hub:1.4.10       "/bin/sh -c 'echo \"$…"   6 weeks ago         Up 10 days          0.0.0.0:443->443/tcp, 0.0.0.0:5671->5671/tcp, 0.0.0.0:8883->8883/tcp   edgeHub
5e96e96eb440        mcr.microsoft.com/azureiotedge-agent:1.4.10     "/bin/sh -c 'exec /a…"    6 weeks ago         Up 10 days                                                                                 edgeAgent

Downloading curiosity might take a while due to the size (~5GB)

You will see in the SWARM Control Center an "Unnamed Device" with the corresponding registration ID:

documentation from NVIDIA
follow the NVIDIA reference
Please create a ticket, therefore.