Bitcraze Forums

Ah, thanks, it makes much more sense now.

P.S. Just checked the latest version and the behavior is very similar. It also appears to be about the same issue as viewtopic.php?f=20&t=4442.

I did testing in this branch and the behavior is very similar (perhaps worse?). What I've noticed upon further inspection is that it doesn't require me to use the position hold. As soon as I start flying the drone (apply thrust) the tracking values explode and become useless. They work fine if I mov...

You are right. I had made that typo. What confused me in this is the series of events. I had made a typo writing radio://80/00/2M which returned that no radio is found. So I realized the error and moved the 80 to the other side, but must have made the typo. However, since the error I got now was dif...

Today when I tried to run get_bs_geometry.py script for LH tracking I got the following error: Connecting to radio://00/08/2M Connection to radio://00/08/2M failed: Too many packets lost Traceback (most recent call last): File "tools/lighthouse/get_bs_geometry.py", line 333, in <module> wi...

It happens where tracking was good earlier. In every case where it happened the drone was still within clear line of sight to both base stations and if I grabbed the drone in my hands and put it in those places manually it showed proper coordinates in my tests earlier (I can retest tho just in case).

When I calibrate the LH base stations, it works consistently. Also, I can have the drone on and connected to the CFC and it'll read correct position. However, after I fly in the assisted flight mode for a little moment, it's positioning starts breaking, the drone starts quickly drifting upwards. I h...

Hey, The current method to configure origin position in a LH setup space using a drone is to run a python script that communicates to drone via radio and either just returns base station coordinates that can be written into firmware, or by using --write argument the origin can be temporarily stored ...

thanks! this line in the console indeed indicates that the firmware does not have that define. LHFL: No Lighthouse support in FW, deck not initialized Have you made sure to do a proper clean before as well before the build? make clean make all make cload If you add a define to the makefile, the pre...

1) Oke, this is indeed a problem. What you are supposed to see is the following sequence: First the red and blue led are on for about 2 seconds then a orange led for a few seconds (which is the flashing of the FPGA firmware to the lighthouse system) and then the blue LED is the only one on See this...