Pinout description for Audio+ V3 to a breadboard

RASPIAUDIO
1

Hi all,

I’m expecting a delivery of the Audio+ V3 any day now, and researching documentation meanwhile.

I find two different pinout descriptions for the Audio+ V2, and additionally some thread about a faulty description for voltage input (3v or 5v?). Generally I fail to find a comprehensive documentation about what Raspberry Pi pins are going to which Audio+ pins (e.g. for use on a breadboard)?.

Can I please have some assistance on how to connect the Audio+ V3 to a breadboard (via a T-Cobbler).
The intention is to eventually move everything to a prototype board, and use it for a MiniDexed project.

Thank you!

2

For Audio V3 you will need both 5V and 3.3V input
For pinout follow Audio V2 guide picture poinout in the guide are updated.

Kind regards

3

Thank you, but still not clear enough for me to understand.
According to the Installation link AUDIO+ installation guide the following should be used on the Raspberry:
-GPIO21 (pin 40)
-GPIO19 (pin 35)
-GPIO18 (pin 12)
-Ground pin (connect at least one : pin 6, 9, 14, 20, 25, 30, 34, 39)
-3.3v pin (connect at least one: : pin 1, 17)
But nothing about the corresponding holes on the Audio+ V3. And nothing in the guide about 5V.

As fairly new to the Raspberry platform, it is not clear to me where to put the above Pins from the Raspberry, onto the Audio+ V3 board, using something like a breadboard or a protocard?

I can see that the Audio+ V3 board has a 2x20 pin layout as well as a 1x25 row but it is not clear to me if the 1x25 row doubles some of the 2x20 row pins, and/or where the Raspberry GPIO pins are connected on the Audio+ V3 board.

Please advise for me as a novice.
Kind regards, Ricotico

4

Hi! I have now received my Audio+ V3 and used my volt-meter to better understand where all pins on the single 25-pin row is matched to on the 2x20 pin row.
It appears that the third from right pin (labeled 19) on the single row is routed to GPIO 26 on the double row, rather than GPIO 19 as one would assume. Can you please confirm this as a known error?

Also, the printed QR-code on the board goes to nowhere. You might want to look into that!