Renderer V2 Module has failed!

Hello MSB People,

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

Checked your network cables?

1 Like

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.

1 Like

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.

Thanks and a Happy Weekend to all!

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.:grinning:

1 Like

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.

Plugged into the HIFI Switch And the Switch connect to the Router.

Antipodes K50 & Wadax plugged into the Switch directly the same as.

I can almost confirm that it was caused by the network cable,but I’m still not sure what the specific reason is.:joy:

1 Like