Deploying FactoryTalk Optix to Windows PC

Home / FactoryTalk Optix / Getting Started

In the world of modern HMI and SCADA, FactoryTalk Optix stands out for its flexibility and cross-platform capabilities. Unlike traditional software that requires a heavy installation process, Optix is designed around a lightweight “Runtime” model.

Deploying an application to a remote Windows device—whether it’s an Industrial PC (IPC) on the plant floor or a remote workstation—requires a few specific steps to ensure the handshake between the Optix Studio (development environment) and the Target Device is successful.

FactoryTalk Optix Runtime Setup Online Help Files

Prerequisites for Deployment

Before you begin, ensure you have the following:

  1. Network Connectivity: The development PC and the remote Windows device must be on the same subnet, or reachable via a VPN/Route.
  2. Optix Runtime License: Ensure you have the appropriate “Tokens” or license for the features you are deploying.
  3. Target Device Prep: The remote device should be running a supported version of Windows (10/11 or IoT Enterprise) with the .NET Runtime installed.

Step 1: Install the Optix Runtime on the Remote Device

You cannot simply copy a project folder to a remote PC; the Runtime Environment must be present to execute the code.

  1. Locate the FactoryTalk Optix Runtime installer (available via the Rockwell Automation PCDC or within your Optix installation folder).
  2. Run the installer on the Remote Windows Device.
  3. Ensure the Optix Remote UI service is allowed through the Windows Firewall. By default, Optix uses Port 49100 for communication between Studio and the Runtime.

Step 2: Configure the Remote “Target” in Optix Studio

Back on your development computer, you need to tell Optix Studio where the remote device lives.

  1. Open your project in FactoryTalk Optix Studio.
  2. Navigate to the Project tab and look for the Deployment or Targets section.
  3. Click Add New Target and select Windows.
  4. Enter the IP Address or Host Name of the remote device.
  5. Set the Remote Port (Default is 49100).

Step 3: Compile and Deploy

Optix does not “stream” the project; it compiles it into a compact package and pushes it to the target.

  1. In the Studio toolbar, locate the Deploy button (often a “Cloud” or “Arrow” icon).
  2. Select your configured Remote Target.
  3. Check for Dependencies: Studio will check if the remote device has the correct version of the Optix Runtime. If it is outdated, Studio may prompt you to update the runtime remotely.
  4. Click Deploy and Start.

Step 4: Setting the Application as a Windows Service (Optional but Recommended)

For industrial applications, you want the HMI to start automatically when the IPC powers on, without a user needing to log in.

  1. On the remote device, open the Optix Runtime Manager.
  2. Locate your deployed project.
  3. Enable the toggle for “Start on System Boot” or use the Windows Service Wrapper utility to ensure the application runs in the background.

Troubleshooting Common Deployment Issues

  • “Target Not Found”: Ping the remote IP from your dev PC. If it pings but deployment fails, check if Port 49100 is blocked by the corporate IT firewall.
  • Version Mismatch: If your Studio version is 1.4 but the Remote Runtime is 1.2, the deployment will fail. Always align your Runtime version with your Development version.
  • License Errors: FactoryTalk Optix uses a “Small/Medium/Large” token system. If your project uses 100 tokens but your remote license only supports 50, the application will run in Trial Mode (usually 2 hours) before shutting down.

✅ FactoryTalk Optix Remote Deployment Checklist

1. Remote Device Preparation (The Target)

  • [ ] Operating System: Windows 10/11 or IoT Enterprise is installed and updated.
  • [ ] .NET Framework: Latest .NET Runtime (v6.0 or higher, depending on Optix version) is installed.
  • [ ] Optix Runtime: The FactoryTalk Optix Runtime installer has been executed on the target.
  • [ ] Firewall Exceptions: Inbound rules created for Port 49100 (Deployment) and Port 80/443 (if using Web Presentation).
  • [ ] Static IP: The device has a static IP address or a reserved DHCP lease to prevent losing the connection.

2. Development Environment (The Studio)

  • [ ] Version Alignment: Optix Studio version matches the Runtime version installed on the target.
  • [ ] Target Configuration: Remote IP address and port (49100) are correctly entered in the “Targets” editor.
  • [ ] License Check: Total project “Feature Tokens” do not exceed the license/tokens available on the target device.
  • [ ] Project Build: Project compiles locally with zero errors before attempting the push.

3. The Deployment Process

  • [ ] Connectivity Test: Successfully pinged the target IP from the development workstation.
  • [ ] Transfer Mode: Selected “Compile and Deploy” to ensure the latest changes are packaged.
  • [ ] Start Mode: “Start Application after Deployment” is toggled on to verify immediate success.
  • [ ] Log Monitoring: The “Output” window in Studio is open to monitor for “Transfer Successful” messages.

4. Post-Deployment & Commissioning

  • [ ] Auto-Start: Application is configured as a Windows Service or added to the Startup folder for headless operation.
  • [ ] Resolution Check: The UI scales correctly to the remote device’s physical monitor resolution.
  • [ ] PLC Comms: Verified that the remote device can see the PLCs (check drivers and local network routes on the target).
  • [ ] Trial Timer: If not licensed yet, confirmed the application is running in the 2-hour “Trial Mode” successfully.

Manually Transferring FactoryTalk Optix Projects via USB

When a remote device is on a completely isolated network (OT “air-gapped”), you cannot use the Studio “Push” button. In these cases, you must perform a File-Based Export and a Manual Runtime Import.

Here are the steps to move your project via USB stick.

Step 1: Export the Runtime Package from Optix Studio

Instead of deploying to an IP address, you will create a standalone application file.

  1. Open your project in FactoryTalk Optix Studio.
  2. Go to the Project tab and select Deployment.
  3. Choose Export for Runtime.
  4. Select the Target Platform (in this case, Windows 64-bit).
  5. Choose a destination folder on your USB Stick.
  6. Click Export. Studio will compile the project into a folder containing the .optix file and all necessary binary dependencies.

Step 2: Install the Optix Runtime on the Target PC

The USB stick contains your project, but the Windows PC still needs the engine to run it.

  1. Ensure the FactoryTalk Optix Runtime (the .msi or .exe installer) is also copied onto your USB stick.
  2. Plug the USB into the remote PC and run the Runtime installer.
  3. Follow the prompts to complete the installation.

Step 3: Transfer and Launch the Project

  1. Copy the Folder: Do not run the project directly from the USB stick (this can cause latency and file-lock issues). Copy the exported project folder from the USB to the local C:\ drive (e.g., C:\HMI_Projects\ProjectName).
  2. Launch via Runtime Manager:
    • Open the FactoryTalk Optix Runtime Manager on the Windows PC.
    • Click Load Project or Add.
    • Navigate to your copied folder and select the project file.
    • Click Start.

Step 4: Automating the Launch (The “Headless” Setup)

If this is a permanent installation, the HMI should start without human intervention.

  1. In the Runtime Manager, locate your project.
  2. Toggle the setting “Load on Startup.”
  3. Alternatively, create a shortcut to the OptixRuntime.exe and add the project path as an argument in the “Target” field of the shortcut properties:"C:\Program Files\Rockwell Automation\FactoryTalk Optix\Runtime\OptixRuntime.exe" "C:\HMI_Projects\MyProject.optix"
  4. Place this shortcut in the Windows Startup Folder (shell:startup).

Important: The Licensing Hurdle

When transferring via USB, the license isn’t always “pushed” like it is during an online deployment.

  • If the target PC has an internet connection, it can check the license via the cloud.
  • If the target PC is offline, you must use a Hardware Dongle or an Offline License File generated from the Rockwell Activation Manager and moved via the same USB stick.

Tutorial List

Back to tutorials