Transition MPV in the Jace as 3rd Party device to now being fully hosted by the Jace.
I am sure there is an answer but I wanted to get this out there, but first let me setup the situation. During the process of us doing this beta testing we have an MPV hosted under an ES with the "standard" factory application. Love the self test capability and the application it downloads that when using the E-Commission tool it has functionality built into it as well. Well done and couldn't ask for anything more. So as we have MPVs hosted under the Jace for Beta but we had this "Control" vav and for comparison sake hosted in the ES.
So my question is what is the "best practice" from moving this MPV from the ES to the Jace? I understand I have to unhost the device before I can even wipe the application but what happens to any flow calibration data that was in there. Does deleting the database delete the flow balance data? I am almost certain a factory reset will wipe everything but what about just deleting the application? I guess I am trying to find the best way one could move from the VAV being hosted as a 3rd party device to now being hosted under the Jace.
I bring this up because I have a small project and the customer really wants to use the MPV but wants to use the Jace. By specifications we are required to use the Jace so there is no attempting to try an EBO conversion. I guess my thought would be to set it all up under EBO and then just bring the devices into the Jace as 3rd party and then when the Jace driver and accompanying programming objects are ready to then redo it completely hosted by the Jace. I am open to comments, thoughts or suggestions too!