# PiDog v2 - dual\_touch init ... fail **URL:** \ **Category:** Robotic kit for Raspberry Pi\ **Created:** [October 3, 2026, 4:39pm UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031 "2026-10-03T16:39:40Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![lpo34](https://avatars.discourse-cdn.com/v4/letter/l/e47c2d/32.png) [@lpo34](https://forum.sunfounder.com/u/lpo34)\ **Post date:** [October 3, 2026, 4:39pm UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031/1 "2026-10-03T16:39:40Z")
Hello, PiDog v2 + Raspberry Pi 4 I get a **dual\_touch init …** fail error message each time I launch a script. Dual touch module lights work when I touch it, so power is OK. Any idea ? Is there a log to look at ? > pinctrl get returns : > 0: ip pu | hi // ID\_SDA/GPIO0 = input > > 1: ip pu | hi // ID\_SCL/GPIO1 = input > > 2: a0 pu | hi // GPIO2 = SDA1 > > 3: a0 pu | hi // GPIO3 = SCL1 > > 4: op – pn | lo // GPIO4 = output > > 5: op – pu | hi // GPIO5 = output > > 6: ip pu | lo // GPIO6 = input > > 7: op – pu | hi // GPIO7 = output > > 8: op – pu | hi // GPIO8 = output > > 9: a0 pd | lo // GPIO9 = SPI0\_MISO > > 10: a0 pd | lo // GPIO10 = SPI0\_MOSI > > 11: a0 pd | lo // GPIO11 = SPI0\_SCLK > > 12: op – pd | hi // GPIO12 = output > > 13: ip pd | lo // GPIO13 = input > > 14: ip pn | hi // GPIO14 = input > > 15: ip pu | hi // GPIO15 = input > > 16: op – pn | lo // GPIO16 = output > > 17: ip pd | lo // GPIO17 = input > > 18: a0 pd | hi // GPIO18 = PCM\_CLK > > 19: a0 pd | hi // GPIO19 = PCM\_FS > > 20: a0 pd | lo // GPIO20 = PCM\_DIN > > 21: a0 pd | lo // GPIO21 = PCM\_DOUT > > 22: ip pd | hi // GPIO22 = input > > 23: ip pd | lo // GPIO23 = input > > 24: ip pd | lo // GPIO24 = input > > 25: ip pd | hi // GPIO25 = input > > 26: ip pd | lo // GPIO26 = input > > 27: ip pd | hi // GPIO27 = input > > 28: a5 pu | hi // RGMII\_MDIO/GPIO28 = RGMII\_MDIO > > 29: a5 pd | lo // RGMIO\_MDC/GPIO29 = RGMII\_MDC > > 30: a3 pu | lo // CTS0/GPIO30 = CTS0 > > 31: a3 pn | lo // RTS0/GPIO31 = RTS0 > > 32: a3 pn | hi // TXD0/GPIO32 = TXD0 > > 33: a3 pu | hi // RXD0/GPIO33 = RXD0 > > 34: a3 pn | hi // SD1\_CLK/GPIO34 = SD1\_CLK > > 35: a3 pu | hi // SD1\_CMD/GPIO35 = SD1\_CMD > > 36: a3 pu | hi // SD1\_DATA0/GPIO36 = SD1\_DAT0 > > 37: a3 pu | hi // SD1\_DATA1/GPIO37 = SD1\_DAT1 > > 38: a3 pu | hi // SD1\_DATA2/GPIO38 = SD1\_DAT2 > > 39: a3 pu | hi // SD1\_DATA3/GPIO39 = SD1\_DAT3 > > 40: a0 pn | lo // PWM0\_MISO/GPIO40 = PWM1\_0 > > 41: a0 pn | lo // PWM1\_MOSI/GPIO41 = PWM1\_1 > > 42: op – pu | lo // STATUS\_LED\_G\_CLK/GPIO42 = output > > 43: ip pu | hi // SPIFLASH\_CE\_N/GPIO43 = input > > 44: a1 pu | hi // SDA0/GPIO44 = SDA0 > > 45: a1 pu | hi // SCL0/GPIO45 = SCL0 > > 46: ip pu | lo // RGMII\_RXCLK/GPIO46 = input > > 47: ip pu | lo // RGMII\_RXCTL/GPIO47 = input > > 48: ip pd | lo // RGMII\_RXD0/GPIO48 = input > > 49: ip pd | lo // RGMII\_RXD1/GPIO49 = input > > 50: ip pd | lo // RGMII\_RXD2/GPIO50 = input > > 51: ip pd | lo // RGMII\_RXD3/GPIO51 = input > > 52: ip pd | lo // RGMII\_TXCLK/GPIO52 = input > > 53: ip pd | lo // RGMII\_TXCTL/GPIO53 = input > > 54: ip pd | lo // RGMII\_TXD0/GPIO54 = input > > 55: ip pd | lo // RGMII\_TXD1/GPIO55 = input > > 56: ip pd | lo // RGMII\_TXD2/GPIO56 = input > > 57: ip pd | lo // RGMII\_TXD3/GPIO57 = input > > 100: op dh pn | hi // BT\_ON/FWGPIO0 = output > > 101: op dh pn | hi // WL\_ON/FWGPIO1 = output > > 102: op dl pn | lo // PWR\_LED\_OFF/FWGPIO2 = output > > 103: op dl pn | lo // GLOBAL\_RESET/FWGPIO3 = output > > 104: op dh pn | hi // VDD\_SD\_IO\_SEL/FWGPIO4 = output > > 105: op dl pn | lo // CAM\_GPIO/FWGPIO5 = output > > 106: op dh pn | hi // SD\_PWR\_ON/FWGPIO6 = output > > 107: ip pn | lo // SD\_OC\_N/FWGPIO7 = input Best regards, Olivier ---
**Author:** ![robbo](https://avatars.discourse-cdn.com/v4/letter/r/97f17d/32.png) [@robbo](https://forum.sunfounder.com/u/robbo)\ **Post date:** [October 4, 2026, 11:55pm UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031/2 "2026-10-04T23:55:19Z")
i had that issue Follow sunfounder guide to a T sometimes running the programs twice ,It really needs to stay in order also chatgbt is a huge help as long as you keep him running with sunfounder and stay alert he will tend to run circles if you dont pay attention but he got it worked out with everything just the speaker seems to be my issue but chased the dual touch issue for days ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [October 9, 2026, 6:23am UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031/3 "2026-10-09T06:23:00Z")
Hi Olivier, Sorry for the delayed reply during our National Day holiday. Please power off your PiDog and check the touch switch wiring against the assembly diagram. The yellow signal wire should connect to GPIO22, and the green signal wire should connect to GPIO27. Please make sure the cable is firmly connected at both ends. Then restart your Raspberry Pi and run the standalone touch switch test, with no other PiDog programs running: cd ~/pidog/test sudo python3 dual\_touch\_test.py Try touching each side of the module and send us the terminal output, including any error messages. Please also run the following command and send us the installed library versions: sudo pip3 show pidog robot-hat ---
**Author:** ![lpo34](https://avatars.discourse-cdn.com/v4/letter/l/e47c2d/32.png) [@lpo34](https://forum.sunfounder.com/u/lpo34)\ **Post date:** [October 11, 2026, 9:13am UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031/4 "2026-10-11T09:13:59Z")
Hello, Thanks for your answer ! Done a global apt update & full-upgrade, git repositories pull & re-install. Reboot … Everything is working fine now ! Best regards, Olivier ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [October 12, 2026, 1:13am UTC](https://forum.sunfounder.com/t/pidog-v2-dual-touch-init-fail/5031/5 "2026-10-12T01:13:23Z")
Great，any further help,please feel free to contact.