Known anomalies from
FactoryTalk Edge Gateway
 standalone version 1.00.00

Saving Azure® IoT Hub application without any changes prompts a message to redeploy the application (899689)
When configuring an Azure IoT Hub application, selecting
Save
 without making any change prompts a message to redeploy the application.To work around this issue, select
Cancel
.
Slower performance in applications with Store and Forward
Applications with Store and Forward can experience adverse performance due to:
  • Too many tags are configured per application with high collection rate.
  • Smart Objects (SO) are configured per application even with a minimal number of SOs depending on the collection properties of SO. There will be multiple data values in single buffer read from the controller.
  • The SQL or IOT application loses connection during egress to SQL server or IOT hub.
  • The duration of disconnect from SQL server or IOT hub.
  • The Store and Forward settings Maximum store size (bytes), maximum fetch sizes (bytes), Fetch interval (ms) are not appropriately set according to the amount of data ingress.
    1. The maximum store size can also impact egress. As the size of the store is determined, it takes longer to make the determination if the store is larger. It is recommended to lower the file store size. Large ingress could force the application into a state where it is trying to delete more often than post.
    2. Maximum fetch size has an impact on how fast the data can be removed from the store and egressed. Larger fetch size means the application will remove data in large chunks from the store. There is hardware dependency on how fast it will be processed and sent to the destination. Smaller fetch size means smaller chunks of the store will be removed.
    3. Longer fetch interval means more data stored and store could overflow before the data egress.
The volume of collected data to be egressed exceeds device capability (942141)
The amount of data collected to be egressed is beyond the capability of the device that is running the gateway. If the size of ingress data flow is properly tuned to the performance of the OS and the hardware, then the issue is most likely to occur.To work around this issue:
  • Split the number of tags/smart objects across different applications. If the application stops, clear the application store file in resources directory and re-deploy the application.
  • If the application stops, the solution is to clear the application store file in the resources directory, ex. sql-app2, and re-deploy the application. In rare cases that this does not work, delete the application from the FTEG Config UI and the application store file and then re-create the application.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal