![]() But his problem was that the component's own TouchPress and/or TouchRelease event code would still be executed afterwards, probably going to a different page, which would prevent displaying the help text correctly. So, he thought that he'd use a TouchCap component to intercept the event chain before the component's own event code was executed, to decide if, in case the help mode was active, the help screen would be displayed. Next is the Yellow C.19 which says it is port C, bit 19. Red are differences, where the functionality has moved on Mega2560 compared to UNO. Green have the same function and position as the Arduino UNO R3. This denotes it is physically pin 101 on the IC. Inspired by Nicks UNO pinout I did a similar one for the Arduino Mega2560 R3. ![]() Next is The magenta block with 101 inside. The Mega2560 Pro Mini board has all the IOs of Arduino Mega2560 R3, following are the parameters. Since in his project, there are nearly 1000 components on several screens, reworking each single component's event code to decide if the event code should be executed or the help screen displayed, is definitively not an option. Lets start with your question of pins 44-46: Pin 44: given the yellow circle surrounding the pin, it denotes a high current pin that can source 15 ma, sink 9 ma. That means that after activating this help mode, the user would click on an arbitrary component and instead of executing the component's event code, a help screen with explanations would be displayed. The Arduino Mega 2560 is a microcontroller board based on the ATmega2560. What he wants to achieve is activating a "Help" mode on his Nextion project. In the Nextion user forums, a participant from Europe, let's call him M., asked an interesting question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |