pxt-microbit
pxt-microbit copied to clipboard
microsoft
Pin 0 touch is not working micro:bit v2
when setting pin 0 to capacitive touch it is not detecting any touch and resistive touch also it is not happen. using pin p0 press command
it is always showing value 1 means the pin is pressed. Is it a bug or hardware issue?
I used this project to test: https://makecode.microbit.org/_CL5dp1cX6DFT All combinations seem to work for me except logo + resistive (https://github.com/microsoft/pxt-microbit/issues/3724; https://github.com/lancaster-university/codal-microbit-v2/issues/113) I'm connecting a crocodile clip lead to P0 (and one to ground for P0 + resistive). Just holding the plastic of one lead can trigger P0 + capacitive.
my pin 0 is not responding for resistive as well as capacitive touch. logo is working fine.
On Mon, 4 Jul 2022 at 16:22, Martin Williams @.***> wrote:
I used this project to test: https://makecode.microbit.org/_CL5dp1cX6DFT All combinations seem to work for me except logo + resistive (#3724 https://github.com/microsoft/pxt-microbit/issues/3724) I'm connecting a crocodile clip lead to P0 (and one to ground for P0 + resistive). Just holding the plastic of one lead can trigger P0 + capacitive.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/pxt-microbit/issues/4794#issuecomment-1173671735, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEN35X5KUYFIPZHQQTIHYB3VSK665ANCNFSM52R462DQ . You are receiving this because you authored the thread.Message ID: @.***>
when setting pin 0 to capacitive touch it is not detecting any touch and resistive touch also it is not happen. using pin p0 press command
When I am using digital write and analog write command for pin 0, led is turning on but very dim as compared to connecting it to pin 1, pin 2.
@Nitesh-AI Is this still an issue, or is it a fault with your micro:bit?
We've looked into this in CODAL and the final solution will require a change in MakeCode. I can submit the change in a PR with the next CODAL tag, but in the meantime it'd be good to reopen this issue to be able to track it.
