Troubleshoot FB1811 Alarm Text and Priority in PCS 7 CFC

If a PCS 7 alarm from an FB1811 CFC instance appears with “Text 5” instead of its configured wording, verify the exact message entry, display language, OS compile/load state and message-number concept. Siemens documents that CFC message texts and attributes are transferred to the OS during OS compilation, and that message priorities require a CPU-oriented unique message-number range in documented PCS 7 versions. The report does not identify its PCS 7 release or FB1811 library, so the exact cause remains unresolved.

What the Symptom Indicates

The alarm is triggered and displayed, but the visible text is “Text 5” rather than the wording entered in CFC; the reported priority also differs from the configured value. This shows that a message reaches the OS, but it does not identify whether the wrong text is configured for that event, the runtime OS is stale, the display language differs, or the priority setting is unavailable under the project's message-number concept. The source gives no screenshot, complete message configuration, PCS 7 version or FB1811 library origin.

Confirm the FB1811 Message Configuration

In the affected CFC instance, inspect the message configuration for the exact event that is raised. Siemens' CFC documentation says message-capable blocks expose message attributes and texts through the block's message configuration (Special properties: “Messages”); the text, message class/type and attributes are configurable per instance. Confirm that the configured text belongs to the event/message number shown in the OS, and determine whether “Text 5” is an entered string, a default, or a field label in the actual display. Do not infer the meaning of “Text 5” from the phrase alone.

Also verify that FB1811 is the intended message-capable block from the project's installed library and that no copied block type or older instance has conflicting message settings. The source does not identify the library or establish that FB1811 is a Siemens standard block.

Check Priority Eligibility

PCS 7 Engineering System V9.0 SP3 documentation states that message priorities can be assigned only when the message-number range is configured as “CPU-oriented unique.” Check the project's message-number concept and the message priority on the same CFC message entry that appears at runtime. If the project uses a different message-number scheme, the priority entered in CFC may not be available as expected under that documented version's rules. Verify the rule against the exact installed PCS 7 version before changing project-wide message numbering.

Check the Display Language

Compare the language in which the message text was entered with the active OS display language. PCS 7 Operator Station documentation describes selecting a default language for display devices and configuring message text in CFC. For multilingual projects, verify the text in every language used at runtime and ensure that any CFC text changes are compiled consistently. The forum reply raises a language mismatch as a possibility; it does not establish that this was the cause.

Compile and Load the Correct OS Data

Siemens' CFC V9.0 SP1 manual states that message texts and attributes configured in CFC are transferred to the OS during OS compilation. Recompile the affected OS with message data included, review the compile log for errors or warnings, then load the compiled OS project to the intended runtime OS station(s) using the procedure for the installed PCS 7 release. Confirm which server/client actually displays the alarm and that the loaded project is the one just compiled.

An OS compile/load and an AS program download are separate operations. The source reply mentions full compile and download as possible remedies, but reports no verified result. Do not download the AS merely because the OS shows an old text; download the AS only when the engineering changes alter the AS program and the approved PCS 7 workflow calls for it.

Verification

After loading the correct OS configuration, trigger or inspect the specific FB1811 event under a controlled test or suitable non-production environment. Confirm the event identifier, displayed message text, selected language and priority against the CFC message configuration and project message-number concept. If the text is correct but priority is not, troubleshoot priority eligibility and event association separately. Record the compile/load logs and the runtime station tested. The source reports no reproduced test or confirmed correction.

Limitations and Operational Precautions

The ticket omits the screenshot, PCS 7 version/update, FB1811 library owner/version, message-number range, active OS language, compile options and load status. Siemens behavior cited here is explicitly version-scoped to CFC V9.0 SP1, Engineering System V9.0 SP3 and OS V9.1 documentation; confirm matching instructions for the installed system. Do not change message numbering project-wide or download changes to a production AS without impact review and change control.

Engineer FAQ

What does “Text 5” mean in this alarm? The source does not provide the screenshot or message fields needed to identify it. Check the exact event's configured text and what the OS message list displays.

Does OS compilation transfer CFC message text? Siemens' CFC V9.0 SP1 manual says message configuration data is transferred to the OS during OS compilation. The compiled OS still must be loaded to the runtime station.

Why might a CFC priority not appear? Siemens' V9.0 SP3 Engineering System documentation says message priorities require a CPU-oriented unique message-number range. Confirm the project's numbering concept and exact message entry.

Could the language selection affect the displayed text? Yes, language mismatch is a source-reported possibility; verify the configured CFC text and active OS display language for this version.

Must I download the AS after every message-text change? The cited CFC documentation identifies OS compilation as the transfer of message text/attributes to the OS. An AS download is a separate operation and should follow only when AS program changes and the installed workflow requires it.

Technical References

Siemens, CFC for SIMATIC S7 (V9.0 SP1), Function Manual, 10/2017, A5E41356073-AB, §10.10.1 “Operator control and monitoring”: CFC message configuration, editable message texts/attributes and transfer to OS during OS compilation: https://support.industry.siemens.com/cs/attachments/109755021/s7cfcs7b_en-US.pdf
Siemens, Engineering System (V9.0 SP3), Configuration Manual, 07/2021, A5E39219444-AC, §7.9 “The PCS 7 message system”: priority range and CPU-oriented unique message-number requirement: https://support.industry.siemens.com/cs/attachments/109800501/ps7phesb.pdf
Siemens, Operator Station (V9.1), Configuration Manual, 02/2021, A5E50302515-AA, §6.4.8.2 “How to configure project-specific messages”: display language and CFC message configuration: https://support.industry.siemens.com/cs/attachments/109794374/ps7phosb_en-US.pdf
Siemens, Updating PCS 7 V8.0 SP1 Upd1 to V8.0 SP2, Entry ID 39980937, §3.6–3.7, illustrates the distinct OS compile, OS load and AS program load stages for that specific upgrade: https://support.industry.siemens.com/cs/attachments/39980937/39980937_pcs7_v80sp2_en.pdf

Troubleshoot FB1811 Alarm Text and Priority in PCS 7 CFC