PLCViewerApp required and optional information

Before you configure the PLCViewerApp, you must gather information about the PLC environment whose code execution you want to monitor while running a ViewApp.

• You are expected to be knowledgeable about your production environment. You must specify the names of the following components to configure the PLCViewerApp:

  • Communication Driver Object, also known as a DI Object (OPCClient or DDESuiteLink Client)

  • OI Server path

  • Scan group

• Source logic file (Required)

  You must export a Rockwell, Schneider Electric, or Siemens Step7 source logic file (L5X, ZEF, or S7X) that contains data from your PLC environment and place it in a folder location accessible to the computer hosting the System Platform IDE.

• Asset mapping file (Optional)

  The asset mapping file provides alias information for mapping context to a tag name in a specific controller. You can create an optional asset mapping file and place it in a folder location accessible to the computer hosting the System Platform IDE. For instructions to create an asset mapping file, see Create an asset mapping file.

• Translation file (Optional)

  The PLCViewerApp includes a default translation file that defines function block layouts for Rockwell 30 ladder functions. If you want to show additional data associated with data structures or add layouts for functions that are not included in the default translation file, you can create an optional translation file and add it to the PLCViewerApp. For instructions to create a custom translation file, see Create a translation file. For instructions to add a custom translation file to the PLCViewerApp, see Integrate information from a custom translation file.