Fanuc 0T RS-232: Troubleshooting Program Transfers

A Fanuc 0T RS-232 transfer can appear to have matching serial settings yet fail because the machine does not see the required hardware-status signals. In the documented case, the final fault was an incorrectly wired cable. Use the configuration below as a known working XON/XOFF starting point, then diagnose the control's OUTPUT indication before changing parameters.

Separate Serial Settings from Handshaking

Both ends must use identical baud rate, data length, parity, and stop bits. The evidence supports this working starting configuration:

A reported nonworking setup used 2400 baud, 7 data bits, even parity, 2 stop bits, and hardware handshaking. Although its serial framing matched at both ends, the transfer remained inhibited because the cable did not provide the required control signals. Matching baud and framing alone therefore does not prove that the interface is ready.

Apply the Supported Fanuc Parameter Starting Point

The working XON/XOFF configuration specifies parameter #0002 bit 0 = 1, bit 2 = 0, and bit 7 = 1. Set parameter #552 to 10 for 4800 baud. Set the control's I/O selection to 0 and select ISO format. Other complete parameter bit patterns mentioned in the evidence belong to different machines or unsuccessful configurations, so do not copy them without confirming their applicability.

Record the current values before changing anything. After configuring the control, set the PC software to 4800 baud, 7 data bits, even parity, 2 stop bits, and XON/XOFF. Do not leave the PC configured for hardware handshaking when using the loopback cable described below.

Wire the DB25-to-DB9 XON/XOFF Cable

For a Fanuc-side DB25 male connector and PC-side DB9 female connector, the evidence supplies this working pin assignment:

Continuity-test every conductor and bridge, then check for shorts between unrelated pins. Do not assume that a supplied schematic or cable is correct: the documented fault was resolved only after replacing a cable whose machine-end pin configuration was wrong.

Use the OUTPUT Indication to Locate the Fault

1. Prepare the PC software to receive, then command the Fanuc to output a known program.
2. Watch the control's OUTPUT indication. If it flashes briefly and then clears, the control sent the data; investigate the PC COM port, receive configuration, or data wiring.
3. If OUTPUT continues flashing until the transfer is manually stopped, the control is inhibited from sending. Check for the CTS signal at Fanuc pin 5 and inspect the bridge between machine pins 4 and 5.
4. If the control reports error 086, reader not ready, check the machine-side DSR circuit. In the documented XON/XOFF cable, machine pin 6 must receive its status through the bridge joining pins 6, 8, and 20.
5. If continuity and bridges are correct but no data arrives, use an inline RS-232 tester or an oscilloscope to verify port activity and distinguish a wiring fault from a failed machine or PC interface.

Bridging machine pins 4 and 5 allows the control to send without knowing whether the PC is ready. Always prepare the receiver before outputting a program when using this arrangement.

Transfer Programs and Verify Both Directions

For machine-to-PC transfer, place the PC software in receive mode before starting OUTPUT at the control. Confirm that OUTPUT clears and that the received file contains the expected program.

For PC-to-machine transfer, place the control in EDIT mode. If the transfer program can wait for the control's XON character, arm the PC sender first, then enter O plus the program number and press INPUT. If the file already begins with a valid O program number, press INPUT without entering another number. If the PC software sends immediately, prepare the control with INPUT first and then start transmission from the PC.

Verify communication in both directions. Successful output alone does not prove that the receive handshake is correct; successful input alone does not validate the transmit path.

FAQ