04-03-2025, 03:30 AM
(04-03-2025, 12:12 AM)Pyrowrx Wrote: I am a bit perplexed right now. I have a 3b+ that I am hoping to use as a screen/dac. The full setup is 3b+, raspberry pi touchscreen(1st edition) and raspberry pi DAC pro. So the pi mounts to the screen, cables are run to it, and the dac is a gpio hat that goes on top. I installed the pi on the screen without the dac, I was missing standoffs, and got the current version of moode running on that and displaying on the screen. When I add the dac the touchscreen will not power on. I first thought it was a power issue, but even when I power the screen directly it will not boot up with the DAC installed. What am I missing?
I'm uncertain what your problem is.
To check, I dug an Pi 3B+, an official Touchscreen1, and a HiFiBerry DAC+ Pro out of my project box. I stacked them together, connected the combination to a 5V/2.5A power supply, and booted a fresh image of moOde 9.3.0.
From a web browser on my laptop I brought up the moOde webUI (oh my goodness, I'd forgotten how slowly moOde finishes initializing on the Pi 3B!). On the Audio config screen, I ran through the process of setting up for the HiFi Berry hat (yet another reboot, oh boy!), and, on the Peripherals config screen, I ran through the process of enabling the local display with a Touch 1 screen, etc.
This combo is working fine for me. The moOde webUI comes up bright and shiny, so to speak, on the local display. Of course, it continues to reachable from a web browser on my laptop.
Off the top of my head, did you make sure your RPi DAC Pro HAT GPIO connector was properly registered on the Pi's GPIO pins. It's easy to be off by one row of pins, which can cause all sorts of problems.
As Tim said, the Touch 2 is a nicer screen, although its slightly different physical size means finding a different encasement. I'll add that using a Pi 4B or Pi 5B improves the responsiveness.
Regards,
Kent
