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 4.6.0
  • Free up hard disk space on your Jetson device (optional)
  • Install VPX Agent

Was this helpful?

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

Install VPX Agent on NVIDIA Jetson (Jetpack 4.6)

PreviousSystem requirementsNextInstall VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)

Last updated 1 year ago

Was this helpful?

Install JetPack 4.6.0

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

Make sure to match the exact JetPack version. Don't use newer or older versions.

Free up hard disk space on your Jetson device (optional)

Some Jetson devices don't have enough hard disk space for the VPX agent. You can run the following script which removes non-essential applications. (At your own risk)

Alternative: Use an SSD with >32GB for storage.

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

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.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.

Make sure that the container curiosity-arm64-tensorrtis used.

swarm@VPX:~$ sudo docker ps -a
CONTAINER ID        IMAGE                                             COMMAND                   CREATED             STATUS              PORTS                                                                  NAMES
57eec104e917        swarm.azurecr.io/curiosity-arm64-tensorrt:5.3.0   "./curiosity"             2 weeks ago         Up 5 minutes                                                                               curiosity
82b106f9d3d7        swarm.azurecr.io/azure-module-arm64:1.1.0         "java -jar app.jar"       6 weeks ago         Up 10 days                                                                                 azure-module
27ffd61ab021        mcr.microsoft.com/azureiotedge-hub:1.0.10.3       "/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.0.10.3     "/bin/sh -c 'exec /a…"    6 weeks ago         Up 10 days                                                                                 edgeAgent

Downloading curiosity might take a while

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

documentation from NVIDIA
This registration ID is a sample