Items in File Association dialog box

Items in the
File Association
dialog box include:
  • File extension
    The file extensions (for example, acd, ccwsln, and rss) to be opened by the designated software product. For binders, specify the file extension of the key file. This field is unavailable when you edit an existing file association. If you want to remove this file type from the list, close this dialog box and use the
    Delete
    button in the
    Options dialog box: File Associations
    instead.
  • Program
    The software product to open files with the indicated extension. Click
    Browse
    to select the software product. For the system to find the software, it must be included in the PATH environment variable or the full path should be specified here as well as the executable filename.
    • For Siemens S7 program files, FactoryTalk AssetCentre includes a utility that finds and opens the editing software for .S7P files. This utility comes set up in the
      File Associations
      dialog box, so there is no need to set file associations for these file types.
    • For Allen-Bradley PowerFlex Drive project files, FactoryTalk AssetCentre associates the *.ccwsln file extension with the Connected Components Workbench software. This association is set up on the
      System Associations
      tab of the
      Options dialog box: File Associations
      by default, so there is no need to set file associations for it manually.
  • Command Arg
    Command line arguments for the software product used to open files of this type. In the context of FactoryTalk AssetCentre, command line arguments are applied when you open a file in Archive. For example, you can use the
    /preset
    command line argument to open the project file in the RSTune Faceplate software for trend analysis.
    For many programs the syntax of command line arguments requires the full path and filename of the file that is being opened. That path (the working folder) and filename can be represented in the command line argument with <filespec>. When you add a new file association,
    <filespec>
    is filled in for you. You can remove
    <filespec>
    or type the rest of the command line argument as necessary. For the RSTune example, the full command line argument would be:
    /preset <filespec>
    Refer to the software program's documentation to find out what command line arguments are available in that software and the required syntax. (For example, for many programs the RSTune example above would be reversed, with <filespec> coming before the command line argument.)
  • Description
    The file name in the
    Program
    field can be very different than the actual product name. Enter the name of the software for clarity. For example,enter
    RSLogix 500
    because people may not recognize that software by its filename of
    RS500.exe
    .
  • Automatically check in file or asset after editing
    Select this box if you want files of this type to be automatically checked in when the editing program is closed. For example, if you want your RSLogix 5 project files to be automatically checked in when you close the RSLogix 5 software, select this option.
  • Monitor Type
    This field is only available if you have selected to automatically check in the file or asset after editing. To know when to check the file in, the FactoryTalk AssetCentre software has to know when file editing is complete. Different programs handle files differently so sometimes the FactoryTalk AssetCentre software should monitor the file and sometimes it should monitor the
    process
    which refers to the running program used to edit the file.
    Choose
    File
    for RSLogix 5, RSLogix 500, RSLogix 5000, Logix Designer, Microsoft Word, and Microsoft Excel.
    Choose
    Process
    for Microsoft Notepad, Microsoft WordPad, FactoryTalk View ME (.mer), DriveTools (.dno), PanelBuilder (.pva), and the Siemens S7 Controllers (STEP7) editor.
    TIP:
    If the software does not behave as expected the first time you open the file after changing the monitor type to
    Process
    , close the file and any messages. Open the file again. It will behave correctly the second time.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal