Skip to content

Conversation

@jehlers42
Copy link
Contributor

I made a rough placeholder image to illustrate the display's pins in the hopes of reducing confusion. If it's good enough, perfect. If not, I'll get someone to work up a better one.

I also updated the display article to remove (hopefully) the ambiguity of the original text. The new image plays a role. The warning text is cribbed from the display's product brief.

The initial comment in issue #2977 makes it seem like you could technically power the Pi using the display by plugging into the display while the GPIOs are connected with jumpers, but I didn't include that as an option because it doesn't seem like a great one (if it's even possible).

Closes issues #2977 and #3007.

@aallan
Copy link
Contributor

aallan commented Sep 16, 2023

@jehlers42 Can you create an Asana task to get the placeholder image redone by Design when they get a chance. Thanks.

The following image shows how to attach a Raspberry Pi to the back of the Touch Display using the included standoffs. It also shows the connections you need to make between Raspberry Pi and the display's PCB. You can also mount the touch display in a separate chassis if you have one available. The connections remain the same, though you may need longer cables depending on the chassis you use.

image::images/GPIO_power-500x333.jpg[DSI Display Connections]
image::images/GPIO_power-500x333.jpg[DSI Display pinout]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image needs reshot by Brian. He has an Asana task to reshoot all (most) of the existing documentation imagery. So no need to nudge him about this one.

=== Connecting a Raspberry Pi

The following image shows how to attach the Raspberry Pi to the back of the Touch Display (if required), and how to connect both the data (ribbon cable) and power (red/black wires) from the Raspberry Pi to the display. If you are not attaching the Raspberry Pi to the back of the display, take extra care when attaching the ribbon cable to ensure it is the correct way round. The black and red power wires should be attached to the GND and 5v pins respectively.
The following image shows how to attach a Raspberry Pi to the back of the Touch Display using the included standoffs. It also shows the connections you need to make between Raspberry Pi and the display's PCB. You can also mount the touch display in a separate chassis if you have one available. The connections remain the same, though you may need longer cables depending on the chassis you use.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs properly expanding with several images that show this process step-by-step. Possibly we should go down the route of an animated GIF, e.g. see https://www.raspberrypi.com/documentation/accessories/build-hat.html#preparing-your-build-hat.


==== Powering the Touch Display

There are two options to power the Touch Display: using the Raspberry Pi's GPIO to send power, or powering the display directly with a separate micro USB cable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should sub-section, if there are two options there should be two separate sections.

@aallan aallan removed the request for review from lurch September 16, 2023 09:21
Make sure the Raspberry Pi is powered off and unplugged, then connect one end of the black jumper wire to pin six (GND) on the Raspberry Pi and one end of the red jumper wire to pin four (5V). Next, connect the other end of the black wire to the GND pin on the display and the other end of the red wire to the 5V pin on the display.

.Connect the red and black wires to 5V and GND
image::images/touch-GPIO.png[Illustration of display pins, width=250]
Copy link
Contributor

@aallan aallan Sep 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't use pixel widths, e.g. width=250. Instead use percentiles, e.g. width="50%"

@aallan
Copy link
Contributor

aallan commented Sep 16, 2023

It's a decent start, but was anticipating a bit more of an overhaul here. I'm not the greatest fan of FAQ-based documentation, I think it's a real failure of narrative. This page has both a "troubleshooting" and "tips and tricks" section. These really need to get integrated into the documentation proper.

One thing to bear in mind is that this page has been fairly extensively modified on the bookworm branch in 82d5530 by @lurch. I think the best move here would be to change the base branch you're targeting the PR against and commit onto the bookworm branch.

@aallan aallan changed the base branch from develop to bookworm September 16, 2023 14:08
@aallan
Copy link
Contributor

aallan commented Sep 16, 2023

Flipped it onto bookworm and it looks like there are some merge conflicts as a result. Please resolve in favour of the bookworm changes and work from there. Thanks!

naushir and others added 25 commits September 17, 2023 14:43
This value is 6s only in the legacy firmware stack, which is not functional
in Bookworm.

Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
Remove xscreensaver instructions, as Wayfire comes with a built-in screensaver
X Windows -> desktop. Part of #3057
@jehlers42
Copy link
Contributor Author

Closing this due to messing up during conflict resolution. New PR for redone branch is #3121; comments are being taken into account.

@jehlers42 jehlers42 closed this Sep 17, 2023
@jehlers42 jehlers42 deleted the touch-display branch September 17, 2023 22:39
@jehlers42 jehlers42 mentioned this pull request Sep 17, 2023
@aallan
Copy link
Contributor

aallan commented Sep 18, 2023

What did you do? 😬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation paused Waiting for other things to happen.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Touch Display installation needs better instructions Ambiguity about powering the Touch Display

6 participants