Hi @Aldo-Castro-Freire , We don't support any 5G modems on VOXL today, however we expect to in the next few months.

@Chad-Sweet [image: 1620141446462-img_20210504_100858-1.jpg] These are default connection on the board yocto:/# voxl-configure-cameras 3 attempting to use camera configuration 3 adding override_cam_id value=1 to /etc/snav/camera.downward.xml adding override_cam_id value=2 to /etc/snav/camera.stereo.xml yocto:/# cat /etc/modalai/camera_env.sh export CAM_CONFIG_ID=3 export HIRES_CAM_ID=0 export TRACKING_CAM_ID=1 export STEREO_CAM_ID=2 export TOF_CAM_ID=-1 After setting configuration to 3 as well yocto# roslaunch voxl_cam_ros tracking ... logging to /home/root/.ros/log/1f7737e8-ad09-11eb-b4a1-ec5c68cd1745/roslaunch-apq8096-3742.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://192.168.100.90:46578/ SUMMARY ======== PARAMETERS * /rosdistro: indigo * /rosversion: 1.11.21 * /tracking/voxl_cam_nodelet/cam_id: 0 * /tracking/voxl_cam_nodelet/cam_name: tracking * /tracking/voxl_cam_nodelet/frame_id: tracking_frame * /tracking/voxl_cam_nodelet/frame_rate: 15 * /tracking/voxl_cam_nodelet/height: 480 * /tracking/voxl_cam_nodelet/is_cam_master: False * /tracking/voxl_cam_nodelet/skip_n_frames: 0 * /tracking/voxl_cam_nodelet/snav_raw10_compatability: True * /tracking/voxl_cam_nodelet/width: 640 NODES /tracking/ tracking_nodelet_manager (nodelet/nodelet) voxl_cam_nodelet (nodelet/nodelet) auto-starting new master process[master]: started with pid [3761] ROS_MASTER_URI=http://localhost:11311/ setting /run_id to 1f7737e8-ad09-11eb-b4a1-ec5c68cd1745 process[rosout-1]: started with pid [3774] started core service [/rosout] process[tracking/tracking_nodelet_manager-2]: started with pid [3780] process[tracking/voxl_cam_nodelet-3]: started with pid [3788] [ INFO] [1620154027.140051685]: Initializing nodelet with 4 worker threads. [ INFO] [1620154027.459145704]: SnapCamDriver Starting [ INFO] [1620154027.459566279]: Monotonic offset: 1620153449.753732686 libcam.enable.publish 1 libcam.enable.publish.dump 0 libcam.publish.buffer.policy max libcam.publish.buffer.max 3 libcam.debug.level info libcam.dump.dir /data/misc/camera/dumps ERROR: could not open camera subscriber for cam id 0 [ERROR] [1620154044.976910041]: CameraManager::Initialize() failed [ERROR] [1620154044.977876660]: Unable to open camera.

@Alfonso-Ponce the -f is for a factory setup (a quick way for us to set the default configuration for the m500 drones)

nothing else has changed.

Hi @Sébastien-de-Pret-Roose-de-Calesberg , I'll get an email going to this address on this account, I'm not clear what's going on and perhaps we need to send it in. Thanks and sorry for the inconvenience, Travis

It is likely there were not stable visual features on takeoff. A field of grass is not that great for visual feature tracking. You could try putting something in front of the drone on the ground for it to look at and see if that helps

It sounds like you are putting the drone into offboard mode, with the offboard mode set to "figure_eight". https://docs.modalai.com/voxl-vision-px4-other-features/ You shouldn't need to be in offboard mode to use the apriltag relocalization, see here: https://docs.modalai.com/voxl-vision-px4-apriltag-relocalization/

Hi @kiprock , The motor test commands I've used were from the MAVLink shell, but using the pwm test command: https://dev.px4.io/master/en/middleware/modules_command.html#pwm I've seen similar issues when trying to use the built in QGC PWM calibration feature... Since the Flight Core v1 can't be powered over USB (an artifact of sharing the 5VDC rail with VOXL when paired together and the fact that 500mA isn't enough to juice VOXL), it requires the python util that you linked above.

Thanks you. I'll give it a try

Hi @Arrowtec , I've seen this myself before. In my case the device would then show up after running sudo fastboot devices and I could proceed after trying again. If it's not showing up with either sudo fastboot devices or adb devices it would likely need the Debug board which allows you to force it to boot into fastboot....

The Flight Deck has the two main components (VOXL and FlightCore). They share a 5VDC rail that is fed by the Power Module on the M500. The FlightCore portion of the board is a little STM32 microprocessor running PX4. PX4 reads that 5VDC from an ADC. Depending on your toolset, it could be easy to probe that voltage: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1013---5v-dc-power-input-i2c3-to-power-cable-apm When you did the manual flight you had no issues?

@James-Strawson got it. My test s/w version is volx-vision-px4 0.3.4 and has a same problem, am I right? Okay, I’ll proceed test VOA using 0.2.0 version before releasing new version s/w. Can I know release date for new version? Thanks,

@MattO The instructions should be more clear now: https://gitlab.com/voxl-public/other/voxl-python-3.6.9#installing-the-ipk

I assume you are using the master version of voxl-vision-px4. Since the is_cam_master is false, is voxl-vision-px4 still running? vvpx4 would be the camera master in that case Can you check what TRACKING_CAM_ID is? 'echo $TRACKING_CAM_ID' If you have high-res, stereo and tracking plugged in TRACKING_CAM_ID should be 1 which matches what you have in the launch file

@gauravshukla914 , I for the first time got the "avionics power low" message! I turned off the ADCs on FlightCore for a test and got this error. PX4 monitors the 5VDC rail (and 3.3VDC), and this makes sense now, as the output of that power module was lower than expected. Anyhow, I remembered this post so figured I'd put some details here while I saw it

@FourPointTwoMm I've done this a bunch myself!!

Thanks for the feedback! The documentation has been updated.