uploading from machine

[miljnor]

Serial (RS232) port interface pinout and signals
9pin # 25pin# Acronym Full name Direction Mean
3 2 TxD Transmit Data —» Transmits bytes out of PC
2 3 RxD Receive Data «— Receives bytes into PC
7 4 RTS Request To Send —» RTS/CTS flow control
8 5 CTS Clear To Send «— RTS/CTS flow control
6 6 DSR Data Set Ready «— I'm ready to communicate
4 20 DTR Data Terminal Ready —» I'm ready to communicate
1 8 DCD Data Carrier Detect «— Modem connected to another
9 22 RI Ring Indicator «— Telephone line ringing
5 7 SG Signal Ground

These are the pinouts for the 9db to the 25dp which are standard for most cables.

I have used a xmodem cable to flip the 2 and 3 pin to straight thru with no success.
although the pinouts for the cable wayne hill listed are different than these.

Did you make a cable Wayne?

the book says you only need pins 2,3 and 7 for xmodem trans. and This is what I prefer.

The cable is about 25ft.
The cable from the hass to hass is the same cable with xmodem in line. for the 2,3 pin swap.

[gar]

050516-1256 EST USA

miljnor:

Your cable will not work. You are connecting outputs to outputs and inputs to inputs. Your are probably in luck that normal RS232 circuits are designed with internal current limiting, for a 1488 type about 10 ma limit.

Do you really have XMODEM capability at the PC and is it the same flavor as HAAS uses?

Your best starting point is to use XON/XOFF handshake, and the following wiring.

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.

The cable connector at HAAS is male and female at PC.

To use RTS/CTS (hardware handshake) connect 4 at HAAS to 8 at PC, and 5 at HAAS to 7 at PC. This is what WayneHill showed you in his schematic.

.

[WayneHill]

Originally Posted by miljnor ... Did you make a cable Wayne? ...

Yes. I have four HAAS mini mills wired up and working fine with this cable wiring.

[miljnor]

Originally Posted by gar 050516-1256 EST USA miljnor: Your best starting point is to use XON/XOFF handshake, and the following wiring. 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. The cable connector at HAAS is male and female at PC. To use RTS/CTS (hardware handshake) connect 4 at HAAS to 8 at PC, and 5 at HAAS to 7 at PC. This is what WayneHill showed you in his schematic. .

This works! thanks for all of the help. you would think a commercial 9dp to 25db connector would have the wiring right. :frown:


but thanks to your alls help we are up and running!

[gar]

050602-0913 EST USA

miljnor:

Now that everything is working what parameters and handshake are you using?

.

[miljnor]

xon/xoff, 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.

7 bits, 2 stop, parity - none currently 19200 baud but some of the machines can go as high as 38k baud do to some wiring diffences we keep them all the same at 19200. which is ok because we don't do DNC just download or upload. and the biggest file transferr takes less than 1.5min.

[gar]

050602-1220 EST USA

miljnor:

I suggest that you use 1 stop bit because this reduces your transfer time about 10%. If you transmit with 1 stop bit, then the receiver must be set at 1 stop bit. You can transmit with 2 stop bits or more and receive with 1 stop bit. This is because the stop bit is at the end of the asynchronous transimitted word and is the same as the idle state of the transmit line.

You should use EVEN ( alternatively ODD, but most users use EVEN ) parity because this will detect any odd number of bit errors in the asynchronous transmitted word. A transmitted word is roughly 10 bits long. Length depends upon your parameters. On a HAAS machine a parity error causes a halt and indicates a parity error.

However, when you use parity ( even or odd ) instead of no parity then you add a bit into the transmitted word.

Thus, if you reduce stop bits to 1 and use parity, then your thruput will be the same as 2 stop bits and no parity.

Even though your files are not too large you should use as high a baud rate as your CNC will receive. This reduces transfer time. HAAS machines after about 1998 can operate at 115.2 kbaud. Overall we can transfer about 600,000 bytes per minute at this rate.

If you ran at 115.2 vs 19.2 you could transfer your 1.5 minute file in 15 seconds.

We have a product that allows 115.2 kbaud up to 4000 ft and peak isolation of 2000 v. You can visit our site www.beta-a2.com for more information.

.

[SLOWJOE]

I have read this topic and was nervous about hooking up my new haas machine to the computer for communication. So after reading everything posted I decided to call betatronics to see what he was selling and for some advise on setting up my machine and computer. After talking to Gordon (gar) the owner on Monday I decided to go with his product I232. It was sent out and I recieved it in the mail Wednesday and installed in less then 2 hours (most of that time was running the cable) and I was up in running with no problems. I can now run at 115.2 baud for super fast downloads with the benifets of the isolaters. The price for me to do this was priced very reasonable. I am not here to make a sales pitch for Gordon I am just a happy customer that got what he was sold. So if you need help give Gordon a call I am sure he can help. One more thing Gordon didnt even charge me till I told him that everything was working.

[deanrach]

Have you solved your problem yet?

[gar]

050615-0956 EST USA

deanrach:

If your question was addressed to miljnor, then the result was:

miljnor apparently originally had a cable that connected output to output and input to input. This was a commerical cable. After he corrected his cable, then he reported that everything was working.

.