@svempati said in No detections when running custom YOLOv8 model on voxl-tflite-server:

WARNING: Unknown model type provided! Defaulting post-process to object detection.

@svempati I will try recreating this issue today and get back to you!

@Pelle-Bredegg-Hermansen
Hi Pelle,
I emailed you the schematic review report for your considerations, just wanted to post here this task is completed.

Keep us posted!
Thanks!

Hi @Richa
We have not provided our pinouts for this and have no plans to.
For our Micro Coax direct CMOS based sensors, you need to use our products end-to-end to guarantee functionality.

Hope this helps clarify.

@cbay , you could actually test two leptons by disabling i2c port for one (or both) of them. Lepton starts up streaming data by default via SPI, so you can get frames from it without any communication.

In order to do that, you would need to run two instances of voxl-lepton-server and the second instance would have to be modified to read from a different config file and to not kill the existing voxl-lepton-server process (and probably name itself differently, so that the first server does not kill the second during start-up).

If this all works, then in order to actually test two leptons with i2c communication (which we use the set the FFC mode depending on the flight mode and also reset the sensor if it gets into a weird state while streaming), the lepton server functionality would probably need to be added to a C++ class so that multiple instances could be run from the same process. The reason is that there needs to be a single point where the i2c switcher is set to one or the other lepton, right before communicating to one of the leptons (without the other server / thread creating a race condition and trying to do communicate right at the same time)..

I'd have to think about the fastest way of doing this, but at least you should be able to test two leptons with second not using i2c with very minimal changes.

Here is the source code for the voxl-lepton-server in case you did not already find it: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-lepton-server/-/blob/master/src/

Alex

@brandon You'll need to load SDK v1.6.x to get it.

@Morten-Nissov you have the kernel variant 2.0.2, which works with M0188 and M0195 camera adapters, but not the adapters you are using. Please update your kernel to use 2.0.0, there are details in a recent question here : https://forum.modalai.com/topic/4975/hardware-configuration-for-2-m0014-tracking-1-m0169-pmd-tof-1-m0024-hires/7

Alex

@Sarika-Sharma ,

the screen shot you pasted shows that the second tracking camera has not been found. But above, you mentioned that it is detected. Can you check that?

You can also see which cameras are detected using voxl-camera-server -l to list the cameras and please make sure all 4 cameras are found.

Meanwhile, i wlll test this configuration and get back to you soon.

Alex

Hi @cbay ,

I checked with the team - we have not tested using the second lepton plugged into either M0188 or M0195.

The voxl-lepton-server is not set up to handle two sensors. It would have to be the same process managing both sensors because the i2c communication to both would happen over the same i2c bus and the i2c switcher would need to control which sensor is actually being communicated with via i2c.

We have checked that we can control the i2c switcher, but that's about it. We have not needed to use the second lepton (yet).

If you wanted to try it, that would be a risk, but here are the steps:

• plug in and test lepton in primary port
• unplug the primary lepton and plug it into secondary port
• update the voxl-lepton-server to control the i2c switcher to switch the i2c path to second port
• test the lepton plugged into second port
• *** main task *** update the voxl-lepton-server to manage two lepton sensors, switching the i2c communication path, when it is appropriate
  • please note that during normal operation, the i2c communication with lepton is not needed, i believe we only use it if we need to reset the sensor

Alex

Hi @Jetson-Nano,

Boson is supported on VOXL2 and VOXL2 mini. See info here : https://docs.modalai.com/M0153/#hardware-requirements

You will need either M0162 or M0181 adapter for plugging Boson into VOXL2 as well as M0201 (which plugs into the back of Boson and provides the coax connector.

What you probably want is the following connection:

[Boson] + [M0201] + [coax cable] + [M0181 J1] -> [VOXL2 J8]

We don't have an out-of-the-box solution for tracking features using Boson. You would need to worry about FFC interrupting the image stream (FFC can be disabled or configured not to run very frequently).

I will find some documentation regarding the feature tracker question.

Alex

@Dronodev
ov_overlay is now available under the VIO tab in voxl-portal. Please make sure to update your system to the latest released SDK.