Is this a possible solution for LCD Juno G screen??

[Leo Castro]

Woow!! Great work so far.

[dennis elbow]

great stuff i'm rooting for you.

[dpeddi]

Half work done...

Moved from ESP32 to raspberry pi Pico:

VID_20220929_071607_973.mp4

(9.33 MiB) Downloaded 201 times

E.

[Leo Castro]

Woooohoooo! Awesome.

[dpeddi]

Project completed...

Now is time to build a support for it and put it inside the keyboard

4_5890995864956046432 (1).mp4

(19.65 MiB) Downloaded 216 times

[Leo Castro]

Congratulations! I think there will be a lot of buyers for you project solution! Really awesome.

[dennis elbow]

wow that's amazing.i'm interested to purchase when it's ready.i never thought i'd see the day when a solution would come.massive thumbs up.

[dpeddi]

Project completed
https://github.com/dpeddi/LCDJunoG

At the moment i don't plan to produce any kit.

If you want to replicate just buy the display like mine, a raspberry pi pico, some dil jumpers, solder board, jumpers, wire and so on..

I've printed an adapter for the display with the 3d printer, but needed some rework. the source is on github, if you can do better, feel free to request a pull request on github with updated source.

Sometime appear few missing pixel and/or glitches but i think i can live with them, the result is really near to the perfection

photo_2022-10-04_09-50-41.jpg (156.98 KiB) Viewed 3145 times

photo_2022-10-04_09-50-32.jpg (186.27 KiB) Viewed 3145 times

[mzd6]

Project completed

Incredible! Great work!

[mark_kiwi]

Excellent job! And perfect timing....I recently was given a Juno-G with both an audio issue and screen issue and after a brief search of the web found this forum. (Had difficulties getting registered but finally I'm in!) I found the Service Notes so have the schematic and pretty confident I can track down the audio issue.
I've been examining the files you put on github to try and understand how to built this and am a bit confused. I've been playing with arduinos and esp8266 microcontrollers for some time, but not yet got into the pico or python (so have a bit of a knowledge gap there). I've just purchased a pico and reading up on them I have found that they can be programmed with micropython or using the arduino IDE.
To me, the files on github look like they may be a library for use with the arduino ide but there is no arduino sketch or wiring diagram. Am I correct in assuming what you posted is an arduino library? Any chance you can post the arduino sketch with details on how to use the library and wiring info as well?
Also I believe the pico can't cope with 5v, so I assume the 5v on pin 18 is left unconnected?

I'm in the process of ordering the LCD screen, finding it's data sheet and getting an understanding on how to control it etc...might come in handy for other projects.
Once again great work!

[dpeddi]

Hello,

The project use platformio. I've find it very nice because is much easier then Arduino to keep all the source aligned with the dependent library at the correct versions.

The project is written with Arduino... But platformio use main.cpp instead of project_name.ino

To install platformio you can just install python, then "pip install platformio" or install the "visual studio code" + platformio plugin. I suggest you to look at their documentation...

About the connection, I think the platformio.ini file is quite auto explained. I agree is not really well documented....feel free to pull request!

I've used the 5v to power up the raspberry pi Pico. I've used the pin that should be protected by an internal diode. The Pico have an interval v5-v3 converter...you know you can power it up from 5v usb...
The backlight line from the display to change the background colour... just need to connect the end of the trimmer to v3.3 and the central pin of the trimmer (look at.the schematic) to the analog input A0.

If you want to change the pinout you can just modify the platformio.ini file... The variables are exported in main.cpp automatically.

About the display... I've used the one linked on GitHub.. can't understand why you don't buy the same... However is a pretty standard SPI tft display with an ili9488 controller. If you want to experiment and you have at home an st7735 or an ili9344 the tft_espi library supports both... Just need to adjust few variables (driver/zoom) on platformio.ini

Regards

[sinitsinmike]

This is amazing!
Got all the components.
It is not quite clear how to flash it in to Rapsberry Pi Pico though.
Could anyone please add a bit more details/instructions?

Thank you!

Michael

[sinitsinmike]

Also it would be great to get more details on how to send data from RPI Pico to PC screen like in the video.

[sinitsinmike]

As I am no programmer, so it took me 3 days to connect a display that I had on hand, as I didn’t have the specific one listed in the post.
I have ordered the right display, but for now I have used 240x135px Waveshare 19340 that I already had.
To make this specific display work I had to change a few lines in the code: display driver, zoom level. Also for my specific display I had to switch around CS1 and CS2 wires.
Happy with this temporary display.
The only thing that could be improved is a display refresh rate, but perhaps that would require some hardware that is faster than RPI pico.

[mark_kiwi]

Good work getting that going, I'm still wrestling with VS code and PlatformIO as I'm new to that environment. Having issues getting the code to compile and upload to the Pico. I eventually managed to get a simple blink code loaded to a Pico so thats a good start. Working on successfully compiling and uploading this code now.
There also appears to be a way where you can produce a uf2 file from the code, which when dropped on a Pico, instantly programs the device. Simple way to program many pico devices if needed....I need to look into this more.
I have the recommended display, some new flat cable and a flat cable breakout board.... Hoping in the future to design a board that combines the screen, pico and breakout board into one replacement module.
Eventually I'd also like to figure out how to program a Pico to drive the original screen ie make a device to send a test pattern to the original screen to prove the fault is the screen and not what's feeding it.