You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, this shield is not usable with my particular panel model (P2.5, 128x64px).
On my panel, the spaces between the plastic frame and the input connector are much smaller, so the board hits the plastic frame. As a result, I cannot fully push the input connector in.
For a future iteration of the board, maybe create one where the board connects to the panel via a ribbon cable?
I actually thought about replacing the 16-pin connector you provided with a ribbon-cable (male) connector. Unfortunately, soldering it on the back of the board would mess up the pin order, and soldering it on the front is impossible due to the ESP32 board covering it.
So maybe something to consider for the next iteration of the board? The footprint of the connector is exactly the same, but there will be some rerouting necessary...
Thank you once again for your work!
The text was updated successfully, but these errors were encountered:
Unfortunately, this shield is not usable with my particular panel model (P2.5, 128x64px).
On my panel, the spaces between the plastic frame and the input connector are much smaller, so the board hits the plastic frame. As a result, I cannot fully push the input connector in.
For a future iteration of the board, maybe create one where the board connects to the panel via a ribbon cable?
I actually thought about replacing the 16-pin connector you provided with a ribbon-cable (male) connector. Unfortunately, soldering it on the back of the board would mess up the pin order, and soldering it on the front is impossible due to the ESP32 board covering it.
So maybe something to consider for the next iteration of the board? The footprint of the connector is exactly the same, but there will be some rerouting necessary...
Thank you once again for your work!
The text was updated successfully, but these errors were encountered: