You are welcome! By the way the Starling 2 Max plastics kit (linked above) contains both types of front camera mounts (with and without the TOF sensor).

@Ebenezer-Afrifa , sorry, but Starling 2 Max is not capable of carrying such a large payload. We currently do not offer any platforms capable of carrying 3-4 pounds. Alex

@nickanick is this the right place to ask these questions?

@NikosMav Yes, things will get hotter when running QVIO. But once you arm and start the props everything will cool down. When reflashing the SDK I would grab one of the official releases from our downloads page and not a nightly.

Hi team — just bumping this in case it slipped through. We're ready to buy one evaluation unit and would really appreciate a quick steer: can the Stinger Vision FPV run AUTONOMOUS VIO/SLAM + AprilTag precision landing, or would Starling 2 / Starling 2 Max be the better evaluation platform for the requirements above? I've also emailed sales@modalai.com in parallel, so whichever channel is easier works for us. Thanks!

if no internet is available onboard llm+NPU can help repairing-agent to fix the issue or provide reason of failure.

For visibility, since this seems related to the old BLE/VOXL discussion here: https://forum.modalai.com/topic/1730/bluetooth-ble-communication-on-the-voxl-is-it-possible I was able to get BLE 5.0 extended advertising scanning working on VOXL2 / Starling 2 with an ASUS BT500 / Realtek RTL8761B USB adapter by backporting newer upstream Linux Bluetooth HCI event parsing logic into the QRB5165 4.19 kernel tree. My understanding is future revisions of VOXL will have more up to date kernels that solve this issue without back porting. The issue we were hitting was with LE Extended Advertising Reports. With BLE 5.0 beacons transmitting extended advertising, the older 4.19 Bluetooth path could mis-handle extended advertising report parsing / event-type bits, leading to bad report handling and, in our case, Bluetooth instability / crashes during scanning. The relevant upstream Linux changes I used as reference include: b48b833f9e8a - Bluetooth: HCI: Use skb_pull_data to parse LE Ext Advertising Report event ad38e55e1c89 - Bluetooth: hci_event: Ignore reserved bits in LE Extended Adv Report 0cadf8534f2a - Bluetooth: hci_event: Mask data status from LE ext adv reports There are also related Realtek / extended-scan quirk changes upstream, but for our immediate case the stronger LE extended advertising parser backport was enough to stop the crash path and allow scanning. Validated result: VOXL2 / Starling 2 QRB5165 4.19 kernel ASUS BT500 / RTL8761B USB BLE adapter BLE 5.0 beacons using extended advertising btmgmt --index 0 find -l successfully reports devices and RSSI btmon captures LE Extended Advertising Report events no more Bluetooth NULL pointer dereference / hci_le_ext_adv_report_evt crash during the test observed all 16 expected beacons and repeated RSSI samples I’m not proposing this as a merge-ready ModalAI patch, but I put the build changes and notes here in case anyone else needs BLE 5.0 extended advertising / RSSI collection on VOXL2: https://gitlab.com/steven323/qrb5165-kernel-build-docker Relevant upstream commit links: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b48b833f9e8a https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad38e55e1c89 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0cadf8534f2a

@voxltester As I tried to explain before, don't wait for voxl-mavlink-server to connect to your application. You need to have it initiate the connection to voxl-mavlink-server.

@John-Keller , please try https://docs.modalai.com/voxl2-unbricking/

@Jetson-Nano Can you rebuild to add UAVCAN? The code is here: https://github.com/modalai/px4-firmware/tree/v1.14.0-2.0.133-dev

@Eric-Katzfey UAVCAN is working in the latest versions, when enabled. And yes I meant heading error, thats my mistake. The collision prevention is the major issue I am having. The heading error is in the latest version, and I also came across it in the issues section and it was shown solved, but I did not test it out still with VIO, I was testing with only Optical flow and it was not working.

@gerard I also just remembered we had a stint of bad MCBL-00010's a few months ago... We have since cleared that up, but there is no telling how long ago you may have ordered that cable... Please see this thread for guidance and if you do think your MCBL-00010 is at fault, we will replace your M0048, just reference both threads in your RMA (this one and this one -->) https://forum.modalai.com/topic/4632/flight-core-2-firmware-update-through-qgc?_=1781284416780

@Eric-Katzfey We reinstalled the QGC in a new laptop and it is working fine now.

@Eric-Katzfey We are experiencing connection issues between VOXL2 and QGC. QGroundControl is showing disconnected after inputting the comms link with 192.168.7.2:14550 in UDP. mavlink_to_gcs and mavlink_from_gcs are both reporting data. voxl-px4 and voxl-mavlink-server are running. voxl-my-ip 192.168.7.2 (usb0)

@vmbasvi That appears to be a Microhard modem, not a WiFi dongle.

@Alex-Kushleyev At a bare minimum I just need the additional pwn channels to be controlled by joysticks via QGC. They don't need to be connected to PX4/Autopilot at this point. Does this allow for an easier solution? Thanks! Matt

@j-angel , We had a small batch of color AR0144, but those have run out and due to low demand, we do not have any stock. I would like to clarify something. Motion blur is present when using any camera (global shutter or rolling shutter). Global shutter cameras also have exposure control and long exposure times will cause motion blur. I think what you may be referring to, which is different in rolling shutter cameras (compared to global shutter), is the rolling shutter skew. Rolling shutter cameras use a technique where the start of exposure of each image row is offset slightly, so each row is essentially exposed over a different time frame. The offset is usually very small (4-30 microseconds per line, depends on the camera, mode), but from top to bottom, the rolling shutter effect can add up and be visible when there are moving features in the scene. The fastest rolling shutter camera we have right now is IMX412 and in the 2x2 binning mode, the 1920x1080 resolution, the total frame readout time is 4ms. (https://docs.modalai.com/camera-video/low-latency-video-streaming/#camera-pipeline-latency-in-different-operating-modes). This means that the difference of the center of exposure between the first and last image row is 4ms. Considering the information above, 4ms can seem a lot, but keep in mind that is the time delay across the whole image. depending on the size of features, the rolling shutter effect across a smaller image area will be smaller. Using the height of 1080, we can compute the time offset for each line, 4ms / 1080 ~ 4us. Depending on the size of features that are being tracked, the rolling shutter may not create a lot of local skew. Additionally, the camera timing is deterministic, so it is possible to calculate the time offset of the center of exposure of each line (with respect to the first line). If you want to provide some more details on type of perception, I could provide more guidance. Unfortunately, right now, we do not have a color global shutter camera option. Alex