1991 VF1 RS232 Problems

[lovell110]

Hello all,
I'm sure this is simple enough to fix however I am failing miserably. I have made a RS232 cable to the following.(taken from another thread)

Pin 2 to 2, 3 to 3, 7 on HAAS to 5 on PC, connect 4 to 5 at HAAS, connect 7 to 8 at PC.

Use exactly the same parameter settings at both ends, and use XO/XOFF.

When I try to send a program to the machine it takes about ten lines then jumps to somewhere in the middle of my program. I can upload prgrams with ease which tells me the cable is fine at least in one direction. I have tried using MultiDNC/ MasterCam/ and my PDA that has a DNC package. I have all the parameters set the same.

I have noticed one thing! I used my PDA as the machine and had the same result. I think it has someting to do with my laptop(Dell Insirion 1150) and its com port configuration? Help while I still have some hair left.

[gar]

051120-2127 EST USA

lovell110:

You need to supply more information.

What are your parameter settings at HAAS?
What are the parameter settings at Computer?
How long is your RS232 cable, and what kind of cable?
Does the AC plug to the Dell have 3 prongs?
Is so what happens if you run on battery with the AC cord disconnected?
From the Computer is the sending FIFO set to minium? I do not think it will make a difference on HAAS, but in general it is a good idea.

How large is the file you are sending?
What operating system are you using?

Is the communication program in Mastercam from Cimco? This Cimco program should work well. However, on my Sony FX140 laptop using XP Pro it creates an unexpected break signal and HAAS faults on this. On our desktops using XP Pro the Mastercam Cimco program works fine.

If you run at a low baud rate like 1200 to 4800 does the problem occur?
Does HAAS produce an error message? If so what is it?

Have you used the PDA to send files to the HAAS? Does it work or not? Your comments were not clear on what all you tried with the PDA.

As described your cable appears to be correct.

What seems very strange is the loss of data with no error message. I am assuming no error message because you did not mention one.

Certain kinds of errors HAAS puts into comments. Others HAAS simply aborts the receive function with no useful information provided, for example they do not let you see the program up to the error.

For no HAAS error it implies that whole lines were dropped (delimited by CR LF) and this is an unlikely situation. It takes something other than a random noise error to drop exactly N lines.

.

[lovell110]

Gar,
Wow! I guess I left out too much information. I did a little digging and found my com port was set to: Baud 9600, Parity None, Stop Bits 1, Data bits 8.

I changed these settings to match my Haas and DNC and everything is working now. Thanks for the help. I'll be more descriptive on my next problem.

[gar]

051121-0756 EST USA

lovell110:

I would suggest that you or anyone else use 7 data bits, EVEN parity, 1 stop bit, and the highest baud rate that works reliably. However, you must use 8 data bits for XMODEM mode.

7 data bits vs 8 gives you about 10% greater thruput. EVEN parity catches many noise errors, but there is no correction, HAAS just aborts. 1 stop bit vs 2 is about 10% greater thruput. Admittedly EVEN or ODD parity vs NONE costs 10% in thruput, but the increased value of detecting many errors is worth the loss in thruput.

If you want high baud rate, long cable length, and electrical isolation simultaneously see our I232 System at www.beta-a2.com .