This error happens if you continuously send a freedrive _mode() command. The fix for me was to send the command and then basically go into a loop with a wait inside until I want to exit the command or stop the program.
This is an example how it would work. You just start the Freedrive mode and then make a query for the User which says “Freedrive is now active!” or something like this. When the User now presses the “Yes”-button the if-query ends the freedrive mode with “end_freedrive_mode()”
The freedrive is active till you press the button, the programs basiclly waits for your input.
Hi Jorge and Matthias
Thanks for the response, nice to know that the error can be mediated.
I will make the changes suggested, but would still consider it a bug because of the change in behavior between versions, it would at least be nice with a better error popup…