Hi Cris, some answers to your questions:

1. Ubuntu 18.04 for the time being (datasheet).
2. ROS 1 and 2 are easily installed. Examples are pending. Current SDK is documented here
3. The image sensors are available via gstreamer. We will have an IMU API soon.
4. Soft AP and station mode are supported (docs)
5. VNC/GUI - we have not tried this, but it's Ubuntu so it seems likely something could be tried
6. See datasheet for architecture. Yes, there is an SD Card slot.
7. The kit comes with everything shown here, the 5G modem is optional.
8. The 4G add-on, 5G add-on, Microhard add-on are all optionally supported.

Thanks for posting the ssl fix. We're looking into this. We don't typically use rosdep for anything. Is there something specific you need to get working?

A more traditional ROS experience is easy to achieve running Ubuntu in a Docker on VOXL : https://docs.modalai.com/docker-on-voxl/

It would have shipped with everything tested and working. What do you mean by "passed the wizard"?

Your understanding is correct, ModalAI's supported configurations are a result of Qualcomm limitations

The lens is fixed focus, but if you twist the little black part of the lens you should be able to focus.

You should be able to use the open source PX4 avoidance, but it may require a bit of an atypical architecture. When trying to use big ROS projects we recommended running Ubuntu on VOXL in Docker

The base Yocto layer should be ROS core and expose the VIO and depth from stereo modules:

• voxl-cam-ros
• snap_vio
• depth-from-stereo

Then the Ubuntu OS in the Docker should subscribe to the appropriate hardware layer topics to execute the PX4 Autonomy

We should have this better documented, but keep asking on this thread and we'll try to get you going. Shouldn't be any major blockers, but a few tweaks are probably necessary.

We do not have a thermal option available today, though the Flir Boson and Lepton have been integrated by customers in the past using USB

Stereo cameras need to be co-planar and mounted rigidly. Then they need to be calibrated. Otherwise you should be able to mount wherever convenient

The system was tested in VIO mode for 20 minutes before shipping. All drones are very sensitive to frame modifications, so this needs to be done carefully

• Were you able to fly successfully before frame modifications?
• How well does it fly manually? Have you looked at the logs in manual.mode for vibration?
• Can you please share a log of the VIO output?
• If you reset all of the software, you may need to recalibrate the cameras
• It looks like there are loose parts hanging off of the drone. VIO is VERY sensitive to vibration. Can you revert your frame modifications and try again?

Are you flipping the fastboot switch back? Your symptom is consistent with leaving the fastboot switch engaged instead of setting it back to normal after a few seconds

Might be worth watching the tutorial here if you're unsure

We haven't tried the Avoidance stack in a while, so it's probably going to come down to what you are more comfortable with. If you are comfortable with Gazebo, SITL might be a good way to go.

The trick with ROS always comes down to making sure all of the nodes are talking to each other. There is a good tutorial on debugging ROS here

You'll want to have a list of the ROS topics the Ubuntu PX4 Avoidance stack requires, and then a list of the ROS topics the yocto base layer is providing. Then you'll need to map the two together.

You should only have one roscore, which should likely be in the Yocto layer. Your PC implementation should be able to see that if you have ROS_IP, etc configured properly.

The most valuable tool right now will probably be rostopic list and rostopic echo. Run ros topic on each of the layers:

• yocto base layer
• Ubuntu Docker
• PC workstation

Make sure you see the proper topics in each location and that they are publishing data.

Regarding stereo, I don't think that PX4 docs section is applicable. That RosDfsExample node should already be publishing a disparity map and point cloud. You can see it is publishing the disparity map here and point cloud here

You need to be outdoors, with clear visibility to the sky, to receive GPS

These are usually hardware issues. Some possibilities

1. crimped flex cable
2. exposed copper on the flex cable
3. loose or damaged connector

I don't think we have used a Flight Core PWM to control a servo at ModalAI

Have you reviewed the PX4 docs? The Flight Core is a pretty standard PX4 flight controller, like a pixhawk

https://docs.px4.io/main/en/peripherals/pwm_escs_and_servo.html#pwm-servos-and-escs-motor-controllers

It is likely that driver is not supported. You may need to add it to the VOXL 2 PX4 build if you want to use the integrated flight controller. It may be easier to use an external flight controller if you want to use a broader set of inputs

https://docs.modalai.com/voxl-px4-developer-guide/

are you outdoors? You need to be outdoors to receive GPS.

It was a custom PCB that we do not have available as a product

You can set the resolution of the preview stream in /etc/modalai/voxl-camera-server.conf

That docker example is for VOXL 1. You should not use a Docker on VOXL 2 to access the GPU

It looks like it may need some tuning. Have you tried working through the PID tuning process?
https://docs.px4.io/main/en/config_mc/pid_tuning_guide_multicopter.html

Also, you could put some foam under the main plate of the flight deck. there might be some extra wobble in the roll direction on that setup.