how to use dv-gui on jetson nano 2GB board

[곰탬미]

I want to apply DVS to drones and use them for obstacle recognition. Octacopters using pixhawk4 and arupilot are being used. The companion board is jetson nano 2GB.

I trid to install dv-gui on my jetson, but I faild to install.

I used this method 

sudo add-apt-repository ppa:ubuntu-toolchain-r/test 

sudo add-apt-repository ppa:inivation-ppa/inivation-bionic 

sudo apt-get update 

sudo apt-get install dv-gui

I want to know how to solve this and to use it for drone

[Luca Longinotti]

As per our docs here:
https://inivation.gitlab.io/dv/dv-docs/docs/getting-started/#ubuntu-bionic
"Please note that dv-gui is only available on x86_64, the dv-runtime on
all supported architectures."
so dv-gui cannot be installed on an ARM computer like Jetson.
You can install dv-runtime and connect remotely, see:
https://inivation.gitlab.io/dv/dv-docs/docs/getting-started/#launching-dv-runtime-with-a-remote-gui
--
Luca Longinotti (llongi)

Head of Embedded Platforms
iniVation AG - https://inivation.com/
Zurich, Switzerland
Office: +41 44 500 32 14

[곰탬미]

I now know that dv-remote should be used for Jetson Nano.
So I tried to install dv-runtime on Jetson nano.
Of course, before installation, I removed openv4.1.1 that is pre-installed on Jetson Nano and then proceeded with the following process.

sudo add-apt-repository ppa:ubuntu-toolchain-r/test sudo add-apt-repository ppa:inivation-ppa/inivation-bionic sudo apt-get update

sudo apt-get install dv-runtime-dev

After the installation is finished, I searched the file 'dv-runtime.service' to modify IP to 0.0.0.0, but I cannot find it.

And there is an error in the process of building a catkin for the ros environment. 

This error did not occur before installing dv-runtime, so it is expected that there is a problem with the installation process.

I'm in the process of reinstalling. I don't know what I did wrong during the installation.

  

2021년 11월 1일 월요일 오후 6시 31분 15초 UTC+9에 Luca Longinotti님이 작성:

[Luca Longinotti]

Hello, the dv-runtime.service file should be here:
/lib/systemd/system/dv-runtime.service
And the ROS compilation failure is due to a conflict with the boost-
inivation package, see here:
https://github.com/uzh-rpg/rpg_dvs_ros/issues/117
Just uninstall dv-runtime and boost-inivation, install only libcaer-dev
and then build the ROS driver. After that you can reinstall dv-runtime
and boost-inivation too.