An example would be if you had FTView Studio 6.10 and a then-new PV+ 6 600. In addition, some PV+ terminals are oddballs that were released in between revisions of FactoryTalk View Studio, and the software doesn't correctly know which firmware versions they support.
Similarly, any project that used an ActiveX from version 5.10 or earlier has to have that ActiveX removed and replaced with one that's compatible with v6.0 or later. Any runtime or project from v5.10 or before that used KepServer has to be rebuilt and re-created to run on a PV+6 or newer. The biggest one is that the Windows CE version changed with the PanelView Plus 6, which substantially changed the operation of both KepServer and ActiveX components. *Exceptions: of course there are exceptions. Unfortunately I can't verify this with Version 8.10 of FTView Studio my newest machine is Version 7.0, which gives me the option to create a runtime for version 7.0, 6.10, 6.0, 5.10, 5.0, 4.0, 3.2, and 3.10. The 32 bit/ 64 bit database issue when Rockwell Software migrated FTView Studio from Watcom to SQL only affects *.APA archive and project files, not the ability to create runtimes.
Excluding version 3.0 (which only lasted a few months), you ought* to be able to create any older runtime version with a modern copy of FactoryTalk View Studio ME. You can take a *.MER file from a version 3.2 terminal commissioned in 2003 and run it without modification on a brand new PanelView Plus.Īnd it's been pretty good at the creation of runtimes for older firmware terminals. One of the things that FTView Studio ME has actually been very good about historically is backward compatibility of runtime files.
0 kommentar(er)
