Help with Haas vf2

[EazyE]

Older Haas vf2 throwing alarm 243(bad number). this came after surfacing for 20 min or so the code line looks fine and it was only running a drip feed at 30.ipm so i would not figure that the control got starved. Any ideas?

[chris m]

Do a search for Haas alarm; several have been covered recently

 

BTW, where the f is lemontown? Leominster?

[EazyE]

Leominster it is..... And a search I will do.

[chris m]

Who are you working for, if you don't mind my asking; I live in Fitchburg, so I am not just completely nosy.

 

C

[EazyE]

Well I also live in the dirty burg.. upper side of cleghorn.. shoot me a email [email protected]

[chris m]

you have mail

[robgbritt@westpharma]

Try adjusting your baud rate. I've had this same alarm on a vf3 while drip feeding, but I can't remember wether I went up or down on it. Seemed to work though.

[robgbritt@westpharma]

I want to say I slowed it down.

[Colin Gilchrist]

This is almost certainly a communications error.

 

How long is your cable?

 

Is it shielded?

 

What kind of computer? What OS?

 

All of these things can effect your data transmissions.

 

Is the cable running by any power lines in your shop? These can cause interference.

 

I usually run the baud rate at least 9600 and preferrably 19,200...

 

Because you are surfacing I would lean towards data starvation at 300 baud.

 

HTH,

[EazyE]

Rob thanks I will also give that a try.. It must be the drip I restarted the program without changing anything and going on 30 min without a problem.

[EazyE]

Colin I am currently at 9600. the cable is 6ft only using 3ft so 3 is wound and tied. It is shielded running on a older dell with windows 2000.

[Colin Gilchrist]

Then it is your baud rate. 6 ft is perfect, the shorter, the better.

 

I'm just used to seeing the guys that have a 50 or 100 ft unshielded cable that they have zip-tied to their power lines.

 

Sounds like you know what you are doing. I run all my stuff at 19,200 on a Haas and have never had any problems. 9600 should work just fine as long as the moves in your code aren't too fine. If you are doing some intricate surfacing with lots of code, you might want to go higher than 9600.

 

Anyone else want to chime in on baud rates here?

[John Morris]

Just a sidenote, make sure your power options are all turned off so the computer does not try to hibernate,sleep, shutdown hardrive or anthing of the sort. I run mine with only a blank screen for a screen saver and no other applications running.

[EazyE]

Although it has happened once or twice before with no explanation since starting over an hour ago it has not stopped again..

 

Colin, I will bump that up a bit where this program is not as intricate as others it sounds like it could help anyway... Thanks for your input

[chris m]

quote:

---

Anyone else want to chime in on baud rates here?

---

We run 19200 on every machine we own newer than about mid-1990s. Early '90s machines we run 9600. Machines older than that we run 4800 on down to 1200, depending on what the control will bear. Any machine built in the last 10 years should run 19200 no problem, I think.

[Colin Gilchrist]

Eazy, any time man, I'm happy to help.

 

Chris, my thoughts exactly. Only older controls should be lower.

[EazyE]

Well maybe I should leave it.. This machine has a serial number in the low 4,000's its a couple years old..

[Chris Rizzo]

Whatever the highest speed is listed. Older machines 19,200, newer ones 115,000. Cables in the range of 10-20 feet. Good quality Grizzly cables.

I have used one older O-E with a really lousy cable setup and had to run 9200. 115,000 is great for loading those longer programs into the extended memory control too.

 

I've had very, very bad experiences drip feeding over the Haas ethernet, but that's another story.

[gcode]

quote:

---

zip-tied to their power lines

---

and the computer sitting next to an arc welder