@joshuagaus Even with our new upcoming module we will not support PPM. It looks like there may be some other communication options on that receiver so you may want to review all the possibilities.

Yes, we ship within 10 business days. The payload capability is about 1kg

Reading your post again . . . It looks like you'll have to QGCs running, but using the same router. In the response above, I assumed a single GCS. On each drone, go to /etc/modalai. There should be a file qgc-ip.conf or something similar. You can set the IP of the target laptop, so the MAVLink gets routed properly. Let me know if that works.

We don't believe there are any issues, but we just sent you an email in case.

@MaxG we are currently low on stock of the replacement parts, but they can be found here on our web store. Please check back in the next week or two and those will be in stock. Replacement landing skids can be special ordered. Do you need the entire skid assembly or just the landing skid itself (black part)? Please send a picture to contact@modalai.com and we can get you the parts that you need!

Hi Akash, we do not expect much of the Qualcomm Flight RB5 SDK to work on the RB5 dev kit without a significant amount of work.

@RichieRich GPS unit is mounted by default (as it comes with RB5 5G drone), mast is locked in vertical postion. Turning EKF2_REQ_SACC to 0,75 provided no errors from GPS. Obstacle avoidance was also disabled, so we managed to fly. But I'm still a bit confused why the obstacle avoidance gives error, since the drone was placed on the ground (concrete pavement), no obstacles within few meters, while the minimum distance was set to only 1 m. But this is current setup that works: [image: 1649438004385-0de5d598-3401-4512-9e7b-3ef8202ef635-image.png] Many thanks for your help. We'll try to figure this out and provide info in a few days.

@mrawding Also Apple A1277

If anyone else is interested - I found a way to enable static ip's for ethernet and wlan interfaces. You'll need to install a file like below under /etc/systemd/systetem/ and run the following commands: systemctl enable ipconfig.service systemctl disable dhcpcd.service [Unit] Description=A description for your custom service goes here Requires=systemd-networkd.service After=systemd-networkd-wait-online.service [Service] Type=simple ExecStartPre=/bin/sleep 10 ExecStart=/bin/systemctl restart systemd-networkd.service [Install] WantedBy=multi-user.target You'll also need to add this file under /etc/systemd/network/wlan0.network [Match] Name=wlan0 [Network] Address=192.168.0.169/24 #DHCP=yes Simply installing this service will allow most routers to keep the rb5 address the same when assigning IPs for a lease. Just comment #Address and uncomment DHCP to use dhcp. You will also need to make sure to add the gatway to the routing table: route add default gw $router_IP $network_interface this is best to be configured as a oneshot service where the service has the field Requires=ipconfig.service

For softap, there are references here on how to enable At some point more flexibility will be added for camera configurations. Right now the shipping configuration is all that is supported. There is already a tracking camera at 45°. You should be able to create a mount to point that straight down if you prefer. Only one active gstreamer instance for each camera can be running. The camera servers use gstreamer to get the camera data and publish that to a named pipe. So if an instance of a camera server is running, then a new gstreamer instance for that same camera can't be started. MAVROS is not pre-installed. That is planned in a future version of the SDK, likely one or two months away. We do have customers using it today though. Note in offboard mode the default behavior is a figure-8. See post here for the fix

ModalAI is the only manufacturer of Qualcomm Flight RB5 boards We will release more pricing information soon. The VOA functionality creates the depth map and obstacle map on the CPU and passes that information to PX4 running on the DSP. Yes, there is USB expansion, datasheet has all of the details here The USB expansion through the modem carrier board uses JST-style connectors which are more vibration tolerant. The end UAV manufacturer can equip with a fan. HDMI input is not supported at this point

@Djalma-Ribeiro Awesome thank you, just wanted to make sure your RB5 had the SDK loaded properly, which it does. It's not absolutely necessary to upgrade the SDK, if you do want to you can follow the steps here: https://docs.modalai.com/Qualcomm-Flight-RB5-sdk-installation/#how-to-upgrade One note, if you try to upgrade the SDK while PX4 is running it will fail. So in order to upgrade the SDK you would have to disable PX4 from starting systemctl disable rb5-px4-start and then reboot your drone before upgrading your SDK.

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

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

[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

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

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.

@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.

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