On a Sprint 65 with a Siemens 840C control, WINPCIN could read programs from the machine but every inbound transfer stopped shortly after byte counting began with 110032 - Archiving file is faulty. The confirmed cause was a format mismatch: the affected program originated as a PC-format file from another MF Sprint 65. Exporting and importing the program in paper-tape format resolved the fault.
Recognize the format-mismatch pattern
| Observation | Diagnostic meaning |
|---|---|
| Machine-to-PC transfer completes | The RS232 path can carry data in that direction; this reduces, but does not eliminate, suspicion of a cable or port fault. |
| PC-to-machine transfer starts and both endpoints count bytes | The endpoints establish communication before the control rejects the incoming content. |
| Error 110032 occurs with a newly supplied program | Check the file's source format before changing serial settings. |
| The program came from another MF Sprint 65 in PC format | This was the confirmed incompatibility in the resolved case. |
Separate PC format from paper-tape format
For this case, the Siemens 840C needed the NC program transferred in paper-tape format. The evidence identifies PC format as intended for commissioning-archive backup rather than importing and classifying an NC program. Merely selecting paper-tape mode at the receiving end does not convert a file previously exported in PC format.
Keep the format consistent across the complete file lifecycle: export as paper tape, retain that representation on the PC, and import it as paper tape. A program extracted in PC format and later presented as paper tape can still trigger error 110032.
Apply the confirmed recovery procedure
- Select paper-tape format at the Siemens 840C and in WINPCIN.
- Export a known program from the target machine in paper-tape format. Do not use a PC-format copy as the validation file.
- Return that unchanged paper-tape file to the same control using paper-tape import.
- Once the round trip succeeds, rebuild or correctly convert the externally prepared program using the validated paper-tape file structure.
- Import the corrected program and confirm that transfer continues beyond the point where error 110032 previously appeared.
Avoid editing the validation file with an editor that may alter its stored representation. Preserve the exported file unchanged until the round-trip test is complete.
Check communications only after validating the file
Set both endpoints identically. The evidence supports starting at 2400 baud, then testing 4800 or 9600 baud. It also supports testing either hardware RTS/CTS or software XON/XOFF flow control, provided both endpoints use the same selection. One proposed setup used 8 data bits, 1 stop bit, and no parity.
Another recollected setup proposed 7 data bits, even parity, 1 stop bit, and 9600 baud. Because the evidence contains conflicting character-format recommendations, do not treat either as universally correct. Record the machine's existing settings and make WINPCIN match them. Change one parameter group at a time only after a paper-tape round-trip file has been established.
If RTS/CTS fails, XON/XOFF is a supported diagnostic alternative, particularly when the cable does not carry every hardware-handshake conductor. If neither works, inspect the cable and determine whether the PC uses a physical serial port or a USB-to-serial adapter. The reported cable was approximately 1.5 m, and the successful final result did not require identifying cable length as the cause.
Verify the correction
Use an unchanged file exported from the same control as the acceptance test. A valid result requires the paper-tape export to complete, the same file to import without error 110032, and the control to accept and classify the NC program. Byte counters advancing alone prove only that transfer began; they do not prove that the control accepts the file structure.
If the unchanged round trip passes but an externally prepared program fails, compare their formats and generation paths rather than continuing to tune the serial link. In the resolved case, paper-tape export and re-import succeeded, confirming that the externally supplied PC-format program was the problem.
FAQ
What causes Siemens 840C error 110032 during an NC program import?
In this resolved Sprint 65 case, error 110032 resulted from importing a program derived from another machine's PC-format file. Exporting and importing the NC program in paper-tape format corrected the problem.
Can I import a Siemens 840C PC-format file as paper tape?
No format conversion was demonstrated by changing the receiver setting alone. Create or export the program in paper-tape format and keep that format through the WINPCIN import.
Which WINPCIN serial settings should I use with a Siemens 840C?
Match both endpoints exactly and start at 2400 baud before testing 4800 or 9600 baud. The evidence supports RTS/CTS or XON/XOFF but contains conflicting character-format recommendations, so use the control's documented or existing data-bit, parity, and stop-bit settings.