Known anomalies in this release

Secrets encryption mode remains unavailable after you change the Customize security policies option during reinstallation. For example, if you clear the option during initial installation, then select it during reinstallation,

FactoryTalk Optix

Studio keeps Encryption Mode unavailable. Change the encryption mode by editing the Windows Registry.

This anomaly first identified in version 1.7.5.

FactoryTalk Optix

runtime objects temporarily display a red wireframe after accepting an online edit in the controller program. For example, runtime becomes unresponsive for a short duration after editing and accepting changes in the controller code. To mitigate the issue, monitor runtime behavior and apply edits during non-critical operation times only.

This anomaly first identified in version 1.7.4.

Binding an integer tag to a Boolean control property hides dynamic links for controller tags on the current screen. For example, when an integer value greater than 1 binds to a button Enabled property, label and text display bindings do not update correctly. Bind a Boolean tag or expression to Boolean control properties.

This anomaly first identified in version 1.7.1.

Optix Panel does not display certain accented Latin characters from Micro800 string tags. For example, the character ç displays in the emulator but displays as blank on the panel. Use ASCII characters in Micro800 string tags on Optix Panel.

This anomaly first identified in version 1.8.0.

Online tag re-import does not display Micro800 tags after refreshing a serial connection. For example, the initial import displays tags, but selecting Refresh clears the tag list. Close and reopen the designer before importing tags again.

This anomaly first identified in version 1.8.0.

The Web UI does not indicate when an uploaded file type is invalid. For example, the browser console logs an invalid file type, but the runtime does not display a message. Check the browser console to identify invalid file types.

This anomaly first identified in version 1.8.0.

PowerFlex

755 tags can stop refreshing without a communication error. For example, a tag write updates the local display but does not update the drive. Restart the terminal to restore communication.

This anomaly first identified in version 1.8.0.

Large projects deployed to a

FactoryTalk Optix

High Availability

cluster may fail to start if runtime containers do not have enough allocated memory, even when

FactoryTalk Optix

Studio reports a successful deployment. The runtime may repeatedly restart and remain unavailable and the web client never becomes reachable.

To resolve the issue, increase the allocated memory as described in the

High Availability

cluster troubleshooting section of the

FactoryTalk Optix

Installation Guide.

This anomaly first identified in version 1.8.0.

PowerFlex

755 tags stop updating during screen switching and cause measurement timeouts. For example, with four EOIs connected to the same drives, tags stop updating on the EOI that writes tags. Reduce the number of EOIs connected to the same drives to reduce timeouts.

This anomaly first identified in version 1.8.0.

After an upgrade, NetSolution compilation fails when NetLogics contains an FactoryTalk Optix.EdgeBrokerAddon declaration. For example, compilation fails when a project references Smart Objects that the application does not use. Remove the FactoryTalk Optix.EdgeBrokerAddon declaration from NetLogics to compile the NetSolution.

This anomaly first identified in version 1.8.0.

The cip.nameModel.InfoID tag remains in a fault state after the drive connection is restored. For example, the tag displays a red X while other

PowerFlex

tags display normally. Restart or redeploy the application to restore the tag status.

This anomaly first identified in version 1.8.0.

The

PowerFlex

drive Health Status tag may not update in the

FactoryTalk Optix

runtime after the drive status changes when the RA Device Station maximum polling rate is set to 2 seconds. For example, the tag may continue to show

Healthy

after the drive enters a fault state. To refresh the health status, set the maximum polling rate to 5 or 10 seconds, or restart the runtime.

This anomaly first identified in version 1.8.0.

MQTT transmission with QoS 1 or QoS 2 can experience delays under high event loads. For example, 1,000 changing variables and 10 events can delay delivery by about 10 seconds between separate broker and client systems. Use QoS 0 for high-volume telemetry when delivery requirements permit.

This anomaly first identified in version 1.8.0.