Application notes

These application notes apply to
FactoryTalk Optix
 version 1.5.0.

Threat mitigation

  • Do not lose the USB Key with exported
    FactoryTalk Optix Application
    . The USB key contains inspectable fields, credentials, certificates, and hashed passwords.
  • Protect physical access to
    Rockwell Automation
     manufactured devices.
  • Do not leave connected devices unattended. Protect physical access to the device and protect logs from device web interface, connected diagnostic session, and file system access via remote assistance tool.
  • Prevent unauthorized physical access to the device. Protect physical access to the device and improve security level of application files generated by custom logics.
  • Protect physical access to logged-in user sessions. Prevent the theft of
    FactoryTalk Hub
     refresh token file by locking the session if unattended.
  • Protect physical access to logged-in user sessions. Prevent the removal of
    FactoryTalk Hub
     refresh token file by locking the session if unattended.
  • Protect physical access to logged-in user sessions. Prevent attacks while logging in to GitHub.

Feature preview

Features labeled as preview should not be used in a production environment. Feature preview includes:
  • RA EtherNet/IP communication driver in the FactoryTalk Optix Studio web editor and Emulator
  • Connected IDE mode
  • Contents of Feature Preview library folder
  • Model analysis providing information model graphs
  • Smart Objects / Edge Apps

FactoryTalk Optix Studio web editor

You can use FactoryTalk Optix Studio in a web browser through FactoryTalk Hub.

Emulator features support

FactoryTalk Optix Studio web editor emulator supports all features of FactoryTalk Optix Studio desktop editor emulator except for:
  • Control the
    WebBrowser
     object in the runtime editor.
  • Control the
    PDFViewer
     object in the runtime emulator.
  • Control the
    Video
     object in the runtime editor.
  • Control the
    Window
     object in the runtime emulator.

Editor features support

FactoryTalk Optix Studio web editor supports all FactoryTalk Optix Studio desktop editor features except for:
  • Save logs from the
    Output
     tabs.
  • Edit NetLogic files.
  • Display paths in logs in the
    Output
     tabs
  • Add files and images by dragging and dropping them into FactoryTalk Optix Studio web editor.
  • Restart the application at runtime by using the method.

Spinbox Numeric Input unsigned conversions

When the Spinbox datatype is an unsigned integer, negative inputs are converted to zero.

Mouse Up Event modified behavior

The Mouse Up Event is now executed only when removing the pointer or finger while remaining inside the UI object area. This modification affects the UI controls Panel, Rectangle, Button, Ellipse, Polyline, Image, and AdvancedSvgImage. A new variable related to the pressed status will be included in a future release.

Incorrect status under Micro Controller Driver

When multiple stations are configured, if there is no demand for data the connection status for the station is not updated. To avoid this situation, implement a heartbeat for each station using a runtime Netlogic script to clear a boolean when it is true, and a timer in the station that runs when the boolean is false and sets it to true when the timer completes.

Alarm limits

1 language
Device RAM
Optix Alarms,
Logix Tag-based Alarms, and Logix ALDM Instruction Alarms
Logix ALMA Instruction Alarms
1 GB
2500
400
2 GB
5000
800
4 GB
15000
1600
8 GB
30000
3200
16 GB
60000
6400
4 languages
Device RAM
Optix Alarms,
Logix Tag-based Alarms, and Logix ALDM Instruction Alarms
Logix ALMA Instruction Alarms
1 GB
700
150
2 GB
1000
200
4 GB
3500
500
8 GB
7000
1000
16 GB
14000
2000
NOTE: If your application uses Logix ALMA instruction-based alarms mixed with other types of alarms, count each ALMA alarm as 5 alarms. For example, if the FactoryTalk Optix application has 100 ALMA alarms and 2000 other alarms, the total number of alarms is 2500. Per the table above for a single local language, this is the quantity of alarms that will run inside 1GB with a normal application.
As shown on the table above, each local language requires additional memory. The additional memory required will be reduced in a future release.
If you are not using the new Alarm Manager or Alarm Summary counters, or if you are upgrading from a previous version of FactoryTalk Optix that does not require the new Alarm Manager or Alarm Summary counters, you can reduce the memory required by disabling alarms collection by setting the
Enable alarms collection
 property to
False
.

Logix extended properties must define both Min and Max range

When importing Logix extended properties, both Min and Max must be defined in Logix and must contain valid values in order for the extended properties to be imported.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.