How-to
Showing Thousand Separators in WinCC TIA Portal Output Fields
Short answer
Digit grouping in a WinCC output field is presentation only: set it in the field's format pattern in TIA Portal when the target supports one, otherwise in the target runtime's regional settings, and verify with a known value on the deployed panel or PC runtime. The PLC value stays unchanged.
On this page
- Where does the thousand separator come from in WinCC TIA Portal?
- Is there an analog display object for this in TIA Portal V13?
- How do I set digit grouping in the output field's format pattern?
- Does the runtime's regional settings decide the separator character?
- What test values prove the grouping works?
- Why does the field still show no separator after the change?
- Can I add the separator to the PLC value instead?
- Questions asked
Digit grouping is a display property in WinCC, never part of the value: the output field's format pattern and the runtime's regional settings decide whether 100000 appears as 100000, 100,000 or 100.000, while the PLC tag holds the same number. In TIA Portal you build the pattern from formatting codes in the field's properties, compile, download, and verify on the deployed panel or PC runtime. The steps below identify the layer that formats the field, set the pattern, choose the separator character through the locale, and prove the result with known values.
Where does the thousand separator come from in WinCC TIA Portal? #
It comes from the display layer only: the output field's number-format pattern or the target runtime's regional settings decide whether digits are grouped, and the PLC tag that feeds the field never contains the separator.
A displayed number passes through two layers that matter here: the format settings of the field in the project, and the locale of the runtime that draws the screen. The grouping separator splits the integer part into digit groups; the decimal separator marks the fraction. Both characters come from the runtime's locale. The tag's value and its engineering scaling — a separate job, as scaling a PLC integer into a display value covers — stay untouched by grouping. Identify the target before changing anything: a panel project, a PC runtime, and a WinCC Unified runtime expose these format settings in different places.
Is there an analog display object for this in TIA Portal V13? #
No: the analog display object with an external value connection belongs to the classic WinCC V7 PC runtime, and a TIA Portal V13 panel project offers no equivalent, so the I/O field with a format pattern is the supported route.
If the screens run on a PC under classic WinCC V7.x instead of in TIA Portal, that is the runtime where the analog display fits, and displaying thousand separators in WinCC V7.5 I/O fields covers that route. In a V13 project, stop searching for the object and put a pattern on the fields you already have.
How do I set digit grouping in the output field's format pattern? #
Open the I/O field's properties in TIA Portal, edit its format pattern so the digit placeholders and the grouping separator form groups of three from the right of the integer part, then compile and download — the pattern travels with the project.
- Select the output field on the screen and open its Properties. Find the format setting for the field's mode; its content is the format pattern. WinCC Unified labels the property "Output format", and V20 groups it under "Display > Number representation" with the Mode set to Input/output.
- Build the pattern from formatting codes. The Siemens support entry "I/O field: Format pattern" (ID 109815056) describes the codes as placeholders for groups of characters: one code displays only the digits 0-9, others stand for the separators and the sign. Take the exact code characters from the help of the installed version, because a pattern copied from another WinCC generation may not compile for your target.
- Count the integer digits the field's maximum value needs and place the grouping separator every three digits from the right of the integer part. For a REAL tag, add the decimal-separator code and the decimal digit count the process needs.
- Record the pattern before and after the change, compile the project, and download it to the target with that device's normal transfer procedure.
The pattern keeps the change local to one field. For the wider picture of number formatting across WinCC generations, WinCC number formats that display thousand separators collects the version-specific details.
Does the runtime's regional settings decide the separator character? #
Yes: the format pattern fixes where grouping happens, but the locale of the runtime picks the character — a US-English locale shows 1,000,000 while a German locale shows 1.000.000 and swaps the decimal mark to a comma.
On Windows CE panels, including the WinCC flexible devices, regional settings are a device setting: reboot the panel, catch the startup screen before it closes, open the control panel, and set the regional options there. That change is runtime-wide — every number, date, and time on the device follows the new locale. Use the locale when the whole station should read that way; use the field pattern when only some fields should group.
What test values prove the grouping works? #
Test three values against the deployed target: a whole number that needs grouping, a fractional value that needs both separators, and a negative value — with 100000, 1234567.89 and -1234567 you cover every character the pattern must place.
Force the tag to 100000. The integer part has 6 digits, which is 6 ÷ 3 = 2 groups of three, split from the right as 100|000, so the display reads 100,000 or 100.000 depending on the locale while the tag monitor still shows 100000.
Force 1234567.89. The integer part 1234567 has 7 digits, so the groups from the right are 1|234|567 and the display reads 1,234,567.89. Check the arithmetic: 1 × 1000000 + 234 × 1000 + 567 = 1000000 + 234000 + 567 = 1234567, and the fraction 0.89 follows the decimal separator unchanged.
Force -1234567: the sign stays left of the first group and the display reads -1,234,567. Compare every drawn string with the runtime's tag monitor; the monitored number must equal the forced value digit for digit. You can drive these forces without the machine by testing HMI simulation against a live PLC. Precision is separate from grouping: if the pattern's decimal count is smaller than the value's fraction, the display shortens it, so set the decimal count first.
Why does the field still show no separator after the change? #
Because the change did not reach the layer that formats the field: the usual causes are a project that was never recompiled and downloaded, a pattern written with codes from another WinCC version, and judging the result in the editor preview instead of on the target.
| What you see | What to do |
|---|---|
| No grouping on any field | Recompile and download again, then confirm the pattern sits in the field's format settings on the target itself. |
| Grouping appears with the wrong character | The locale, not the pattern, picked the character; change the runtime's regional settings or accept the locale's convention. |
| One screen groups, another does not | One field carries a pattern while the other still follows the default format; copy the pattern to the remaining fields. |
| Drawn digits differ from the tag value | The tag was converted to a string or its scaling was changed; restore the numeric tag and re-check the monitor. |
| Display clipped or filled with overflow marks | The pattern's digit count or the field's width is smaller than the value; widen both. |
Locale-dependent characters only resolve on the deployed runtime, so the final check happens on the panel or PC the operators use, never in the editor preview.
Can I add the separator to the PLC value instead? #
No: a separator inside a numeric tag is not a number anymore — an integer tag cannot hold a comma, and converting the value to a string breaks every limit, comparison, calculation, and archive that consumes the tag.
The grouping separator is a drawn character, not part of the magnitude. Keep the process tag numeric and let the field format it. If a report or export needs grouped text, build that string at the report layer from the numeric tag, so the process side stays computable.
Questions asked
How many digits should the pattern cover for a DINT tag?
Ten: a signed DINT reaches 2147483647, so a pattern with ten integer digits and grouping displays it as 2,147,483,647, where the leftmost group keeps a single digit. A pattern with fewer integer digits cannot display larger values without overflow.
Do migrated format patterns survive a WinCC flexible to TIA Portal migration?
Treat them as unverified: after the migration, open each output field's format settings and compare the pattern against the code list in the installed TIA help, because generations differ in the codes they accept. Fields whose pattern did not carry over simply show the default numeric format.
Does grouping add load to the PLC connection?
No: the separator never travels with the value. The tag crosses the connection as the same plain number as before, and the runtime draws the grouped string on the panel, so update behavior and transfer load are unchanged.
Can an operator type the separator into an input field?
Plan for plain digits: have operators enter 1000000 without separators and let the field group the result for display. Whether a runtime also parses typed separators varies by version, so confirm with one entry test on your target before publishing the screen.