@groupo We also had this issue, but we had modified the sentinel and was found to be more due to vibrations https://discuss.px4.io/t/stopping-compass-mid-flight/42808

@Alex-Kushleyev Dear Alex, It's the M0025-002 high resolution camera. Perhaps the connection sodder was loose and it popped off real easily. In hindsight, perhaps it's not worth anyone's time. If you can provide any repair tricks that'd be neat otherwise I'll probably have to send a new order in. Best, Milton

@Cody , please double check the actual and desired roll / pitch / yaw values in the flight review. When the vehicle is level, then roll and pitch should be close to zero and desired roll/pitch will be zero as well if you don't touch RC sticks. If the attitude estimate is incorrect (for whatever reason) this can cause the vehicle to not be level during flight / take-off. Alex

@tom After flashing, I cannot connect to the QGC. After setting up the IP address, I try to connect via UDP using the IP and port 14550, this is what I get [image: 1740736258690-e032a3a6-32d8-4b3f-9f56-dba442f9aaa4-image.png] drone(connected) is the one not connecting to QGC.

The 3000mAh packs use Sony VTC60 LiIon cells and the 4000mAh packs use Amprius Silicon Anode cells

@ramp Yes you could still do HITL with a starling 2 max, would just require unplugging the ESC from the VOXL 2 and using that connector

@antenna-eng What hardware do you have connected to the VOXL 2 board? Cameras etc.

@Alex-Kushleyev Thank you for your response, it was the issue with the battery, May be my battery is damaged, when I provide external power source of 12 volt power supply, then it is working perfectly fine. Now I am able to access the portal and voxl2 as well. thank you

@starlinguser Thank you for your response, now my problem is resolved, I just used "voxl-configure-mpa --debug" and now everything is working fine. thank you

Hi @muhammad-kazim-0 , For saving h264 / h265 you can use voxl-streamer tool to serve the video via RTSP from VOXL2 and then on your host PC use ffmpeg or ffplay (or similar tools) to view / save the video. For simple playback of rtsp video, you can run a command on your linux PC : ffplay rtsp://<voxl-ip>:<rtsp-port>/live -- the IP of voxl2 you can get using ifconfig, the rtsp port will be printed out by voxl-streamer when it strarts up. You can run multiple instances of voxl-streamer on different ports, please check help for this command-line tool. I would not recommend streaming uncompressed images for the purpose of recording the video. Just to clarify, any camera stream that is not named *_encoded is going to be uncompressed RAW8 or YUV format and when you view it using voxl-portal, what happens is the back-end of voxl-portal (running on voxl2) will take the original image from the requested stream and it will use JPG compression before sending the JPG to your voxl-portal in the browser for viewing. Jpeg is a lot less efficient than h264/5, so you will need a lot more bandwidth. You can still use the jpeg approach if you really want to. For example, you can use ffplay to play the jpeg stream (this is kind of an undocumented feature): ffplay -f mjpeg -framerate 30 -probesize 32 -analyzeduration 0 -fflags -nobuffer -flags low_delay -i http://<voxl-ip>/video_raw/<camera-stream-name> Please note if you use these streams (which are generated by voxl-portal backend), if you also concurrently actually use voxl-portal in browser, the streams might interfere / stop. You should also be able to figure out how to use ffplay / ffmpeg to how save the file to disk. If you have too many jpeg streams (especially high resolution camera), VOXL2 may not be able to keep up. Specifically for hires streams, you should definitely make use of the encoded streams. You can always use the tool top on voxl2 to check the cpu usage of individual processes, specifically voxl-portal to make sure it is not overloading the system. if the streams that you are getting are not the FPS that you are expecting, then it probably means that voxl2 cannot keep up with sending the streams (either encoding to jpg or limited network bandwidth). Please try this out and let me know if you have any questions. Alex

Hi @Eric-Katzfey yes, i can see lrwxrwxrwx 1 1000 1000 7 Feb 11 16:00 hexagon-link -> ld.qcld and also -rw-rw-rw- 1 1000 1000 46687200 Feb 11 16:00 ld.qcld So it seems " ld.qcld'" is not executable. then I made it executable using. "chmod +x /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/ld.qcld" Then, it seems the voxl-PX4 build is working. Thank you for the help. root@798402fd070f:/usr/local/workspace# ./build.sh *** Starting build *** Setting up the Hexagon SDK environment locally HEXAGON_SDK_ROOT is : /home/4.1.0.4 Setting up the QAIC binary for the platform make: Entering directory '/home/4.1.0.4/ipc/fastrpc/qaic' make: 'bin/qaic' is up to date. make: Leaving directory '/home/4.1.0.4/ipc/fastrpc/qaic' Could not find Androd ndk at /home/4.1.0.4/tools/android-ndk-r19c Please refer to /home/4.1.0.4/docs/tools/setup.html for installing the missed components *** Starting dependencies build *** -- The C compiler identification is GNU 7.5.0 -- The CXX compiler identification is GNU 9.4.0 -- Check for working C compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-gcc -- Check for working C compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done -- Generating done -- Build files have been written to: /usr/local/workspace/px4-firmware/boards/modalai/voxl2/libfc-sensor-api/build Scanning dependencies of target fc_sensor [ 50%] Building C object CMakeFiles/fc_sensor.dir/src/fc_sensor_stub.c.o [100%] Linking C shared library libfc_sensor.so [100%] Built target fc_sensor *** End of dependencies build *** *** Starting apps processor build *** -- PX4 version: v1.14.0-2.0.94-dev (1.14.0) -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.10", minimum required is "3") -- PX4 config file: /usr/local/workspace/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 GNU 7.5.0 -- The C compiler identification is GNU 7.5.0 -- The ASM compiler identification is GNU -- Found assembler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-gcc -- Check for working CXX compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-g++ -- Check for working CXX compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check for working C compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-gcc -- Check for working C compiler: /home/4.1.0.4/tools/linaro64/bin/aarch64-linux-gnu-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- cmake build type: RelWithDebInfo -- ccache enabled (export CCACHE_DISABLE=1 to disable) -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/linux_pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/pca9685_pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/modules/simulation/pwm_out_sim/module_hil.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/modules/simulation/pwm_out_sim/module_sim.yaml for VOXL2 -- ROMFS: ROMFS/px4fmu_common Architecture: amd64 ==> CPACK_INSTALL_PREFIX = @DEB_INSTALL_PREFIX@ -- Configuring done -- Generating done -- Build files have been written to: /usr/local/workspace/px4-firmware/build/modalai_voxl2_default [0/562] git submodule src/modules/microdds_client/Micro-XRCE-DDS-Client [2/562] git submodule src/drivers/gps/devices [6/562] git submodule src/modules/mavlink/mavlink [64/562] Performing configure step for 'libmicroxrceddsclient_project' -- libmicroxrceddsclient_project configure command succeeded. See also /usr/local/workspace/px4-firmware/build/modalai_voxl2_default/src/modules/microdds_client/src/libmicroxrceddsclient_project-stamp/libmicroxrceddsclient_project-configure-*.log [555/562] Performing build step for 'libmicroxrceddsclient_project' -- libmicroxrceddsclient_project build command succeeded. See also /usr/local/workspace/px4-firmware/build/modalai_voxl2_default/src/modules/microdds_client/src/libmicroxrceddsclient_project-stamp/libmicroxrceddsclient_project-build-*.log [556/562] Performing install step for 'libmicroxrceddsclient_project' -- libmicroxrceddsclient_project install command succeeded. See also /usr/local/workspace/px4-firmware/build/modalai_voxl2_default/src/modules/microdds_client/src/libmicroxrceddsclient_project-stamp/libmicroxrceddsclient_project-install-*.log [562/562] Linking CXX executable bin/px4 /* Auto Magically Generated file */ /* Do not edit! */ #pragma once #define PX4_GIT_VERSION_STR "5e6a8c257371b6c45e55662daac5fe9fbd08040b" #define PX4_GIT_VERSION_BINARY 0x5e6a8c257371b6c4 #define PX4_GIT_TAG_STR "v1.14.0-2.0.94-dev-dirty" #define PX4_GIT_BRANCH_NAME "" #define PX4_GIT_OEM_VERSION_STR "" #define PX4_GIT_TAG_OR_BRANCH_NAME "v1.14.0-2.0.94-dev-dirty" // special variable: git tag, release or master branch #define MAVLINK_LIB_GIT_VERSION_STR "3ee5382d0c96134b0e1c250d8c2d54bfed0166fa" #define MAVLINK_LIB_GIT_VERSION_BINARY 0x3ee5382d0c96134b #define NUTTX_GIT_VERSION_STR "3f77354c0dc88793a47ff3b57595195ab45f7ba9" #define NUTTX_GIT_VERSION_BINARY 0x3f77354c0dc88793 #define NUTTX_GIT_TAG_STR "v11.0.0" *** End of apps processor build *** *** Starting qurt slpi build *** -- PX4 version: v1.14.0-2.0.94-dev (1.14.0) -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.10", minimum required is "3") -- PX4 config file: /usr/local/workspace/px4-firmware/boards/modalai/voxl2-slpi/default.px4board -- PLATFORM qurt -- TOOLCHAIN qurt -- ROMFSROOT px4fmu_common -- PX4 config: modalai_voxl2-slpi_default -- PX4 platform: qurt -- The CXX compiler identification is Clang 10.0.0 -- The C compiler identification is Clang 10.0.0 -- The ASM compiler identification is unknown -- Found assembler: /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/hexagon-clang -- Check for working CXX compiler: /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/hexagon-clang++ -- Check for working CXX compiler: /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/hexagon-clang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - failed -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check for working C compiler: /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/hexagon-clang -- Check for working C compiler: /home/4.1.0.4/tools/HEXAGON_Tools/8.4.05/Tools/bin/hexagon-clang -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - failed -- Detecting C compile features -- Detecting C compile features - done -- Warning: Did not find file Compiler/-ASM -- cmake build type: RelWithDebInfo -- ccache enabled (export CCACHE_DISABLE=1 to disable) -- Mavlink include directory: /usr/local/workspace/px4-firmware/../build/modalai_voxl2_default/mavlink/standard -- Mavlink include directory: /usr/local/workspace/px4-firmware/../build/modalai_voxl2_default/mavlink/common -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/linux_pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/pca9685_pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/drivers/pwm_out/module.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/modules/simulation/pwm_out_sim/module_hil.yaml for VOXL2 -- Skipping pwm file path /usr/local/workspace/px4-firmware/src/modules/simulation/pwm_out_sim/module_sim.yaml for VOXL2 Architecture: amd64 ==> CPACK_INSTALL_PREFIX = @DEB_INSTALL_PREFIX@ -- Configuring done -- Generating done -- Build files have been written to: /usr/local/workspace/px4-firmware/build/modalai_voxl2-slpi_default [0/724] git submodule src/drivers/gps/devices [724/724] Linking CXX shared library platforms/qurt/libpx4.so /* Auto Magically Generated file */ /* Do not edit! */ #pragma once #define PX4_GIT_VERSION_STR "5e6a8c257371b6c45e55662daac5fe9fbd08040b" #define PX4_GIT_VERSION_BINARY 0x5e6a8c257371b6c4 #define PX4_GIT_TAG_STR "v1.14.0-2.0.94-dev-dirty" #define PX4_GIT_BRANCH_NAME "" #define PX4_GIT_OEM_VERSION_STR "" #define PX4_GIT_TAG_OR_BRANCH_NAME "v1.14.0-2.0.94-dev-dirty" // special variable: git tag, release or master branch #define MAVLINK_LIB_GIT_VERSION_STR "3ee5382d0c96134b0e1c250d8c2d54bfed0166fa" #define MAVLINK_LIB_GIT_VERSION_BINARY 0x3ee5382d0c96134b #define NUTTX_GIT_VERSION_STR "3f77354c0dc88793a47ff3b57595195ab45f7ba9" #define NUTTX_GIT_VERSION_BINARY 0x3f77354c0dc88793 #define NUTTX_GIT_TAG_STR "v11.0.0" *** End of qurt slpi build *** /usr/local/workspace User ID is 1000 Group ID is 1000 *** End of build *** root@798402fd070f:/usr/local/workspace# ls

@teddy-zaremba EV_CTRL changed from 15 in 1.15 and earlier to 0 in 1.16. Either check this parameter is set to 15 or run "voxl-configure-px4-params -p MRB-D0006" for Starling V1 or "voxl-configure-px4-params -p MRB-D0005-V2" for Starling V2.

@Taka (1) VOXL 2 does not have any RF transmitters. RF could be transmitted by external WiFi, RC, Cellular modem, etc., etc. (2) How are you configuring the WiFi module? Is it in access point mode or station mode? The SDK will set everything up correctly when using the WiFi in "SoftAP" or access point mode.

@Alex-Kushleyev Hi Alex, Thanks! Yes, that was exactly the problem. I switched to the dev branch using 'voxl-configure-pkg-config', downloaded the latest voxl-portal ('apt get update && apt install voxl-portal'), and then switched back to the 1.4.0 pkg. Voxl-Portal works just fine now.

@griffin Great to hear!! It is possible, depending on what size tip and what kind of soldering iron you were using, that 650F may actually not have been hot enough. After talking about it with my team I realized that we have set our irons up to the 750-800F range. Nonetheless, it is likely the safest option to just splice in the new wires just as you have done

@Amin-Bassiri You can either fully re-flash the drone or just run voxl-configure-mpa in order to bring the drone back to it's default state based on the SKU

@kham https://www.modalai.com/products/m10000045?_pos=1&_sid=0d63c4c00&_ss=r