SINUMERIK 840D PLC Alarm Generation via DB2.DBX190.0

SINUMERIK 840D PLC Alarm Generation via DB2.DBX190.0

On a SINUMERIK 840D / 840D sl control, PLC user alarms in the 700000–700999 range are the standard channel through which the PLC raises operator-visible messages on the HMI. The bit pattern DB2.DBX190.0 is one of the most common assignments used by machine builders (Deckel-Maho, DMG MORI, Gildemeister, and similar DMC-class machines) to trigger an alarm such as 700116. This reference explains how DB2 is structured, why STEP 7 cross-reference tools display DB?.DBX190.0 instead of the literal block name, and how to modify alarm logic in an existing program without corrupting the original PLC-NCK interface.

1. SINUMERIK 840D PLC Alarm Architecture

The SINUMERIK 840D integrates a SIMATIC S7 PLC (S7-300 in classic 840D, S7-1500 in 840D sl with newer PLC versions). The PLC and the NCK exchange information through a fixed set of interface data blocks. The HMI renders alarm messages that the PLC triggers by setting a single bit in a designated DB.

The 7xxxxx series is reserved for PLC user alarms. Each alarm is bound to one bit in the user-alarm data block. By Siemens convention in the standard PLC program template (Basic Program Plus / Basic Program), DB2 is the central user-alarm image DB on classic 840D, and the bit pattern begins at DBX180.0 and extends byte-wise. A bit such as DB2.DBX190.0 therefore activates alarm 700016 if the mapping follows the default template.

2. DB2 as the User Alarm Interface

In the classic SINUMERIK 840D PLC program (Basic Program, STEP 7 V5.x), DB2 is the user-alarm interface data block. Its structure is byte-aligned:

When the PLC sets DB2.DBX190.0 = 1, the HMI alarm handler polls the user-alarm image during each PLC cycle. The handler converts the bit position to the configured alarm number, retrieves the localized text string, and renders the message in the alarm line. The alarm remains active until the PLC clears the bit (or until power-off if the builder configured it as latching).

To activate the alarm the program can use any of the standard bit-assignment operations: S (Set), = (Assign), or conditional A / O followed by assignment. The simplest case is an unconditional latch:

// STL – Unconditional user alarm 700116
S   DB2.DBX190.0

More typically, the alarm is conditional on a process event:

// STL – Conditional user alarm
A   I 32.0          // e.g. door interlock open
S   DB2.DBX190.0    // raises alarm 700116

For a clearable alarm the PLC must reset the bit on a confirmation signal:

// STL – Reset on HMI Cancel
A   I 33.0          // HMI Cancel key (NCK->PLC bit mapped in DB10)
R   DB2.DBX190.0    // clears alarm 700116

3. Why the Cross-Reference Shows DB?.DBX190.0

STEP 7 cross-reference lists every address touched by the program. When the program writes the bit with an absolute block qualifier, the tool resolves the address to its literal DB number. When the program writes the bit with a relative qualifier, the tool cannot resolve the actual DB at compile time and prints DB?.

The STEP 7 instruction set allows two equivalent notations for DB-bit operations:

// Form A – absolute qualifier
OPN DB2             // open DB2 as the active data block
A   I 32.0
=   DB2.DBX190.0    // cross-reference shows DB2.DBX190.0

// Form B – relative qualifier
OPN DB2             // open DB2 as the active data block
A   I 32.0
=   DBX190.0        // cross-reference shows DB?.DBX190.0

Both forms write to the same memory location (DB2.DBX190.0). The difference is purely in how the program text is expressed. The compiler emits the same machine code for both. Cross-reference tools flag form B with DB? because they only track explicit DB references; they do not track the side-effect of OPN across statements.

4. STEP 7 OPN Statement Mechanics

The OPN (Open Data Block) instruction changes the active data block for all subsequent DBX / DBW / DBD references until another OPN DB, OPN DI, or block boundary resets it. The CPU maintains two internal registers: DB and DI. Most STEP 7 code uses the DB register; instance DBs use the DI register.

The hazard arises when an engineer inserts new code inside a network that already contains an OPN:

// Original program (before modification)
OPN DB31
A   I 32.0
=   DBX2.1       // writes DB31.DBX2.1
=   DBX21.1      // writes DB31.DBX21.1

// Engineer inserts new lines
OPN DB31
A   I 32.0
=   DBX2.1       // writes DB31.DBX2.1
A   I 32.1
=   DB2.DBX190.0 // absolute – writes DB2.DBX190.0 (correct)
=   DBX21.1      // writes DB2.DBX21.1 (BUG – should be DB31.DBX21.1)

The line = DB2.DBX190.0 does not change the active DB register; it is a one-shot absolute reference. The next relative reference = DBX21.1 still uses the previously opened DB2, not DB31. The original line = DBX21.1 silently changes its target from DB31 to DB2.

5. STL Code Examples for Alarm Generation

The following examples use standard STEP 7 STL (Statement List) syntax compatible with classic 840D projects in STEP 7 V5.x.

5.1 Basic Set / Reset Alarm

NETWORK 1   // Door interlock alarm
A   I 32.0          ; door contact
S   DB2.DBX190.0    ; set alarm 700116

NETWORK 2   // Reset on HMI Cancel
A   "HMI_Cancel_Key"
R   DB2.DBX190.0    ; reset alarm 700116

5.2 Edge-Triggered Alarm

NETWORK 3   // Latch on rising edge of fault
A   I 32.1
FP   M 200.0        ; positive edge flag
S   DB2.DBX190.0    ; latch alarm until reset

5.3 Grouped Alarm with Common Reset

NETWORK 4   // Spindle temperature alarm group
A   "SpindleTemp_High"
S   DB2.DBX190.0
A   "SpindleTemp_Critical"
S   DB2.DBX190.1

NETWORK 5   // Common reset
A   "HMI_Cancel_Key"
R   DB2.DBX190.0
R   DB2.DBX190.1

5.4 Alarm with Operator Acknowledgement (Quittierung)

SINUMERIK distinguishes clear (Cancel key) and acknowledge (Quittierung). Some user alarms require the operator to acknowledge the alarm before the bit clears. Implement this with a status handshake:

NETWORK 6   // Latch on fault
A   "DoorOpen"
S   DB2.DBX190.0

NETWORK 7   // Clear only after door closed AND ack received
A(   
O   "DoorClosed"
O   "DoorOpen_Ack"
)
A   "HMI_Cancel_Key"
R   DB2.DBX190.0

6. Ladder Logic Equivalents

In LAD/FBD the same operations are represented graphically. The key benefit of LAD/FBD is that OPN is implicit in the network's address notation; you always see the absolute DB qualifier:

|   I32.0    |   DB2.DBX190.0   |
|----| |-----|------(S)---------|     // Set alarm 700116

|  HMI_Cancel|   DB2.DBX190.0   |
|----| |-----|------(R)---------|     // Reset alarm 700116

If the existing PLC program uses STL with relative DB references, you can convert your alarm additions to LAD to remove the ambiguity. STEP 7 V5.x supports mixed STL/LAD/FBD blocks (single block source, mixed network types).

7. Risk Patterns When Modifying Existing Programs

When retrofitting a user alarm into an existing DMC-class machine PLC program, four patterns account for nearly all field regressions:

7.1 Recommended Insertion Pattern

To avoid breaking existing program flow, isolate alarm-setting logic in its own network block with absolute DB qualifiers:

NETWORK 100   // << ISOLATED ALARM INSERT >>
A   I 32.0
S   DB2.DBX190.0   // absolute – cannot leak DB state

Place this network at the end of the OB1 cycle, after all existing OPN statements have been resolved. The explicit qualifier protects against OPN side-effects from earlier networks.

8. Verification Procedures

After inserting alarm logic, perform the following four verifications before commissioning:

8.1 Static Cross-Reference Comparison

1. Open the project in STEP 7 V5.x (or TIA Portal for 840D sl with S7-1500 PLC).
2. Select Options → Reference Data → Display.
3. Filter on DBX190.0 in the cross-reference list.
4. Confirm every entry uses the absolute DB2.DBX190.0 notation, or trace each OPN statement preceding a relative reference.
5. Save the reference data before and after the change for diff comparison.

8.2 Runtime PLC Trace

Use the STEP 7 Monitor / Modify function or a watch table to force DB2.DBX190.0 to 1, then verify the HMI renders the expected alarm text. Confirm:

• Alarm number matches the configured 700116 identifier.
• Alarm text matches the operator manual / OEM text file.
• Alarm clears when the bit is reset from the watch table.
• No spurious alarms appear (indicating a corrupted DB reference).

8.3 Bit-Coverage Audit

Scan the entire PLC program for any OPN statement that could affect the DB active when your alarm network executes:

// Find in STEP 7 cross-reference:
OPN DBxx  // any open DB statement
A   ...
=   DBX... // relative – audit risk

If your new alarm network is inserted between such patterns, verify with the PLC in RUN mode and a watch table that the bit changes target the correct DB2 byte.

8.4 HMI Alarm Log Verification

1. Trigger the alarm from the PLC.
2. Open Diagnostics → Alarm Log on the HMI.
3. Confirm the entry shows alarm number 700116 with the expected text and clear time.
4. Confirm the alarm history persists across NC reset.

9. TIA Portal and SINUMERIK 840D sl Considerations

On SINUMERIK 840D sl with the S7-1500-based PLC (Basic Program Plus), the alarm interface is no longer DB2 but is exposed via PLC tags and the HMI alarm configuration in TIA Portal. The legacy DB2.DBX190.0 notation only applies to classic 840D projects using STEP 7 V5.x and the Basic Program (S7-300 PLC).

If the DMC machine is running TIA Portal Basic Program Plus, the DB?.DBX190.0 cross-reference artifact is replaced by tag-based cross-reference. The investigation described in this article applies to classic 840D projects only.

10. Best Practices for PLC Alarm Programming

1. Always use absolute DB qualifiers when writing alarm bits. This makes cross-reference unambiguous and prevents OPN side-effect bugs.
2. Group alarm logic in dedicated networks at the end of OB1 to avoid interleaving with existing OPN statements.
3. Reserve a contiguous byte range (e.g. DBX180.0–DBX195.7) for user alarms and document the bit-to-alarm mapping in a project README.
4. Latch alarms only when required by the safety case (ISO 13849-1 PL d/e functions). Unlatched alarms reset automatically when the trigger clears.
5. Provide explicit reset networks driven by the HMI Cancel key (NCK → PLC interface in DB10.DBX0.0 / DBX0.1) or by a defined operator action.
6. Avoid bit sharing: never write the same bit from two FBs or two networks — debug tracing becomes ambiguous.
7. Use DB2 only for user alarms: do not mix alarm bits with other process signals in DB2; this prevents accidental reuse by future modifications.
8. Document the alarm text source: alarm 700116's text comes from alm.txt (classic) or the HMI alarm list (TIA Portal). Cross-reference the alarm number with the text file before final commissioning.
9. Cross-check the basic program version: the alarm interface structure varies between Basic Program versions. Verify against the specific PLC library version in your project.
10. Capture reference data before each modification: STEP 7 reference data is the fastest way to detect unintended DB-state changes.

11. Troubleshooting Matrix

12. SINUMERIK Documentation and Standards References

The following manufacturer documentation is relevant for SINUMERIK 840D PLC alarm generation:

• SINUMERIK 840D sl product page — system overview, hardware variants, and PLC options.
• Siemens Industry Online Support — search index for SINUMERIK 840D manuals, Basic Program library release notes, and application examples.
• SINUMERIK 840D sl Function Manual — Basic Program — documents the standard user-alarm DB layout and the FB / FC blocks for alarm handling.
• SINUMERIK 840D sl Programming Manual — PLC — covers STEP 7 / TIA Portal project structure for SINUMERIK PLC programs.
• IEC 61131-3 — Programmable controllers, Part 3: Programming languages (defines STL/FBD/LAD semantics including DB handling).
• ISO 13849-1 — Safety of machinery: Safety-related parts of control systems (relevant when alarm bits are part of a safety function).