Just Some Guy
Member
I'm implementing several FTView 8.1 HMI applications for a client which are conversions from RSView32 & I've come across this wonderful idiosyncrasy.
I develop, test and archive the application from station 1, move the archive to the second PC and after restoring it, It is rare that all components work properly, and usually one or more of these doesn't work:
RSLinx Enterprise
Alarm And Event Server
Dataloggers
The workaround I've found for the RSLinx and Alarm servers is to delete the existing and then recreate, but I haven't found a way to get the Dataloggers going on the second station?
Not sure what I'll do once the grace period on the development runs out on the second station?
Now this also ties the client's hands since they cannot simply restore an archive I send them if they have to do the song and dance of deleting/rebuilding... and again, once the development grace period runs out... what then?
Why is this such a POS?
I develop, test and archive the application from station 1, move the archive to the second PC and after restoring it, It is rare that all components work properly, and usually one or more of these doesn't work:
RSLinx Enterprise
Alarm And Event Server
Dataloggers
The workaround I've found for the RSLinx and Alarm servers is to delete the existing and then recreate, but I haven't found a way to get the Dataloggers going on the second station?
Not sure what I'll do once the grace period on the development runs out on the second station?
Now this also ties the client's hands since they cannot simply restore an archive I send them if they have to do the song and dance of deleting/rebuilding... and again, once the development grace period runs out... what then?
Why is this such a POS?