# Testing Station pinout

**URL:** <https://crucible.hubbe.net/t/testing-station-pinout/6515>\
**Category:** Proffieboards\
**Created:** [March 14, 2025, 5:02pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515 "2025-03-14T17:02:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![baldusi](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/baldusi/32/70_2.png) [@baldusi](https://crucible.hubbe.net/u/baldusi)\
**Post date:** [March 14, 2025, 5:02pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/1 "2025-03-14T17:02:51Z")

</div>

@profezzorn I want to do a testing station, and currently want to have two OLEDs in series (with different addresses, of course), plus an ST7735 TFT, and six buttons.  
Can I have OLED in “series” plus the TFT?  
Second issue is that after connecting all those displays, I’m only left with Data4, RX and TX for Button 4, Button 5 and LatchingButton 6. Can I use those pins?  
Thanks!

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [March 14, 2025, 6:09pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/2 "2025-03-14T18:09:54Z")

</div>

Yes, you can have two displays on the i2c bus. In theory you can have lots of them, as long as they have different addresses. You can also have a TFT display at the same time, but I’m not sure if all of that will operate smoothly if you run it all at the same time.

Any “GPIO” pin can be used for buttons, so RX, TX and Data4 are fine for buttons.

---

<div class="post-metadata">

**Author:** ![baldusi](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/baldusi/32/70_2.png) [@baldusi](https://crucible.hubbe.net/u/baldusi)\
**Post date:** [March 14, 2025, 7:37pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/3 "2025-03-14T19:37:18Z")

</div>

Well, I thought that if I’m going to make a test station, I should go all in and test as much as possible. I’m using a 128x32 OLED plus a 128x64. So I want to see how do I configure the non-standard resolution for the OLED, too. My objective is obviously to look for corner cases. But this would enable a blaster worth dedicated OLED for battery, round counter plus the TFT for effects, for example.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [March 14, 2025, 7:48pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/4 "2025-03-14T19:48:18Z")

</div>

You could do connectors instead.  
Like, you could wire in one of these instead of a color display: [Adafruit EYESPI Breakout Board - 18 Pin FPC Connector : ID 5613 : Adafruit Industries, Unique & fun DIY electronics and kits](https://www.adafruit.com/product/5613)

Then if you _don’t_ plug in a display, then you can use those pins for something else, like servos for instance.

And you could add a qwiic connector insted of OLED (for something like this: [SparkFun Qwiic OLED Display (0.91 in., 128x32)](https://www.sparkfun.com/sparkfun-qwiic-oled-display-0-91-in-128x32-lcd-24606.html))

Having connectors is potentially more versatile as you can switch out the display.

---

<div class="post-metadata">

**Author:** ![baldusi](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/baldusi/32/70_2.png) [@baldusi](https://crucible.hubbe.net/u/baldusi)\
**Post date:** [March 14, 2025, 8:04pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/5 "2025-03-14T20:04:02Z")

</div>

I already have the board to a 2x20 pin cable and so I was planning on connecting the testing station through the cables. I’m actually waiting for the pogo pins. But now that you mention it, I have no trouble soldering some pins to the boards I have and putting the female connectors. Thanks for the idea.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [March 14, 2025, 9:28pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/6 "2025-03-14T21:28:51Z")

</div>

I’ve been thinking that I need to design a new version of this board:

[https://fredrik.hubbe.net/lightsaber/v6/test\_rig\_breakout.html](https://fredrik.hubbe.net/lightsaber/v6/test_rig_breakout.html)

With quiic and eyespi connectors, and maybe some easy connectors for pixels.

---

<div class="post-metadata">

**Author:** ![baldusi](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/baldusi/32/70_2.png) [@baldusi](https://crucible.hubbe.net/u/baldusi)\
**Post date:** [March 14, 2025, 11:41pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/7 "2025-03-14T23:41:27Z")

</div>

A different question. For the blaster case, can I do this:

```auto
//128 x 32 OLED
BlasterDisplayController<128, uint32_t, STRTYPE("oled1/")> display_controller1;
SSD1306Template<128, uint32_t> display1(&display_controller1, 0x3C);
//128 x 64 OLED
StandardDisplayController<128, uint64_t, STRTYPE("oled2/")> display_controller2;
SSD1306Template<128, uint64_t> display2(&display_controller2, 0x7B);

```

Questions:

1. BlasterDisplay enables the blaster specific effects?
2. How could I change the resolution on the second display? Replacing `uint32_t` with `uint64_t`, right?
3. The standard I2C address of 128x32 OLEDs is `0x3c`?

---

<div class="post-metadata">

**Author:** ![baldusi](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/baldusi/32/70_2.png) [@baldusi](https://crucible.hubbe.net/u/baldusi)\
**Post date:** [March 14, 2025, 11:45pm UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/8 "2025-03-14T23:45:15Z")

</div>

i do have the pogo adapter board. But I am designing a 3D printed solution so I only need one board and can easily press the board.  
And then I’m planing on using the plane cable straight to the necessary pins. It’s something I’m still desinging.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [March 15, 2025, 12:44am UTC](https://crucible.hubbe.net/t/testing-station-pinout/6515/9 "2025-03-15T00:44:36Z")

</div>

> [@baldusi](#):
>
> can I do this:

Yes, and that looks about right.

> [@baldusi](#):
>
> Questions

Answers:

1. yes
2. correct
3. indeed: [ProffieOS/display/ssd1306.h at 493a85d9cf4e7aa77caa0928bccf16f0df101d30 · profezzorn/ProffieOS · GitHub](https://github.com/profezzorn/ProffieOS/blob/493a85d9cf4e7aa77caa0928bccf16f0df101d30/display/ssd1306.h#L1058)
