Sinumerik 802D RS-232 PC-to-CNC File Transfer Troubleshooting

Asymmetric RS-232 file transfer on a Sinumerik 802D controller - where the CNC-to-PC direction works but the PC-to-CNC direction fails silently without raising any alarm - is one of the most common commissioning and shop-floor issues on Minimill-class CNC machines. The asymmetry is itself the diagnostic key: the receive path on the CNC side, the receive framing logic, or the receive handshake path has degraded, while the transmit path remains healthy. This reference covers the complete diagnostic tree from physical cable wiring through protocol configuration to part-program header requirements, and is written for engineers who need to restore bidirectional DNC/loading capability without returning the controller to the OEM.

1. Problem Definition and Failure Mode

The reported fault pattern is specific and reproducible:

• CNC to PC (receive on PC): Works correctly. The 802D transmits files, the PC receives them, and the file contents are correct.
• PC to CNC (receive on CNC): Fails silently. No alarm is raised on the HMI, no error code is logged, and the transfer appears to start and never complete.
• Cable: Verified visually, and was functional 48 hours prior.
• Part program sample shown by operator: Begins with %_N_16KK_MPF followed by ;$PATH=/_N_MPF_DIR, then standard preparatory commands G291 G64 G91 G28 Z0 G0 G17 G40 G49 G80 G90.

A silent PC-to-CNC failure (no alarm, no message) is most often caused by one of five root causes, ranked by field frequency:

1. Null-modem cable RX/TX crossover degraded or intermittent on one conductor pair only.
2. Receive protocol mismatch (XON/XOFF vs. RTS/CTS) between 802D and PC software.
3. Baud rate, data bits, parity, or stop bit mismatch on the receive side.
4. MPF file header malformed or path declaration missing the leading $ in column 1.
5. PC-side COM port or USB-to-serial adapter driver fault.

2. Sinumerik 802D V.24 (RS-232) Interface Specifications

The Sinumerik 802D exposes a single V.24 (RS-232-C compatible) channel on the rear panel, typically labelled X6 on the PCU / CCU housing. The interface conforms to the EIA/TIA-232-E and ITU-T V.24 electrical and mechanical specification and is intended for short-cable (<=15 m), point-to-point DNC file transfer to a host PC.

Key electrical characteristics inherited from the RS-232 standard:

The 802D V.24 channel is a true DTE (Data Terminal Equipment) port. To communicate with a PC, which is also a DTE, you require a null-modem (crossover) cable. A straight-through cable will yield exactly the symptoms described: TX from CNC reaches the PC, but RX from the PC is looped back to the CNC TX pin, not its RX pin.

3. RS-232 Protocol Fundamentals

RS-232 is asynchronous serial communication. Each transmitted character is framed between a start bit (space) and one or more stop bits (mark), with an optional parity bit. No shared clock exists; both ends must be configured identically for bits per character, parity, and stop bits or framing errors will silently corrupt every character.

Reference framing for a single byte (e.g. 0x41, the ASCII letter 'A', with 8N1, no parity):

Bits are transmitted LSB first. Bit time at 19200 baud is 52.08 microseconds; at 9600 baud it is 104.17 microseconds. Mismatch between sender and receiver of even a few percent in bit time will eventually produce framing errors, manifesting as silent receive failure on the 802D because the protocol layer discards the broken frame.

4. Cable Wiring: Null-Modem Requirements

Because both the 802D and the PC are DTEs, the cable must implement a null-modem crossover. The minimum required signal set is:

4.1 Minimum null-modem (3-wire, no handshake)

Used when both sides are configured for XON/XOFF (software handshake):

• DB9-2 (RXD) - 802D - to - DB9-3 (TXD) - PC
• DB9-3 (TXD) - 802D - to - DB9-2 (RXD) - PC
• DB9-5 (SG) - 802D - to - DB9-5 (SG) - PC

4.2 Full null-modem (7-wire, hardware handshake RTS/CTS)

• DB9-2 <-> DB9-3 (RXD/TXD crossover)
• DB9-3 <-> DB9-2 (TXD/RXD crossover)
• DB9-4 (DTR 802D) <-> DB9-6 (DSR PC) AND DB9-1 (CD PC) - loopback to assert DTE-ready to PC
• DB9-6 (DSR 802D) <-> DB9-4 (DTR PC) AND DB9-1 (CD PC) - assert DTE-ready to 802D
• DB9-7 (RTS 802D) <-> DB9-8 (CTS PC)
• DB9-8 (CTS 802D) <-> DB9-7 (RTS PC)
• DB9-5 (SG) <-> DB9-5 (SG)

4.3 Recommended cable

Use a shielded, twisted-pair null-modem cable with metalised backshells. The Siemens catalog reference for a ready-made V.24 cable for Sinumerik controllers is the 6FX2 series; consult the Siemens Industry Online Support portal for the current part number for your specific 802D variant. For a field-fabricated replacement, use at minimum three twisted pairs (TX/RX, RTS/CTS, DTR/DSR) with overall foil + braid shield bonded to the connector shell at both ends.

5. 802D RS-232 Parameter Configuration

Access the interface parameters through the operator panel:

1. Press Setup on the HMI.
2. Navigate to RS-232 (or V.24 on localised builds).
3. Open the Interface configuration page.

The relevant parameters for receive-side debugging are:

6. PC Software: PCIN and WinPCIN Setup

Siemens historically ships two transfer utilities for the Sinumerik family:

• PCIN - DOS-lineage utility. Configurable protocol and baud. Useful for legacy controllers.
• WinPCIN - Windows-native port of PCIN with the same configuration fields plus GUI feedback.

Whichever tool you use, the PC-side configuration must match the 802D byte-for-byte:

If you are using a USB-to-RS-232 adapter (very common today because no modern PC has a native DB9), verify the following before blaming the 802D:

1. The adapter uses a proven chipset (FTDI FT232, Silicon Labs CP2102, or WCH CH340 are widely compatible).
2. The driver is signed and current. Open Device Manager and confirm no yellow exclamation on the COM port.
3. The COM port number assigned by Windows is the one configured in WinPCIN. WinPCIN does not auto-detect.
4. The adapter supports the chosen baud rate. Some low-cost adapters cap at 115200 or have poor timing accuracy at 19200 in heavy electrical noise environments. Test at 9600 as a fallback.

7. MPF File Format Requirements

The Sinumerik 802D expects every part program file to begin with a specific two-line header before any G-code or comment lines. The file shown in the source ticket has the correct first header line and an incorrect second header line position. The format is rigid:

%_N_<filename>_MPF
;$PATH=/_N_MPF_DIR
; (program body starts here - comments, G-code, etc.)

Key requirements:

• % must be in column 1 of the first line. No leading whitespace, no BOM.
• The filename inside _N_..._MPF must be <= 24 characters, alphanumeric and underscore only.
• The _MPF extension identifies the file as a Main Program File. Use _SPF for subprograms and _INI for initialisation files. The 802D will silently reject a file whose extension does not match its target directory.
• The path declaration ;$PATH=/_N_MPF_DIR must be on line 2 and must start with ;$. A space between ; and $ causes the path to be ignored and the file lands in the wrong directory - a common cause of "transferred but not visible" symptoms.
• The line terminator must be CR+LF or LF. Some editors (notably Notepad in Windows) save with CR-only which older 802D firmware handles correctly but a few tools mangle. WinPCIN transmits raw bytes; the file's terminator is preserved.

8. Step-by-Step Diagnostic Procedure

Follow this sequence. Each step is non-destructive and produces a yes/no answer that localises the fault.

Step 1 - Inspect the cable physically

1. Unplug both ends.
2. Inspect each pin in the DB9 hood. Bent or recessed pins are the most common cause of "it worked yesterday" failures.
3. Check the backshell screws - loose shields invite noise pickup on RX.

Step 2 - Loopback test the cable

1. At one end only, jumper pins 2 and 3 (RXD to TXD). Leave the other end connected to the PC.
2. Run WinPCIN in Send mode with a short text file.
3. If the sent text comes back in the Receive window, the PC TX/RX/Ground path through the cable is healthy.
4. Remove the jumper.

Step 3 - Verify parameter parity

1. Open the 802D Setup > RS-232 page and write down every parameter.
2. Open WinPCIN's Configuration dialog and write down every parameter.
3. Compare them line by line. Any difference is a candidate root cause.

Step 4 - Test with a known-good minimal MPF

1. Create a file with the minimum legal content:

%_N_TEST_MPF
;$PATH=/_N_MPF_DIR
G91 G28 Z0
M30

2. Send it through WinPCIN to the 802D.
3. Watch the 802D HMI. If the file appears under Programs, the receive path is functional and your original file has a header problem.
4. If the file does not appear, proceed to Step 5.

Step 5 - Use a V.24 breakout box (line monitor)

A V.24 line monitor with per-signal LEDs (commonly available from electronics distributors) is the single most effective diagnostic tool for this fault. See the related Tripp Lite (Eaton) RS-232 cable reference for guidance on connector types and signal identification.

1. Insert the breakout box between the 802D X6 and the PC end of the cable.
2. Initiate a PC-to-CNC transfer of the TEST file.
3. Observe TXD LED on the PC side - it must flash on each character.
4. Observe RXD LED on the 802D side - it must mirror TXD on the PC side. If it does not, the cable crossover is faulty or the wrong pins are crossed.
5. Observe RTS (PC) and CTS (802D). If RTS is asserted by the PC but CTS is not asserted by the 802D within ~1 second, the 802D is in a non-ready state (alarm, wrong mode, full buffer).
6. For XON/XOFF mode, observe the XON (0x11) and XOFF (0x13) flow-control bytes appearing on the data line.

Step 6 - Capture and decode the byte stream

1. If a line monitor with a tap or a serial port sniffer is available, capture the bytes the PC transmits.
2. Verify the first two bytes transmitted are 0x25 0x5F (ASCII %_) and that the file begins exactly as the 802D expects.
3. Compare against what the 802D receives. If the bytes differ, the PC COM port or driver is altering the stream.

Step 7 - Re-seat or replace the cable

If Steps 1-6 point to the cable, swap it for a known-good null-modem cable. The original may have a partially fractured conductor (intermittent) that allows low-current TX from the 802D to register on the PC but fails on the higher-impedance RX path back into the 802D.

9. Cable Continuity Verification with a Multimeter

If a breakout box is not available, a digital multimeter with continuity mode is sufficient for verifying the null-modem wiring. With the cable unplugged at both ends:

For a 3-wire XON/XOFF cable, the RTS/CTS and DTR/DSR rows are simply not wired. For a hardware-handshake cable, every row must show continuity in the indicated pair.

10. Fault Symptom to Root Cause Matrix

11. Verification and Acceptance

After repair, perform the following three-step acceptance test before returning the machine to production:

1. Bidirectional transfer of a known-good program. Transfer a small test MPF from PC to CNC, then back from CNC to PC. Diff the two files. They must be byte-identical.
2. Program execution test. Load the transferred program on the 802D, single-block through the first five blocks, then run in AUTO. Confirm no alarm (in particular no 12080 syntax error, no 14011 path not found, and no 14012 file not found).
3. Long-file stress test. Transfer the largest program you intend to DNC (typically a 2-axis contour around 200 kB). Confirm completion without retry. If errors occur at high baud rates, fall back to 9600 baud and document the configuration.

12. Quick Reference - Minimum Required MPF Header

For operators who only need to fix the immediate problem without reading the full diagnostic, the two-line mandatory header is:

%_N_PROGRAMNAME_MPF
;$PATH=/_N_MPF_DIR

Rules of thumb:

• Filename <= 24 chars, uppercase letters, digits, underscore only.
• Use _MPF for main programs, _SPF for subprograms, _INI for initialisation files.
• ;$ at the start of the path line is mandatory - do not insert a space.
• Save as plain ASCII or UTF-8 without BOM. CR+LF or LF line endings both work.

13. Standards and Reference Documentation

• DigiKey - Understanding the RS-232 Standard for electrical and signalling fundamentals.
• Texas Instruments SLLA607 - RS-232 Glossary and Selection Guide for transceiver selection and timing.
• Tripp Lite (Eaton) RS-232 Cable and Connector Reference for cable assembly and connector pin identification.
• Wikipedia - RS-232 historical standard reference for protocol history and revision timeline.
• Siemens Industry Online Support for the official Sinumerik 802D operating manual, programming manual, and parameter manual (search "802D" or "SINUMERIK 802D base line").