ABB 800xA Trend Issue
Voted best answer
IM lives in symbiosis with Basic History (BH do primary logging while IM secondary).
Your test prove spikes in primary log data with "Raw, Good" quality obtained from the 3rd party OPC server (Simatic).
You must ask the vendor of the OPC server why it spikes and what options you have to solve it.
Is the actual Data stored correctly via the Status Tab --> Read in the Log Configuration ? Or after a refresh the Trend Spike goes away ? I have a case submitted where the Trend Display randomly ignores the "Knee Function" on the Trend Display yet when you refresh it corrects itself so it is not a Storage Data issue but a Trend Display Update issue. I am wondering if the Spikes are only on the Display and not in the Stored Data ?
Let us know.
What is your type of historian?
I've not seen Basic History inventing any value. If spike is in the Basic History log when reading from the Status tab --> Read, I would say with 99% certainty the spike did come from your OPC DA server.
What is your OPC DA Server and PLC behind it?
How are you checking the spike data? This needs to be checked with the OPC source at that time.
I would suggest checking Data storage as you might be running out of HD space on the Histrocial collection nodes (usually CS). Also this might be a sign of HD problems. Check yopur HD SMART data with a good tool (eg Crystal disc). Also as each CS in a redundant setup collects it's own data, swicthing over from the primary to redundant unit (ensure properly paired first) might highlight where the fault is, if the 'other' CS is not exhibiting the problem.
Hi, thank you for your all response.
Please find attached details on spike data and trend configuration.
We are using IM historian and data is coming from SIMATIC NET OPC server to ABB800xA. The PLC behind is Siemens PLC S7-300 series.
Can you please let me know if you spot any mistake in our trend configuration or why data spike may be happening?