I understand that. But maybe you can remove this limitation for the local server?
I assume we may need to do it by ourselves, and as the Blynk library is open source (Thanks to Blynk Team!) it shouldnāt be that hard for some skilled coder (well, Iām not the one!). Perhaps comparing files in 0.4.8 with affected (new library) ??
of course. But we need a hint of the author where to look for it, not to waste time
Somewhere near Blynk.virtualwrite()
?? No time for now, but as a challenge - I may look at sources. Who knowsā¦
Quick search, probably a blind shot, butā¦ What will happen, IF we define following:
#define BLYNK_MSG_LIMIT 0
??? Anybody dare to try?
Really no time for more
add: there is the following:
#if defined(BLYNK_MSG_LIMIT) && BLYNK_MSG_LIMIT > 0
and then some time countdowns. So probably it needs to be ZEROā¦ (orā¦Iām totally wrongā¦ probably :P)
So to confirmā¦ all I have done is add #define BLYNK_MSG_LIMIT 0
to one of my fast processing RGB sketchesā¦ and it seems to have less issues, allowing me to push the timer to 10ms (sending two Blynk commands each loop) without seeing āas muchā pausing in my running projectā¦ but still happens every so often (App just pauses for almost 2-3 seconds, then seems to play rapid catch up and carry on smoothly for another 30+ seconds or so)
I used to be able to drop the timer to 8msā¦ So, anything else I need to do to revoke the governor nanny oversight?
How exactly it pauses? Freezez? And how many commands do you send at the time?
Yesā¦ just stops all action on the Appā¦ then 2-3 seconds later it acts like it is on fast forward for perhaps a second then normal operation. The length of time for normal operation seems random. The sketch itself keeps running smoothly as I am also controlling a physical RGB with same loop and values.
2 commands each timed loop: both Blynk.setProperty()
One for the random LED on my matrix and one for a button on another tab that flashes rapidly like my physical LED.
As stated, it is not stalling out nearly as bad as before I changed the #define BLYNK_MSG_LIMIT 0
to zeroā¦ so at 10ms I am pushing a steady 200 Blynk commands a second (confirmed with a counter)ā¦ so perhaps I am just hitting the top limit for my setup?
Quite mesmerizing when it runs smoothly
and please make it available on YouTube as some people will not be able to watch in your local time. Thanks
thanks guys
I have been spending so much time testing stuff on my ESP32 (darn that thing is fast ) ā¦ so I needed to try this āfixā on an ESP8266 with a scaled down version of the vRGB matrix I am running on my ESP32 (and processing 200 Blynk commands a second).
However, I am NOT seeing any improvement? The best I can get before seeing void loop slowdown is 10 commands a second (1 Blynk.setProperty()
on a 100ms timer) ā¦ and this is with the CPU running at 160Mhz and half the background processes of the ESP32 sketch
@vshymanskyy is this BLYNK_MSG_LIMIT 0
the correct way to disable this throttling or not?
Yes, it is. You can always check if a particular piece of code gets compiled by inserting #error "Compiles"
directive there.
if it fails to compile - it means the code gets compiled. Then you can remove #error
OK, thanksā¦ maybe I am just getting spoiled with the speed of the ESP32
Yikesā¦ new coding tricks I need to understandā¦ I will try to figure it out.
Well, I canāt figure out the #error
syntax
However, I did discover that having #define BLYNK_MSG_LIMIT 0
load AFTER the libraries was the issueā¦ doh
Now you can all witness the flickerpower of this partially armed and almost fully operational battlā¦erā¦ testbench
Hi @vshymanskyy
Just checking if you still working on developing the webinar ? (in case I may have missed it )