"Elite" and "Standard" are just two different SW configurations running on the same HW platforms.
The MPS4 was made in HW platforms V1 and V2. "V2" is written on the front panel whereas "V1" has a VGA port covered at the back that you can reveal.
I have the same installation on both V1 with extra RAM and V2 without. Both work fine, but the V2 is faster so I prefer that model (it has a slightly newer motherboard).
If I were you, I would go for the installation on V2 directly if you have one as it will be easier for us to share experience, but V1 works fine too (even with original HDD).
To get a feeling for the scripting and the set-up, look at one of the very early posts containing code for a basic yet very functional solution: How to install HomeSeer - ChromeCast solution.
. There is a video a few posts earlier. Since then, the code has become very much improved which I will be happy to share once you get to that point.
Also, look at the very first post to find a link to
's install procedure for Win7 and MPS4 SW: Resurrecting an MPS4
(save a copy of your current license, just in case...)
It would be great if you with your fresh eyes could commit to documenting the process and then publishing it?
Approximate steps (to be refined):
A) Install Windows 7.
- follow available write-up in post "Resurrecting an MPS4"
1) Define two to three three partitions (A:Autonomic, B:Media, C:Backup). Windows + Autonomic + HomeSeer on partition A: requires about 25+ Gb.
2) Invest time to make your new Win7 installation really clean and easy to maintain:
- reduce as soon as you can to only one user account: "Administrator" (gain access through CMD instruction: "net user administrator /active:yes")
- configure "auto logon" with password to the account above (https://docs.microsoft.com/en-us/sys...oads/autologon
). Necessary for power cuts and handy to reboot from MSP4 web config page)
- configure remote desktop access to the account above (I use mRemoteNG. It will be good for Telnet, etc... as well.)
The points above are important. Your life will otherwise become miserable if you are going to do further work from your A/V closet!
3) Save restore point
4) Do all the updating in a few iterations (a few years worth, takes some time). Allow automatic downloads, but not installs.
5) Set the firewall to ask before enabling traffic. This way you will configure the firewall as you go. Important.
6) Defragment disk
7) Save restore point
B) Install the MPS4 SW (aka Autonomic SW or MCS)
1) Download installation file USB Firmware update
and follow "Resurrecting an MPS4" (you can skip step 10, IIS) with comments in the adjacent post
2) Configure the MPS4 (http://musicport/Config/
) and get it back to the same functionality that it had before (well integrated with the nuvo concerto, content sources and apps)
3) test thoroughly and do several reboots
4) Save system image and restore points
C) Install Chrome.
- Use, but don't make standard (yet)
D) Install HomeSeer
1) Install HS3 on trial.
- You will not need the "pro" version. If you are still curious about pro, you can install it and downgrade after a pro trial w/o problems.
- You will install a newer .Net framework in this process, but it will not affect your old .Net code used by Autonomic.
2) Configure the port for the HS3 web server to avoid collisions with Autonomic's. I chose 800.
- shut down Autonomic and
its 3 services, then start HS3 and select: http://musicport/setup
. Change server port from 80 to 800 under the network tab. After relaunch, verify at http://musicport:800/setup
3) Install Chromecast plugin, assuming you want to use it (will be freely included in upcoming HS4, get on trial for now)
4) Save restore point
E) Enable serial communication between Nuvo and HS3
- have a look at post Internal Serial Communication
and simplifications in 246 and 256
1) Install the free port splitter VSPE to share port #1 (for V2) used internally by the MPS4 with a virtual one that you need for Nuvo protocol serial communication to HS3 (e.g.#5)
2) You will need to fire up a configuration file for the app at startup BEFORE Autonomic takes control of port #1. (edit registry)
- We have found no other way of starting the MPS4 service successfully other than allowing for an undisturbed boot sequence. Scheduling the boot events for Autonomic, HS3 and VSPE is a little touch-and-go and varies depending on V1/V2, RAM and SSD. VSPE should always be fired immediately, before Autonomic. For V2 w/o RAM, I let HS3 start after 15 seconds. For V1 with RAM but HDD, I had to wait 120 seconds. (We can elaborate on this when you are ready to automate the full sequence.)
3) Save restore point
0) install a few handy tools for scripting and debugging (let's discuss later)
1) start getting some basics running to understand how it works.
2) then we can discuss in more detail depending on your needs. Maybe
will have a whole package ready to install, but in any case we both have special tricks that you may want e.g. Spotify playlists on the MPS4, Sonos zone control, etc...
(don't quote this post as it will be edited)