So happy to report that the MD600 is working well, as is the MS200. However, the MC600, not so much. My challenge is that I am not 100% sure this is a v2.435 upgrade issue. I moved the MC (new house, new network) with the arrival of the MD and didn't bother setting up until the update came. Foolishly I didn't remember to undo the static IP. Despite this, the update came and was able to connect via Control:PC, was prompted for the upgrade and confirmed. At that point it all went downhill.
In the reboot, I seemed to have lost a drive and communication. I rebooted the unit a couple times and still telling me there was an issue with HD#2. So over the week got the HD (2, just in case) and last night added the second, restarted and allowed for the unit to replicate. So this morning, was expecting all to be fine.
While these are no blinking lights indicating a HD failure, I still cannot communicate with the MC600. I can see the IP when I scan the IP but even when I try to connect directly via the IP, the connection timeouts. I worry that the disk drive failure during the upgrade might have caused an issue?
Sometimes I feel like I am the the only person who owns a MC600, but wondering if there are any issues with this line specifically?
Thank you
Primary: MD600, MS200 (SpeakerLink to AES), Trinnov ST-2, Ayre V6-xe, Salk SS8 3x LRC. Secondary: MC600 (whole house). Zone one: 568.2, G57, MS200, Spatial Hologram M2SE. Zone 2-6 (Awaiting assignment).
Google Search
|
Meridian Systems
|
Meridian Streaming
|
Restaurant
|
WiKi
|
Duncan's Meridian Info
|
Board Rules
|
Restaurant Rules
