Data collection issues

Symptom
Solution
The
System Status
 section on the Home page shows that the data collection is in the "Stopped" mode.
  • Check the module STS LED light. Solid red indicates that the data collection is inactive.
  • Go to the
    Advanced
     tab to view the System Log page. Check the log for messages about the issue and export log data.
  • The data collection may have stopped because it reached the user-configured Archive Usage Threshold percentage on the Data Storage page.
    Wait for the system to process overflow events and return to a state that allows you to restart the data collection.
    or
    Increase the Archive Usage Threshold percentage.
  • Go to the
    Data Collection
     page. Click
    Start
     to restart the data collection.
  • If the data collection does not appear to have stopped due to a user configuration, go to the
    Data Collection
     page. Click
    Start
     to restart the data collection.
The
System Status
 section on the Home page shows that the data collection is in the "Error" mode.
  • Check the module STS LED light. Solid red indicates that the data collection is inactive.
  • Go to the
    Advanced
     tab to view the System Log page. Check the log for messages about the issue and export log data.
  • Go to the
    Web Diagnostics Firmware
     tab, and check the
    Data Collection
     page. Process information can confirm whether or not the data collection is in an undesirable state. N/A indicates an error state.
  • Download additional information that will assist in troubleshooting as described in the Provide issue information, Reboot the module, and Work in the safe mode sections.
  • Reboot the module.
  • Contact Technical Support if the issue persists.
Tags are collecting bad quality data.
If you change a tag's external access attribute to
none
, then the data collected by that tag for FactoryTalk Historian ME will be bad quality. To fix this issue, you must change the tag external access attribute to either
Read/Write
 or
Read only
.
Snapshot data points displayed on the Current Data page contain timestamps that are not being updated.
Check the status of the data collection on the Home page.
Go to
Time Source > Controller
 in the web interface. Check for a message that indicates that data collection has discarded data.
If the data collection status is "Running", check the Collection Rate in the
System Status
 section in the left navigation bar.
  • Ensure that the Collection Rate is zero; this confirms that the data collection is not collecting data.
  • Go to the
    Web Diagnostics Firmware
     tab, and check the Data Sever page.
    N/A
     indicates an error state.
  • Reboot the module.
  • If the data collection stops again, go to the
    Configure Historian
     tab, and click
    Data Storage
    . Ensure that the Archive Disk Threshold and Archive Usage Threshold are still valid. If these thresholds have been reached, wait for the system to process overflow events and return to a state that allows you to restart the data collection.
  • If the Collection Rate is not zero, check the status of the Data Server on the Home page.
  • If the Point Server status is "Stopped" or "Error", reboot the module.
If the data collection status is "Stopped", go to the
Data Collection
 page and restart the data collection.
A single point has not collected data for a significant time period.
  • Check the point configuration on the Point Property page.
  • Ensure that the scan rate is not set too low, and ensure that the Exception and Compression values are configured properly for the point.
The module receives a high-speed event with a timestamp 10 minutes into the future, discards that event, and logs the following error message into the system log:
[ERROR] TagProcessingForPolledAndAdvised() dropped future event for point<ID> with <timestamp> with timeDelta=<number of seconds into future>.
  • Check the controller time.
  • Ensure that the controller time is correct.
The following message is logged on the
System Log
 page:
[ERROR] Unable to keep pace with High Speed Trend causing data loss.
Due to performance issues with the controller, the backplane or the module, the module cannot receive new high-speed events from the controller. To mitigate the impact, stop and restart the data collection.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal