[fordav11]

terminal not ready can mean either the transfer settings are not correct or the cable is not correct or your handshaking method doesn't match the cable type.
you don't need to mess with cnc parameters.
look in the operation manual where it shows the parameters at the back. check the parameters in the
machine and write those down for baud, data bits, stop bits and parity.
set your PC software to the same settings then use PIP to read/punch a simple program.
if the transfer is working but it comes out as junk it means the data bits/stop bits are not correct.
really all 4 things must match on both PC and CNC (baud/parity/data bits/stop bits) and your handshaking
method must match the type of cable you are using (i.e. null modem cable with software handshaking or hard-wired
full handshaking).
If you can't get a known good cable working buy a simple RS232 tester on ebay (the type with LEDs showing RX/TX/DTR/DSR etc)
and test the ports on the machine.
I suggest you read some theory on rs232 wiring and functionality.....
RS-232 - Connecting Devices

[meposo]

fordav11

Thank you for the info on RS-232 wiring and functionality. The cable i made was from CIMCO Integration / Support. IT is the first one for hardware handshake. what does that mean regarding the CNC. Any specific mode or parameters i should put it in?

[meposo]

I am trying all morning to send a file to the computer using PIP. I keep getting the

320 RS232C terminal not ready ERROR 'write' error.

from MDI> CHECK DATA > DNC(B) pannel i get :


HOST CPU STATUS 1
CNC STATUS 0
PARAMETER Nb 0 byte
No 0 Byte
Ne 0 times
Tp 0 sec
To 0 sec
Ti 0 msec
Tx 0 msec
Tw 0 sec
CONVERT CODE 00
CONVERTED CODE 00

and of course the received data screen has all zero elements


Does this help? I would like to change the CNC status from 0 (not ready) to 1(CNC in normal status) but i dont know how...