Removing Default APL Alarm Event Texts (OUT-Binary Value Set) from MonDiL Blocks in SIMATIC PCS 7 WinCC

To permanently remove the default 'OUT: Binary value set' event text from MonDiL blocks in SIMATIC PCS 7 WinCC, the message text definition must be modified at the Master Data Library block type level or via Process Object View across all language columns. If changes in the Process Object View fail to compile into WinCC Alarm Logging, it indicates a project multilingual text mismatch, an un-synchronized block type in the Master Data Library, or an active text library cache in WinCC that requires an OS compile with 'Entire OS' and 'With memory reset'.

Root Cause of Persistent APL Message Texts in MonDiL Alarms

In PCS 7 v8.0, v8.1, and v8.2, the MonDiL (FB1848) digital monitoring block from the Advanced Process Library (APL) uses an embedded Alarm_8P call (SFB35) to report state changes. By default, Signal 1 (SIG1) is configured with the message event text OUT: Binary value set (or localized equivalents such as OUT: Binärwert gesetzt):
* The POV Disconnect:
Engineers frequently open the Process Object View (POV) -> Messages tab and delete or alter the text string. However, if the active project language in SIMATIC Manager does not match the default WinCC runtime language, the edit is stored only in the secondary language column. When the OS compiles, WinCC extracts the string from the default language table, restoring the unwanted text.
* Master Data Library Inheritance:
If the MonDiL block type in the project block folder differs from the Master Data Library (MDL) or if the block type template has locked system attributes, performing an OS compile without updating the Master Data Library block type can lead to inconsistent compilation results.
* WinCC Alarm Logging Cache:
WinCC Alarm Logging stores pre-compiled message texts in its Sybase/SQL CS database. A standard delta compilation will not overwrite existing message text fields unless changes are registered as a complete type update or compiled with memory reset.

The Message Architecture of Alarm_8P in PCS 7 Advanced Process Library

Every APL monitoring block relies on Alarm_8P message structures configured at the block type interface:
* SIG1: Monitored digital state change (Event: OUT: Binary value set).
* SIG2: Discrepancy alarm (Discrepancy error).
* SIG3 - SIG8: Maintenance, simulation, and auxiliary state alarms.
Each message event string contains format tags (e.g., @1%d@ or @1%s@) that substitute process tag comments and dynamic block attributes. When customer specifications require clean event descriptions (e.g., displaying only the equipment description rather than the raw engineering output string), the Event column in the block's Special Properties -> Messages dialog must be cleared or set to a custom descriptor.

Parameter and Message Attribute Matrix for MonDiL (FB1848)

The table below details the message configuration structure for MonDiL in PCS 7:

Message IDSignal AssignmentDefault Event TextMessage ClassConfigurable via POVLanguage DependentSIG1Out.Value (Digital Inversion)OUT: Binary value setAlarm High / WarningYesYes (English, German, French)SIG2DiscrErr.ValueDiscrepancy errorAlarm HighYesYesSIG3Auxiliary Message 1Ext. Value 1Status / OperationYesYesSIG4Auxiliary Message 2Ext. Value 2Status / OperationYesYesSIG5Simulation ActiveSimulation activeStatus MessageYesYesSIG6Maintenance RequiredMaintenance requiredMaintenance MessageYesYesSIG7Maintenance DemandMaintenance demandMaintenance MessageYesYesSIG8Unused / Reserved----

Step-by-Step Procedure to Remove Default Event Texts Across All Language Tables

To permanently eliminate or customize the default event text across the entire plant:
1. Synchronize Multilingual Settings:
In SIMATIC Manager, navigate to Options -> Manage Multilingual Texts -> Change Language. Note the current display language. Set the default language to match your WinCC OS runtime target (e.g., English (United States)).
2. Update Block Type in Master Data Library:
* Open the Master Data Library (MDL) for your project.
* Open the Blocks folder and locate FB1848 (MonDiL).
* Right-click FB1848 and select Special Properties -> Messages.
* In the Message configuration table, locate SIG1. Highlight the text in the Event column (OUT: Binary value set) and delete it or enter the desired replacement string.
* Click OK to save the block type.
3. Propagate Block Type to Component Projects:
Select the modified FB1848 in the MDL and click Options -> Charts -> Update Block Types. Select all target AS projects in the multiproject to ensure every instance inherits the clean message configuration.
4. Verify Process Object View (POV):
* Open the Multiproject in SIMATIC Manager.
* Select the root project node and switch to Process Object View -> Messages tab.
* Filter by Block Type MonDiL. Confirm that the Event column for Signal 1 is blank across all charts.
* If any instances still show text, select the entire column and press Delete.
5. Compile and Download OS:
* Right-click the OS Server object and select Compile.
* In the OS compilation wizard, select Entire OS and check the box With memory reset.
* Once compilation completes, perform a full download to the WinCC OS Server (or delta if runtime permits).

Resolving OS Compile Synchronization Glitches Between POV and WinCC Alarm Logging

If the unwanted string persists in WinCC Alarm Logging despite the steps above:
1. Inspect WinCC Text Library:
Open WinCC Explorer on the Engineering Station. Open Text Library. Search for the string OUT: Binary value set. If found, delete the entry directly from the Text Library table or rename it.
2. Verify Text Ref ID in Alarm Logging:
Open Alarm Logging in WinCC Explorer. Select the message corresponding to the MonDiL instance. In the properties pane, inspect the Event field and the associated Text ID. If the Text ID points to an old entry, forcing a full AS-OS text recompilation will rewrite the cross-reference pointers.
3. Reset Alarm Logging Runtime Cache:
In redundant OS pairs, stop runtime on Server B, delete the local DCF file or temporary cache, trigger an OS download, and restart runtime. Repeat for Server A.

Verification

To verify that the default text is removed:
1. Open the WinCC OS Runtime alarm page.
2. Trigger the digital input connected to the MonDiL block so that Out.Value transitions to active alarm state.
3. Verify that the incoming alarm entry displays only the block comment, tag name, and area descriptor without the string OUT: Binary value set.
4. Check the alarm log in both active runtime and historical alarm journal views to confirm consistency.

Limitations and Operational Precautions

Library Service Pack Overwrites: Installing a new PCS 7 APL Library update or running the APL Library Setup may overwrite standard blocks in the system library. Always maintain customized block templates inside your project-specific Master Data Library rather than system folders.
Empty Event Column Display: If the Event column is left completely blank, WinCC Alarm Logging might display an empty cell in the Alarm Banner. Verify that your plant HMI standards accept blank event descriptions or substitute a generic descriptor such as Alarm Active.
Compile Time Overhead: Compiling the entire OS with memory reset rebuilds the WinCC tag and alarm database from scratch, which can take 15 to 45 minutes on large projects with over 5,000 process tags.