@RyanH ,

Sometimes there is small pieces of random magnetic debris that gets stuck in the motor.

First, you could try using compressed air to clear out the motor.

Additionally, It could help to spin the motor up and down using voxl-esc command line tools a few times to clear it out (without prop is best, just for safety). Spinning the motor without prop a bunch of times could get the debris dislodged and actually broken up by the moving motor parts, so that the debris is no longer large enough to cause a problem. Reversing motor spin using voxl-esc test tools can help dislodge the debris (you can commend negative power/rpm).

You can find useful info regarding motor testing here : https://docs.modalai.com/voxl-escs/faq/

Alex

@restore , a few more things:

you should set the auto exposure to lme_msv, which is the non-isp option, since we would not be using isp in this case before saving the raw bayer, start the misp output stream, so that AE can actually process, otherwise the exposure will be stuck in default value -- the bayer stream does not trigger AE to process.

Alex

The Device ID continues to increase.

We are using a webcam with a built-in SD card.
We switch between SD card mode and Webcam mode by pressing a button.
When power is supplied to the camera, SD card mode is set by default, and pressing the button switches it to Webcam mode.
The DEVICE ID number increases every time the camera is connected.

Thank you.
Kim

@cbay , yes this should work.

Whenever you add cameras of the same type, you should always check for possible I2C (CCI) conflicts. If you look here https://docs.modalai.com/M0188/#image-sensor-interfaces , the sensor IDs 0,2,3,6 (which is what you use) use unique CCI buses 0-3, so that is all good.

If you used ID 1, it would conflict with with another AR0144 on ID6 (both use CCI1)

One last thing to check is the sensor sync.

if you see fsin in the configuration of the sensor (and name of the sensormodule in /usr/lib/camera/), it means it is set up as a sync slave currently you have the IDs 0 and 6 set up as sync slaves, but ID 2 and 3 as free-running

There are two issues enabling sync'ed drivers for AR0144 in ID 2 and 3:

the driver is provided only for ID2 in : /usr/share/modalai/chi-cdk/ar0144-fsin/ - this is easy to fix ID1 and ID3 on M0188 do not have the sync line connected to the camera connector this is easy to fix by installing a 0-ohm resistor, which is DNI by default.

Depending on your requirements for VIO (which VIO are you using?), you may or may not need the cameras synchronized.

Please let me know your requirements and we can go from there..

Alex

@Alex-Kushleyev Hi Alex,

Thanks for your response.

To answer your question - the ESC does not appear to be booting at all.

I tested the ESC independently:

Connected battery directly to ESC (no VOXL connected) There are no motor tones and no visible LED activity

Additionally:

voxl-esc-scan.py does not detect any ESCs at any baud rate UART debug shows TX packets being sent but no valid RX response SLPI reports “Bus 12 not initialized”

Since the ESC does not produce any startup tones even when powered directly, it seems the ESC MCU is not booting.

Could this indicate a hardware failure of the ESC logic section?

Please let me know if you would still recommend testing via USB-to-serial, or if this is sufficient to consider the ESC faulty.

Thanks,
Koti.

@Michael-Soul , it is EAR99

Hello @adam , please see the following post regarding GPS signal quality on Starling 2 and Starling 2 Max : https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines

There is no voxl-gps service - voxl-px4 handles the GPS functionality, so as long as that is running, the GPS module should be active. Please go through the documentation linked above, there are some mitigation steps that are relatively easy to implement.

We apologize for the inconvenience, but enabling usable GPS on Starling 2 will require some tweaks.

Alex

@wilkinsaf

I did the following and was able to get it

installed arducopter 4.7 disabled serial2_option for mavlink forward configured compass configured acceleromter turned off GPS_AUTO_CONFIG set SERIAL3_BAUD to 115200

https://www.loom.com/share/b96c3edd2286477ea294ddbd262dc31e

@fhaltmayer , it looks like there maybe something missing from /usr/lib/camera/, as the camera is detected by the i2c probe but not accepted by the system.

Can you please let me know how exactly the camera is connected (to camera slot/id 2, it seems) and also list all the contents of /usr/lib/camera/.

Alex

@ktrieu , you can find the STEP file for the M0166 camera module here : https://docs.modalai.com/pcb-catalog/

@Nikos-Mavr I have an extra ac1300 to use that lsusb recognizes but I don't think the driver is implemented. Ac600 Antenna might be malfunctioning after all because even if it lights up on other pcs and identifies WiFis it cannot connect. Is there a way to implement a driver for ac1300?

@austin-c , The GPS driver is built for SLPI as well as APPS PROC, so you could connect it to a apps-proc UART and start the driver on the apps proc side of PX4.

This was done on RB5 : https://docs.modalai.com/Qualcomm-Flight-RB5-linux-user-guide/

https://docs.modalai.com/voxl2-linux-user-guide/

Regarding magnetometer, just like with the GPS driver, you should be able to enable the mag driver to build for apps proc. Since the apps proc i2c uses standard posix interface, it should just work. However, i don't think we have ever tried it.

Alex

@MikeR Does your commando 8 have an orq ghost transmitter module connected to it? If it doesn't then it is likely using ELRS which is not compatible with a ghost receiver.

You'd need a orqa transmitter like this one: https://shop.orqafpv.com/products/orqa-orqa-fpv-ctrl-radio-controller

Maybe your other drone had an ELRS receiver on it?