Please follow the safety guidelines before running any mission: https://modalai.com/safety The failsafe is configured in PX4 via QGC. We do not set that explicitly as that before is up to you how to configure. Please review the PX4 failsafe documentation and understand how it behaves, and then test in safe conditions, before flying again https://docs.px4.io/main/en/config/safety.html These are drones for developers, and are highly configurable. Please take precaution and test each function before making any assumptions about behavior.

I have discovered that the entire module seems to stop. I had been assuming it was the UART that was failing. Is there some PX4 setting where when a telemetry link occurs that something would stop/pause running modules?

@Troi said in Stereo camera does not appear in Camera Calibrator Overlay: Hello, I am trying to calibrate the stereo camera using the instructions on the website (https://docs.modalai.com/calibrate-cameras/). I use the following command to start the calibration process: voxl-calibrate-camera stereo -l 0.04 -s 4x7 I tried to view the calibration progress via the voxl-portal's Camera Calibrator Overlay. The Camera Calibrator Overlay option appears in the voxl-portal drop-down menu. However, the stereo view with overlay never appears. When I try to exit camera calibration (via Ctrl + C), the program hangs and I have to exit the terminal to stop the program. What should I do to solve the issue with the camera calibrator overlay and the stereo camera calibration? I am having the same issue, any help will be appreciated. @Troi How did you resolve this?

@m4v3r said in Flight Core w/ BMI088: Thanks so much for clarifyiing this for me and I take it you wouldn't suggest using it since it's an older part? My only suggestion is to use the ICM parts since that will always be installed on our boards, and you'll have no software mismatch builds across platforms old and new. It's the Bosch parts that have fallen out of favor lately in the market and were also very hard to get last year hence the move to start DNI'ing them. Thanks!

Hey the answer is yes. I use DroneBridge for ESP32 but I believe there's a ton of other similar mavlink apps for ESPs. cheers

I just found out, that the voxl-dfs-server is disabled at default. So I run systemctl enable voxl-dfs-server and it worked fin.

Has someone already solve this?

Nice work locating that setting, agreed it's not obvious to locate all of this info... Although this is VOXL2 documentation, the graphic here might be helpful to see the plumbing: https://docs.modalai.com/voxl2-external-flight-controller/#component-overview

Originally the FW update via QGC worked, and ideally that would be the way it works, but at some point the update stopped working (note that our bootloader didn't change). The px_uploader tool to me uses the same protocol as QGC, and as this works, I have a hunch the issue will be QGC side, but the jury is still out while we track it down. I decided to proceed to ship Flight Core v2 as I found the work around acceptable and had the work around publicly documented. I agree that our product line is still a bit bent towards power users at this point, so the use of git and such is a big ask for most people. If you have the chance, with respect to this topic in particular on this thread, please let me know where you got stuck with this particular process with our documentation and then I can use that feedback to improve things. https://docs.modalai.com/flight-core-v2-firmware/#how-to-upgrade-using-px_uploader-tool

@Adrian-Hidalgo said in rx-tx from v2 to voxl: px4_uart_bus": 12, for J11 connection worked transmitting data now

Hello, @Nicolas-Brissonneau: I am trying to do the same thing as you and am stuck with the same problem. Did you manage to solve it?

Hi @billybob I just stumbled upon this thread. Thanks for contributing to this forum!! If you need us to respond to anything or have any questions, the best bet is always a new thread. We get alerted (the entire company) on new threads, but not so for thread responses or "tack-on" thread posts. Just an FYI I've been updating that cables section recently (still have more to do!!!) and we are finding and posting workaround solutions for various Mavlink ports when someone's port breaks or they wish to change for mechanical reasons. I'm happy to see you found some of my notes. We are working to improve that too, especially since the older 5V on Voxl J12 is problematic on some new stuff, so I want to be sure everyone has all the info they need!!

Looks like the foam did the trick. No amount of tuning was able to stabilize the oscillations. The only issue with adding the foam was the FC reported "High Accelerometer Bias" which I was able to circumvent by loosening the tolerance by changing the COM_ARM_EKF_AB parameter. After all of that, the vehicle was rock steady

Sweet! Thanks Vinny!

Note, voxl-record-video is not documented, finished, or released yet. It's dependent on an internal version of voxl-camera-server that's not been released yet. You can expect this feature in the next SDK release (1.0).

The VOXL CAM is a development kit for SLAM that comes with a number of reference implementations. None of the reference implementations require a closed loop. voxl-qvio-server provides a dead reckoning service based on visual inertial odometry voxl-mapper provides a mapping and planning service for navigating congested spaces

Hi Asif, I'm not totally sure about the final use case (sensor driver and sensor implementations vary) but I can comment on the I2Cs on the hardware. In general you can have multiple I2C devices on the same bus (given they have ability to change slave addresses), so you may get away with multiples on a bus? I2C1 at J10 --> here normal use case is a magnetometer but yes you could use this, provided the driver looks for this port I2C2 at J14 -> here - this is 'spare' in our generic use case so should be OK Can you share PN of what you're trying to use? We don't have direct experience with ToF from Flight Core at this point to reference