Sign in Subscribe
Resources

Optix Tips and Tricks

Practical tips and tricks from real FactoryTalk Optix development — keyboard shortcuts, workspace navigation, and small wins that save time.

Carter Gray

• 4 min read

This post is a collection of tips, tricks, and small wins I’ve picked up from spending time inside FactoryTalk Optix and other visualization platforms. If you’ve ever thought “there has to be a better way to do this,” you’re probably right. Hopefully these notes save you time, reduce frustration, and help you build smarter, cleaner projects.

Essential Shortcuts

  • Alt+Left / Alt+Right: Navigate back / forward (great to bind to mouse buttons).
  • Alt+Enter: Insert a line break in text fields (useful for multiline labels and notes).
  • Use the Project View search icon to quickly find screens, templates, tags, and resources — this is a newer, powerful feature many overlook.
  • Hyperlink in the top right to navigate to a Template/type definition.

Quick Actions

  • Right‑click on a component → Show References / Instances (your “where used” / cross‑reference).
  • Right‑click on a tab → Close All (there is a practical limit to how many tabs can remain open).
  • Right‑click on a component → Collapse All to tidy up the Project View.

Workspace Setup

  • Pin frequently used directories in File Explorer:
    • Projects: C:\Users\{user}\Documents\Rockwell Automation\FactoryTalk Optix\Projects
    • Emulator output: C:\Users\{user}\AppData\Local\Rockwell Automation\FactoryTalk Optix\Emulator
    • Know the difference between Project (design-time artifacts) vs Application (runtime/deployment files).
  • Download a SQLite browser for alarm/recipe debugging (useful for inspecting the emulator database).

Emulator & Runtime

  • Keep the emulator output path pinned. When deploying to a PC, double‑check the runtime output directory to find deployed files and logs for debugging.

Critical Awareness

  • Always confirm what you are editing:
    • Project View highlight shows which component is selected.
    • Properties Panel title shows which component you are modifying.
  • Avoid spam‑clicking in the UI to drill down. Optix navigation differs from FactoryTalk ME.
  • Use Lock / Unlock liberally when you want to expand or protect components during editing.

Properties & Bindings

Property Indicators (visual cues)

  • Italics = property was overridden on the instance (differs from the type/template default).
  • Blue hyperlink = click to navigate to the type/variable definition.
  • Blue value = binding is valid.
  • Red value = broken/invalid binding.
  • Blue exclamation = runtime‑only binding (won’t evaluate in design mode).

Binding Best Practices (balanced view)

  • Remove / Reset an existing binding before creating a new one — keeps the property clean.
  • Use expression evaluators where they make the logic clearer and more maintainable. However, conditional converters or custom converters also have valid uses depending on team preference and reusability.
  • Multi‑select components (Ctrl+click) and change properties en masse when appropriate.
  • Use the tag search field when browsing for tags; you can drag tags or bindings from Project View to the Properties Panel.

Layout & Positioning

Core Concepts

  • Stretch (fill the parent) vs Auto (size to content). Let Optix handle sizing rather than hardcoding pixels where possible.
  • Anchoring: Left, Right, Top, Bottom.
  • Horizontal and Vertical Layout containers are powerful, especially inside scroll views.

Gotchas & Nesting Considerations

  • Nesting layouts can change sizing behavior unexpectedly. When embedding a Horizontal/Vertical layout inside another layout or a scroll view, test resizing and runtime behavior in the emulator.
  • Auto vs Stretch combined with anchoring can produce non‑intuitive results when parent container sizes change; test container resizing.

Z‑Axis / Layering

  • Z‑order follows Project View vertical order. Drag to reorder. Lower in the Project View is closer to the Operator.
  • Avoid layering interactive elements under translucent widgets. Prefer dynamic opacity/visibility rather than stacking invisible controls on top of active ones.
  • Use the Dialog Window for Popups.

Images & Resources

  • Store images in a predictable place inside the project: ../ProjectDirectory/Images/ or reference from the file system if shared across projects.

Templates, Types, and Reusability

Type vs Instance

  • Editing a type changes the defaults for all instances (unless an instance has overridden properties).
  • Editing an instance changes that instance only. Such overridden properties are shown in italics in the Properties Panel.
  • Demonstrate common workflows: how to navigate to the type, change a default property, and then show instances where overrides exist.

Best Practices for Types

  • Avoid placing types within types. It creates complexity and confusion about where edits should happen. See Inception for details.
  • However, deriving new types by overloading or extending existing types is a powerful OOP practice.

UX & Design Standards

Avoid bad layering

  • Don’t use invisible dummy buttons with opacity for enablement. Prefer enabling/disabling or visibility toggles that are explicit.
  • Avoid stacking layers to hide content. This makes maintenance and accessibility harder.

Follow UX standards

  • Emphasize following ISA‑101 (operator display and HMI standards) or your site’s UX checklist: consistent typography, spacing, color for status, and predictable behavior for alarms and confirmations.

Design‑time Workspace vs Runtime

  • Set default screen/container sizes to match the device default window dimensions so the design canvas is representative of runtime display. This reduces surprises when deploying to target devices.

Common Gotchas

Dos

  • Use search fields liberally (Project View, binding dialogs, tag browsing).
  • Cross‑reference before deleting (Show Instances / References).
  • Lock components when not actively editing.
  • Keep the Properties Panel title visible to know what you’re editing.
  • Commit frequently and iterate via emulator. It launches much faster than a full test app in ME.

Don’ts

  • Don’t start component names with numbers (Optix may auto‑rename).
  • Don’t template within templates: clarify intent and avoid nested type editing complexity.
  • Don’t rely on spam clicks to drill down: use the Project View and Properties Panel.
  • Don’t layer pop‑ups unnecessarily: use visibility and enablement.

Where Work Happens

  • Properties Panel — 80% of configuration work.
  • Project View — navigation, organization, hierarchy, and z‑order.
  • Methods Panel — logic, events, scripting.
  • Output Window — debugging, runtime logs.
  • Canvas is a visual reference; most work is in the panels.

Ready for Custom Training?

ASQI delivers tailored, hands-on training designed around your real projects, your equipment, and your team’s workflow.

Start learning with systems that match what you actually build.

Request Custom Training →

Or email directly: [email protected] 

Development Best Practices for Optix — The comprehensive guide these tips and tricks complement.

Optix Layout & Positioning — More practical guidance on positioning and responsive design.