1. Run-time RAM Usage File integrity checking RecipePlus Run-time file to application file conversion Enhanced language switching New FactoryTalk View ME Features

2. New feature in CPR 9 –Part of the Terminal Configuration settings –Allows for easy monitoring of terminal memory usage at runtime –Can be enabled and disabled via Terminal settings –Can also update memory usage values to HMI tags via Global Connections –Can also be configured to start updating HMI tags via a remote Global Connection When to use this feature? –It is strongly recommended that this feature be used during development and testing of FactoryTalk View ME applications to ensure that they do not exceed the limitations of the hardware. – Do this during development, do not wait until the application is being deployed at the customers site – you need to monitor these values right from the start! FactoryTalk View ME Runtime RAM Usage monitor

3. Global Connections changed to tab format “Memory” tab added for this feature Design time options “Global Connections” FactoryTalk View ME Runtime RAM Usage

4. Terminal Information Configuration Mode Screen Available on the CE Runtime only. Popup will appear every 10 seconds when enabled FactoryTalk View ME Runtime RAM Usage

5. Total RAM Usage and Available RAM –Monitor these two values to determine if the running application consumes the installed physical RAM on the terminal. –You can add more memory to the terminal if these counters show high memory usage. What do the numbers mean?

6. Why enable this feature? –Allows developers to monitor how much memory is used by the application when it is running. –If the application is designed beyond the limitations of the PanelView Plus and PanelView Plus CE hardware, it should be modified to reduce memory usage, or possibly deployed on a PC-based platform such as the VersaView Industrial PC. –As the application is developed and tested, the application must be run on the PanelView Plus or PanelView Plus CE terminal with the ME Runtime RAM Usage feature enabled. The application developer should then navigate to all screens and exercise all functions of the application to monitor memory usage. Best Practices for Optimizing Performance & Memory

7. File Integrity Check New in CPR9. Enabled by default, can be disabled in Terminal Settings. Will slow overall ME application startup time as it examines the files, slowdown is minimal. Warning messages help to identify file corruption issues that had previously caused terminals to be sent back for repair. –EG: Corrupted Alarm log causes blue screen at startup. Validates the following: –Alarm log –Data log –MER –RSLinx Enterprise configuration files: RSLinxNG.xml, DefaultTemplate.xml. HardwareDatabase.xml

8. Ingredients – EG: Water, Salt, Flour –They can be either of type String or Numeric. If numeric, the user can specify a minimum and maximum data value for the ingredient. Numeric ingredients can be boolean, integer or floating point numbers. If you were to add a type ‘String’ ingredient, the ‘Min’ and ‘Max’ value field will be left empty and the data type will be set to ‘String’. Note: One recipe can have up to 15000 ingredients. Data Set – EG: 50, 75, 300 –Each recipe can contain up to 500 data sets. Each data set represents the set of data values where each data value is associated with a specific ingredient. The data sets are to be downloaded (or uploaded) to a controller. The data in the Data Set is saved in the recipe file with the extension.rpp. Tag Set – EG: Tag1, Tag2, Tag3 –Each recipe can contain up to 50 tag sets where each tag set represents the set of tags to write to during a download (or read during an upload) operation. Each of the tag names is associated with a specific ingredient. Units – EG: What you are making –A unit is a data set paired with a tag set. For example, you could pair 10 data sets with a single tag set. This pairing is called units. A single recipe can contain up to 25000 recipe units. The maximum number of data sets is 500 and the maximum number of tag sets is 50. It is the recipe units that are acted upon at runtime (e.g. Download unit). RecipePlus

9. CPR9 will contain Delete/Rename capability RecipePlus

10. CPR9 will contain Language Switching phase2 to include Alarms, Local and Information Messages. Alarm messages will be logged in the current language –As a result the alarm log will contain messages in different languages if you are switching languages at runtime. Only one language can be visible at development time. –You must close Studio and re-open in a different language to edit/work in that language. Use the 4.00 “CPR7+ Runtime Editing improvements, HMI Redundancy replication, and String Spreadsheet editing” patch to add the “Export strings for all languages to an Excel spreadsheet” –This will allow you to edit one spreadsheet for all languages. Answer ID: 34125 Custom String Popup Keyboard ActiveX Control for RSView Machine Edition. –Keypad support for Asian fonts Answer ID: 33400 Make sure the fonts you want to use are linked on the terminal. Language Switching

11. . Language Switching Enhancements CPR9 String spreadsheet editing - text strings for all languages supported by an application can be exported to a Microsoft Excel spreadsheet in one easy operation. You can also import text strings in one or multiple languages from an Excel spreadsheet to an application. Default language - each ME application now has a default language, not necessarily the initial language. Undefined strings are displayed in the default language instead of appearing as question marks. Enhanced language switching - application developers can view user-defined text strings in an application in up to 40 languages, and switch up to 20 languages dynamically at run time. As well, information, alarm and local messages now support language switching.

12. MER to MED Application Conversion Run-time file to application file conversion - beginning with FactoryTalk Machine Edition 5.00, users can create a development file (also called a project file, or.med file) from a run-time file (.mer). This does not apply to.mer files made with earlier versions of RSView

13. RSAsset Security A-P codes can now be entered in the Runtime Editor