Sinumerik 808D M-Code Not Activating PLC Bit: Troubleshooting Guide

The Sinumerik 808D ships with an integrated PLC that decodes every M-function called by the NCK before any user-defined side effect (coolant on, chuck open, bar-feeder advance, custom aux) becomes visible to the machine. When an operator types M11 into the MDI line and nothing happens on the PLC side, the failure is almost always one of four things: the user M-code is not pre-decoded by the 808D firmware and the PLC decode network is missing; the M-code strobe signal is not being read; the program is loaded on the controller but the wrong project is active on the PLC; or the M-function acknowledgement (M-ACK) is not being returned so the NCK never presents the M-code again. This guide walks through the full signal chain on the 808D, isolates each failure mode, and provides a working decode network that you can paste into your PLC project.

1. Problem Summary

The reported symptom is straightforward:

• Controller: Sinumerik 808D (turning or milling).
• Programming tool: PLC Programming Tool (ladder / FBD editor shipped with the commissioning package).
• User action: enters M11 in MDI mode and presses Cycle Start / NC Start.
• Expected result: PLC bit (intended to drive an auxiliary function, e.g., M100.0) goes TRUE while the M-function is active.
• Actual result: nothing happens on the PLC side. Trying other M-codes produces the same silent result.

The first suspicion usually falls on the NC program, but on the 808D, M-codes are decoded exclusively in the PLC. The NCK only transports the M-code number and a strobe; the PLC decides what to do with it. The fix is therefore in the PLC project, not in any G-code.

2. Sinumerik 808D M-Code Signal Architecture

The 808D NCK and PLC communicate through a fixed set of interface signals. M-functions flow from the NCK to the PLC along this path:

1. The NCK decodes a part-program block containing an M-word.
2. The NCK writes the M-function number to the M-function number interface word (typically M_FCT_NUM) and sets the strobe M_FCT.
3. The PLC reads the strobe and number, executes the user-defined action (set a memory bit, energize an output, run a subroutine), and acknowledges the M-function by toggling M_ACK or by reading the relevant pre-decoded signal.
4. The NCK clears the strobe after acknowledgement and continues with the next block.

The 808D pre-decodes a small set of standard M-codes that are required by DIN 66025 / ISO 6983 turning and milling conventions. Any M-code that is not pre-decoded must be handled by the PLC. The complete signal map is documented in the Sinumerik 808D Programming and Operating Procedures for Turning manual and the matching 808D milling documentation.

The critical implication: M11 is not automatically handled by the 808D. The NCK delivers it to the PLC interface, but if no PLC network reads it, the part program appears to do nothing. This is the most common root cause on 808D installations where operators or programmers expect "M-code support" out of the box.

3. Root Cause Analysis: Why M11 Doesn't Trigger the PLC

When a user-defined M-code such as M11 produces no reaction, work through the following checklist. Each item corresponds to a specific failure mode that has been seen on production 808D machines.

3.1 The PLC decode network for M11 does not exist

This is the single most common cause. A user adds M11 to the part program, writes a PLC network expecting the bit to come on, but never adds the network that compares the M-function number to 11 and sets the corresponding bit. Without that comparison, the NCK strobe pulses and the PLC ignores it.

3.2 The PLC project on the controller does not match the source project

The PLC project may exist on the programming PC but was never downloaded, or a different project was downloaded last. The 808D displays the project CRC / version string at boot — verify that the version shown on the HMI matches what you are editing. Many "the M-code doesn't work" tickets trace back to the PLC being in a stale or empty state.

3.3 The PLC is in stop / error

If the PLC has gone to STOP (SF LED on, BF LED on for bus errors), all M-code decoding halts. The HMI may show an alarm. Resolve the PLC fault first.

3.4 The M-function strobe is being read on the wrong edge

A common PLC error is using a level-sensitive contact on M_FCT rather than an edge-triggered comparison. On 808D the strobe is a pulse that returns low once acknowledged. Reading it as a steady-state signal can lead to missed M-codes, especially when the part program executes two M-codes in consecutive blocks.

3.5 The M-code is acknowledged before the user action completes

If the PLC acknowledges the M-code and the NCK advances before the user logic has latched the desired bit, the next decode cycle can miss the M-code. This is rare for simple bits but common when the action is delayed (e.g., waiting for a hydraulic cylinder to reach end-of-stroke).

3.6 M-code range or prefix conflict

The 808D distinguishes between single-digit M-codes (M0–M9), two-digit M-codes (M10–M99), and extended M-codes (M100+). Some user programs prefix M-codes with leading zeros (e.g., M011); the NCK interprets this as M11, but a ladder compare with the literal 11 still works. Confirm by reading the M-code number interface word.

4. Step-by-Step: Decoding a User M-Code on the 808D PLC

Use the following procedure to add M11 decoding to your PLC project. The procedure assumes you have the PLC Programming Tool for 808D installed and a working connection to the controller.

4.1 Prerequisites

• PLC Programming Tool for Sinumerik 808D installed on the engineering PC.
• Online connection to the 808D via Ethernet (X130 on the PPU) or RS232 service port.
• The current PLC project archive (.ptp or matching format) backed up to the engineering PC.
• Read/write access; the 808D must be in commissioning or service mode to download.

4.2 Procedure

1. Open the PLC project in the Programming Tool and confirm it compiles cleanly. Any pre-existing errors block the download.
2. Locate the section of the PLC program where M-code decoding lives. On a fresh 808D project this is typically in OB1 / main scan, but more often inside the spindle / auxiliary subprograms. Insert a new network titled M11_USER_DECODE.
3. Add a normally-open contact tied to the M-function strobe signal from the NCK→PLC interface (the symbol is typically named M_FCT or appears in the SINUMERIK symbol table as a flag representing the active M-function strobe).
4. Add a comparison instruction that reads the M-function number (the integer word, often M_FCT_NUM or the equivalent flag) and compares it to the constant 11.
5. On the comparison's TRUE output, set the desired internal memory bit (commonly M100.0 or a marker bit you have reserved for this auxiliary function).
6. If you need the bit to stay TRUE until explicitly cleared, latch it with a SET coil and add a separate reset network. If you need it to mirror the strobe, use a direct assignment.
7. Repeat the pattern for any other user M-codes (M12, M13, etc.) — one comparison per network, or one comparison block driving multiple SET coils if you prefer a single decode block.
8. Compile, download, and put the controller in a safe state (no part program running, doors closed, drives inhibited).

4.3 Ladder example

The following snippet shows a minimal decode network. Replace the symbol names with the ones defined in your project's symbol table. On the 808D the exact signal name varies by firmware version, but the structure is consistent.

Network 1: M11 decode (rising edge)
|  M_FCT  |     |  M_FCT_NUM = 11  |     | ( S ) M100.0 |
|  (NO)   |     |     ==           |     |              |
|         |-----|                  |-----|              |

Network 2: Clear M11 bit on strobe falling edge
|  NOT M_FCT  |     |  M_FCT_NUM = 0  |     | ( R ) M100.0 |
|  (NC)       |     |     ==          |     |              |
|             |-----|                 |-----|              |

For FBD users, the equivalent is a comparator block driving an SR flip-flop, with the strobe enabling the comparator.

5. M-Code Acknowledgement and Timing

On the 808D, the M-function strobe (M_FCT) must be acknowledged before the NCK continues. If your decode network never sends the acknowledgement, the part program will appear to stall at the M-line and the operator will see a "waiting for PLC" state. The acknowledgement mechanism depends on the M-code:

For most user M-codes on the 808D, a single acknowledgement pulse from the PLC suffices. If your action is fast (set a bit), wire the acknowledgement to the same network that sets the bit. If your action is slow (advance a turret and wait for an "in position" input), generate the acknowledgement only after the in-position input arrives.

6. Verification: Confirming M-Code Decoding Works

After downloading the modified PLC project, verify the decode network with the following sequence. Do this in MDI mode first, then with a short test part program.

1. Go online with the PLC and open the status / watch table view for the symbols M_FCT, M_FCT_NUM, and your target bit (e.g., M100.0).
2. Switch the controller to MDI mode. Ensure single block is OFF and the spindle / feed override is at zero for safety.
3. Type M11 on the MDI line and press NC Start / Cycle Start.
4. Observe the watch table: M_FCT should pulse TRUE for the duration of the decode, M_FCT_NUM should show 11, and M100.0 should transition TRUE (or pulse, depending on your latching logic).
5. Reset the controller and run a short program: M11 ; G04 F2 ; M30 ;. Confirm that the bit transitions at the M11 line and clears cleanly before M30.

7. Common Errors and Fault Codes

The 808D reports several alarm categories that overlap with M-code behavior. The ones most relevant to user-defined M-codes are summarized below.

8. Extended M-Codes (M100+)

If you need to use M-codes above M99 — for example to coordinate with a bar feeder or parts catcher that ships its own M-code convention — the 808D supports extended M-functions. These use a separate handshake, typically signalled by a "high" M-function strobe. Extended M-functions are disabled by default on most 808D builds; enable them through the relevant machine data in the commissioning area of SINUMERIK Operate, then add the corresponding decode network in the PLC. Confirm the exact machine data number against your commissioning manual before changing it on a production machine.

9. Alternative Decoding Patterns

Beyond the single-network comparator, two patterns are worth knowing.

9.1 Indexed decode block

For machines with dozens of user M-codes, a single decode block that reads M_FCT_NUM and drives a shift register or a demultiplexer saves ladder real estate and makes the project easier to maintain. The pattern is: strobe rising edge → latch M_FCT_NUM into a holding word → demux the holding word to N bits.

9.2 Edge-triggered SET with explicit reset

For safety-relevant auxiliaries (e.g., clamp, gate interlock), use a rising-edge SET on the decode comparator and reset only when an external "action complete" input arrives. This prevents the bit from being cleared by an unintended second M-function strobe or by a power-cycle glitch.

10. Field-Commissioning Checklist

Before signing off a machine that uses user M-codes, run through the following list:

• Each user M-code in the part program has a matching decode network in the live PLC project (verify via project CRC and online compare).
• Each user M-code is acknowledged within the time the NCK allows, or the part program has a G04 / dwell if the action is slow.
• The M-code decode networks are documented in the machine's PLC functional description.
• Standard M-codes (M00, M01, M02, M03, M04, M05, M06, M07/M08, M09, M30) still trigger their default behavior — your additions must not have overwritten any of the pre-decoded networks.
• The PLC project is archived both on the engineering PC and on a backup medium.
• If extended M-codes are used, the corresponding machine data is documented in the machine data sheet.

11. Quick Diagnostic Procedure

When a user reports "my M-code doesn't work," use this flow to localize the fault in under five minutes:

1. Confirm the PLC is running (no SF / BF LED, RUN LED on).
2. Confirm the PLC project version on the HMI matches the project on your engineering PC.
3. Open the watch table and confirm M_FCT pulses when the M-code is executed in MDI.
4. Confirm M_FCT_NUM shows the expected integer.
5. Confirm the decode comparator output transitions.
6. Confirm the target bit transitions and is not being reset elsewhere.
7. If all six steps pass and the physical output does not energize, the fault is downstream of the PLC (wiring, contactor, valve, E-stop).