Bitcraze Forums

I am not from bitcraze but recommend running the propeller test (button in console tab) and posting results

thanks GPT3 very insightful

I am not an expert, but regarding section 1 , this question has been answered few times already, search for "push demo" in the search box regarding section 2, I can say in the function SetHoverSetpoint there is a priority parameter. I think the remote control commands are sent in priority ...

suggest connecting via USB just to make sure that works.

this is good information to have in the documentation. maximum recommended bytes or blocks per second. Also on USB (I assume it is higher)

first, you are using PARAM_ADD where LOG_ADD should be
second, you can use log variables to internally transfer data between tasks, also RTOS queues are used
I didn't use pointers so will be also interested to hear if this is supposed to work

I used very similar hardware successfully. make sure you put the camera where it won't imbalance the drone too much.
yes you need the video receiver and it can work independently from the crazyradio without issues.

I think you need to flip something in the IMU too

did you compile the firmware using DDECK_FORCE flag to force it to compile your virtual deck? see the tutorials if not.
also, I recommend posting the output from the console (self test results)

unrelated to lighthouse issues, I also found that in some crazyflies the motor PWM values differ consistently while hovering. In many cases two motors will have higher values and the other two will have lower values. you can use motors.m1 .. motors.m4 log variables to test this while hovering. Repla...