# Screen Module Model/Controller **URL:** \ **Category:** PicoCalc\ **Tags:** hardware, software, diy, micropython\ **Created:** [August 10, 2025, 2:18pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116 "2025-08-10T14:18:40Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ArielPalazzesi](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/arielpalazzesi/32/16836_2.png) [@ArielPalazzesi](https://forum.clockworkpi.com/u/ArielPalazzesi)\ **Post date:** [August 10, 2025, 2:18pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/1 "2025-08-10T14:18:40Z")
Hola! Mi PicoCalc ya está en camino. 🤞 Uno de los proyectos que me gustaría realizar consiste en ejecutar y editar código MicroPython en ella. Para eso, entre otras cosas, necesito saber que modelo de controlador tiene la pantalla del dispositivo. ¿Alguien tiene esa información? Se que es una pantalla de 320x320 y como es su conector, pero no se que librería de MicroPython debería usar con ella.. Cualquier ayuda es bienvenida. PD: Se que ya existe un port de MicroPython para PicoCalc, pero tiene algunas limitaciones con las que no me siento muy cómodo. Por eso estoy “jugando” con esta idea. * * * My PicoCalc is already on the way.🤞 One of the projects I’d like to work on is running and editing MicroPython code on it. To do that, among other things, I need to know which display controller the device uses. Does anyone have that information? I know it’s a 320×320 display and I’m familiar with its connector, but I’m not sure which MicroPython library I should use with it. Any help is welcome. P.S.: I know there’s already a MicroPython port for PicoCalc, but it has some limitations I’m not entirely comfortable with, so I’m “playing” with this idea. ---
**Author:** ![DigitalDreams](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/digitaldreams/32/16007_2.png) [@DigitalDreams](https://forum.clockworkpi.com/u/DigitalDreams)\ **Post date:** [August 10, 2025, 8:24pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/2 "2025-08-10T20:24:32Z")
The initial PicoCalc modified ‘webmite/picomite’ builds used a ILI9488P display driver, now using a much faster ST7796SP. ---
**Author:** ![beapig](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/beapig/32/11901_2.png) [@beapig](https://forum.clockworkpi.com/u/beapig)\ **Post date:** [August 12, 2025, 5:49am UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/3 "2025-08-12T05:49:33Z")
[https://www.txwlcd.cn/en/h-pd-545.html](https://www.txwlcd.cn/en/h-pd-545.html) According to the information provided by the screen supplier, the driving IC is ST7365P. the same model on this page get a 480x480 resolution，weird。 I really want to test this alternate screen,but the Minimal order quantity is 2,a little expensive for me ---
**Author:** ![ArielPalazzesi](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/arielpalazzesi/32/16836_2.png) [@ArielPalazzesi](https://forum.clockworkpi.com/u/ArielPalazzesi)\ **Post date:** [August 12, 2025, 12:12pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/4 "2025-08-12T12:12:01Z")
Thank you all for the information. I now have enough to start digging into it. Thanks again. Greetings from Argentina. ---
**Author:** ![DigitalDreams](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/digitaldreams/32/16007_2.png) [@DigitalDreams](https://forum.clockworkpi.com/u/DigitalDreams)\ **Post date:** [August 12, 2025, 2:10pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/5 "2025-08-12T14:10:04Z")
We need someone to write a program to read the actual display ID from the controller nvram…. Will put this to bed once and for all. ---
**Author:** ![BlairLeduc](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/blairleduc/32/11808_2.png) [@BlairLeduc](https://forum.clockworkpi.com/u/BlairLeduc)\ **Post date:** [August 12, 2025, 4:14pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/6 "2025-08-12T16:14:49Z")
From my research, this is not possible, there is no ID to read. ---
**Author:** ![DigitalDreams](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/digitaldreams/32/16007_2.png) [@DigitalDreams](https://forum.clockworkpi.com/u/DigitalDreams)\ **Post date:** [August 13, 2025, 1:04pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/7 "2025-08-13T13:04:55Z")
A good start…. RDID1 (Dah): Read ID1 This read byte identifies the LCD module’s manufacturer. RDID2 (DBh): Read ID2 This read byte is used to track the LCD module/driver IC version. RDID3 (DCh): Read ID3 This read byte identifies the LCD module/driver. ---
**Author:** ![BlairLeduc](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/blairleduc/32/11808_2.png) [@BlairLeduc](https://forum.clockworkpi.com/u/BlairLeduc)\ **Post date:** [August 13, 2025, 11:15pm UTC](https://forum.clockworkpi.com/t/screen-module-model-controller/19116/8 "2025-08-13T23:15:51Z")
Those are not listed in the datasheets I have?