Recently, the Renderer V2 module (Fireware R2.10R) did’t worked,I have tried many solutions but cannot sloved it. Has anyone else encountered this problem?
The specific situation is that the Renderer V2 module cannot obtain the IP address, Restarted the Router & network switch and the DAC, restarted the Roon Server..Re-flash the DAC firmware (The latest version 37.21), but the Renderer v2 IP Address show is 127.0.0.1 in the LED Display.
So I can’t find it in Audio tab of the Roon. All others Roon Ready devices are working.
BTW, I have also replaced the slot from A move to B/C/D, but the problem still.The LED of Renderer v2 module is working.I have used MSB products for many years and have never encountered this problem before. Thanks
This happened to me before, and I blamed the etherRegen Ethernet switch. I got in touch with the UpTone guys, and we debugged.
In short: Roon is extremely busy on your network. I rebooted my system, starting at the cable modem, then router, and network switch. By the time I restarted the whole system, everything worked.
Just my experience, of course. Look into your network before going much further. Simplify it, try another device from the cable that runs to the Renderer, temporarily disconnect other devices.
The only times I could not find the Renderer in Roon, it was the network’s fault.
Not saying that a Renderer can’t have a fault though. Just not sure how to check it yourself, unless you have a buddy with an MSB DAC.
When this IP address is reported, it means the Renderer has turned on, but your network hasn’t issued the DAC an IP address. I would check between the DAC and your home router.
If it reported 0.0.0.0 it would indicate a different problem.
Ensure you have not turned off DHCP on your network. Based on its network behavior, the renderer is configured for the network’s DHCP source to assign an IP address if you’ve assigned a static IP it’s likely the renderer will fail to receive an expected IP assignment.
if you’ve assigned it a static. The next time it reboots it will expect a new assignment which your DHCP host won’t assign it.
It works, but the cause of it cannot be explained at present.
I was changed the another network cable it works @jvdijk but actually, I had replaced the network cable before. My system works two DAC now, MSB DAC and Wadax Studio Player.
When the Renderer v2 can’t display in the roon app, I was used the network cable of Wadax Studio Player to connect the Renderer V2, the same! so at that time, I didn’t think it was a problem with the network cable. The I was tried to the network cable to connect my Antipodes K50, it works.
Today, I’m rethinking this issue and found the MSB DAC and Wadax Studio Player are using the same model network cable, I’m considering whether it’s really caused by the network cable,I decided to plug the network cable from connected to Antipodes K50 move into the Renderer V2, Unexpected things appeared, the Renderer V2 works in my roon app.
The network cable connected to the Antipodes K50 is a very cheap one. Up to now, I still can’t understand how this issue was caused? I have been using MSB DAC for seven years,this is the first time I’ve encountered it @Jonathan_Gullman Thank you for your analysis which has inspired me.
Is your MSB plugged into an Ethernet router/switch/hub, or instead hooked directly up to the Antipodes? I know Some players have a direct Ethernet connection to hook up the DAC to.
I have seen these on devices, but never interacted with one. The “bridge” Ethernet function would require some study for me, but, I have no practical experience with this type of connection.
I am having the exact issue after adding the renderer to a digital director. I have tried everything that has been tried above and nothing. I have rebooted every device, changed ethernet cables. I have rebooted the router to hopefully initiate DHCP. Nothing comes up when using msbtech.local. Taken any other Roon endpoints off the network. Nothing. Only thing I can think of is I have never updated the firmware since I bought the Premier many years ago. Could this be it and is there a way to update firmware when nothing sees the renderer? SOS SOS
Have you tried to delete the Digital Director and install the Renderer on the Premier? Delete the ISL module from the Premier, delete all Premier connections, and leave only power + Renderer module.
If it is not seen like this… I don’t know other tips, unfortunately
The last time Roon could not see the Renderer v2 in my system, it was a VLAN issue. The Renderer stayed on the default 192.168.1.1 subnet, while I had moved everything else to my own VLAN addresses. The network bridge configuration could be involved for people who use that in their dedicated music server with that function. I could even see a situation where the music server could play music (not Roon), while the main network could not “see” the Renderer, or do updates.
It would be nice to be able to assign a fixed IP address. Does it still show up as an audibleOS device, or something like that? Being able to see it as the MSB Renderer v2 in the network diagram might be helpful too,.
With the Renderer not functioning for whatever reason, you could try updating DAC/DD firmware via SPDIF or USB connections. SPDIF from a computer is less common than it once was though, and tricky to get it bit perfect. (My first forays into computer audio involved this process a few decades ago)
If you don’t have a USB module, you can find cheap USB to SPDIf adapters for a computer to be able to update your firmware. Roon, or other simple music players should be able to use that device to play bit perfect to your DAC.
Thanks for the info. Great higher level networking troubleshooting!!! I have had trouble with the Renderer staying “visible” since I have had it. Vince went over several troubleshooting ideas with no resolution…Thanks Vince. Using the msbtech.local command would never bring up the Renderer. What is odd is all the other Roon endpoints on my network show up with never an issue. Vince issued me an RMA and it is on its way to sunny California. I am curious what the issue may be.
