Thanks Anup,
The network troubleshooting link given there is very informative, and helpful:
2 Likes
Thanks Anup. My Nucleus was installed and hardwired via Ethernet by my audio dealer. In this configuration, I had used my Nucleus with my previous DAC, the Ayre QX-5 without indecent for months.
It’s been only 3 weeks since I’ve owned the Rossini that this problem occurred. Maybe it’s quincentennial, but suspicious? Anyway, I’ll check into the Roon as a possible cause and call my dealer later tomorrow for troubleshooting.
I turned my Rossini DAC, Rossini clock, and Roon Nucleus off all night and lo and behold, when I turned everything back on this morning, everything is working again! I guess that it needed it’s head cleared? When I initially had the problem, I forgot to reboot my Roon Nucleus. Maybe doing that might have solved the problem?
Thanks to all who replied with their help and suggestions.
Bob…I also have a Roon Nucleus with a Samsung SSD, connected to my Bartók. I get that error message from Roon quite often. Infact, just a couple of days ago.The error message last Saturday was when I was playing Internet radio. I have contacted Roon support, still waiting to hear back.
I think it’s definitely a Roon issue as I got an error message whilst demoing a Auralic Vega. (Before I ordered the Bartók)
Hi Bob…Thanks for your reply.
A reboot appears to solve most issues, but something must have triggered it initially. I turned my Bartók off from the back of the unit, same with the Nucleus. Left it for two-three minutes, switched both back on, all back to normal.
Funnily enough, whilst typing this message, Roon support have sent me an email.
"Can you please try to reboot your Nucleus via the Web UI and power cycle that DAC as well?"
For both of us, this has clearly worked. But as I’ve said, something in Roon bust be triggering this.
As this is not a dCS issue, our ‘Admin’ may prefer us to discuss this elsewhere? 
David,
I deleted my last post and the quote from my dealer in my last reply as I don’t want to get them negatively involved as they were only speculating their thoughts in a private e-mail to me as to possible causes of my problem. Incidentally they are a well respected high-end dealer in my area and their troubleshooting has always been first rate in resolving problems such as this.
Since my Ayre QX-5 DAC paired with my Roon Nucleus via my same Network never gave problems in playing music, from either my library or Qobus, and the Rossini and its external clock were the only recent changes to my system when the problem occurred, they became suspect.
Since my new Rossini & it’s external Rossini clock are very expensive components and I put my faith, trust, and hard earned money towards their company with my recent DCS purchase, I would only hope that DCS would be helpful in resolving my problem if it becomes a reoccurring issue.
1 Like
I searched the Roon Community and it looks like the same problem has occured with not just dCS and Auralic, but also Oppo, MSB, and quite a few other Audio devices.
That being the case, if I were to venture a guess, I’d say the problem has to do with Roon Core’s communication to its end-point - i.e. the RAAT stack within the Roon Ready Audio Devices; for some reason that TCP session between the Core and RAAT end-point goes haywire, and only a reset of that link resolves the issue.
I’d guess the issue should be “easily” fixable once Roon support has replicated and identified the problem 
1 Like
I agree with you Anup 
…The Roon post relating to the ‘Auralic’ is mine. So it’s not just happening to dCS products.
1 Like
Hi Bob…
For what it’s worth…before I demoed the Auralic, dCS Bridge and Bartók, I had a Matrix Audio, Pro Sabre MQA DAC, connected directly to the Nucleus by USB (Not an ideal setup) I didn’t have any connection issues or error messages. Obviously the sound was nowhere near to that of the Bridge or Bartók.
1 Like
There are known issues with the network board:
1 Like
Erno…It is possible, that these are two separate issues.
The issue I have, I believe is a Roon issue, as I had the same on a Auralic Vega G2 that I was demoing, before finally choosing the Bartók.
robertt and Billk are experiencing connection problems with their dCS unit, but in a different way.
I don’t know if their issues included the use of Roon?
It is difficult to determine where the problem(s) come from: either or your network setup, Roon, the proprietary Auralic Lightning Streaming framework, or the proprietary dCS implementation of Mosaic and the StreamUnlimited network board they use.
1 Like
My case is a bit different as I only lost I lost connection once with my network when I powered down my Rossini DAC to install a RS232 cable between my Rossini DAC and my Rossini clock. It was only after powering my Rossini DAC back on after installing the RS232 cable that the Rossini would no longer communicate with my Roon Nucleus until I rebooted the Nucleus. Otherwise my former Ayre DAC worked perfectly with my Roon Nucleus in my network for over the 3 months until I bought DCS Rossini, and then perfectly with it too until I powered the Rossini down to install the RS232 cable between it and it’s clock. Otherwise, in my setup I’m having no issues.
BTW, my dealer originally connected my network to my Ayre DAC and then the DCS. What he said which I deleted from this DCS thread above applies to my situation only and not to the others here who are appearing to loose connection with their DCS and Roon Nucleus spontaneously.
Roon just published Roon 1.7 Build 710, which contains stability improvements for the device discovery protocol. It might be useful to update, and see if it improves current issues.
3 Likes
Thanks Erno…just done that.
Thanks for the reminder Erno.
I received the update reminder this morning from Roon and hope that this will stop the losses in communication between my Rossini DAC and Roon Nucleus.
Sorry Erno, if I’ve slotted this message into the wrong part of the thread…but, I’ve just had a reply back from Roon, re communication issues. I have asked then to explain it in ‘Layman’s Terms’ as I’m not overly Tech savvy. I sent them my Roon Logs, and this was the gist of their reply.
“It looks like Roon tried to request the supported formats from the dCS and it didn’t get a response back. I’m also seeing a few general network timeouts in the logs”.
Not sure what they mean about, “Tried to request supported formats from dCS?”
Roon has to bind itself with a dCS endpoint, in your case the Bartók. It has to check its network state, wireless or wired. It needs to know how that network state is configured, so it requests for the supported formats of the Bartók. Bartók, while firing up, booting, is checking for its own configuration and network state, and communicates that with Roon.
If you look into the logs of this process, not everything seems to run smoothly. But in about 12 seconds everything settles and runs as intended, most of the time
The logs look like this:
20201215 16:39:41.281 Watchdog: Starting app: /usr/bin/scwd
scwd.cpp:33 scwd version:1.99
scwd.cpp:34 Copyright (c) StreamUnlimited Engineering GmbH.
20201215 16:39:43.951 [745.745] CRIT: ScwProcess.cpp:50 ScwProcess: "killall udhcpc" finished with error code: 1
20201215 16:39:43.952 [745.745] CRIT: ScwProcess.cpp:52 ScwProcess output: "killall: udhcpc: no process killed"
20201215 16:39:44.068 [745.745] INFO: AutoIpD.cpp:44 Stopping autoipd on eth0
20201215 16:39:44.352 [745.745] CRIT: ScwProcess.cpp:50 ScwProcess: "avahi-autoipd -k eth0" finished with error code: 1
20201215 16:39:44.353 [745.745] CRIT: ScwProcess.cpp:52 ScwProcess output: "Failed to kill daemon: No such file or directory"
20201215 16:39:44.373 [745.745] CRIT: InterfaceWired.cpp:347 Couldn't read status from wired interface carrier file:"/sys/class/net/eth0/carrier"
20201215 16:39:44.409 [745.745] WARN: NetworkManager.cpp:728 Coludn't find wireless interface, retry 1 of 5
20201215 16:39:45.412 [745.745] WARN: NetworkManager.cpp:728 Coludn't find wireless interface, retry 2 of 5
20201215 16:39:46.416 [745.745] WARN: NetworkManager.cpp:728 Coludn't find wireless interface, retry 3 of 5
20201215 16:39:47.419 [745.745] WARN: NetworkManager.cpp:728 Coludn't find wireless interface, retry 4 of 5
20201215 16:39:48.422 [745.745] WARN: NetworkManager.cpp:728 Coludn't find wireless interface, retry 5 of 5
20201215 16:39:49.425 [745.745] WARN: NetworkManager.cpp:760 Interface"wlan0"is missing, wireless interface is disabled!
20201215 16:39:49.463 [745.745] INFO: scwd.cpp:66 Finished setting up, starting main loop...
20201215 16:39:49.468 [745.745] INFO: AddressManager.cpp:40 Address Manager entering state:NothingUp
20201215 16:39:49.518 [745.745] CRIT: ScwProcess.cpp:50 ScwProcess: "ip -4 address flush dev wlan0" finished with error code: 1
20201215 16:39:49.519 [745.745] CRIT: ScwProcess.cpp:52 ScwProcess output: "ip: can't find device 'wlan0'"
20201215 16:39:49.523 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: disabled
20201215 16:39:49.538 [745.745] INFO: NetworkManager.cpp:92 Entering state:"OffMode"
20201215 16:39:49.541 [745.745] INFO: InterfaceWired.cpp:272 eth0 disabling...
20201215 16:39:49.545 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"
20201215 16:39:49.549 [745.745] CRIT: InterfaceWired.cpp:347 Couldn't read status from wired interface carrier file:"/sys/class/net/eth0/carrier"
20201215 16:39:49.565 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: disabled
20201215 16:39:49.569 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: disabled
20201215 16:39:49.600 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"wlan0"
20201215 16:39:49.603 [745.745] WARN: NetworkManager.cpp:887 No such interface:"wlan0"
20201215 16:39:49.623 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"
20201215 16:39:49.629 [745.745] CRIT: InterfaceWired.cpp:347 Couldn't read status from wired interface carrier file:"/sys/class/net/eth0/carrier"
20201215 16:39:49.673 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"
20201215 16:39:49.677 [745.745] CRIT: InterfaceWired.cpp:347 Couldn't read status from wired interface carrier file:"/sys/class/net/eth0/carrier"
20201215 16:39:49.792 [745.745] INFO: NetworkManager.cpp:1045 COMMAND: Received wireless networks:()
20201215 16:39:49.823 [745.745] INFO: NetworkManager.cpp:1112 COMMAND: Setting Wired Ip to DHCP settings:QMap()
20201215 16:39:49.826 [745.745] INFO: InterfaceWired.cpp:291 eth0 reloading IP...
20201215 16:39:49.862 [745.745] INFO: NetworkManager.cpp:975 COMMAND: Setting normal mode:"automatic"
20201215 16:39:49.871 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"OffMode"
20201215 16:39:49.873 [745.745] INFO: NetworkManager.cpp:92 Entering state:"AutomaticMode"
20201215 16:39:49.874 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredStateContainer"
20201215 16:39:49.874 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredWaitingState"
20201215 16:39:49.876 [745.745] INFO: InterfaceWired.cpp:278 eth0 enabling...
20201215 16:39:49.882 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WirelessStateContainer"
20201215 16:39:49.884 [745.745] INFO: NetworkManager.cpp:92 Entering state:"AutomaticWirelessEnabledContainer"
20201215 16:39:49.885 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WirelessWaitingState"
20201215 16:39:49.887 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: disabled
20201215 16:39:49.890 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waiting
20201215 16:39:50.273 [745.745] INFO: NetlinkWatcher.cpp:83 Netlink received interface status update: eth0: +UP +RUNNING -LOWER_UP -DORMANT
20201215 16:39:50.274 [745.745] INFO: InterfaceWired.cpp:322 eth0 Cable plugged in
20201215 16:39:50.276 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waiting
20201215 16:39:50.283 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waitingInterfaceRunning
20201215 16:39:50.363 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WiredWaitingState"
20201215 16:39:50.364 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WirelessDisabledState"
20201215 16:39:50.365 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WirelessDisabledState"
20201215 16:39:50.365 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredIpsetupState"
20201215 16:39:50.366 [745.745] INFO: InterfaceWired.cpp:284 eth0 activating...
20201215 16:39:50.446 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waitingInterfaceRunning
20201215 16:39:50.447 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: ipRunning
20201215 16:39:50.463 [745.745] INFO: IpConfiguration.cpp:88 Starting dhcp client"/sbin/udhcpc"w/args:("-f", "-x", "hostname:dcs-bartok", "-i", "eth0", "-s", "/usr/share/scwd/scwd_udhcpc.sh")
20201215 16:39:50.483 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waitingIpSetup
20201215 16:39:50.498 [745.745] INFO: NetlinkWatcher.cpp:83 Netlink received interface status update: eth0: +UP -RUNNING -LOWER_UP -DORMANT
20201215 16:39:50.501 [745.745] INFO: InterfaceWired.cpp:330 eth0 Cable unplugged
20201215 16:39:50.506 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waitingIpSetup
20201215 16:39:50.507 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: ipRunning
20201215 16:39:50.521 [745.745] INFO: InterfaceWired.cpp:314 eth0 ip setup returned an error: "dhcpc: eth0: an error occurred!"
20201215 16:39:50.528 [745.745] CRIT: IpConfiguration.cpp:144 eth0 : An error occurred in the dhcp client 1
20201215 16:39:50.542 [745.745] INFO: IpConfiguration.cpp:138 eth0 : dhcp client process finished, exit code: 0
20201215 16:39:50.551 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: disconnected
20201215 16:39:50.580 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WiredIpsetupState"
20201215 16:39:50.581 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredWaitingState"
20201215 16:39:50.581 [745.745] INFO: InterfaceWired.cpp:278 eth0 enabling...
20201215 16:39:50.582 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: disconnected
20201215 16:39:50.583 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waiting
20201215 16:39:52.180 [745.745] INFO: NetlinkWatcher.cpp:83 Netlink received interface status update: eth0: +UP -RUNNING -LOWER_UP -DORMANT
20201215 16:39:52.180 [745.745] INFO: InterfaceWired.cpp:330 eth0 Cable unplugged
20201215 16:39:54.180 [745.745] INFO: NetlinkWatcher.cpp:83 Netlink received interface status update: eth0: +UP +RUNNING +LOWER_UP -DORMANT
20201215 16:39:54.181 [745.745] INFO: InterfaceWired.cpp:322 eth0 Cable plugged in
20201215 16:39:54.185 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waiting
20201215 16:39:54.186 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waitingInterfaceRunning
20201215 16:39:54.234 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WiredWaitingState"
20201215 16:39:54.235 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WirelessDisabledState"
20201215 16:39:54.235 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WirelessDisabledState"
20201215 16:39:54.236 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredIpsetupState"
20201215 16:39:54.236 [745.745] INFO: InterfaceWired.cpp:284 eth0 activating...
20201215 16:39:54.268 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waitingInterfaceRunning
20201215 16:39:54.269 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: ipRunning
20201215 16:39:54.269 [745.745] INFO: IpConfiguration.cpp:88 Starting dhcp client"/sbin/udhcpc"w/args:("-f", "-x", "hostname:dcs-bartok", "-i", "eth0", "-s", "/usr/share/scwd/scwd_udhcpc.sh")
20201215 16:39:54.272 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: waitingIpSetup
20201215 16:39:55.487 [745.745] INFO: IpConfiguration.cpp:103 eth0 Finished setup, parsing dhcp data from output:
20201215 16:39:55.488 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "udhcpc (v1.23.2) started"
20201215 16:39:55.488 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "Sending discover..."
20201215 16:39:55.488 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "Sending select for xxx.xxx.xxx.xx..." [IP address of Bartók]
20201215 16:39:55.488 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "Lease of xxx.xxx.xxx.xx obtained, lease time 86400"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_INTERFACE=eth0"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_IP=xxx.xxx.xxx.xx"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_NETMASK=255.255.255.0"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_GATEWAY=xxx.xxx.xxx.1"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_DNS=89.101.251.228 89.101.251.229"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_DOMAIN=dynamic.yyy.zz" [WLAN address]
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:105 Dhcp output: "SCWD_FINISHED"
20201215 16:39:55.489 [745.745] INFO: IpConfiguration.cpp:131 eth0 Dhcp settings: "xxx.xxx.xxx.xx" "255.255.255.0" "xxx.xxx.xxx.1" "89.101.251.228 89.101.251.229"
20201215 16:39:55.512 [745.745] INFO: InterfaceWired.cpp:303 eth0 ip setup finished sucessfully
20201215 16:39:55.514 [745.745] INFO: InterfaceState.cpp:34 Interface eth0 exiting state: waitingIpSetup
20201215 16:39:55.515 [745.745] INFO: InterfaceState.cpp:29 Interface eth0 entering state: ready
20201215 16:39:55.516 [745.745] INFO: NetworkManager.cpp:97 Exiting state:"WiredIpsetupState"
20201215 16:39:55.517 [745.745] INFO: NetworkManager.cpp:92 Entering state:"WiredConnectedState"
20201215 16:39:55.518 [745.745] INFO: AddressManager.cpp:45 Address Manager exiting state:NothingUp
20201215 16:39:55.518 [745.745] INFO: AddressManager.cpp:40 Address Manager entering state:WiredUp
20201215 16:39:55.788 [745.745] CRIT: ScwProcess.cpp:50 ScwProcess: "ip -4 address flush dev wlan0" finished with error code: 1
20201215 16:39:55.789 [745.745] CRIT: ScwProcess.cpp:52 ScwProcess output: "ip: can't find device 'wlan0'"
20201215 16:39:55.821 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"
20201215 16:39:55.871 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"
20201221 10:47:11.580 [745.745] INFO: NetworkManager.cpp:877 COMMAND: Getting interface details for"eth0"So is it the case…Roon Nucleus is checking the credentials of the Bartók, and at the same time, the Bartók is checking the credentials of Roon?
Whilst this occurring, there is a void, and occasionally a drop in communication between the two?
Or, something like that!
Roon speaks RAAT, and the Bartók is speaking it back, or something like that indeed 
And sometimes they do not listen well, and/ or talk too much 
RAAT (Roon Advanced Audio Transport) is the backbone of Roon’s audio distribution technology.
It is designed to support a wide range of software and hardware applications without format support restrictions or quality compromises. It provides rich user experiences by integrating with displays, buttons, volume controls, and source switching capabilities.
In November of 2015, we released the Roon Ready SDK to hardware manufacturers to enable them to create hardware products that speak RAAT.
The details:
1 Like