Set up Direct Drives Connectivity

  1. Create or open a project.
  2. From the toolbar, select Template Libraries, and from the Scripts Library select the Direct Drive Connectivity script.
  3. Drag the Direct Drive Connectivity script to the NetLogic folder in the project structure.
    The NetLogic folder is updated with the following objects:
    • NetLogic[Folder]
      • UpdateRateEnum[DataType]
      • DriverTypeEnum[DataType]
      • DirectDriveConnectivity[Folder]
        • DriveConnectionDesignTimeNetLogic[NetLogic Script]
        • DriveConnectionRuntimeNetLogic[NetLogic Script]
  4. Navigate to the Product Compatibility and Download Center (PCDC), and select Download by Product.
    See https://compatibility.rockwellautomation.com/Pages/home.aspx.
  5. In the search field, enter Optix
  6. Select FactoryTalk Optix, and select Downloads.
  7. Choose theSelect Files check box .
  8. Download and extract the package Direct_Drive_Connectivity_v1.00.00.zip on the local drive.
  9. Open config.xml, and modify required settings:
    1. Provide the FactoryTalk Optix Studio location path.
    2. Provide the FactoryTalk Optix Studio installation path.
    For example: 
    <Settings>
  <!--Enter proper path to your FT Optix Studio folder (for example: C:\Program Files\Rockwell Automation\FactoryTalk Optix\Studio)-->
  <FTOptixStudioPath>C:\Program Files\Rockwell Automation\FactoryTalk Optix\Studio</FTOptixStudioPath>
  <!--Enter proper path to your FT Optix project folder (for example: C:\Users\User1\Documents\Rockwell Automation\FactoryTalk Optix\Projects\NewHMIProject)-->
  <FTOptixProjectPath>C:\Users\User1\Documents\Rockwell Automation\FactoryTalk Optix\Projects\NewHMIProject</FTOptixProjectPath>
</Settings>
    where:
    • C:\Program Files\Rockwell Automation\FactoryTalk Optix\Studio is the FactoryTalk Optix Studio location path.
    • C:\Users\User1\Documents\Rockwell Automation\FactoryTalk Optix\Projects\NewHMIProject is the FactoryTalk Optix Studio installation path.
  10. In PowerShell, run the install.bat script file.
    Tip: You may need to adjust the Windows® PowerShell execution policy to enable the script.
    The NuGet package is injected to your project defined in the config.xml file.