ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. kerct
    K
    • Profile
    • Following 1
    • Followers 0
    • Topics 9
    • Posts 26
    • Best 1
    • Controversial 0
    • Groups 0

    kerct

    @kerct

    1
    Reputation
    4
    Profile views
    26
    Posts
    0
    Followers
    1
    Following
    Joined Last Online

    kerct Unfollow Follow

    Best posts made by kerct

    • RE: HITL on VOXL2

      @Eric-Katzfey Thanks! I am able to do a basic HITL now. However I get this error message on QGC

      78afda14-a360-4188-9725-cd2a97201c34-image.png

      I see that the flight mode on QGC is always "unknown", is this expected?

      fe5d9451-5cee-4e1c-a2f3-65386fb011a5-image.png
      5a82fcef-cd34-4ca1-9a9b-d569310af5be-image.png

      posted in Ask your questions right here!
      K
      kerct

    Latest posts made by kerct

    • RE: CPU Temperature Logging

      @tom Is there a way to voxl-logger the outputs from voxl-inspect-cpu and play it so that I can see the graphs on voxl-portal? Currently I can only voxl-inspect-cpu or view the graphs in real-time on voxl-portal, but I would like to record the data when the drone flies and review it post-flight

      posted in VOXL 2
      K
      kerct
    • RE: cpu 0 to 3 vs 4 to 7

      @Moderator oh I see, so to reduce overheating would it be recommended to use the default settings instead of limiting my process to cpu 4 to 7?

      posted in Ask your questions right here!
      K
      kerct
    • cpu 0 to 3 vs 4 to 7

      I realised that the default behaviour for cpu 0 to 3 on the VOXL2 is to run at a higher frequency (and utilisation) than cpu 4 to 7
      bad06afa-5154-4351-9cbd-34eea09591d4-image.png

      This happens even for a compute intensive process
      cc40ccd4-0f44-4a56-825f-8223f68620ac-image.png

      Would it help to limit my process to cpu 4 to 7 as such?
      c32d257a-75c1-4c07-beca-264752d68d42-4-7.png

      Or should I stick to the default, using all available cores?
      193e05c6-9bb1-4bfe-a7e8-90f93f574602-image.png

      posted in Ask your questions right here!
      K
      kerct
    • RE: MAVSDK running on another computer for HITL

      @Eric-Katzfey will this work with SDK 1.0.0 too? would like to stick with that version for now since we have been testing with this version for our project

      posted in Ask your questions right here!
      K
      kerct
    • RE: MAVSDK running on another computer for HITL

      @Eric-Katzfey I'm also unable to connect to QGC now (without HITL). On VOXL portal I can still see the camera and pointclouds, but not the status of the drone.

      6fd26783-7309-4806-8e97-2be46d5a6973-image.png

      11db34e0-4c9a-4a38-b6cd-91f9fb7be2a9-image.png

      c856daa6-409a-4791-8759-c551cc293489-image.png

      9a66f134-b08e-4ded-8e30-e5aa118bb773-image.png

      posted in Ask your questions right here!
      K
      kerct
    • RE: MAVSDK running on another computer for HITL

      @Eric-Katzfey Yes I still get the same error after power cycle

      posted in Ask your questions right here!
      K
      kerct
    • RE: MAVSDK running on another computer for HITL

      @Zachary-Lowell-0 I was trying the MAVSDK example which didn't work but after trying the example, I can't run HITL anymore (which worked previously)... not sure what's the issue here?

      9366dea7-4e64-4a39-9d27-c91ac223a206-image.png

      99b36e87-9f24-4f59-9387-87a6c4bccb02-image.png

      posted in Ask your questions right here!
      K
      kerct
    • MAVSDK running on another computer for HITL

      For SITL, I can connect to PX4 with MAVSDK using port 14540. However, for HITL, port 14540 or 14551 does not work. VOXL2 wifi is configured in AP mode, and I have connected my laptop to it. I have also checked that voxl-vision-hub and voxl-mavlink-server are running, and my config files are as such:
      voxl-vision-hub
      036bccc5-76c7-4e9a-95dc-3c9f23591d82-image.png

      voxl-mavlink-server
      784be9e4-8d6e-40f0-a0a8-a59608137837-image.png

      How can I get HITL to work with MAVSDK running on my linux computer? Or does it only work when MAVSDK is running on VOXL2 like the example here https://docs.modalai.com/mavsdk/?

      posted in Ask your questions right here!
      K
      kerct
    • RE: SITL using VOXL2 PX4 software

      @Moderator @Zachary-Lowell-0 @Eric-Katzfey Thanks for your replies! I am looking to do multi-vehicle simulation so SITL would be ideal, but I would definitely try out HITL too (although that would be limited to only 1 vehicle in the simulation right?)

      posted in Ask your questions right here!
      K
      kerct
    • SITL using VOXL2 PX4 software

      Is it possible to run SITL using ModalAI's version of the PX4 software? I am using this repo https://github.com/modalai/px4-firmware/ and followed the same steps as I would with PX4's Autopilot repo:

      1. roslaunch my gazebo world
      2. in px4-firmware, make px4_sitl_default none
      3. start my own ros app

      However, I recently discovered that there's the option to make modalai_voxl2 (instead of make px4_sitl_default), so I am not sure if I am actually using the ModalAI version. What is the correct way to do so?

      I am unable to make modalai_voxl2 successfully:

      $ make modalai_voxl2
      -- PX4 version: v1.14.0-2.0.43-dev (1.14.0)
      -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.10", minimum required is "3")
      -- PX4 config file: /home/xx/px4-firmware/boards/modalai/voxl2/default.px4board
      -- PLATFORM posix
      -- LINUX_TARGET y
      -- TOOLCHAIN aarch64-linux-gnu
      -- ROMFSROOT px4fmu_common
      -- ROOTFSDIR /data/px4
      -- PX4 config: modalai_voxl2_default
      -- PX4 platform: posix
      -- PX4 lockstep: disabled
      -- The CXX compiler identification is unknown
      -- The C compiler identification is unknown
      -- The ASM compiler identification is unknown
      -- Found assembler: /bin/aarch64-linux-gnu-gcc
      CMake Error at CMakeLists.txt:219 (project):
      The CMAKE_CXX_COMPILER:

      /bin/aarch64-linux-gnu-g++
      

      is not a full path to an existing compiler tool.

      Tell CMake where to find the compiler by setting either the environment
      variable "CXX" or 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 at CMakeLists.txt:219 (project):
      The CMAKE_C_COMPILER:

      /bin/aarch64-linux-gnu-gcc
      

      is not a full path to an existing compiler tool.

      Tell CMake where to find the compiler by setting either the environment
      variable "CC" or 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:219 (project):
      The CMAKE_ASM_COMPILER:

      /bin/aarch64-linux-gnu-gcc
      

      is not a full path to an existing compiler tool.

      Tell CMake where to find the compiler by setting either the environment
      variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
      to the compiler, or to the compiler name if it is in the PATH.

      -- Warning: Did not find file Compiler/-ASM
      -- Configuring incomplete, errors occurred!
      See also "/home/xx/px4-firmware/build/modalai_voxl2_default/CMakeFiles/CMakeOutput.log".
      See also "/home/xx/px4-firmware/build/modalai_voxl2_default/CMakeFiles/CMakeError.log".
      Error: /home/xx/px4-firmware/build/modalai_voxl2_default is not a directory
      make: *** [Makefile:232: modalai_voxl2] Error 1

      posted in Ask your questions right here!
      K
      kerct