It can be caused by a poor connection, but specifically is means that Data Terminal Ready signal has turned off, the cause of which is defective I/O Power Supply or Cable not connected or a defective P.C.B.
With regards to the Cable Configuration for a FS3 Control being different to most other Fanuc Controls, that has not been my experience and would be rather illogical for Fanuc to depart from what is considered normal RS232 cable configuration just for that control, notwithstanding that RS232 standards are rather loose.
The above parameters 0005 and 0068 should work, as I/O Device is set to "0", with the following PC Software settings:
Data Bits = 7
Stop Bits = 2
Parity = Even
Baud Rate = 4800
The cable configuration is neither your arse, nor your elbow and is a half baked Hardware Handshake cable and would have at best, through dumb luck, worked in one direction only.
The 6&8 bridge at the Control end, connected to pin 4 at the PC, is the typical workaround when you have an I/O power supply issue at the Control. Pin 4 at the PC is the Control's pin 20 counter part. Normally with a Software Handshake cable configuration, you have a bridge between pins 6-8 and 20 at the Control end, with pins 6 and 8 being asserted by pin 20. Check the voltage between pin 20 and 7(signal ground), or pin 20 and pin 1(protective ground); it should be circa 13vdc, or at least above 5vdc. In the case where the voltage between pin 20 and 1 or 7 is less that 5vdc, the workaround is to connect pins 6 and 8 at the Control to pin 4 at the PC.
The fact that you're getting the p/s086 alarm immediately, with a cable configured with pins 6,8 and 20 bridged, points to an I/O power supply issue; check the voltage on pin 20 at the Control end as described above. On any Fanuc Control, you can test the occurrence of the p/s086 alarm simply by disconnecting the cable from the Control and attempting a Send or Receive; the p/s086 alarm will be raised immediately.
There are normally two PC Software options when sending a program to the Control:
1. Have the Control made ready first, then initiate the Send from the PC immediately.
2. Have the PC made ready to send and wait for the Control to initiate the Send.
To achieve the above, the PC Software must have some means of selecting which method to use. The following picture shows the Pull Down of my home grown Editor/Comms Software, where either method can be selected. If "Wait for Machine" is selected, the Software will wait forever, whilst the Software is running, for the Control to initiate the Send.
View attachment 343727
With regards your PC Software displaying (waiting on XON from cnc to start transfer), I suspect that the Software is set to wait for the Control to initiate the Send. It does this by sending an Xon character (DC1 - ASCII 17) to the PC. If your PC is set to wait for the Control to initiate the Send, but the Control is made ready to send first, followed by having the PC Software send the program, the Xon signal from the Control will have been sent before the PC Software is made ready and therefore, the PC Software will have missed the Xon and remain waiting for the Xon that will never come.
Regards,
Bill