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.

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.

DNS names used in the

SubjectAltName

field of the certificate configuration are only recognized if they are lower case.

This anomaly first identified in version 1.2.0.

Installing

FactoryTalk Optix Studio

and FactoryTalk Motion Analyzer on the same computer prevents FactoryTalk Motion Analyzer from working.

This anomaly first identified in version 1.0.2

Excessive screen switching to screens that contain PDF and Video controls causes memory leaks on OptixPanels and Embedded Edge Compute devices.

This anomaly first identified in version 1.2.0.

Special characters are not supported in PDF filenames, FTP Server usernames, Git repository names, ODBC database names, or when using the Microsoft Pinyin input method on the device or at design time in FactoryTalk Optix Studio web editor.

This anomaly first identified in version 1.2.0.

Deploying to a device with a name that contains a slash results in an error or the application not running on the device.

This anomaly first identified in version 1.2.0.

Loading an application to a device from a USB results in multiple applications on the device if the exported application is not encrypted.

This anomaly first identified in version 1.2.0.

Pulling from the remote repository when an Object Type name has been modified both remotely and locally causes a merge conflict. The operation creates two different objects when keeping local changes and causes the loss of the renamed type when accepting remote changes. To avoid data loss, all users collaborating on the project must manually update the Object Type name on their local project before pulling from the remote repository.

This anomaly first identified in version 1.2.0.

The default application may not load on the device after deleting an application using Device Manager. A deployed application may also display a blank screen after the deletion. To load an application on the device again, reboot the device.

This anomaly first identified in version 1.2.0.

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 application deploys with the NativePresentation Engine, the library cannot load and the application does not run on the device. Replace the NativePresentation engine with a WebPresentation engine to allow a remote client to connect to the device.

This anomaly first identified in version 1.2.0.

Embedded Edge Compute module AOP Electronic keying may result in an unexpected error or connection in Logix for a minor revision mismatch.  Update the AOP Definition to disable keying for the module.

This anomaly first identified in version 1.2.0

Unable to download the Embedded Edge Compute module EDS file over the backplane. Download the EDS file using the Eth 2 port on the Embedded Edge Compute.

This anomaly first identified in version 1.2.0