A-axis error?

[Donkey Hotey]

OK, this one has me stumped. Late 2009 VF-5, has 4th axis but, it's been out for months and disabled.

Up until a few days ago, if you had an A-axis command in a program, the control would just ignore it and move on. This morning, I tried to run a program and it's giving me an A-axis alarm. Basically, it's commanding it and it's not there (duh).

The problem is that our post in Mastercam outputs A0.0 commands as safe moves after a tool change. The Haas used to just step over these commands without a hiccup. Now, we're out of business.

Anybody know what might have changed in the Haas and what to look for?

[underthetire]

Is there a dummy plug on the A axis hookup? If so, might want to take it off and clean/check it.

[Donkey Hotey]

Nope, no dummy plug of any kind.

[HuFlungDung]

To me, it seems strange that it would have had no problem skipping over an A command when that axis is not enabled.

Have you upgraded the Haas control software in the interim?

Personally, I don't see much logic in including A0 as a safety line for every tool change. As a program start line safety, yes.

But perhaps you can fool the controller by commanding G92 A0, which would have the effect of calling the current A position zero, and then, perhaps, the control might skip over any subsequent A0 commands. You'd just be lucky if it worked

[Donkey Hotey]

Nope, only two of us that use the laptop with Mastercam or the VF5. Nobody has touched it except us. I went through the alarm history and nothing out of the ordinary has been recorded (setting 51 override, random axis overtravel alarms from Graphics mode, etc).

I thought this was a new feature in the control (ignoring the A axis if it's not installed). I mentioned it to somebody in the Haas booth at Westec and they acknowledged that it was a good change (I guess other posts must do this as well). No mistaking: it has been ignoring A-axis commands since we got it nine months ago; this morning it changed its mind.

[Pondo]

You got yourself a female machine.

[Ydna]

Man I can never get any of our mills to accept an A code if the axis isn't enabled. Because of that I assumed it was the law! Granted all those machines are pre-2000. We have some newer machines but I've never tried it. Think I might do that later today....

I took out the A0 move from my 4 axis post because it usually just made unnecessary return-to-zero moves. You do have a 3-axis masterclam post yes?

Edit: I tried our 2010 machine and it accepted the block. hah

[haastec]

Originally Posted by Pondo You got yourself a female machine.

Or maybe the Mastercam software is the Canadian version.... A

[Delw]

Mine wont accept a "A0.0" unless the a axis is on. its a new one

Originally Posted by haastec Or maybe the Mastercam software is the Canadian version.... A

Thats funny stuff right there.

Delw

[Donkey Hotey]

OK guys, this one is odd. I just looked at our gantry router. Both machines were made the same month (one year ago). Every program I bring up on the gantry router has the same A0.0 commands near the start and end of the program. It causes no problems on the GR-712 and hasn't caused a problem until now on the VF-5.

I called the local HFO apps guy and he said the same thing (it shouldn't have worked in the past...don't know what's causing that).

So does anybody have any new ideas? Two machines, same month of build and they're behaving differently.

[KenFoulks]

Is there any difference in the code? For example:


G00 A0 X0 Y0 Z0

or

G00 Z0
A0
X0 Y0

[HuFlungDung]

Wouldn't it be easier just to modify the Mastercam post? Duplicate it, and name it so you know that it is for use when you have the A axis installed? Then modify the original and rename it as a 3 axis post. No point in trying to figure out how to force the controller to work incorrectly.