@Dan-Jennings I'm also guessing that the driver may not be detecting the hardware so is not able to get the data for the battery_status. Have you tried swapping some other hardware to see if the problem is associated with a particular unit?

@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

@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

@Jskim , you should check dmesg to see maybe there are some warnings. Perhaps the device is not de-initialized properly (how are you powering it off?) and next time the OS allocates a new Device ID.

Either way, using udev rule should help resolve the issue, however make sure there is no resource leak as a result of the device on/off. Also, if you keep turning the device on/off, does the device ID increment indefinitely?

Alex

@Alex-Kushleyev Thank you for the hint. We have fixed the issue by changing the resolution to 2704x1540 in the voxl-camera-server.conf. Now, the actual DFOV is 150°.

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/

@syamala-kotireddy ,

If your M0129 ESC only has a label that says M0129, it most likely means it is M012-3. The only difference between -3 and -6 is that -6 is rated for 6S battery voltage (which is irrelevant for Starling 2).

Was the ESC working? How did it get into non-working state?

Please make sure PX4 is not running before you use the voxl-esc tools : systemctl stop voxl-px4. You should reboot, disable voxl-px4 and try to use voxl-esc tools directly from /usr/share/modalai/voxl-esc/

In order to test if the ESC itself is working, the best way to connect it directly to a Linux PC using a serial-to-usb adapter and use voxl-esc to scan, test, etc. You can make your own adapter or purchase one here.

Also, double check if the status of ESC LEDs when you turn on the power. Additionally, does the ESC make motor sounds? See additional debugging information here : https://docs.modalai.com/voxl-escs/faq/

Alex

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

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

@aheyne , please send us a message via contact form. We don't sell this part separately as a product, but will help you with a replacement.

You will need the M0177 flex cable (as the print states on the cable).

https://www.modalai.com/pages/contact-us

Alex

@fhaltmayer , unfortunately, we do not have any updates at this time. It looks like we may never release Ubuntu 20.04 for VOXL2 because it is a LOT of work to switch to a new major Ubuntu release and test + maintain everything. Additionally, even Ubuntu 20.04 is already relatively old, so we are trying to focus our efforts on more forward-looking software development with larger impact.

Alex