@Darshit-Desai Unfortunately I am now getting different error
Best posts made by riteshsharma
-
RE: Error running voxl-mpa-to-ros2
-
Error running voxl-mpa-to-ros2
I tried running following commands:
-
RE: Error running voxl-mpa-to-ros2
@Darshit-Desai Try running voxl-configure-mpa-to-ros2. It should do all what you are looking for.
Latest posts made by riteshsharma
-
RE: Camera server failing after the update
@tom In that case, how can I downgrade and go back to initial stage. Do you have any suggestion?
-
Camera server failing after the update
Voxl-camera-server is failing after I upgraded the packages on starling drone.
voxl2:/$ voxl-version -------------------------------------------------------------------------------- system-image: 1.7.4-M0054-14.1a-perf kernel: #1 SMP PREEMPT Fri Feb 9 21:59:24 UTC 2024 4.19.125 -------------------------------------------------------------------------------- hw platform: M0054 mach.var: 1.0 -------------------------------------------------------------------------------- voxl-suite: 1.2.0-202404022201 -------------------------------------------------------------------------------- Packages: Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/ Last Updated: 2024-04-03 16:41:43 List: kernel-module-voxl-fsync-mod-4.19.125 1.0-r0 kernel-module-voxl-gpio-mod-4.19.125 1.0-r0 kernel-module-voxl-platform-mod-4.19.125 1.0-r0 libmodal-cv 0.5.5-202402131035 libmodal-exposure 0.1.0-202310231718 libmodal-journal 0.2.2-202211021731 libmodal-json 0.4.3-202209281920 libmodal-pipe 2.10.0-202311162306 libqrb5165-io 0.4.4-202401141445 libvoxl-cci-direct 0.2.1-202309211746 libvoxl-cutils 0.1.1-202210072352 modalai-slpi 1.1.12-202312191452 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0-202309221318 qrb5165-imu-server 1.0.1-202312010251 qrb5165-rangefinder-server 0.1.1-202312111703 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.2.6-202402151128 qrb5165-tflite 2.8.0-2-202210071637 voxl-bind-spektrum 0.1.1-202403271220 voxl-camera-calibration 0.5.4-202401081655 voxl-camera-server 1.9.0-202403211533 voxl-capture 0.0.1-202206110121 voxl-ceres-solver 2:1.14.0-10-202310130020 voxl-configurator 0.5.3-202403121650 voxl-cpu-monitor 0.4.8-202402061134 voxl-docker-support 1.3.0-202309201525 voxl-elrs 0.2.1-202403141429 voxl-esc 1.4.0-202403251514 voxl-feature-tracker 0.3.8-202403261346 voxl-flow-server 0.3.6-202403180603 voxl-fsync-mod 1.0-r0 voxl-gphoto2-server 0.0.10-202210072352 voxl-gpio-mod 1.0-r0 voxl-jpeg-turbo 2.1.3-5-202311071550 voxl-lepton-server 1.2.1-202403180611 voxl-lepton-tracker 0.0.1-202402261317 voxl-libgphoto2 0.0.4-202204111958 voxl-libuvc 1.0.7-202210072357 voxl-logger 0.3.12-202403261022 voxl-mapper 0.2.1-202403201826 voxl-mavcam-manager 0.5.4-202401290941 voxl-mavlink 0.1.1-202305011701 voxl-mavlink-server 1.4.0-202403191520 voxl-microdds-agent 2.4.1-0-202311211206 voxl-modem 1.0.9-202403121543 voxl-mongoose 7.7.0-1-202210072105 voxl-mpa-to-ros 0.3.7-202310131817 voxl-mpa-to-ros2 0.0.2-202402291159 voxl-mpa-tools 1.1.5-202403201735 voxl-neopixel-manager 0.0.3-202312061522 voxl-nlopt 2.5.0-4-202210072358 voxl-open-vins 0.4.10-202403281925 voxl-open-vins-server 0.2.46-202403281925 voxl-opencv 4.5.5-2-202311071601 voxl-platform-mod 1.0-r0 voxl-portal 0.6.5-202403201802 voxl-px4 1.14.0-2.0.69-202402061301 voxl-px4-imu-server 0.1.2-202205131833 voxl-px4-params 0.3.6-202403111442 voxl-qvio-server 1.0.2-202403151128 voxl-remote-id 0.0.9-202309191605 voxl-ros2-foxy 0.0.1-202310061042 voxl-rtp 0.0.1-202206101543 voxl-stitcher 0.0.2-202206161634 voxl-streamer 0.7.4-202309221610 voxl-suite 1.2.0-202404022201 voxl-tag-detector 0.0.4-202206302112 voxl-tflite-server 0.3.2-202401161222 voxl-utils 1.3.8-202402131713 voxl-uvc-server 0.1.6-202311050848 voxl-vision-hub 1.7.4-202401161503 voxl-voxblox 1.1.5-202310122350 voxl-wifi-broadcast 0.0.10-202206122258 voxl2-io 0.0.1-202401181810 voxl2-system-image 1.7.4-r0 voxl2-wlan 1.0-r0 --------------------------------------------------------------------------------```
voxl2:/$ voxl-inspect-services
Scanning services...Service Name | Enabled | Running | CPU Usage
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.7%
voxl-dfs-server | Disabled | Not Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 6.0%
voxl-lepton-server | Disabled | Not Running |
voxl-lepton-tracker | Disabled | Not Running |
voxl-mapper | Enabled | Running | 0.4%
voxl-mavcam-manager | Enabled | Running | 0.0%
voxl-mavlink-server | Enabled | Running | 4.4%
voxl-microdds-agent | Disabled | Not Running |
voxl-modem | Disabled | Not Running |
voxl-neopixel-manager | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.6%
voxl-px4-imu-server | Disabled | Not Running |
voxl-px4 | Enabled | Running | 38.9%
voxl-qvio-server | Enabled | Running | 5.0%
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-stitcher | Disabled | Not Running |
voxl-streamer | Enabled | Running | 0.1%
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.8%
voxl-wait-for-fs | Enabled | Completed |
voxl-wfb-rx-video | Disabled | Not Running |
voxl-wfb-rx | Disabled | Not Running |
voxl-wfb-tx-video | Disabled | Not Running |
voxl-wfb-tx | Disabled | Not Running |voxl2:/$ voxl-camera-server
voxl-camera-server: symbol lookup error: voxl-camera-server: undefined symbol: _ZTIN6royale3pal13II2cBusAccessE -
RE: Using Logitech Brio USB camera as device in voxl-uvc-server
Update on following up on this topic. I was able to use other camera including Logitech Brio as suggested on ModalAI webpage. It only support YUV format not MJPEG streaming. With YUV format on Logitech Brio, I was only able to get 1920x1080 at 5 fps. But could not get MJPEG working.
-
Using Logitech Brio USB camera as device in voxl-uvc-server
I am wondering if anyone have ever used Logitech Brio USB camera as a device in voxl-uvc-server running on voxl-deck. If yes, what is the highest resolution you have obtained at 30 fps ?
I am trying to use a very high resolution camera 4k or more with high fps for live inspection. Will voxl allow to configure such camera with uvc-server?
-
RE: Adding USB camera to Voxl1
@Alex-Kushleyev
Thank you @Alex-Kushleyev . Finally I was able to modify the code to make it work for 2 USB cameras. -
RE: Adding USB camera to Voxl1
@Moderator Can you please provide updated instruction to build voxl-uvc-server package so that I can deploy it to Voxl1? I followed the instruction on the link (https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server). It is giving me errors.
voxl-emulator:~$ ./install_build_deps.sh apq8096 dev using apq8096 dev repo Downloading http://voxl-packages.modalai.com/dists/apq8096/dev/binary-arm64//Packages.gz. Updated source 'dev'. installing: libmodal-json libmodal-pipe voxl-libuvc Package libmodal-json (0.4.3) installed in root is up to date. Package libmodal-pipe (2.10.0) installed in root is up to date. Package voxl-libuvc (1.0.7) installed in root is up to date. Done installing dependencies voxl-emulator:~$ ./build.sh apq8096 CMake Error at /usr/share/cmake-3.3/Modules/CMakeDetermineSystem.cmake:104 (message): Could not find toolchain file: /opt/cross_toolchain/arm-gnueabi-4.9.toolchain.cmake Call Stack (most recent call first): CMakeLists.txt:2 (project) CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_C_COMPILER_ENV_VAR CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_C_COMPILER CMake Error: Could not find cmake module file: /home/root/build/CMakeFiles/3.3.1/CMakeCCompiler.cmake CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_CXX_COMPILER_ENV_VAR CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_CXX_COMPILER CMake Error: Could not find cmake module file: /home/root/build/CMakeFiles/3.3.1/CMakeCXXCompiler.cmake CMake Error at CMakeLists.txt:2 (project): No CMAKE_C_COMPILER could be found. Tell CMake where to find the compiler by setting the CMake cache entry CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. CMake Error at CMakeLists.txt:2 (project): No CMAKE_CXX_COMPILER could be found. Tell CMake where to find the compiler by setting the CMake cache entry CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage -- Configuring incomplete, errors occurred! make: *** No targets specified and no makefile found. Stop.
I also tried using voxl-cross. It was able to build the package correctly but gave me error while executing.
voxl:~$ voxl-uvc-server voxl-uvc-server: error while loading shared libraries: libuvc.so.0: cannot open shared object file: No such file or directory
-
RE: Adding USB camera to Voxl1
@Moderator I was able to start two camera (thermal camera and hires camera) connected through two USB using the command below.
voxl-uvc-server -d -v 0c45 -p 636b -r 1920x1080 -f 5 -o uvc_hires (Hires Camera)
voxl-uvc-server -d -v 09cb -p4007 -r 640x512 -f 30 -o uvc_boson (Thermal Camera)
But I could not find a way to start both the camera together. Only one works at a time as the configuration file overrides. It can only accept one UVC configuration settings. I would appreciate if you could provide me a way to correctly set up configuration file for both the camera.
I have already gone through documentation at https://docs.modalai.com/voxl-uvc-server/. It only mentions that we need to have different setup for each camera which in my case is evident from the two commands above.
-
RE: Adding USB camera to Voxl1
Thank you for your reply. It gives me hope that I can connect two camera together. However, I wonder how should I configure uvc for each of my camera. Each time I use voxl-uvc-server with one of the option popping up on my terminal (options are shown below), the configuration file at /etc/modalai/voxl-uvc-server.conf get replaced with new settings.
Also, I tried changing configuration file manually but then only the first configuration shows up on voxl-portal.
{
"pipe_name": "uvc_hires",
"width": 1920,
"height": 1080,
"fps": 5,"pipe_name": "uvc_boson", "width": 640, "height": 480, "fps": 30
}
-
RE: Adding USB camera to Voxl1
@Moderator Thank you for your suggestion. I would like to know if two USB supported camera (Thermal and Hires) can use UVC configurations. In other words, Can I use UVC pipe to connect attached USB cameras together? If yes, Can you provide example of the configuration file.
-
RE: Adding USB camera to Voxl1
Can we use MIPI repeater to extend the length of the cable? Do you have some suggestion what kind of MIPI repeater will be compatible with the existing pin connection on Voxl1-Deck?