We do not have any recommended or supported gimbal solutions at this time, sorry. We have had a difficult time finding one that is readily available. Some folks have had luck with Tarot gimbals though, you could try that.

sorry for the slow reply. We have a bunch of data from our dyno bench here

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!

@Developer-Evaluation Exactly. If you're using an alternate data link for motor control such as LTE or Microhard the RC radio is purely for safety purposes.

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.

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

This issue pops up from time to time and it is, without fail, a hardware issue. Can you check not just the connectors for your stereo cameras but also the cables themselves. They can develop kinks or get scratched and expose the traces if they go through any number of unfriendly environments, which will regularly lead to hal3 being unable to see the device.

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!

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

Great, thanks for the info. I suspected something along those lines.

@PawelJ Thanks for sharing! Great work!

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

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)

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.

Hi @jsearlePSU_ARL , I wouldn't expect battery affecting the measurement, but possibly vehicle response (although not at 34%). The default params are setup for 4s as well. When batteries get low, 'power' gets low, and thus response, so the oomph to move to desired location, but not the sensors ability to measure (that power source is from the VOXL power module output, not tied to the motors power per-se).