Real-Time Trends & Historical Data Logging in WinCC Runtime Advanced: Complete Contents
- 1. Start with a Trustworthy Engineering Value
- 2. Analog Scaling with NORM_X and SCALE_X
- 3. SCL Scaling Example
- 4. Create a Tag Logging Archive
- 5. Choose Sampling and Logging Cycles Intentionally
- 6. Configure the Runtime Trend View
- 7. Add Time Navigation and Operator Controls
- 8. Handle Bad or Missing Data
- 9. Industrial Trend Applications
- 10. Trend Troubleshooting
- 11. Hands-On Trend Lab
Practical WinCC Runtime Advanced Engineering Guide
1. Start with a Trustworthy Engineering Value
Trend quality begins in the PLC. Validate the raw analog signal, module configuration, sensor range and fault behavior before logging anything. The HMI should normally receive a scaled engineering value such as °C, bar, %, mm or rpm plus diagnostic quality/status information where required.
2. Analog Scaling with NORM_X and SCALE_X
For a common Siemens raw range, normalize the integer input and scale it into engineering units. Always confirm the actual module range and sensor configuration before copying constants.
3. SCL Scaling Example
// Example only: verify your analog module raw range
TempNorm := NORM_X(MIN := 0, VALUE := RawTempAI, MAX := 27648);
TempPV := SCALE_X(MIN := 0.0, VALUE := TempNorm, MAX := 1200.0);
// Example alarm preparation
TempHigh := TempPV > TempHighLimit;4. Create a Tag Logging Archive
In WinCC Runtime Advanced, configure tag logging for the process values that require history. Do not archive every animation tag. Select values that support operation, troubleshooting, quality or reporting: temperature PV/SP, pressure, speed, current, production count and key states. Define storage and retention according to the machine requirement.
5. Choose Sampling and Logging Cycles Intentionally
The logging cycle should match process dynamics. A furnace temperature may not need a 100 ms archive; a fast motion signal may require a different diagnostic tool entirely. Faster logging increases data volume and can reduce usefulness when the process changes slowly. Set the interval from the engineering question you need the trend to answer.
6. Configure the Runtime Trend View
Add a trend view/control and connect archived or real-time tags as required. Use clear pen names, engineering units and sensible Y-axis ranges. Display PV and SP together where operator comparison matters. Avoid putting too many unrelated variables into one chart; create purpose-specific trend screens for temperature, drive load or production rate.
7. Add Time Navigation and Operator Controls
Give operators useful controls for time range, scrolling, zoom and curve selection. A trend that only shows the last few seconds is not useful for investigating a 20-minute process upset. Define a default view for normal operation and a maintenance/history view for deeper analysis.
8. Handle Bad or Missing Data
Communication loss, PLC stop, invalid analog input and Runtime restart can create gaps or misleading values. Make data quality visible where practical and avoid substituting zero for an invalid process signal unless zero is genuinely meaningful. A discontinuity is often more honest than a fabricated value.
9. Industrial Trend Applications
Useful applications include furnace heat cycles, pressure stability, VFD speed/current comparison, tank filling profiles, PID response, batch setpoint tracking and production-rate analysis. Pair the trend with event/alarm timestamps so engineers can correlate process changes with machine states.
10. Trend Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Flat line | Wrong tag or scaling | PLC watch table and HMI tag value |
| No history | Archive not logging | Logging settings, storage, runtime state |
| Trend too noisy | Signal/process noise | Sensor, grounding, filtering, sample strategy |
| Huge data volume | Cycle too fast | Recalculate required sampling interval |
11. Hands-On Trend Lab
Scale one analog input, create PV and SP HMI tags, configure an archive, display both values in a Runtime trend and deliberately create a step change. Record response time, overshoot and stabilization. Then stop communication briefly and confirm the engineer can identify the resulting data-quality/history behavior.
WinCC Runtime Advanced Hands-On Lab
Use a non-production PLC/HMI project, document the test conditions, and verify every HMI behavior against the PLC watch table or diagnostics. The objective is not only to make the screen work, but to prove that the engineer can diagnose a deliberate fault and recover the system methodically.
Frequently Asked Questions
What is tag logging in WinCC Runtime Advanced?
Tag logging stores selected process values over time so Runtime can display historical trends and support troubleshooting or process review.
How fast should WinCC Runtime Advanced log data?
Use a cycle appropriate to the process dynamics and diagnostic need. Logging faster than necessary creates more data without automatically producing better insight.
Should analog scaling be done in the PLC or HMI?
For control-oriented systems, scaling and signal validation are normally clearer and more reusable in the PLC, while the HMI visualizes the engineering value.
Can I trend PV and setpoint together?
Yes. Displaying process value and setpoint together is a common way to evaluate control response and operator/process behavior.
Related WinCC Runtime Advanced & Siemens HMI Resources
Need Practical WinCC Runtime Advanced Training?
Build the complete HMI workflow from PLC communication and tags through alarms, trends, recipes and user administration with a practical Siemens automation project.
Discuss Training or Project Support