5ax primary axis angle question

[DaveR]

Trying to post out a 5 axis simultaneous program

 

I'm getting a message when I post the program, a window pops up and asks what the primary axis angle is.

 

I do not know what it is asking.

 

I have tried zero and 90, both result in an error message that I have exceeded motion limits, but he program still posts out after the error message.

 

the part is 1" tall so I don't know how that could have happened.

 

This is with the standard Haas trunion post

 

Any guidance appreciated.

 

Dave

[Jimmy Wakeford from Barefoot CNC]

Check your miscellaneous values. It sounds like you have told it to set an axis there.

[DaveR]

Well I left the misc values alone.

 

 

Where does it say to add an axis?

 

I just went back and looked at the error message again

 

Says

 

"vertical tool detected! Enter primary axis angle."

 

Currently trying a 5axMsurf path.

 

And its funny also because I ran this post with a part last week, with both simultaneous and positing tool paths and it worked fine

[K2csq7]

"vertical tool detected! Enter primary axis angle."

I have seen this error when there is an infinite number of positions the primary rotary axis can be positioned and still make a good part. If the code is good, you will need to look into your rotary limits (in the post or machine def)...not sure where, but I would check the post first (search inside for "limits"). If you can find and fix the limits, the second error (about exceeding the limits) should go away, but the first will always be there when there is an infinite number of positions the primary rotary axis can be positioned and still make a good part. Its not so much an error but a question asking you where you want the primary to be when carrying out the op.

[gcode]

Is the first operation in the file a 5axis toolpath??

If so try adding a point operation in Top/Top/Top to trick the post into setting B=0 A=0

[DaveR]

Here are my limits from the post, they appear to be correct.

 

Is it correct that the primary is the B axis, secondary is the A? Seems counter intuitive for some reason.

 

#Rotary axis travel limits, always in terms of normal angle output

#Set the absolute angles for axis travel on primary

pri_limlo$ : -9999

pri_limhi$ : 9999

#Set intermediate angle, in limits, for post to reposition machine

pri_intlo$ : -9999

pri_inthi$ : 9999

 

#Set the absolute angles for axis travel on secondary

sec_limlo$ : -120

sec_limhi$ : 120

#Set intermediate angle, in limits, for post to reposition machine

sec_intlo$ : -120

sec_inthi$ : 120

 

 

This is the first op, I tried adding a drill op from the top, WCS T and C planes but I still get the same errors or messages.

 

even with the machine def settings matching the post as far as axis limits go

 

 

 

Still getting that "tool cannot be positioned within machine rotary limits" message

 

could be the settings in the program, maybe I asked it to tilt too much without knowing it?

[Zoober]

Go ahead and post.

Then, after you get the error, you can open up what posted, and see where it quit. check the .err file also to make sure there are no other problems.

You will see it posted up to the point it can't continue because of the limits.

The vertical tool is because you are getting close to rotary zero. That will always cause grief.

See if you can add some tilt to keep from approaching rotary zero, as there are too many solutions as Keith said.

[JohnW@Kauffman]

What are the physical axis limits of your machine? On my 5 ax with C as the primary and A as the secondary, the post had a "C" limit of -120, +300. Problem was, the machine physical limit was -120, +295. If the program forced the machine to any point beyond 295, things got very interesting in a hurry

[Nils N]

I have that happen when I use curve 5 axis. I get the same message. It happens because I am using a line as my axis control, at zero or straight up and down where the rotary is zero. The controls are not sure where to start so I just except the 0.0 or put it in so it knows to start at zero. They post out correct and I've never had a problem

 

 

[Aaron Eberhard]

Depending on how your post is set up (I haven't run a HAAS 5 axis setup), You may be able to get it to stop posting the message by editing the initial primary angle in the misc values.

 

As was already mentioned, it's complaining because there's too many possible "starting" positions, and it doesn't know where it should start.

 

I've seen this sort of things on toolpaths where it needs to rotate to say, +185*, and it physically must move in the positive direction due to rotational constraints. If you want it to go +, but it calculates it as faster to get to A-175 (360 - 180 = 175), it can ruin your day.

 

What we do is use the "inital primary angle" to tell it "oh, hey, the machine is already at +90*, so you can calculate the first move from there," resulting in it saying, "well, if it's already at +90, it'll be faster to just the rest of the 95* in the + direction, instead of moving 265* in the - direction."

[DaveR]

Thanks for all of your replies.

 

I have used 90 degrees and it seems to post out OK, except it skips 1/2 of the part features because I've asked it to tilt out of range.

 

It's pretty clear to me now these are two separate issues, one fixed (the primary axis angle thing) and one user error...me telling it via some parameter to tilt too far.

 

The back plot shows this wild tilt that occurs during lead in and I'll bet that is where the problem is....I'll have to spend some time trying to figure that out.

 

I am getting some 5 axis training arranged, this 5 axis thing (simultaneous paths) is more daunting than I thought it would be.

[Zoober]

Not sure what lead-in strategy you are using, but try using fixed for lead in tool orientation as opposed to tangential.

That may tighten large tilt angles on approach.

[DaveR]

 

 

I tried using a fixed type lead in and out.

 

It did not appear to change this gouge, which is a lead in, not a tilt.

 

I still get the message that I've exceeded rotary limits but the back plot does not seem to show any violation of the limits.

 

The posted code appears to only cut 1/2 of the part although the sim and backplot cut the whole thing.

 

The part is just a cylinder with twisted blades around it

[DaveR]

Ahhhhhhahahahah

 

I got it!

 

Combination of the lead in and out and my cut order setting.

 

I changed that and now it does exactly what I wanted, cuts all blades all the way around.

 

Posted code looks good as far as tilt direction and all.

 

Thanks for your help!