@vjuliani yes, it will update everything

Yes, @tom. Thank you

follow this adb shell sudo nano /etc/dhcpcd.conf copy your ip in the page like this: interface wlan0 static ip_address=192.168.1.35/24 static routers=192.168.1.7 static domain_name_servers=192.168.1.7 have look at this link also. https://www.makeuseof.com/raspberry-pi-set-static-ip/

@enrico-bandera-0 Awesome! I am glad you figured it out.

@frafrat Hi. The sensor is integrated into the VOXL SDK and raw data can be viewed through ADB or SSH with the voxl-inspect-rangefinders command line tool. All PX4 Autonomy Dev kids have this sensor. That data is sent from qrb5165-rangefinder-server to PX4 via voxl-mavlink-server. To enable in PX4 set the PX4 EKF2_RNG_CTRL param to 1. You will likely need to fiddle with PX4's other rangefinder params to achieve the behavior you want. Best, James

@pfranklin can you please share which website you are referring to?

@Jetson-Nano Looks like MPC_POS_MODE is needed as well per the documentation https://docs.px4.io/main/en/computer_vision/collision_prevention.html

@xav04 I am trying to do the same thing as you, by using the J9 port on the 5G Modem to attach an RTK GPS. Were you able to do so?

@Eric-Katzfey Thanks for your help. I've confirmed that I was able to use J19 with the "RC=M0065_SBUS" option successfully. Hence, if no VOXL_ESC, one should use J18 for the VOXL2 IO board and if there IS a VOXL_ESC board, one should use the J19 for the VOXL2 IO board. The firmware seems to be "smart" enough to figure out as long as /etc/modalai/voxl-px4.conf is set as you suggested. -Joe

Hi @riteshsharma We usually recommend a small screwdriver (flat edge) or tweezers to actuate those small switches. For the FASTBOOT switch, you need to use something less likely to break the top plastic, so the back end of a qtip or a pencil is good for that one.

Hi Erik, thanks for pointing that out. It was a mistake, it has now been fixed as there are no CH-201 sensors

@jmltt no, if you use the standard battery all should work as expected

@tom thanks tom! with voxl-configure-sku -w I assumed the option to select is 6) px4-autonomy-dev-kit i then ran voxl-configure-mpa saw a few errors but the qvio is working now with no errors. Sabri

@Alex-Kushleyev Thanks for getting back to me I can't fly again until tomorrow but I will upload the log after we attempt a hover test. We were actually able to fly on Monday and we could achieve stable flight in acro mode off a fresh battery but only for about 30 seconds. We're getting new batteries to see if that's contributing. Don't know why it would cause the system (or at-least PX4) to continuously crash/reboot though. Here are the results of the esc checks: voxl2:/usr/share/modalai/voxl-esc-tools$ ./voxl-esc-scan.py Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00) [GCC 8.4.0] Found voxl-esc tools bin version: 1.4 VOXL Platform: M0054 Detected RB5 Flight, VOXL2 M0054 or M0104! INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000 Sending library name request: libslpi_qrb5165_io.so Received standard error event 2 Sending initialization request INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000, protocol: firmware INFO: Verifying ESC Params.. INFO: ESC Information: INFO: --------------------- ID : 0 Board : version 31: ModalAi 4-in-1 ESC V2 RevB (M0049) UID : 0x2033393953435708003A0048 Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 0a80a32a Params : ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml ID : 1 Board : version 31: ModalAi 4-in-1 ESC V2 RevB (M0049) UID : 0x203339395343570800340041 Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 0a80a32a Params : ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml ID : 2 Board : version 31: ModalAi 4-in-1 ESC V2 RevB (M0049) UID : 0x2033393953435708003A004F Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 0a80a32a Params : ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml ID : 3 Board : version 31: ModalAi 4-in-1 ESC V2 RevB (M0049) UID : 0x2033393953435708003A0056 Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 0a80a32a Params : ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml voxl2:/usr/share/modalai/voxl-esc-tools$ ./voxl-esc-verify-params.py Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00) [GCC 8.4.0] Found voxl-esc tools bin version: 1.4 VOXL Platform: M0054 Detected RB5 Flight, VOXL2 M0054 or M0104! INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000 Sending library name request: libslpi_qrb5165_io.so Received standard error event 2 Sending initialization request INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000 INFO: Params from ID 0 match ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml INFO: Params from ID 1 match ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml INFO: Params from ID 2 match ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml INFO: Params from ID 3 match ../voxl-esc-params/Sentinel_V1/Sentinel_V1.xml INFO: Success! Params in all ESCs are valid and identical. Let me know if you'd like me to look at anything specifically in the flight logs from our previous attempts. Otherwise I'll follow up tomorrow after our next attempt. Thanks!

@Eric-Katzfey thanks, I completed all steps successfully and also built the px4 image for voxl2 Thanks a lot for your help Enrico

@tom Thank you for your response, I went through the link you mentioned and had the following issues: I had already setup the environment source from the video I mentioned earlier with the line: source opt/ros/dashing/setup.bash Is there a way to change it, or would it require a clean install? Moreover, as I am new to this, I am having some trouble understanding the "MPA - to - Ros2" steps mentioned in the document. Can you please elaborate on the command lines I should execute for the steps mentioned. Thanks again!

@Andre-Moura That's alright, thank you so much for all your help on this!

@josephmlullo The build environment for px4 is within a Docker container. You can find the instructions on how to create this Docker image here: https://gitlab.com/voxl-public/rb5-flight/rb5-flight-px4-build-docker

@Darshit-Desai , yes i believe you are showing the TOF and Hires camera local frames correctly. As for the vehicle, the convention we normally use is FRD, but since you mentioned that you are assuming FLU in your case, that also looks correct.