Daniel,

In regards to other migration issues, please do tell!   I tested the migration/sync scenario twice yesterday.  Interestingly enough, the case where I had a time server on the LAN, nvoRtTimeDate maintained the correct time after the migration/sync. But the case where I didn't have a time server on the LAN, the time stored in nvoRtTimeDate froze upon syncing, I believe.  I will retest this case today. 

Hello Jonathan,

Yes there were other migration issues. I can't remember all of them. One issue was with the TypeTranslator, which I tried to solve with the Echelon Support. As we didn't find the problem, I decided to manually recreate all the TypeTranslators according to my logic. Now the TypeTranslators work fine. There was also an issue with the bindings between the functional blocks. Here too: after recreating all the bindings manually, it worked.

Therefore I decided to manually recreate the whole network (!), all FB's and all bindings. Now it seems to work. But the nvoRtTimeDate is still frozen. As the Smart is Standalone, I can't have a time server on the LAN.

Thanks and best regards,
Daniel