@Nitin-Varma-Vegesna If you are just flying in manual or altitude hold modes then those shouldn't be an issue.

@Zachary-Lowell-0 Got it, I will try that out and will let you know if I have any more questions. Thanks for your help!

@Alex-Kushleyev
Thank you very much for your reply!

We bought the USB C adapter from Flir and followed your guide to enable MIPI. Now it works and I can get the video from the Boson over MIPI.

Thanks for your help!

@Nitin-Varma-Vegesna said in GPS for Starling2:

I got the compass sensor missing error for my Starling2, and I think it's an issue with the GPS. I want to buy a new GPS for the Starling2 ASAP, and I didn't see it on the products on the website. Is there a way for me to do that?

1 Reply Last reply a day ago Reply

@Nitin-Varma-Vegesna https://store.3dr.com/mini-gps-ublox-max-m10s/ <-- this is the gps that comes default with the starlings.

@remill libusb doesn't use cmake. It uses autogen.sh, configure, make, etc. These are standard Linux build tools. If you enter a query such as "How do I build libusb on Linux?" into Google and check AI mode it will provide you with all the steps.

@mkriesel , a few tips..

I suspect FETtec ESC is using a pretty accurate xtal or accurate RC oscillator, so you should not need to calibrate the ESC You can check the current calibration by using QGC to control the individual motors to see at which command they start up and make sure that is very close to the same (typically around 1000us or a bit more) Additionally, you can spin up each motor with propeller at certain % power, lets say 20% or 30% and using an optical tachometer (RPM meter) to measure the speed of each motor Those are some sanity checks you can do without being able to calibrate and without having any ESC telemetry.

Regarding the ESC PWM range, the procedure is documented for VOXL2 IO board : https://docs.modalai.com/voxl2-io-user-guide/#how-to-perform-esc-calibration -- please go over that and make sure you did it correctly.
Alex

Documentation for the flight deck platform can be found here: https://docs.modalai.com/voxl2-flight-deck/.

The user guide section provides links to using obstacle avoidance and VIO, that page is here[https://docs.modalai.com/voxl2-flight-deck-userguide-software/](https://docs.modalai.com/voxl2-flight-deck-userguide-software/].

The camera setup for the setup is here https://docs.modalai.com/voxl2-flight-deck-userguide-connections/.

The documentation on this website should also be helpful, there are specific sections about the sdk that may be helpful, including the voxl sdk camera server and other features.

Hope this helps,
Robbie

@leandro I found M0188 here: https://docs.modalai.com/M0188/#3d-drawings

@jonathankampia ,

Here is something i tried, you can try as well. You are right, there is a background service that may be taking over, I think i found how to disable it:

systemctl disable QCMAP_ConnectionManagerd systemctl disable qti_pppd systemctl disable qtid rm /lib/systemd/system/multi-user.target.wants/QCMAP_ConnectionManagerd.service rm /lib/systemd/system/multi-user.target.wants/qti_pppd.service rm /lib/systemd/system/multi-user.target.wants/qtid.service #edit: instead of disabling the above 3 services and removing the entries from `multi-user.target.wants`, it seems you can do the following: systemctl mask QCMAP_ConnectionManagerd systemctl mask qti_pppd systemctl mask qtid # you may want to disable dhcpcd as well, but i dont think that is strictly necessary: systemctl disable dhcpcd

Now, set up static connection:

#create a new network interface file vi /etc/systemd/network/10-eth0.network [Match] Name=eth0 [Network] Address=192.168.xx.xx/24 Gateway=192.168.xx.1 DNS=8.8.8.8 1.1.1.1

enable networkd

systemctl enable systemd-networkd

Then reboot voxl2...

I think if dhcpcd is enabled, it may first take over the interface, but then networkd takes it back.. For example, here is the log from networkd when dhcpcd is enabled:

... Dec 10 06:01:00 m0054 systemd-networkd[1126]: dummy0: Gained carrier Dec 10 06:01:00 m0054 systemd-networkd[1126]: dummy0: Gained IPv6LL Dec 10 06:01:11 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:02:13 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:02:13 m0054 systemd-networkd[1126]: eth0: Configured Dec 10 06:02:13 m0054 systemd-networkd[1126]: docker0: Link UP Dec 10 06:02:21 m0054 systemd-networkd[1126]: eth0: Lost carrier Dec 10 06:02:36 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Configured

and the log with dhcpcd disabled:

... Dec 10 06:02:13 m0054 systemd-networkd[1126]: bond0: Link is not managed by us Dec 10 06:02:13 m0054 systemd-networkd[1126]: sit0: Link is not managed by us Dec 10 06:02:14 m0054 systemd-networkd[1126]: eth0: Link UP Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:09:56 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:09:56 m0054 systemd-networkd[1126]: eth0: Configured Dec 10 06:09:56 m0054 systemd-networkd[1126]: docker0: Link UP

Can you try and see if that solves your issue?

Alex

I did some additional testing and was able to narrow things down a bit. After reconfiguring the WiFi as a SoftAP using voxl-wifi and then rebooting the VOXL, the network now shows up consistently again. So the broadcast issue seems to be resolved for the moment. However, the core problem remains: I still can’t actually connect to the AP — the connection attempt starts, prompts for the password, and then fails just like before.

If anyone has ideas on what else I could check or has seen similar behavior with this setup, I’d really appreciate the help.