I have a project on the go that displays 64 values on the screen, I have reduced the send rate of the data so that touch events are not ignored, but I have a problem; while the values are changing a page change event caused by a touch is often lost by the mcu, my program still tries to send data to the screen and gets lots of recvRetCommandFinished err back.
I have written a watchdog to cause a reset of the micro if it counts more than 5 of these errors, but this is a bit of a mess, ideally on error it would instead return the correct page number and continue. Has anyone else had any experience of this ?
grep the Iteadlib source for recvRetCommandFinished err
I would think there is little reason to reset a micro on any count
but a successful non-err would or should reset the watchdog.
Calculating an estimate, or even measuring what actual byte usage is on serial.
- such a long serial debug message ~ 25 bytes? still takes sequential time
unless your MCU is multi-threaded multi-cored and multitasking
Changing a page
Nextion dumps the current page from mem to load new loading page.
Program purposefully with this in mind
Page 0x66 Return Data
will tell you what page is current
If the components you are sending to aren't on the current page
it will make less sense to send to a non active page ... ?
Unless of course you create a scenario to accommodate such
If sending 64 values at once, most likely leading to buffer overloads