Configuring Free Text Fields and Macro Expansion in PCS 7 Process Object View Messages

In SIMATIC PCS 7 Process Object View (Messages tab), the 5 Free Text fields (User Text Blocks) do not evaluate dynamic macro keywords such as $$BlockComment$$, $$ChartComment$$, or $$BlockType$$ during OS compilation. The PCS 7 Message Generator restricts macro keyword substitution strictly to the Event Text and Info Text fields. If entered into Free Text fields, the literal text '$$BlockComment$$' is displayed verbatim in WinCC Alarm Logging. To populate Free Text fields with block comments, chart names, or alarm limits, enter explicit text values in Process Object View or utilize the Import/Export Assistant (IEA).

Architecture of User Text Blocks and Message Fields in PCS 7

In SIMATIC PCS 7, alarm messages originating from technological blocks (via SFB35 ALARM_8P) carry structured message attributes into WinCC Alarm Logging. In the Process Object View (Messages tab), an engineer can inspect and edit standardized message properties across hundreds of blocks simultaneously.

The message table exposes several discrete text columns:
* Event Text: Describes the specific process condition (e.g., High Limit Violation, Motor Fault).
* Info Text: Contextual operator instructions.
* Origin / Area: Technological plant hierarchy path (e.g., Plant/Area01/Reactor).
* Free Text 1 to 5 (User Text Blocks): Five customizable text columns (UserText1 through UserText5) defined in the WinCC OS Project Editor to display supplemental diagnostic metadata (e.g., Equipment Tag, Unit Designation, Operating Limits).

Macro Keyword Substitution Rules in OS Compilation

To simplify message engineering, PCS 7 supports special macro keywords that automatically extract technological properties from CFC charts. However, the OS Compiler applies strict rules regarding where these macros are expanded:

Macro KeywordExtracted MetadataEvaluated in Event Text?Evaluated in Free Text (1..5)?$$BlockComment$$Comment entered in CFC block propertiesYes (Substituted during OS Compile)No (Output as literal string)$$ChartComment$$Header comment of the parent CFC chartYes (Substituted during OS Compile)No (Output as literal string)$$BlockType$$Name of the function block (e.g., MotL)Yes (Substituted during OS Compile)No (Output as literal string)$$Area$$Plant hierarchy area nameYes (Substituted during OS Compile)No (Output as literal string)@1%s@ / @1%d@Dynamic process value from ALARM_8P associated valueYes (Evaluated at runtime in WinCC)Yes (If configured as format parameter)

Table 1: Macro keyword evaluation rules across PCS 7 message columns.

Because the OS Compiler's message text parser does not process $$...$$ tokens within User Text Blocks, entering $$BlockComment$$ into Free Text 2 leaves the unparsed literal string in WinCC Alarm Logging.

Configuring Free Text Fields in Process Object View

To properly display block comments and custom information in alarm lists:

Configure Column Roles in OS Project Editor:
* In WinCC Explorer on the ES, open OS Project Editor.
* Switch to the Message Display tab.
* Under User Text Blocks, assign meaningful names to the 5 Free Text blocks (e.g., User Text 1 = Chart Name, User Text 2 = Block Comment).
Assign Values in Process Object View:
* In SIMATIC Manager, select the plant hierarchy folder and open Process Object View.
* Switch to the Messages tab.
* Locate columns Free Text 1 through Free Text 5.
* Instead of typing macro keywords, enter the actual desired string (e.g., enter the explicit chart name or comment).
* Utilize column copy-and-paste or fill-down operations across multiple rows to populate tags rapidly.
Execute OS Compilation:
* Compile the OS with option Changes Only.
* Confirm that the explicit text propagates into WinCC Alarm Logging.

Alternative Automation via Import/Export Assistant (IEA) and Scripts

For large facilities containing thousands of alarms, manually typing block comments into Free Text fields is impractical. Engineers automate this mapping using IEA:
1. In Process Object View, select all rows on the Messages tab, right-click, and select Export to File (CSV).
2. Open the exported .csv file in Microsoft Excel.
3. Use Excel string concatenation formulas to copy the Block Comment column directly into the Free Text 2 column.
4. Copy the Chart Name column into the Free Text 1 column.
5. Save the .csv file and execute Process Object View > Import from File.
6. This populates all Free Text fields across thousands of technological blocks in seconds without relying on unsupported compiler macros.

Verification

To confirm proper message text configuration:

In SIMATIC Manager, execute Compile OS (Changes Only).
Open WinCC Explorer on the ES or OS Server.
Open Alarm Logging: inspect the compiled message table.
Check columns User Text 1 and User Text 2: verify they contain actual chart names and block comments, rather than $$BlockComment$$.
Activate WinCC Runtime: trigger a test alarm and confirm that the alarm banner displays the customized user text columns cleanly.

Limitations and Operational Precautions

User text blocks are limited to a maximum length of 32 characters in standard PCS 7 alarm displays; text exceeding this length will be truncated on operator faceplates.
Free text entries are language-dependent: if the project supports multiple runtime languages, ensure translations are maintained across all active languages in the Text Library.
Modifying user text block definitions in the OS Project Editor requires recompiling all OS pictures and updating message screen layouts.

Engineer FAQ

Can dynamic process values like alarm setpoints be shown in Free Text fields?

Yes, but they must be connected as associated values (SD_1 to SD_10) on the ALARM_8P block and referenced using format placeholders such as @4%f@ rather than static macros.

Why does $$BlockComment$$ work in Event Text but not Free Text?

Siemens designed the OS Compiler message generator to scan for substitution macros only in specific technological event text templates, treating User Text fields as arbitrary user-defined static strings.