Posts: 5
Threads: 2
Joined: Apr 2025
Reputation:
0
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?
Posts: 14,591
Threads: 335
Joined: Mar 2018
Reputation:
599
I'm not sure how to troubleshoot that but maybe another user can help out :-)
I would recommend getting a Pi Touch 2 if you want to have a good touch screen experience.
Posts: 5
Threads: 2
Joined: Apr 2025
Reputation:
0
(04-03-2025, 12:47 AM)Tim Curtis Wrote: I'm not sure how to troubleshoot that but maybe another user can help out :-)
I would recommend getting a Pi Touch 2 if you want to have a good touch screen experience.
Yeah, Moode is running even now. I can go to moode.local and it is there and running just fine. I thought maybe I was missing something that needed a configuration change. As an aside, would it be possible to run headless and use a second pi to use the tablet by installing raspian and keeping moode.local open on it?
Posts: 52
Threads: 6
Joined: Mar 2025
Reputation:
2
As the UI is available via moode.local, there's no need for a second PI to serve the UI. Here I've a couple of moodes and access them via the browser from my phone, laptop, tablet, ... and via ssh when needed.
What do you mean by "keeping moode.local open on it"?
Posts: 5
Threads: 2
Joined: Apr 2025
Reputation:
0
(04-03-2025, 01:19 AM)ils1974 Wrote: As the UI is available via moode.local, there's no need for a second PI to serve the UI. Here I've a couple of moodes and access them via the browser from my phone, laptop, tablet, ... and via ssh when needed.
What do you mean by "keeping moode.local open on it"? I am picturing a now playing screen, so it would indicate what is playing when it comes from a digital source, on a visible screen on the console with the stereo. Its a looks thing. Not needed for the actual operation of moode. I would say moode is working as advertised, I am just not smart enough to troubleshoot what is likely a hardware problem.
Posts: 6,413
Threads: 187
Joined: Apr 2018
Reputation:
261
(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
Posts: 5
Threads: 2
Joined: Apr 2025
Reputation:
0
(04-03-2025, 03:30 AM)TheOldPresbyope Wrote: (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 Thank you for going through that. You basically created the exact same setup as me with just a different brand hat. I think that confirms there is some hardware incompatibility here. I will run it headless and probably look at getting a pi5 and newer touchscreen later down the road.
|
