Recently I had to upgrade an HMI server from Rockwell Automation’s FactoryTalk View SE 6.0 which is a 32 bit system to a Rockwell Automation’s FactoryTalk View SE 7.0 64 bit system while the system was running.
At this point I will not get to far into how that process went although it is a quick and painless process using the best practices that I have developed using Rockwell Automation software. These items that I have developed will make things easily understandable. This process went well and the server is running healthy.
Is Finding ActiveX Files Easy?
I would like to talk on an issue that I have had in the past and maybe you have as well, that is, how to check and add the correct ActiveX files to your HMI Server. You have to use windows CABARC to make a cab file and to also view a current ActiveX file version then you need to use the GetVers. There are many knowledgebase notes on this done but after reading them myself they all refer to using VBA code and can be long and drawn out.
If anyone would like to know the streamline process that I have developed for this please just let me know by emailing me at plcsupport@onlineplcsupport.com and I will be glad to help you out in anyway.
I have made a document that streamline the method that I created using Windows command prompts.
A small example of Windows CMD.exe:
I will be adding this document to the HMI documents section of the site to aid in any efforts regarding Rockwell Automation’s FactoryTalk ActiveX.
Feel free to drop me a line in the comment box if you would like the complete ActiveX process.
Thanks,
Shane
Thank you Shane for bringing this topic to light in your recent post, we have been having issues with these types of ActiveX files. After I emailed Shane@onlineplcsupport.com and they responded we were finally able to fixed the graphic errors that we had.
Thanks,
Brian W.
I very glad that we could help you in resolving this issue.
If you have anything else that we can help with then please stop back by and leave a comment or email and I will get back to you.
Thanks again,
Shane