Known anomalies in this release

Use the identification information in parenthesis to track the anomaly in future releases or for reference when receiving assistance from Customer Support with a related issue.

The Compute Module cannot communicate with the controller if there is more than one Backplane in the controller path. For example, the module is unable to communicate with the controller if the path is Backplane\1\A\10.220.173.66\Backplane\3. However, paths resembling either Backplane\3 or Backplane\1\A\10.220.173.66 allow the module to communicate with the controller.

This anomaly first identified in version 1.2.0.

If an image file in a project does not appear in the runtime application, use a third party application to resize the image and make it smaller.

This anomaly first identified in version 1.3.0.

Assigning a string tag to a Discrete input memory area does not display an error message and causes read errors on all tags for the Modbus Station containing the misconfigured tag.

This anomaly first identified in version 1.3.0.

Elements added to a custom library do not appear in

Libraries

search until you restart FactoryTalk Optix.

This anomaly first identified in version 1.3.0.

If you emulate a project on a computer that is running

Microsoft®

Windows®

, some videos may not play. Videos will play if you deploy the project to a device.

This anomaly first identified in version 1.1.0.

When trying to connect to one of the following controller types over a ControlNet network:

You cannot route through a 1756-ENxT(R) module to connect to the controller. You need to use one of the following EtherNet/IP modules:

Attempting to create a project in a network folder displays an error indicating that

FactoryTalk Optix

cannot rename the project template.

This anomaly first identified in version 1.4.0.

Use Runtime Tools to connect the InfluxDB server via VPN. You can then deploy the project to the selected device.

This anomaly first identified in version 1.4.0.

Rotated accordions are not supported.

This anomaly first identified in version 1.4.0.

An application that terminates after uploading the project with application files to FactoryTalk Optix Studio will not automatically restart when running FactoryTalk Optix as a Service. Manually start the runtime serve or redeploy the application.

This anomaly first identified in version 1.4.0.

Application deployment will abort with error message “Unable to prepare project source archive: copy” if any NetLogic script is open. Close the script and deploy the application again.

This anomaly first identified in version 1.4.0.

The OptixPanel and Embedded Edge Compute module cannot communicate with a controller using the WAN port. The OptixPanel uses port 2 for WAN and port 1 for LAN and the Embedded Edge Compute module uses port 1 for WAN and port 2 for LAN. Use the LAN port to communicate with the controller.

This anomaly first identified in version 1.4.0.

Opacity applied to sub-elements of an advanced SVG image is not shown as expected when running in the emulator or OptixPanel when it is defined at the group level. Apply the opacity at the element level for expected results.

This anomaly first identified in version 1.4.0.

Engineering unit converters set directly on a property with the raw max and min values left at the default 0 do not show converted values. Create a custom engineering unit converter under the converters folder and reference it when creating an advanced dynamic link instead.

This anomaly first identified in version 1.4.0.

Project retentivity does not work as expected using multiple projects with the same name in different locations. Ensure projects have unique names when using retentivity.

This anomaly first identified in version 1.4.0.

A blank screen may appear in the Desktop IDE when toggling between local and remote desktop sessions.

This anomaly first identified in version 1.4.0.

If you use the RA EtherNet/IP Driver with a controller running V20 firmware, FactoryTalk Optix will not detect new or deleted tags when those changes are done while online with the controller.

To resolve this, deploy your project again and in

Project already exists

, select

Replace

.

This anomaly first identified in version 1.4.0.

Using a datatype other than the default on a UI control may result in a loss of precision in the value displayed.

This anomaly first identified in version 1.5.0.

The PDF is not generated when the sum of its Header, Sections and Footer exceeds the Page Size.

This anomaly first identified in version 1.5.0

Some Chinese, Japanese and Korean Unicode characters are shown incorrectly when entered into a text box or label that is connected to tags in Micro Logix 1400 or SLC-500 controllers under the Micro controller driver.

This anomaly first identified in version 1.5.0.

The MouseDoubleClick event is not yet available for configuration, but will be available in a future release.

This anomaly first identified in version 1.5.0.

When multiple stations are used, non-active screens with data from stations that do not have data on active screen, may not show correct status. See application notes for additional information.

This anomaly first identified in version 1.5.0.

Importing tags using an L5X file does not import the PlantPAx process instruction HMI extended tag properties. Import the properties offline using a Logix v37 ACD file or online from the controller.

This anomaly first identified in version 1.5.0.

In FactoryTalk Optix Studio, updating or replacing an image file with a new file of the same name results in the previous image being displayed. Use a unique name when updating or replacing an image file.

This anomaly identified in version 1.5.0.

Numeric input will not accept proper input until the virtual keyboard is used to switch the input mode to Japanese. This can be accomplished by clicking on any text input field.

This anomaly first identified in version 1.5.0.

When deploying or emulating a project and selecting transfer application files, the deployment results in an error if the application folders is missing. Create the Application Files directory manually and emulate or deploy the project again.

This anomaly first identified in version 1.5.0.

Clearing or removing EU/ST0/ST1 on an element of boolean array or boolean addressing on a scalar removes the overriding of the EU/ST0/ST1 in the Logix project. Optix will not recognize the EU/ST0/ST1 from the parent tag until reimported via online import.

This anomaly first identified in version 1.5.0.

When using the emulator, PDF report files are not generated on initial button press. Press the button again to generate the report.

This anomaly first identified in version 1.5.0.

When importing extended properties using an .L5X file, alias extended properties are not imported correctly and will not be retrieved at runtime.

This anomaly first identified in version 1.5.0.

Importing extended properties from the base tag of an alias does not work with online tag importer.

This anomaly identified in version 1.5.0.

When using local languages with extended properties passthrough, if a translation for the selected local language in

FactoryTalk Optix

is not available, the default local language will not be retrieved from the controller.

This anomaly first identified in version 1.5.0.

When UDTs are nested deeper than one level, the engineering unit defined on the UDT (not members) cannot be read.

This anomaly first identified in version 1.5.0.

When using local language keyboard inside

FactoryTalk Optix

Studio,

Alt + (key)

returns special characters where they exist, and returns capitalized characters for all other keys.

This anomaly first identified in version 1.5.0.

If the

FactoryTalk Optix

project name contains local language special characters, the MQTT Broker does not start.  When using the embedded MQTT Broker, do not use special characters in the project name.

This anomaly first identified in version 1.5.0.

Certain functionality may be blocked by an updated version of Visual Studio [3852883]

Close Visual Studio or shutdown the indexing service if you are unable to:

Transfer a project to any target when Transfer application source code is enabled.
Save a project with a new name.
Export the compiled runtime project to a folder.
Perform a Git task.

This anomaly first identified in version 1.5.0.

Logix extended properties passthrough bit level descriptions do not import online and do not update properly. To avoid this, assign bit level descriptions on instances.

This anomaly first identified in version 1.5.0.

The

FactoryTalk Optix

web editor may become unresponsive during large offline tag import operations. Try importing the tags online from the controller or use the

FactoryTalk Optix

desktop editor.

This anomaly first identified in version 1.5.0.

Logix extended properties are not writeable. Changes to engineering units do not indicate a write failure.

This anomaly first identified in version 1.5.0.

Special characters are not supported in Git repository names, ODBC database names, or when using Chinese, Korean, or Japanese input methods at design time in FactoryTalk Optix Studio web editor.

This anomaly first identified in version 1.2.0.