a HiFiBerry DAC+ Pro card (uses Burr Brown DAC) with RCA outputs.
See link below: HiFiBerry Spec Sheet
a Raspberry Pi (think it’s a 3B model)
Metal Case
MicroSD card
Power supply
I bought it because it was already supposed to be Roon-compatible, already assembled, and ready for use. But despite that, I can’t get my Roon install (now on a Mac mini) to recognize it. Both the device and Roon are on the same Ethernet network; I have a Roon-recognized AudioQuest Dragonfly plugged into the device; I’ve checked network settings & firewalls.
When I go online, I find instructions on setting up such a device from scratch using some special screen device (that costs more than the device itself). I profoundly DON’T want to have to reengineer or reprogram this device - the reason I bought it was because I thought it was “plug-and-play.”
Is there some setting I’m missing that would allow Roon to see this?
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
2
But does it have any software already loaded on it?
It will need something like Ropieee or similar on the SD card to be able to work with Roon.
I sold my R-Pi based HiFiBerry DAC Pro+ to someone, and it worked fine in my system. The new owner plugged it in, and Roon doesn’t see it. The Pi is plugged in, hardwired to the web, and even if he goes into Roon’s setup/audio and searches for new devices - the Pi doesn’t show up. The Pi is running RoPieee. His Roon core is on a Mac Mini, FYI.
I’m not sure I understand. The HAT was working when I had it, so Ropieee was working in my home (Windows PC with Roon Core saw it fine). How does he check to see if Roon Bridge has the device listed in Roon Settings? I thought that was done in the Settings/Audio…?
The hat was previously working in my network, so…it was selected. Would that change if someone connected it to their network instead of mine? If so, can you provide a link for how to check that? It’s been so long since I set it up that I don’t even recall doing it.
If the wireless setting was set to DHCP, then the next step is to learn the new IP (through the router settings or a port scanner on the same network).
If set to a static fixed IP, the easiest path is a re-flash (rather than emulate the old network address space, which may be harder to explain and execute).
Or, just do a re-flash now. The process is very quick.