@Michael-Hatton Yes, you need to have a separate battery charger. I'll see if I can get a recommendation from the team on a good charger to use. I use a Hota D6 Pro, personally.

@jon You may want to update to the latest release. There have been some updates to voxl-reset-slpi. How do you normally restart voxl-px4? Are you running from the command line or as a service?

Hi @gerard
Do you not get these LEDs either?
https://docs.modalai.com/microhard-usb-carrier/

Without a Microhard module installed, the 5V LED and the USB Hub LEDs should all still illuminate.
When the MH is properly configured, then you should start to see the other Activity and RSSI/Status LEDS. Those not appearing indicate the module is not configured, not seated, or in error.
Images will help.
Thanks!

@bschulzhf Sort of. The timestamp from voxl-vision-hub and voxl-mavlink-server is just the Linux processor monotonic time. But because voxl-mavlink-server has been responding to the time sync protocol messages from PX4 it allows PX4 itself to update the timestamp to PX4 time when it comes in.

Hi @gerard
Can you share a photo of the setup, ideally with the working unit next to the problematic one?

A couple of possible causes come to mind, but we'd need a bit more information to narrow it down:

The modem module may not be fully seated in the socket. These modules can be difficult to install correctly, and if the thermal pad underneath shifted or lifted slightly during installation, it can prevent proper seating.
The socket may be cracked. It's fairly easy to damage the socket during module removal, especially with Microhard modules, which can lead to intermittent electrical connections.

A side-by-side photo of the good and bad units would be very helpful for troubleshooting.
Thanks!

@wilkinsaf You can disable compass with SYS_HAS_MAG = 0 and EKF2_MAG_TYPE = 5. But if you enable it and it isn't healthy you won't be able to arm. Power compensation may work, it depends on your particular drone model and use case.

@jon That looks like the DSP portion of PX4 didn't exit completely / cleanly from the previous run. What version of the SDK are you running?

@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

@JB1 I'll look into your questions. There is no RTC on VOXL2.

@jon And you can find a lot of detailed information about the agent, including the start options, here: https://docs.px4.io/main/en/middleware/uxrce_dds