Search found 4 matches

by chronob
Wed May 27, 2020 12:16 pm
Forum: Developer Discussions
Topic: go_to command python unexpected trajectory
Replies: 7
Views: 220

Re: go_to command python unexpected trajectory

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#position-estimation-methods...
by chronob
Wed May 27, 2020 9:07 am
Forum: Developer Discussions
Topic: go_to command python unexpected trajectory
Replies: 7
Views: 220

Re: go_to command python unexpected trajectory

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.
by chronob
Wed May 27, 2020 7:11 am
Forum: Developer Discussions
Topic: go_to command python unexpected trajectory
Replies: 7
Views: 220

Re: go_to command python unexpected trajectory

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" (https:...
by chronob
Fri May 22, 2020 8:52 am
Forum: Developer Discussions
Topic: go_to command python unexpected trajectory
Replies: 7
Views: 220

go_to command python unexpected trajectory

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...