Bitcraze Forums

Thank you for the help. I downloaded the original repos and tried again, now it works. One of the problems was that one of the PARAMs had a too long name. Turns out that this: PARAM_ADD(PARAM_FLOAT, enableAltHoldTargetInput , &enableAltHoldTargetInput) Does not work, however if you shorten the n...

Okay, so now I somehow made it work. It must have been errors in my previous code that made the bug. Jeeesus Ive spent several hours trying to figure that out.

Hi and thank you for your reply. I am not sure I made myself completly clear. So Ive made an example. I went to firmware/modules/src/stabilizer.c and added the following static float teste = 0.0; LOG_GROUP_START(test) LOG_ADD(LOG_FLOAT, test, &teste) LOG_GROUP_STOP(test) PARAM_GROUP_START(test) ...

Im using the 0.5VM, it is possible that the poor performance was due to some changes I made to the code. And therefore was fixed when I changed back to the "original" client and firmware. I will try again later today with the new firmware and give you an update on how that works out.

let me rephrase a bit. How do I use param.set_value("complete_name", value) ? If I have a paramtere who's value is a float, how do I set it when set_value demands a string? I know that it should be possible since I can do it using the GUI! And yes, I have tried to just write the value as a...

Hi again. I am really not sure lets hope one of the mods or more experienced users gets involved in this thread. I am not very well-versed in programming and Im not familiar with the headless client, Ive been writing my programs/functions importing cflib libraries and sending thrust using the alread...

Okay, very cool. But the positionHold mode is new too me, did you make that one too? Unfortunatly when I download your firmware+client it all ran very very slow. There was a delay of perhaps 10s between moving the cf and actually seeing changes in pitch/roll and so on in the client. So I had to chan...

This problem has been discussed, it turns out that you have to constantly, 100Hz, have to set the thrust to 32767 to maintain a constant target altitude. This is because in althold-mode you are able to either decrease or increase the target altitude by increasing or decreasing thrust.

Hi I am having trouble understanding how the Param's work. The specific problem is related to the altitude_hold mode, I wanna be able to set the target_altitude myself, via the Python code. I though the easiest way to do this was to add the variable on the PARAM-list and then access it like: cf.para...

Would you care to explain what CareFree-mode is and how you enable and use it? From what I can understand you've implemented a position-hold, and I am very eager to see how well this works :D Also I notice that in commander.py where youve updated a whole bit, much of the new functionality is written...