Replies: 3 comments 1 reply
-
|
Thanks for reporting back. I am considering writing a LCD screen setup guide for ORM, and this is a pretty good start! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the guiding on the username, that needs to be pi. I have no experience on this, and this help me to be able to get system running. |
Beta Was this translation helpful? Give feedback.
-
|
@Paku1964 Thank you for this good explanation to make the 3,5" display running. I got it working. But you are right: it takes ages for the system to start.. After some tries I got even the calibration right, although But I have an essential question. In my case, the display-head uses the Pins 1-26 of the Raspberry Pinout, so that I can connect SIG to GPI0 26 on Pin 37 and GND to Pin 39. But where can I get 3,3 V from? Or do you have flexible connections to the pins that are mandatory to run the display? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Here's some instructions that would have helped me set up openrowingmonitor on my Raspberry Pi 3B with a 3.5" MPI3501 gpio lcd screen:
Using Raspberry Pi Imager:
For the operating system choose "Raspberry Pi OS (other)" -> "Raspberry Pi OS (Legacy, 64-bit) Lite".
For OS customisation settings, leave the username as "pi" because the openrowingmonitor install script expects it.
Set hostname as "rowingmonitor".
Configure wireless LAN so the pi can connect to your wifi and so you can access it with PuTTY. And on the Services tab, enable SSH.
With the sdcard in the pi and it powered on, you should be able to connect to it with PuTTY if you set the Host Name to rowingmonitor.local but it might take a few minutes before it'll work.
After connecting and logging in with PuTTY, run the install script:
reboot takes a while the first time after the script.
Check the samba share is working before proceeding, you might need to run the script again.
In windows explorer, you should be able to access the samba share by typing "\\rowingmonitor.local" in the address bar. In the Configuration folder, you can edit config.js in Notepad, add "gpioPin: 26," on the line above the final '}'. This is because the screen uses gpio 17.
Alternatively, you could edit the file via PuTTY:
Also edit /boot/firmware/config.txt, change gpio=17=pu,ip to gpio=26=pu,ip:
The following instructions are mostly from https://www.reddit.com/r/raspberry_pi/comments/1bnav0y/i_finally_have_the_35inch_gpio_spi_lcd_working/
fresh install of RPI OS bookworm (Expand file system -> reboot -> and then run sudo rpi-update)
Advanced -> change wayland to X11
Interface-> SPI - enable
Add a "#" in front of the line "dtoverlay=vc4-kms-v3d"
add this line at the end of the file " dtoverlay=piscreen,speed=18000000,drm,rotate=0 "
(remove the double inverted commas "")
you can edit rotate=0 to 180 etc to change screen orientation.
be very patient (takes ages). At this point the screen should work but not the touch screen. I was impatient and connected via SSH, just after I did that the screen started working, showing openrowingmonitor. I'm not sure if logging in triggered it to work.
Add these lines at the end of the file
NOTE: if the touch input is still not working correctly , then play around with Option "InvertX" "false", Option "InvertY" "true" in the step 7 untill you get the desired result.
Calibration software will run and will be visible on the screen, press the 4 markers to calibrate and the touch would become pretty accurate.
One last note, don't be tempted to try setting up chromium as a web kiosk unless you know what you're doing (it's reported to work worse anyway).
Beta Was this translation helpful? Give feedback.
All reactions