Topics created by K.Stute

Adding more cameras can definitely improve robustness, but synchronization and calibration become super important once you go beyond the default setup. Even small timestamp offsets between sensors can throw VIO off pretty badly. I’d also keep an eye on bandwidth and CPU usage because extra camera streams add up fast on embedded systems.

@Zachary-Lowell-0 @Moderator A really important question here is what if there are two drones publishing the same name FMU topics and you haven't set the domain id different for those drones for data sharing through your custom interfaces. PX4 ROS2 docs provide a way to change the namespace of the FMU topics to be published but MODAL AI docs mention no such thing? Is there a way to do that? As most of the starling systems are being used as a swarm platform this thing is really critical

@K-Stute here is the directory in voxl-dev px4-firmware: https://github.com/modalai/px4-firmware/blob/voxl-dev/src/modules/microdds_client/dds_topics.yaml

@K-Stute , sounds great! if it happens again, let us know, we can debug.

Alex

@Vinny Thanks for your quick reply.
I have no idea what caused this problem. After the first flight i noticed a certain smell that could have been caused by the capacitor transcending into the shadow realm - but that is the only time I remember anything odd happening to the chip.
Since the modem is used in combination with the voxl2 in a research project at my university I'm not the only one that had his hands on it. Thus i can not rule out that a device was connected backwards causing this whole mess.

Thank you for your time!

@K-Stute Running in a Docker is the most straightforward way to do this. We are planning an update to Ubuntu 20.04 in the future but the timeline on that isn't certain yet.