Deploying FactoryTalk Optix to Linux Devices

Home / FactoryTalk Optix / Getting Started

One of the most powerful features of FactoryTalk Optix is its native compatibility with Linux. This allows you to deploy high-performance HMI and data applications to low-cost, headless IoT gateways, Raspberry Pis, or industrial Linux PCs.

While the deployment process is similar to Windows, Linux requires a few extra steps regarding permissions and the “Update Server.”

FactoryTalk Optix Runtime Setup Online Help Files

Step 1: Prepare the Linux Environment

Unlike Windows, where you run a standard installer, Linux deployment often involves a lightweight Update Server that listens for incoming projects from Optix Studio.

  1. Download Runtime Tools: From the Rockwell PCDC or FactoryTalk Hub, download the FactoryTalk Optix Runtime Tools for Ubuntu/Linux.
  2. Extract and Install: Transfer the package to your Linux device and install it. If you are using a Debian-based system (like Ubuntu or Raspberry Pi OS), you will typically use:sudo dpkg -i ftoptix-runtime-tools.deb
  3. Check Dependencies: Ensure you have the necessary .NET dependencies installed. Most modern industrial Linux distros require:sudo apt-get install -y dotnet-runtime-6.0 (or the version matching your Optix release).

Step 2: Start the Update Server

The Update Server is a background process on the Linux device that “catches” the project file sent by your development PC.

  1. Navigate to the installation directory (usually /opt/Rockwell_Automation/FactoryTalk_Optix/).
  2. Start the update server:./FTOptixUpdateServer
  3. Port Configuration: Ensure TCP Port 49100 is open on the Linux firewall (ufw or iptables). This is the default port Optix Studio uses to push the application.

Step 3: Configure the Remote Linux Target in Studio

Back in FactoryTalk Optix Studio on your engineering workstation:

  1. Go to the Project tab -> Deployment.
  2. Add a New Target and select Linux.
  3. Enter the IP Address of your Linux device.
  4. Credential Check: If your Linux device requires SSH or specific user permissions, ensure your user has read/write access to the /home/admin/Rockwell_Automation/ (or equivalent) directory.

Step 4: Deploy and Verify

  1. Click the Deploy button in Studio.
  2. Optix Studio will compile the project specifically for the Linux architecture (ARM or x64) and push it.
  3. Verify via CLI: On the Linux device, you can check if the process is running using:ps aux | grep FTOptix
  4. Log Files: If the app doesn’t start, check the logs located at:/persistent/log/Rockwell_Automation/FactoryTalk_Optix/

Pro Tip: Using Docker for Deployment

For advanced smart manufacturing setups, many professionals deploy the Optix Runtime as a Docker Container. This allows you to manage the HMI as a “microservice,” making it easy to restart, update, or roll back without touching the host OS.

  • Command Example:docker run -itd -p 49100:49100 -p 8080:80 ftoptix-runtime-image

To deploy the FactoryTalk Optix Runtime as a containerized service, you can use Docker Compose. This is the preferred method for industrial Linux deployments because it ensures that if the device reboots or the application crashes, the HMI service will automatically restart.

The Docker Compose File (docker-compose.yml)

Create a file named docker-compose.yml on your Linux device and paste the following configuration:

version: '3.8'

services:
  optix-runtime:
    image: rockwellautomation/ftoptix-runtime:latest  # Ensure image name matches your local/registry name
    container_name: ftoptix_hmi
    restart: always
    ports:
      - "49100:49100"  # Deployment Port (Studio to Runtime)
      - "8080:80"      # Web Presentation Port (Access HMI via Browser)
      - "5900:5900"    # VNC Port (If Remote UI is enabled)
    volumes:
      - ./project:/opt/ftoptix/project:rw   # Map local project folder to container
      - ./logs:/var/log/ftoptix:rw          # Persist logs on the host machine
    environment:
      - ACCEPT_EULA=Y
      - OPTIX_RUNTIME_PASSWORD=YourSecurePassword
    networks:
      - ot-network

networks:
  ot-network:
    driver: bridge

Breakdown of Key Settings

  • restart: always: This is critical for industrial environments. If the Linux IPC loses power, Docker will automatically relaunch the HMI as soon as the OS boots.
  • Port Mapping (49100): This allows FactoryTalk Optix Studio on your Windows laptop to “see” the container on the network and push updates to it.
  • Volumes:
    • The ./project mapping allows you to swap or update the .optix project file on the Linux host without needing to rebuild the entire Docker image.
    • The ./logs mapping is essential for troubleshooting; it allows you to view error logs directly from the Linux terminal without entering the container.
  • ACCEPT_EULA=Y: Most industrial container images require this environment variable to acknowledge software terms during a headless deployment.

How to Deploy the Container

  1. Transfer the file: Put the docker-compose.yml in a folder on your Linux device (e.g., /home/admin/optix_app/).
  2. Launch the service: Run the following command in that directory:Bashdocker-compose up -d
  3. Verify: Check that the container is running:Bashdocker ps

Tutorial List

Back to tutorials