My normally reliable SOtM sMS200 Mini (network audio bridge) is no longer visible as a Roon network zone when Roon Rock is connected via Ethernet to my SOtM - and then onto my Meridian Prime/PSU Headphone Amp/DAC via USB.
A direct USB connection between Prime and Roon Rock correctly identifies Prime as a Roon Zone.
The SOtM front panel activity light flickers as expected when an Ethernet connection is made. The SOtM Eunhasu software menu correctly identifies Roon as the streaming method.
I have checked all cables to ensure they are all fully plugged into their socket inputs/outputs.
I use a direct Ethernet connection between my Router and EE8Switch (network hub), which connects via Ethernet to my SOtM, Meridian 218, and Meridian 210. The latter Meridian devices are both correctly identified as Roon Zones.
I have tried changing the Ethernet cable connecting SOtM to the EE8Switch. Nothing changes. The operational LED on the SOtM illuminates when connected to the EE8Switch.
On my Routerâs software menu, both Roon Rock and the SOtM are identified as connected network devices.
I have tried different permutations of power cycling my Roon Rock and Meridian Prime/PSU, to no avail.
Suggestions welcome.
This old screenshot illustrates what the connection should beâŚ
Oh, i suggest to image the latest version (5.7) onto a low level formatted microSD, see the first post in the linked thread!
You will be pleasantly surprised!
And, there seem to be some issue with your internet access, the SOtM servers are available to me. And your firmware seem to be from last summer.
Thank you for your post. Please see the response from @May_Park in the thread that @Mikael_Ollars has helpfully linked above. Once youâve verified that your SOtM-side settings are configured and the latest image has been flashed per the instructions, if you are still encountering the issue, then try these steps:
yes, the firmware & the kernel version numbers are the old one, please update both to the latest version and test it out. You can follow the instruction here, en:eunhasu:burn_sdcard_image [SOtM docs]
Why canât I simply download the latest software/kernel directly from the server to my sMS-200 as usual, rather than having to use a third-party app to write to a microSD Card?
Because it is the safest and most effective way.
One could argue why SOtM doesnât use Cloud Distribution Networks to allow swifter downloading, but i prefer that they concentrate on what they do so well, optimizing the software for our devices so we can have greatly improved sound quality at no added cost.
And in the given situation, this is most effective and allows for error checking and verifying the image is written correctly.
Please give it a try, itâs not a big chore, and iâm sure youâll like the results.
Since I donât own a MicroSD Card or card writer, I discarded my iPad Pro for my Mac Mini. I subsequently discovered via the Eunhasu app that my sMS-200 was set to âStaticâ rather than âDCHPâ. Once that anomaly was corrected the SOtM Server became visible.
Subsequently, I ran through 2 successive upgrades before I was presented with the most recent mega download. Given that I have a wired network connection between my Mac Mini and my sMS-200 - and a healthy FTTP connection - I chose to engage a download of this large file.
I successfully downloaded the latest v5.7 Eunhasu software on my Mac then into a 32GB microSD card prior to inserting it into my sMS-200 Mini SE.
Then, once Eunhasu is successfully opened on my iPad, Roon is activated, DCHP selected, and the sMS-200 is rebooted - and my Roon Rock NUC is powered-up, I cannot subsequently select my Meridian Prime as my Roon Zone.
Do you have any other USB DAC you can try?
I have two sMS-200 and they work just fine with fw 5.7 and these: Simaudio Moon 280D, Simaudio Moon 430HAD (DAC3), Denafrips Ares II, Audiobyte Black Dragon, Topping E50, Chord Hugo 2, Chord Mojo.
Irritating, that when I insert the older microSD card containing Eunhasu v5.62, and restart my sMS-200, my Meridian Prime is instantly recognised as a Roon Zone.
Had the same problem after updating to FW 5.7 (using the device only as Roon endpoint).
Only after going to the setting site and reload here the Roon setting (which was always shown as active), it appears as endpoint.
Solution for me was: Save the Roon settings again with the used DAC connected.
Touch Wood; I do believe that Iâve resolved the issue.
In the Eunhasu menu; changing the buffer duration and resync delay on the Roon configuration - and on switching-off DSD Mode - resulted in my Meridian Prime being instantly visible as a Roon Zone.
After the firmware update, I needed to go to ROON â SETTINGS â AUDIO to enable/activate the SMS-200 again or it wouldnât be selectable as a device. If nothing works, try that. The device should be showing there under ROON READY.
