RepPanel - A DIY alternative to the PanelDue with WiFi support
-
I thought I would just give it a try to see if something showed up. So I:
- Saved the configuration in the menuconfig
- Ran idf.py build
- Connected USB to the ESP32 and found that it was on COM9
- Ran idf.py -p COM9 flash
Unfortunately, the display never came on. So I wondered if it needed power on other pins and used my multimeter to check. I could see that the two 3.3V pins on the screen are internally connected, so are the two 5V pins and the five ground pins.
So I thought that it probably needs both 5V and 3.3V, so I wired 5V from the ESP32 to pin 2 on the screen.
When I plugged USB back in, the screen lit up, but nothing happened:
-
@pandaym Your config looks good now. Yes you got the commit thing right. Otherwise you'd get a compile error.
Can you check the debug log please? You can do that by running:idf.py monitorThe 5V & 3.3V thing is strange. I'll take a look at the data sheet later.
-
@seeul8er Thanks for your reply. I had in fact bought the LCD but the resistive touch version. I've been waiting for the capacitive one to come so that I can have another try. Would there be much reprogramming needed to use the resistive touch version?
-
@pd said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
@seeul8er Thanks for your reply. I had in fact bought the LCD but the resistive touch version. I've been waiting for the capacitive one to come so that I can have another try. Would there be much reprogramming needed to use the resistive touch version?
Not at all, but you'll need to compile and flash the image yourself. Choose the XPT2046 chip as a touch screen controller and the ILI9488 for TFT in "idf.py menuconfig" and set the pins you want to use (take a look at above posts for the XPT2046 & the RepPanel repo for TFT related pins). After that check the datasheet of the display and connect the wires accordingly (You'll have two SPIs - TFT and touch). For the TFT related GPIOs you can use my config. Only the touch controller will be different.
-
@seeul8er said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
@pandaym Your config looks good now. Yes you got the commit thing right. Otherwise you'd get a compile error.
Can you check the debug log please? You can do that by running:idf.py monitorThe 5V & 3.3V thing is strange. I'll take a look at the data sheet later.
I ran idf.py monitor, and it looks like something from the Matrix. Still haven't gotten anything on screen.
-
@pandaym Check the docs on that. Further down it says changing the Main XTAL frequency might solve the output issue. Maybe autodetect does the trick.
-
@seeul8er said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
@pandaym Check the docs on that. Further down it says changing the Main XTAL frequency might solve the output issue. Maybe autodetect does the trick.
Same thing regardless of XTAL frequency. I rebuilt and reflashed between attempting them. Then I disconnected all my wiring to run the ESP32 on its own, still no luck.
I then navigated to the examples and tried to build and flash the hello world example - this works fine:
I went through the menuconfig on this vs. RepPanel, and found some differences in flash size and baud rate for monitor. I changed the Flash size to 2 like on Hello World, but then it would not flash because of insufficient space. I then tried changing idf.py monitor baud rate to 115200, while keeping 4mb flash size, and then I got monitor running:
Shall I try and wire it back up? Also, what do you think I have to do about power? Still haven't figured whether I should need to connect both a 5V and a 3.3V cable from the ESP32 to the screen.
-
@pandaym said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
Shall I try and wire it back up? Also, what do you think I have to do about power? Still haven't figured whether I should need to connect both a 5V and a 3.3V cable from the ESP32 to the screen.
Try using only the 5V input. I am pretty sure you do not need both.
Looking at the logs I'd say that the flash and startup of RepPanel were a success. I'd go wire it up again. Can only be a GPIO config or wiring issue.
Does your display feature any switches/bridged pins? Read something about that in the forums. -
@seeul8er said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
@pandaym said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
Shall I try and wire it back up? Also, what do you think I have to do about power? Still haven't figured whether I should need to connect both a 5V and a 3.3V cable from the ESP32 to the screen.
Try using only the 5V input. I am pretty sure you do not need both.
Looking at the logs I'd say that the flash and startup of RepPanel were a success. I'd go wire it up again. Can only be a GPIO config or wiring issue.
Does your display feature any switches/bridged pins? Read something about that in the forums.Still no luck unfortunately.
I tried wiring it up to a Raspberry, just to confirm that it works. And that worked fine.
Must be a wiring issue, but I cannot find any diagram for it anywhere, I have just been counting them out and using their table.
-
@PCR Are plans still afoot to design a PCB for this project? I'd be interested... also thinking about the possibility of adding a small LiPo battery + charge controller to make it a dockable / portable interface!
-
I have managed to get the screen alive, but without any touch.
If I just set the touch panel to none in the menuconfig, then the screen comes alive. But if I actually configure the touch, it just blanks it out.Any idea?
-
After a ton of work, it's finally alive:
https://www.youtube.com/watch?v=LbLHOhdqSiEI had to set both display and touch to HSPI and change some GPIOs for some reason. But in the end it worked. The resisitive touch screen just isn't that great - should have gotten capacitive
-
-
-
@pandaym said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
After a ton of work, it's finally alive:
https://www.youtube.com/watch?v=LbLHOhdqSiEI had to set both display and touch to HSPI and change some GPIOs for some reason. But in the end, it worked. The resistive touch screen just isn't that great - should have gotten capacitive
My replay is a bit delayed due to my vacation, but I am very glad to hear you got it working! Seems like the manufacturer needs to work on the docs a bot more.
-
@seeul8er Do you have a link where to get the display in Germany?
-
-
@PCR said in RepPanel - A DIY alternative to the PanelDue with WiFi support:
@seeul8er Do you have a link where to get the display in Germany?
If you want to use the compiled images you need to order it form Buydisplay. I do not know any German reseller. The link carlo postet seems to be a display that is lower in quality. Pandaym seemed to get it working but it was a bit tricky
-
@pandaym @seeul8er Glad you got it working and huge thanks for sharing your troubleshooting process. It's been incredibly valuable detailing everything you tried and has no doubt saved me hours. It seems I am in a similar situation with SPI for both the display and touch but have a different touch controller.
I am currently stuck with nothing being displayed. I have tried setting the touch to none as you did but no luck. You said you changed some GPIO? Could you share your sdkconfig file. I would very much appreciate it.
-
So I made some progress, I got the display working but no touch and the colours are all off. There are lots of posts in arduino forums of people having problems with ILI9488 displays and something about inverting the display but I can't make sense of how to do it in this application. I've tried changing a couple of parameters in the LVGL driver but to no avail. I think the RGB is in the wrong order but not entirely sure.
As far as the touch goes, I get responses with the monitor on but no co-ordinates, they're all 0,0.
after my summer holiday!
