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

@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

@awagner , I believe on VOXL2 Mini should be able to support any 4 cameras on the J6L, J6U, J7L, J7U (specifically the AR0144 (M0149) and IMX412 (M0107), which I assume you are using)

Can you please clarify the error that you are seeing? Is the issue the lack of correct sensormodule or something else? (you can check if correct sensormodules are present in /usr/lib/camera after configuring the cameras). As a reminder, the J6L, maps to slot 0, J6U, slot 1, J7L slot 2 and J7U slot 3.

Are you able to connect the 2 AR0144 cameras to J6 and J7?

What is your goal - how many of each cameras do you need to use? We can test it.

Alex

@LukeNow Correct I am just using it as a normal GPIO watching for an input signal. I'm also running SDK 1.6.3 if that helps. Thanks

@Jetson-Nano ,

In a case like this, if the ESC works and suddenly stops working, the resulting state is probably a hardware problem (possibly caused by software action or hardware damage). In this state, it is probably impossible to recover the ESC using software and remote diagnostics would be difficult and you would probably not be able to fix the ESC hardware anyway.

Do you have any additional information that could help us understand what happened and the frequency of occurrence? you mentioned two occurrences "recently" -- any more details? What motor/prop/battery was used and was there anything unusual that happened during the test? Do you have a px4 log from the flight? (you could share it privately if needed).

If you are able to ship two failed ESC boards back to us for investigation, i'll ask our team if we can send you new replacement(s).

Alex

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.

Hi @jameskuesel ,

Please check these threads:

https://forum.modalai.com/topic/5010/m0173-with-4-ar0144-tracking-cameras https://forum.modalai.com/topic/4491/ar0144-rgb-output-on-voxl2

Specifically, look for the post with these details:

OK, I was able to confirm this configuration: VOXL2 M0173 + 3x AR0144 + 1x IMX412 (C27 config) M0155 + 1x AR0144 plugged into J8 AR0144 i2c slave id change via resistor small camera driver modification for new slave id also verified the synchronization between the 4 AR0144

You will need to switch the CCI slave id of one of the AR0144 to avoid bus conflicts, as described in the posts, otherwise no issues.

Do you need all 4 AR0144 sync'ed to the same sync pulse (as normally is done in our dual AR0144 config) ? Please keep in mind that sync may not make sense if the 4 cameras are using different exposure values -- on AR0144 cameras, the sync pulse triggers Start of Exposure, so center of exposure could still be different in the "sync'ed" cameras if the exposure length is different. We can discuss more.

Alex

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

@Barry-Hammond https://docs.modalai.com/voxl-streamer/#how-to-stream-video-with-rtsp-on-voxl

Quality greatly depends on your LTE coverage and VPN performance. I recommend lowering the bitrate in /etc/modalai/voxl-streamer.conf until you're happy with the response rate.

Tailscale can add overhead as well and our recent LTE testing has involved hosting a custom WireGuard server.

@Michael-Hatton When you arm the drone it is in flight mode and the motors start to spin. It's that spinning of the motors that you don't want while plugged into a power supply. Only use your battery to actually spin the motors and fly.

@Jskim This is the repo we use for support of UVC cameras: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server. I don't think it will work directly with Seek cameras but you can try. In my experience each new camera requires a bit of integration work and updates to that code.