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

Thanks!!

Hi @張為超 All right, thanks so much for that, and I will then have a look at it

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.

Thank you for the response! I didn't have time to look into this yet. But there is more going on with the system I think. WIFI also doesn't work anymore. And after trying to solve the WIFI, the ADB of the VOXL stopped working. So we for now we are using a different VOXL. Something else we are running against is the message Reject position control, with working VOXL CAM systems installed on our drones. When we fly everything is super! When we land, after the drone has bumped into things while flying (drone is collision proof) or when heavy wind was pushing it. We cannot take off after landing, it will display Reject position control. Only when the we connect a laptop to the QGC, we can hear that the VOXL reboots and then the Reject position control is gone, and we can go fly again. But if we use QGC via the PX4 Telemetry port, this doesn't happen, and we need to unplug and replug the battery to be able to get the Reject position control message away again. We don't really know why this happens and how we can solve this. It would of course be great if the VOXL didn't need to reboot in order the drone can fly again in position mode. But it already would be helpful that the VOXL would reboot without having to have WIFI connection with QGC. Please help!

Yes, chr is an issue most likely. Take a look at how uint8 from a binary representation is sent here : https://gitlab.com/voxl-public/voxl-sdk/core-libs/libapq8096-io/-/blob/master/lib/python/voxl_i2c_apm_v1.py#L48 you can do something similar (also example for hex). The data type needs to be some sort of an int. #values of configuration registers CTRLA (address 0x00) and CTRLB (address 0x01) CTRLA = np.uint8(int('0b01011000',2)) #offset calib every 128 conv, volt=Sense+; so sampling takes about 35ms (for both voltage and current together) CTRLB = np.uint8(int('0b00000100',2)) #addresses of registers for reading data REG_VRAW = int('0x1E',16) REG_IRAW = int('0x14',16) #write configuration to both LTC2946 devices p.slave_config(ID0) p.write(0,8,CTRLA) p.write(1,8,CTRLB) ... p.slave_config(ID0) vraw_batt = p.read(REG_VRAW,8,2) iraw_batt = p.read(REG_IRAW,8,2)

@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

Additionally, I am unable to view the pointcloud in RViz It connects and can show images but not spatial data: No tf data. Actual error: Fixed Frame [map] does not exist Maybe there is a misconfiguration of ros on the seeker?

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

+1 for this functionality if possible. Would it be possible to merge the color branch into dev/master for the next release? If speed is a problem I think it would be acceptable to limit this to lower resolutions as a starting point

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