Hi,

The drone visualized by the 3-axis in the 3D map view goes away intermittently. However the dot in 2D can be still clearly seen and moving. If I restart voxl-portal, I can again see the drone in 3D. Any idea how to fix it?

On the related note, where are the html files of the portal located in the docker/voxl board? Suppose I want to change the color etc., which html/css files should I change?

Many thanks. Warm regards,
Arjun

@Alex-Gardner hi alex! How to go back to the default configuration? We didn’t change actually, not sure why the configuration is looking for different cameras. Many thanks!

@Anubhav smells like a version mismatch problem. Can you also run Voxl-mapper with -d for more info?

@Nishkala please write a more meaningful question so that people on this forum can help you. What are the symptoms? Why do you think it is bricked? What all did you try?

@darwin-keem you can save the map from the web portal. It gets saved on the board at a specific location. You can then copy it and render it in your software.

@Jeff-Delaune try screen

@Matthew-Booker thank you!

@Alex-Gardner anyone? Thanks in advance for your answer.

Hi all! I wanted to confirm if the following was true:

1. The ToF data is used for collision avoidance feature
2. The downward facing cameras a used for apriltag localization and for tracking features on the ground for VIO.

If true, why are we not using also the ToF for the localization and VIO? Another related question is can we have vertical apriltags (like on walls) and also re-localize based on them?

Many thanks in advance.

Hi @ahmed-mustahid : I am no expert, but I too get that warning sometimes but the voxl-mapper still works and generates a valid scene. I thought it is just when the camera is blocked or it doesn't have enough features or something like that it displays that warning. I am also curious to learn from the voxl team what this warning means.