On e again, you’re not listening to the answers you’re being given.
But to answer your question, the 10 seconds comes from the BLYNK_HEARTBEAT setting, which defaults to 10 seconds. You can change it by adding this line to your sketch…
#define BLYNK_HEARTBEAT xx // replace xx with the time in seconds.
OK… then either pursue this direction of modifying Blynk’s essential way of working (probably best with a simple test sketch, timers, etc.), or just fix that which sounds like the real issue… reign in your motors, and/or fix your WiFi
I think that what @Gunner was saying is that basically you have two options:
Option 1
Ignore the advice about fixing the underlying issues in your code, and instead are focus on trying to change the way that Blynk works to get around your coding issues.
Option 2
Listen to the advice you’re being given and fix your code problems.
If you’re going for option 1 then these experiments would be best conducted with a simplified sketch, so that you can best observe the impact of your ‘hacks’ of Blynk’s underlying functionality.
Either way, I’m stepping back from this debate, as you clearly don’t seem interested in the advice that I’ve provided.
Feel free to ask as many questions as you like, although my advice would be not to ask questions if you aren’t going to listen to the advice that forum members provide in response.