No, V1 uses WNC modems and V2 uses Sierra

Hi Tamas, this video is how to get the voxl2 running with HITL: https://www.youtube.com/watch?v=ysvpJdXFWaM&ab_channel=AscendEngineering Also - unless you are running the voxl-dev branch, then you will not be able to do a SERIAL connection from the voxl2 to QGC, you can only leverage a UDP connection. If you are running the voxl-dev branch and flashed the board, then you can leverage the voxl-px4-hitl executable and connect to QGC. However, you cannot have gazebo open simultaneously because the serial connection will then be interrupted. If you wish to run HITL while running QGC, then run this using an FTDI cable and then turn on the required services (voxl-vision-px4, voxl-mavlink-server) and then connect to gazebo serially, and QGC via UDP signal. Let me know if this makes sense.

@rohitpillai Good morning, As long as you complete our online form then we have no problem with you dropping it off to us since you're local.

Honestly, I have zero experience building and tuning a custom drone. This custom drone was handed to me by my research group and it's my job to get it to fly programmatically with MAVROS. I was under the impression that the VOXL Flight Deck would already have its PID controllers tuned as I didn't see a section on PID tuning on the documentation for the Flight core. Regarding that tuning procedure, it requires the drone take off and hover. My drone can't take off, it starts tilting to one side and I have to immediately lower the throttle else it will tip over. Not sure how to address this, do I just trial and error different controller values until it is "stable enough" ? Or will disabling MC_AIRMODE automatically make it able to take off? My understanding is if its disabled then there is no roll/pitch/yaw so the drone should be only be able to move up or down, but I have never touched that setting.

Hi @Tamas-Pal-0 - looks like you are correct in that the voxl-px4-hitl has not been pulled into voxl-master. I would recommend for now switching over to the voxl-dev branch and running with the steps through there. Once it has been pulled into voxl-master, then you can recompile, reflash, and run through it on that branch. Other options as well is you can copy the file voxl-px4-hitl from the voxl-dev branch into your current working voxl-master, recompile, and reflash the voxl2 with the newer firmware containing the correct executable.

@Moderator I just tried running those instructions for VOXL1 build, but have an issue downloading the manifest package from codeaurora. I posted an issue here about it. Please let me know if there is an update!

@Chad-Sweet What is the "basic drone bring up process"? I can fly it in manual mode, it's not easy to fly, but I felt like its more due to my skill level as its behavior from virtual joystick was somewhat similar to when I tried virtual joystick with your RB5 drone. It does drift noticeably. I think this drift is excessive but again, I'm not sure if it's an issue with the drone or my skill level using virtual joystick. It didn't seem to respond to virtual joystick inputs in position mode but I didn't extensively enough test that mode. I'll test that mode again and see what happens.

@local-ad What are you trying to do?

@rohitpillai We have tried to connect RealSense in the past and weren't able to get it working. We have never tried the UWB radio.

@Hyosun-Yoo said in [yocto:/# roslaunch voxl_cam_ros tracking_slave.launch] Error Message ?: Re: AprilTag Relocalization Dear I got an error message when I run this command. [yocto:/# roslaunch voxl_cam_ros tracking_slave.launch] Please tell me how to solve this message. VOXL Vision (modalai-3-2-0-0.3.4-b.tar.gz) VOXL Vision PX4 Apriltag Relocalization error Error message ERROR: could not open camera subscriber for cam id 1 [ERROR] [1034.046473200]: CameraManager::Initialize() failed [ERROR] [1034.046845023]: Unable to open camera. ===============* Thank you so much. Mr. Yoo, hyosun

Hi, In the latest release on voxl we've added the voxl-mavlink-server service to rout mavlink messages from vvpx4, it's possible that this service is not running. Can you show the output of voxl-inspect-services on your drone.

@Tamas-Pal-0 Please try with branch "voxl-dev"

Hi, There are two answers to your question: You can pipe depth input from voxl-dfs-server (if you're running stereo cameras) to voxl-mapper, or any other service that you may create that produces depth estimates (i.e. if you had a depth from motion project). We absolutely plan to support the tof camera on voxl2, we're working on this right now internally and hope to support it in the next month or two.

@Yohai, Are you building in the correct docker environment? voxl-qvio-server must be built within the voxl-emulator image, which has the necessary files baked in. From the README of the project: prerequisite: voxl-emulator docker image >= v1.7 for APQ8096, qrb5165-emulator (>=1.3) for qrb5165 builds.

I've figured out why. My original MPC_LAND_SPEED and MPC_Z_VEL_MAX_DN were 0.6 and 0.5 respectively. Thanks to the following chunk of code from MulticopterLandDetector.cpp, descend_vel_sp will never be true. if (_flag_control_climb_rate_enabled) { vehicle_local_position_setpoint_s vehicle_local_position_setpoint; if (_vehicle_local_position_setpoint_sub.update(&vehicle_local_position_setpoint)) { // setpoints can briefly be NAN to signal resets, TODO: fix in multicopter position controller const bool descend_vel_sp = PX4_ISFINITE(vehicle_local_position_setpoint.vz) && (vehicle_local_position_setpoint.vz >= land_speed_threshold); Had to increase MPC_Z_VEL_MAX_DN and that solved my problem

Ok i resolved the issue. You actually need to run voxl-mavlink-server and voxl-vision-px4 to get Autopilot enabled for Mavsdk.

@Nishkala, This looks like a version mismatch between the voxl-voxblox you built against and the version you have on your VOXL. To ensure the versions match, you need to install the build dependencies from the last release in voxl-cross before deploying to voxl. This can be done by running: ./install_build_deps.sh apq8096 sdk-0.8 instead of ./install_build_deps.sh apq8096 stable