Yes, we will be providing a full SDK similar to what we offer on Voxl. In fact the new SDK will have some benefits in that the underlying platform is based on Ubuntu. And we are trying to keep the software interfaces identical in the SDK to facilitate easy migration of software.

Hi @Jesús-Pestana-Puerta ,

Yes we ship international. As an example, we shipped an m500 drone (similar weight/size) to Belgium via DHL for right around $100 USD via 3 day express. It varies though so please take this with some possible error margin 😉

Hi @Matthew-Howlett ,

No the m500 currently has a BMP388.

Hi @mrawding ,

The current early release on the EVT hardware relies on gstreamer.... for example:

cd /data/misc/camera rm * gst-launch-1.0 -e qtiqmmfsrc camera=0 name=tracker ! video/x-h264,format=NV12,width=640,height=480,framerate=30/1 ! queue ! h264parse ! avdec_h264 ! videoconvert ! pngenc ! multifilesink enable-last-sample=false location="/data/misc/camera/cam0_img_%d_.png"

This will save images to the path specified. We're actively working on getting the same interfacing as VOXL up on this ;). Next few weeks should have some good PUBLIC REPO updates.

We are currently working on this, there's no definite timeline but it's one of the main projects we're currently working on. Note that there will be no port of the voxl-docker project since rb5 is an ubuntu platform (so you can install docker normally with the standard ubuntu process)

That is correct. They are the same binaries with target-specific integration software around them.

@tom said in Can I control the drone through 5G (No Spektrum Transmitter) ?:

/etc/systemd/system/rb5-net-check.service

Thank you @tom ! It worked!

In theory, yes. It would require setting up the proper routing tables in Linux. Should be standard Linux configurations, though we have not tried it. If you get it to work, please report back here! 🙂

@modaltb Excellent! Happy to help if you need it. Don't hesitate to reach out to myself or @mrawding

Hi @Francesco-Jacomel,

We are having a hard time reproducing your issue on our end. Here are the steps we took in order to connect to QGroundControl (Mobile - iPhone) Version 4.0.10

Setup wifi on RB5 by modifying the /data/misc/wifi/wpa_supplicant.conf with our wifi, rebooting the RB5, and connecting our mobile device to the same network which we had setup on the RB5 Open QGroundControl on our mobile device and wait for a connection

Following these steps we were able to successfully connect. If these steps were also taken on your end then we think there may be a UDP broadcasting conflict that is causing the issue. We can troubleshoot this by having you make some modifications to your full-m0052.config file on target.

You'll want to disable MAV_BROADCAST as well as add your Iphone's IP in the /etc/modalai/full-m0052.config file on target. Configure this file in the appropriate section so it looks as follows:

# This is needed for altitude and position hold modes flight_mode_manager start # Add this line to disable MAV_BROADCAST param set MAV_BROADCAST 0 # Edit this line to add your phones IP mavlink start -x -u 14557 -r 40000 -t <Iphone IP> mavlink start -u 14556 -t 127.0.0.1 -n lo -m custom sleep 1 mavlink stream -u 14557 -s HIGHRES_IMU -r 5 mavlink stream -u 14557 -s ATTITUDE -r 5 mavlink stream -u 14557 -s RC_CHANNELS -r 20 sleep 1

Make sure to fill in the IP with your mobile phones IP. On an IPhone you can get the IP by going to settings>Wi-Fi and clicking the info button on your network. After configuring these parameters reboot your RB5 and open the QGC application on the mobile phone and see if the issue is still present.

Thank you for being patient with us. If needed, we can also arrange a phone call to try and further troubleshoot this issue.

Hi @benjamin-linne,

Supporting more ESCs in the future is definitely on the roadmap, but no hard timelines to provide.

In general, the current ESC is interfaced with a UART based driver, eg. here:
https://github.com/modalai/px4-firmware/blob/v1.2.x-modalai-rb5-flight-alpha/src/drivers/uart_esc/modalai_esc/modalai_esc_serial.cpp#L50

This UART itself actually resides in the DSP, so it's customizable but we need to get a bit more docs up for this to make it achievable for others!

Sorry I see the step I missed! I'll give it a try soon. Thank you for clearing that up for me.

@MaxG Glad to hear that! Thanks for the update.

@umlr said in QGroundControl USB connection for sensor calibration:

Performing sensor calibration over a WiFi connection is known to be unreliable. You should disconnect and perform calibration using a direct USB connection instead.

Alright good to know that calibrating over WiFi is fine.

Yes WiFi connection with QGroundControl worked pretty much out-of-the-box.

Another update that could be useful to someone:

I needed to have a high enough frequency on the local position feedback (ROS topic /mavros/local_position/pose) but I was only receiving at 1hz. Usual solution with most FCU is to set the parameter MAV_1_MODE to Onboard but this parameter is not available on the RB5.

Instead I added the line mavlink stream -u 14558 -s LOCAL_POSITION_NED -r 100 in /etc/modalai/full-m0052.config to set the stream rate. The end of my file looks like that.

# Configure a second mavlink instance for onboard messages (e.g. VIO and VOA) mavlink start -u 14556 -t 127.0.0.1 -n lo -m custom mavlink start -x -o 14540 -u 14558 -n lo sleep 1 mavlink stream -u 14557 -s HIGHRES_IMU -r 5 mavlink stream -u 14557 -s ATTITUDE -r 5 mavlink stream -u 14557 -s RC_CHANNELS -r 20 mavlink stream -u 14558 -s LOCAL_POSITION_NED -r 100 sleep 1 # Start up the IMU server to support VIO imu_server start

And this way I managed to get a frequency of around 55hz on /mavros/local_position/pose.

@Jeremy-Schmidt
Ah you are right they are all here, I thought I erased everything when flashing the new image.

[voxl-configure-extrinsics](https://docs.modalai.com/configure-extrinsics/) provides a tool for configuration, voxl-inspect-extrinsics provides a tool to view the current settings

@Hector-Nevarez Thanks for the quick reply. If the camera server are disabled I guess VIO can not work?

@chris_macdonald Oops, my bad. It is on board at /usr/bin/set-mode-pref