dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorCODESYS Visualizationdl-breadcrumb-item__separatorRecording Data and Displaying as a Trend dl-breadcrumb-item__separatorConfiguring a Recording dl-breadcrumb-item__separatorConfiguring a Task-Dependent Recording
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Configuring a Task-Dependent Recording dl-permalink__symbolPermalink

You can configure a database on the runtime system and the data buffering.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

Timeout for trend recording

During a trend recording, it can happen that the application task triggers a timeout that is caught with an exception when transitioning from “Running” to “Stop”. Causes can be that file operations with the SQLite database are taking too long or that too many variables are being recorded. This usually happens on a target device with weak performance.

You can avoid the occurrence of an exception:

  • Configure the trend recording with less memory demand so that the amount of data that is stored is adapted to the target system.

  • Reduce the number of variables.

  • Assigning tasks
  • Adding IEC variables
  • Removing variables from the configuration
  • Starting conditional trend recording
  • Add Parameters
  • Configure data buffering on RTS
  • Configuring additional buffering