-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How long a simple blynk.run() from examples complete? #32
Comments
Adding related to this issue is that using BlynkLib from other source and almost same terminal or any other example like the ones at https://github.com/vshymanskyy/blynk-library-python blynk.run() is as fast is it has only takes 0.1 secs each round. |
Hi kindmartin! For ESP32 due to memory limitations I suggest check such things:
Let's check these thing first and then continue investigation. |
Thanks antoUa for replying. to explain my self better I just was saying that using this v0.2.6 library even using examples the time consumptions for blynk.run() loops is about one minute. I tried all, using a mpy byte code lib, extract all comments, etc, overclocking the ESP32, etc. ALL. <M |
Kindmartin,
But if to measure real time of command response with timer clock it will be less that 1 sec Anyway i will try to investigate such strange situation with time displaying. |
I use same time import with the other lib, and blynk.run() just consume ~100ms, including timer.run() I have two codes. I m learning python so it is not any clean or optimized, full of global variables usages, etc so for that reason I was back to basic examples check. now im focus the other lib, that have other problem with text input widget updates messages from server to device. but I will like to help/ one coment, if I just use instead time.time() prints just prints like print('PRINTING NOW') I see those prints in the REPL console each minute, so no doubt blynk.run() do not pass fast to next command. |
I see the diff in imports |
Closed (no reply for a long time). But feel free to re-open |
Hi all there in this uPy community. I was debugging tons of code ending to test a simple example like terminal at ESP32, https://github.com/blynkkk/lib-python/blob/master/examples/esp32/02_terminal_cli.py.
I just uploaded that script only editing to have an idea of how long run() takes to other things in main loop. Im running at ESP32 standard 2020 FW version.
while True:
LoopStarts = time.time()
blynk.run()
LoopEnds = time.time()
delta = LoopEnds - LoopStarts
print('---->> Delta RunLoop :', delta)
here my results, with fast (0) / slow (~60+ secs) cicles.
All registered pins like this example v2 works in real time, but Im wondering what I m not doing well as we need more than run() timeslots !
Hints ?
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 14
---------->> Delta RunLoop : 64
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 65
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 63
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 65
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 63
---------->> Delta RunLoop : 0
---------->> Delta RunLoop : 65
The text was updated successfully, but these errors were encountered: