P16 doesn't work on micro:bit V2

[PSLLSP]

Joystick:bit has vibration motor connected to pin P16.

microbit:bit V1 can control vibration motor. The same program running on micro:bit V2 doesn't control vibration motor.

I first assumed that motor on the Joystick:bit is broken but when I tried the same program with micro:bit V1, motor started to vibrate. That implies that something wrong is with micro:bit V2...

DEMO

---

I tried NEOpixels connected to P16 and in that case, there was no issue at V1 or V2, I was able to control NEOPIXELs...

[martinwork]

Does the Joystick:bit always work with the V1? I'm thinking you have tested V2 P16 is working, and the code for controlling the vibration is very simple, so maybe it's an intermittent connection problem?

[PSLLSP]

I do not think it is a connector issue. I removed micro:bit from joystick:bit shield several times and the pattern was clear. Vibration motor was not working when V2 was controlling the joystick:bit. Maybe I can test it in some other way, like I will use different "shield" and connect LED to pin P16 and check if LED is activated or not. It looks like P16 on our microbit:V2 is not damaged as Neopixel strip connected to pin P16 was working as expected. But Neopixel library uses different code to drive the PIN, doesn't it? There is some assembly code that drives the pin to produce signal with good timing sequence...

When I opened this issue I assumed there is some problem in the IO library for P16... I can try to do more tests to prove it or to find other explanation... The only small problem is that I do not have V2 and it can take some to do more experiments with V2...

Other note is that it is difficult to troubleshoot directly with joystick:bit as there is no easy access to the motor when micro:bit is in the slot.

[martinwork]

The joystickbit extension uses digital write to change the P16 voltage, setting it low to turn on the motor.
https://github.com/tinkertanker/pxt-joystickbit/blob/master/joystickbit.ts#L94

I find an LED+resistor connected from 3V to P16 is on when P16 is low. When connected from P16 to GND, it is on when P16 is high. V1 and V2 appear to be the same.

I would have thought using neopixels is a good test of the digital output capabilities.