Known Anomalies in this Release

The list identifies the known anomalies in

FactoryTalk Edge Gateway

version 1.04.00. Use the identification information provided in the anomaly heading to track the anomaly in future releases or for reference when receiving assistance from customer support with a related issue.

OPCDA via FTLD driver - Two servers in one area/application are not working properly with FTEG (2113717)

When two OPC DA Servers are in one area/application following issue occurs:

Tags are not collected, because the server information is in the tag name path.

The select path tree (FTLD Data Source) does not show both KEP Servers on the second and subsequent attempts to expand the tree.

The similar issue occurs in the FTLD Test Client also.

Workaround: Keep one OPCDA server per one FTLD Application/Area.

When OPC DA Server (not RSLinx Classic) contains “Online” or “Offline” in the tags structure, then the data source cannot populate - there is “never ending loading”. (2115497)

When OPC DA Server (not RSLinx Classic) contains “Online” or “Offline” in the tags structure, then the data source cannot populate - there is “never ending loading”.Workaround: Just rename the problematic “Online” / “Offline” node.

Browsing big data source while creating model is crashing fteg-ct process

When browsing data source with significant amount of tags, it is suggested to verify hardware resources (i.e. for data sources with more then 100k tags we suggest 16GB of RAM and 4-core CPU)”.

64-bit FactoryTalk Activation files being removed after FactoryTalk Service Platform upgrade (1962904)

The issue has been observed when FactoryTalk Services Platform is upgraded to version 6.31.00 without a subsequent install of FactoryTalk Activation Manager. This results in the 64-bit FactoryTalk Activation files being removed from C:\Program Files\Common Files\Rockwell. To Walkaround this issue, you can use any of following solutions:

Perform a clean reinstall of FactoryTalk Activation Manager using tech note - https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/573887

Uninstall FactoryTalk Activation Manager and Application Code Manager. After it is done, install Application Code Manager first and then FactoryTalk Activation Manager.

In case of upgrading the FactoryTalk Edge Gateway to 1.04, Device Discovery model can not be repopulated (2165876)

In case of upgrading the FactoryTalk Edge Gateway from version 1.03.00 to 1.04.00, Device Discovery model can not be re-populated without editing and saving particular data source. The model is not affected and stays fulfilled, but after direct re-populating, the model is cleared out.Workaround: To avoid deletion of Device Discovery model which was created in FTEG version 1.03 and then upgraded to 1.04, you need to edit particular Device Discovery datasource and Save new list of selected device profiles (which are already selected) before proceeding with re-population process.

ThingWorx does not support the new types: DT, LDT, LTIME, TIME, TIME32 (2072007)

When you deploy the ThingWorx application with the “Unsupported types” (DT, LDT, LTIME, TIME, TIME32), it ends with a timeout after 15 minutes. During these 15 minutes, it is impossible to repair the application by doing a second deploy without unsupported types (even after restarting fteg).

No UI notification about missing license (2036106)

When missing license, user is not informed on UI what is a reason that nothing happens after clicking Deploy or trying to start application when paused/stopped.