Scale the physical signal once, preferably in the PLC, and expose a named engineering-unit value to WinCC. Avoid repeating different scaling formulas in PLC, HMI scripts and reports.
- Confirm the analog module measuring range before assuming a raw range.
- Use NORM_X to normalize the configured raw span and SCALE_X to convert it to engineering units.
- Trend the engineering value, not an unexplained raw count, unless raw diagnostics are intentionally required.
- Choose archive cycle based on process dynamics and reporting need, not the fastest possible interval.
Practical WinCC Engineering Guide
This technical guide focuses on NORM_X SCALE_X, analog scaling Siemens PLC and hands-on Siemens PLC / SCADA commissioning practices.
1. Analog Signal Path: Sensor → PLC → WinCC
The complete path is Transmitter → Analog Input Module → Raw PLC Value → Normalized Value → Engineering Unit → WinCC Tag → Archive → Trend. Each stage should have a documented range. If the transmitter is 0–100 °C, the SCADA engineer should not have to guess what a raw value such as 13824 means.
2. Confirm Raw Range and Module Configuration
Many Siemens analog examples use a nominal raw range of 0…27648 for a unipolar configured measuring range. However, diagnostic overrange/underrange behavior and exact representation depend on the module and selected range. Always check the hardware configuration and module documentation for the channel you are commissioning.
3. Normalize the Raw Value with NORM_X
NORM_X converts a value between a defined minimum and maximum into a normalized REAL value, typically 0.0 to 1.0 for an in-range signal.
// Example: raw input represented from 0 to 27648
#Normalized := NORM_X(
MIN := 0,
VALUE := #AI_Raw,
MAX := 27648
);
Monitor the normalized value online. At approximately half scale, it should be close to 0.5. If it is negative or above 1.0 under normal conditions, verify wiring, measuring range and constants before continuing.
4. Convert to Engineering Units with SCALE_X
SCALE_X maps the normalized value to the required engineering range. For a 0–100 °C process:
#Temp_C := SCALE_X(
MIN := 0.0,
VALUE := #Normalized,
MAX := 100.0
);
For a pressure transmitter of 0–16 bar, change the engineering limits to 0.0 and 16.0. Keep the engineering unit in the tag name or documentation so a later SCADA/report engineer does not misinterpret the number.
5. Add Validation, Limits and Signal Fault Handling
Scaling is only one part of analog engineering. Add plausibility checks and decide what WinCC should display if the input channel reports a diagnostic condition.
#AI_Valid := (#AI_Raw >= #RawValidMin) AND (#AI_Raw <= #RawValidMax);
IF #AI_Valid THEN
#Temp_QualityOK := TRUE;
#Temp_PV := SCALE_X(MIN := 0.0, VALUE := #Normalized, MAX := 100.0);
ELSE
#Temp_QualityOK := FALSE;
END_IF;
The exact diagnostic strategy should use the module status available in your hardware. The key point is to expose a separate quality/validity status instead of silently presenting a faulty signal as a believable process value.
6. Map the Engineering Value to WinCC
Create a WinCC process tag mapped to the final engineering value, such as Furnace.Temp_PV_C, and if useful a second Boolean such as Furnace.Temp_QualityOK. Use the engineering tag for numeric displays, alarms and trends.
| WinCC tag | Purpose | Archive? |
|---|---|---|
| Temp_PV_C | Actual process temperature | Yes |
| Temp_SP_C | Operator/process setpoint | Often yes |
| Temp_QualityOK | Signal validity | Event/diagnostic as required |
| AI_Raw | Raw diagnostic value | Usually no, unless troubleshooting requires it |
7. Configure WinCC Tag Logging / Historical Acquisition
In WinCC Classic, historical process values are configured through Tag Logging archives. In TIA-integrated WinCC products, configure historical tags/archive acquisition using the tools available in that generation. Define the acquisition mode and cycle from process requirements.
- Fast-changing motion/process loops may need sub-second or short-cycle visualization.
- Slow furnace temperature may be adequately archived every few seconds.
- Production reports may use event-based or longer-cycle values.
- Do not archive every tag at the fastest rate “just in case”.
8. Build the Real-Time Trend in WinCC
- Insert the appropriate trend control on a diagnostic/process screen.
- Add
Temp_PV_Cas the primary pen. - Add
Temp_SP_Cas a second pen for setpoint comparison. - Select online/live or archived data source as required.
- Configure Y-axis engineering range and units.
- Choose a meaningful time window.
- Verify cursor/readout functions for commissioning.
A useful trend tells a process story. For temperature control, plotting PV and SP together is more valuable than plotting PV alone.
9. Sampling, Archive Size and Performance
Archive load is approximately proportional to tag count and acquisition frequency. A 250 ms archive cycle generates four samples per second per tag, while a 5 s cycle generates one sample every five seconds. Choose the cycle from process dynamics, investigation needs and retention requirements.
Use a fast live display where needed, but do not assume the historical archive must use the same frequency. Separate operator visualization needs from long-term historian/reporting requirements.
10. Troubleshooting Analog Scaling and WinCC Trends
| Symptom | Likely cause | Check |
|---|---|---|
| PV always 0 | Raw input/connection issue | PLC online raw value and channel diagnostics |
| PV wrong by constant factor | Wrong engineering range | SCALE_X MIN/MAX |
| PV reaches only part of range | Wrong raw span/module range | Channel configuration and NORM_X limits |
| WinCC value correct, trend empty | Archive/pen configuration issue | Historical tag, acquisition, time range |
| Trend has excessive data | Archive cycle too fast | Process dynamics vs logging frequency |
11. Hands-On Lab: Temperature PV + SP Trend
Simulate a raw value from 0 to 27648, scale it to 0–100 °C with NORM_X and SCALE_X, map the engineering value to WinCC, archive PV and SP, and display both on a trend. Step the setpoint and observe process response.
Siemens Analog Scaling + WinCC Trend Lab
Hands-on lab- Use a training or test system, not a live production plant.
- Document the starting PLC/WinCC state and expected result.
- Verify communication and backups before applying engineering changes.
Verify raw signal
Monitor the analog raw input and channel status.
Scale in PLC
Apply NORM_X and SCALE_X using documented ranges.
Archive in WinCC
Create historical acquisition for PV and SP.
Commission the trend
Plot PV and SP with correct units/time range.
Frequently Asked Questions
What do NORM_X and SCALE_X do in Siemens PLCs?
NORM_X converts a value from a defined raw range into a normalized value. SCALE_X converts that normalized value into the required engineering range.
Is 0 to 27648 always the Siemens analog raw range?
No. It is a common nominal example for certain configured ranges. Confirm the actual module and measuring-range representation before using scaling constants.
Should WinCC trend the raw value or engineering value?
Normally trend the validated engineering-unit value. Archive raw data only when it has a defined diagnostic purpose.
Why does my WinCC trend show no historical data?
Check historical tag configuration, acquisition cycle, Runtime archive activation, pen data source and selected time range.
Should the WinCC archive cycle equal the PLC scan time?
No. Archive frequency should be based on process dynamics and analysis requirements, not the PLC scan cycle.
