View trend errors
The
Trend Error Log
displays all unacknowledged trend error messages. Each message contains:- The error type (such as, Warning or Fatal Error)
- The time the error occurred
- A brief description of the error
Once you have viewed the errors, select the
Clear Log
button to clear all errors from the trend error log. If any of the errors are significant enough to stop the trend, it is stopped once you select this button.Select the
Refresh
button to update the trend error log with the most recent errors.The possible errors you might see in the
Trend Error Log
are as follows:Error | Cause | Result of Error | Solution |
Can't initialize RSLinx . | RSLinx is not installed, an incompatible version is installed, or a bad harmony path is specified. | The trend will not start. | Install the correct version of RSLinx , or run RSWho to check the harmony path. |
Can't communicate with RSLinx . | RSLinx is not installed, an incompatible version is installed, or a bad harmony path is specified. | The trend will not start. | Install the correct version of RSLinx , or run RSWho to check the harmony path. |
Can't open the specified RSLinx driver. | RSLinx is not installed, an incompatible version is installed, or a bad harmony path is specified. | The trend will not start. | Install the correct version of RSLinx , or run RSWho to check the harmony path. |
An error occurred in a call to RSLinx . | RSLinx is not installed, an incompatible version is installed, or a bad harmony path is specified. | The trend will not start. | Install the correct version of RSLinx , or run RSWho to check the harmony path. |
Communications timed out. | The controller may be turned off, or no cable is connected between the controller and the PC. | The trend is halted internally. | Click the Clear Log button or the Stop button to stop the trend and release all resources. Then, check the connection between the controller and the PC, and make sure the controller is turned on. |
WARNING:
Buffer overrun - Increase the trend capture size. | The configured capture buffer size is too small. | Trending stops. | Make the Size of Each Capture larger (on the RSTrendX Properties - Sampling tab). |
WARNING:
Missing data sample(s) - Check your trend configuration. | Wrong type of communication (e.g., serial port, PC is too slow, trend on too many tags on too fast a sampling period, etc.) | Trending continues. This error is reported only once per trending. It is not reported again until the current trend is stopped and a new trend is started. | Adjust the number of trending tags and the sampling period, based on the PC and the type of controller you are using. |
WARNING:
Data sample(s) discarded - Duplicate timestamps. | The controller's Wall Clock Time was set back, which can be caused by PTP updates, SSV instructions, or user actions. | Trending continues. Data samples with duplicate time stamps are discarded. | If PTP is enabled, large changes to Wall Clock Time should diminish automatically; if SSV instructions or user actions are causing this issue, stop performing those actions while collecting trend data. |
Provide Feedback