Topics created by m1baldwin

Hi @m1baldwin , are you using VOXL1 and VOXL2 ?

@m1baldwin With that platform release PX4 crashing causes ADB to crash as well, so that's one possibility. (This is fixed in future releases)

If it was a camera issue, that would be low level device tree code causing the crash

@tom That qdl reset did the trick, thanks!

Thanks! this is helpful confirmation

With regards to camera server, the "types" that it takes define behavior more than actual reading of drivers. The underlying camera layer will deal with the actual querying of the sensor and using those drivers that you've posted, and the type in the camera server config file will define a few behaviors like resolutions, image format, allowable streams, etc, some of which are customizable in the config file.

The imx214 type in there is named as such because initially that was the only imx sensor that we used, and its behavior is applicable to (at the very least that we've tested) the 377 and 412 as well; and would likely work on some of the others that you've mentioned.

@Chad-Sweet Thanks; any comment on what temperatures you or the team have seen trying to stream higher than vga resolution through voxl-streamer? Interested if you are seeing the same using 1080p or the full resolution of the sensor, for example.

Would love a solution to this too, having the same problem

No, we don't have an EU marking label.

@Chad-Sweet Great, very exciting!

@Vinny Thanks, this helps a lot!

@Steve-Turner Great, thanks! As luck would have it skycharge is already on our short list; I'll look at the page and see what I learn

@m1baldwin I think things will work as you expect if you first run voxl-send_command hires stop_ae. You may also need an update to the voxl-camera-server code, refer to this post.

The best place to start would be try to reinstall the Flight Core firmware. It sounds like the VOXL side of things is OK.

The most common failure mode for Flight Core is plugging USB into the R/C port. Any chance that happened?

@Adrian-Hidalgo Appreciate the response, thank you!

I had the same issue. Updating the voxl_mpa_to_ros package resolved it for me:

opkg update opkg install voxl-nodes

We have not done a direct comparison. In general though, all of those systems typically achieve 1-1.5% drift over distance which is something we see pretty consistently with the qvio-server