<![CDATA[[UIFlow] Capacitive Touch Blocks.]]>This may sound stupid but......
Can we have some simple blocks in UIFlow for Setting pins a Capacitive touch.
I think Separate Cap Touch pins would be easer for new young and inexperienced programmers.

]]>https://community.m5stack.com/topic/2813/uiflow-capacitive-touch-blocksRSS for NodeTue, 28 Apr 2026 23:21:52 GMTSun, 24 Jan 2021 12:17:00 GMT60<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Fri, 29 Jan 2021 23:41:52 GMT]]>@felmue
Ok thanks for the info 😀

]]>https://community.m5stack.com/post/12172https://community.m5stack.com/post/12172Fri, 29 Jan 2021 23:41:52 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Fri, 29 Jan 2021 15:58:46 GMT]]>@world101 said in [UIFlow] Capacitive Touch Blocks.:

Do you know if port A on the M5StickC/C+ has the same I2C assignment, or is it just standard GPIO?

M5StickC and M5StickC Plus do not have that I2C assignment, eg. no pull-up resistor. I've checked the schematics and did some measurements. (BTW: same is true for M5AtomLite, M5AtomMatrix and M5CoreInk.)

FWIKT M5Core2 is the only 'black' sheep in that regard.

Thanks
Felix

]]>https://community.m5stack.com/post/12160https://community.m5stack.com/post/12160Fri, 29 Jan 2021 15:58:46 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Fri, 29 Jan 2021 14:19:54 GMT]]>@felmue said in [UIFlow] Capacitive Touch Blocks.:

In addition GPIO32 and GPIO33 (normally used for I2C) have pull-up resistors (5.1k each).

Ah that's probably the reason. If pins 32 and 33 are assigned for I2C, that is why I'm getting a touchpad error conflict.

I wonder why it works on the M5StickC/C+. Do you know if port A on the M5StickC/C+ has the same I2C assignment, or is it just standard GPIO?

]]>https://community.m5stack.com/post/12158https://community.m5stack.com/post/12158Fri, 29 Jan 2021 14:19:54 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Fri, 29 Jan 2021 12:40:24 GMT]]>Hello @world101

M5Core2 has some protection circuit on each externally used GPIO line (47R series resistor and some diodes). In addition GPIO32 and GPIO33 (normally used for I2C) have pull-up resistors (5.1k each).

Thanks
Felix

]]>https://community.m5stack.com/post/12155https://community.m5stack.com/post/12155Fri, 29 Jan 2021 12:40:24 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Fri, 29 Jan 2021 11:57:15 GMT]]>@ajb2k3, @Zontex,
I created some basic custom Touchpad blocks for capacitive touch using Block-Maker. They work on the Core (black or grey), M5StickC/C+, and M5Atom Lite/Matrix. I could not get it to work on the Core2 PortA due to some internal conflict on pins 32 and 33 that I haven’t figured out yet. If you remove the bottom micro module, it might work on the Core2 by accessing the Mbus pin 27.

Anyway, if you want to test them I can give you the m5b file.

]]>https://community.m5stack.com/post/12153https://community.m5stack.com/post/12153Fri, 29 Jan 2021 11:57:15 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Thu, 28 Jan 2021 14:58:20 GMT]]>@ajb2k3 Sounds interesting, thank you for your wish :) we will push it forward for consideration !

]]>https://community.m5stack.com/post/12097https://community.m5stack.com/post/12097Thu, 28 Jan 2021 14:58:20 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Tue, 26 Jan 2021 17:06:15 GMT]]>@zontex Yes a simple way for users to select which pin is to be used as a capacitive sensing in.
Like the digital read pin (pinnum) block
but
Capacitive read pin (pinnum)

]]>https://community.m5stack.com/post/12025https://community.m5stack.com/post/12025Tue, 26 Jan 2021 17:06:15 GMT<![CDATA[Reply to [UIFlow] Capacitive Touch Blocks. on Tue, 26 Jan 2021 09:20:51 GMT]]>Hi @ajb2k3 Could you elaborate a little further? do you mean some extra simple IO (input/output) functionalities?

]]>https://community.m5stack.com/post/12004https://community.m5stack.com/post/12004Tue, 26 Jan 2021 09:20:51 GMT