Bitcraze Forums

Ah wow, i'm sorry.
Because we were working with the lighthouse position system all the time in my head the LPS was referring to Lighthouse positioning system instead of Loco positioning system.

We are sticking with the crossbeams for now because our time is running but thanks a lot for the help!

yes, the estimationmethod i changed in the lighthouse_core.c file just changes the "sweep angle"-method to the "crossing beam" method.(https://github.com/bitcraze/crazyflie-firmware/blob/b7f560e6c2ffc9eb2138706e5a203700f7c8fc3e/docs/functional-areas/lighthouse_overview.md#positio...

Hi,

i just changed the estimation method in the lighthouse_core.c file of the firmware to 0 (using the crossing beams method).
Did around 40 testflights with two different drones and had no problems.

I will do some more test flights with multiple drones but it seems to me that it's the right path.

Hey, thanks for the reply! Yes, it does actually increase the offset distance. I added a go_to(-0.5,0) as the first command of the with-statement. I was looking through the docs and will try some methods to narrow the problem down: - changing the lighthouse position method to "crossing beam&quo...

Hello, i'm having trouble with the standard go_to command of the python library. In 20-40% of the tries a simple go_to(1,0,0.8) is resulting in this behaviour: https://youtu.be/FbTOqZQXPFY Setup is one drone in a LPSv1 with two stations. Code is the standard position_commander_demo.py where the simp...