Rendu Support Thread

[esmit]

2 hours ago, arrjmai said:

What do you guys think of this unit? I just posted that I bought microrendu direct from the company the refurbished one and it didn’t work then I have offered to replace the micro sd card. I just received the micro sd  card and as I show in these videos. It still didn’t work. What do you guys think if anything wrong with the unit?

1 voltage I used in the video is 8.6v1a (I tried adjust voltage several between 7-9v all are the same result)

2 micro sd card click locked in place

3 both microrendu and MacBook connected direct to the same router 

4 nothing works

 

 

 

 

 

 

 

F126A240-6F94-4887-B5C0-324E6DE51005.MOV

ED3DA3F6-6115-4C05-B179-2DFE01AE2086.MOV

6FB15F87-AAE3-4358-8DB5-064DEE5BC1B7.MOV

I could not see in your movie if the green light on the network connection also starts to blink when you connect network and power. Does it?

 

If so, your router should see it. Make sure it is on DHCP, by the way. And open the sonicorbiter site in the privacy mode of your browser to make sure caching is not a problem.

[esmit]

4 minutes ago, stevebythebay said:

Thanks.  I know this is supposed to work.  I think some sort of networking problem is happening.  Wondering if this is the right place to get an answer.  I don't see any unusual configuration action.  The IP addresses are remaining correctly assigned so it wouldn't seem to have anything to do with DNS, and it's all within my local network.  Everything looks good on the microRendu side (though I'm hard pressed to understand both the DAC Diagnostics page or the Roon Ready Diag page.  Guessing one or both may help find the underlying problem.  

 

Hoping Jesus sees the post and works with me on this strange situation.

They do have a different System name, don't they?

[esmit]

I do not need an update in any way - microRendu and ultraRendu working fine - but I get an error when trying to update: Cannot resolve sonicorbiter.com. Upgrade does not start. Your DNS might not be working. Server down? My DNS seems to be working fine.

[esmit]

On 6/17/2018 at 1:21 PM, vortecjr said:

If you have a VPN you need to disable it. 

I do not have VPN (as far as I am aware), and I am able to install packages (just installed mpd to check), but updating still gives this error. Are there any ports that should be open for this to work, or other things to check? I can ping sonicorbiter.com:

Pinging sonicorbiter.com [66.241.100.214] with 32 bytes of data:
Reply from 66.241.100.214: bytes=32 time=232ms TTL=50
Reply from 66.241.100.214: bytes=32 time=186ms TTL=50
Reply from 66.241.100.214: bytes=32 time=170ms TTL=50
Reply from 66.241.100.214: bytes=32 time=180ms TTL=50

and tracert:

Tracing route to sonicorbiter.com [66.241.100.214]
over a maximum of 30 hops:

  1    31 ms   286 ms    32 ms  192.168.178.1
  2     *        *        *     Request timed out.
  3    14 ms    29 ms    11 ms  gv-rc0011-cr101-ae98-0.core.as9143.net [213.51.174.233]
  4    93 ms    21 ms    42 ms  asd-rc0001-cr101-bundle-ether106-1.aorta.net [84.116.194.73]
  5     *        *        *     Request timed out.
  6    22 ms    99 ms    18 ms  nl-ams09b-ri1-ae5-0.aorta.net [84.116.134.54]
  7    52 ms    59 ms    17 ms  213-46-161-146.aorta.net [213.46.161.146]
  8   112 ms   141 ms   134 ms  xe-8-3-0.cr0-nyc2.ip4.gtt.net [89.149.134.46]
  9   120 ms   124 ms   114 ms  ip4.gtt.net [69.174.2.90]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   174 ms   202 ms   174 ms  66.241.100.214

Trace complete.

 

[esmit]

3 hours ago, esmit said:

I do not have VPN (as far as I am aware), and I am able to install packages (just installed mpd to check), but updating still gives this error. Are there any ports that should be open for this to work, or other things to check? I can ping sonicorbiter.com:

Pinging sonicorbiter.com [66.241.100.214] with 32 bytes of data:
Reply from 66.241.100.214: bytes=32 time=232ms TTL=50
Reply from 66.241.100.214: bytes=32 time=186ms TTL=50
Reply from 66.241.100.214: bytes=32 time=170ms TTL=50
Reply from 66.241.100.214: bytes=32 time=180ms TTL=50

and tracert:

 

 

Rebooting all stuff seems to have helped.

[esmit]

9 minutes ago, TheAttorney said:

I don't understand that recommendation. I already have the V1.4 H/W and V2.6 S/W. Whate else is there to update?

I hit Update alle the time. Almost every week there is a minor update although the version number stays 2.6.

[esmit]

1 hour ago, vortecjr said:

It's just the way Linux works and not all DACs are created equally. My DAC does not have this issue. 

I am happy my DAC also does not have this issue but the Rendu's are just running software and software can be resilient. Rechecking, double-checking, using alternative routes might be possible, but not necessarily easy, or indeed possible when depending on third party drivers or OS.

[esmit]

6 minutes ago, Distinctive said:

Are you saying that my network influence üR DAC-discovery on it’s USB output?

üR always turn up in Fing with the same IP given by DHCP and always respond when I ping it. My high capacity network is pretty solid so this will be surprising.

I have also tried connecting the üR directly to my router.

I have tried many DAC’s and the most successful was the Chord Mojo.

 

 

 

I once had a similar problem in combination with my Chord TT. It turned out to be that the usb connector on the TT had cracks in it, but it gave the same symptoms. Maybe the usb connector on your Rendu needs a check, with magnifying glasses? And make sure it gets the right voltage, when my microRendu got just 5v it was a bit flaky too.

[esmit]

4 minutes ago, Distinctive said:

Thx. I am using the recommended Ifi iPower 9V supply bought together with the üR. I am also sometimes using the Uptone LPS-1 powered by a battery.

Ok that leaves the USB port on the uR to check. My TTs usb port got loose because of frequent insertion and wobbling of the rigid uspcb isoregen usbpcb ultrarendu stack.

[esmit]

On 8/27/2018 at 5:03 PM, charlesphoto said:

I get this problem occasionally using the Bridge app to feed Roon to my Naim. Lots of restarts and it usually goes away but frustrating. 

 

The times I got this I re-did the link between Roon and Tidal and that seemed to work.

[esmit]

3 hours ago, ksalno said:

Thanks, I ordered two cards earlier today, anticipating that might be the answer. Weird that two would go bad at the same time, while the microRendu soldiers on.

You can try your microRendu card in the ultraRendu to check.

[esmit]

3 hours ago, ksalno said:

I replaced the two SD cards in my two failed ultraRendus. The first one booted up fine with the new card. The second one didn't. The LED goes from red to orange but never goes green. Device is not seen by mysonicorbiter.com. Any other ideas?+

Switch power supplies and check again?

[esmit]

25 minutes ago, Blake said:

Hi, I updated my software to 2.8, rebooted, but the version still shows as 2.7.  I tried multiple times.  Any suggestions?

 

Yes. The 2.8 version is on a new sdcard you can buy from Sonore or one of its partners, with a much newer version of the OS (as has happened once before). The page just indicates it is available.