Linear Ramp Rapid Move

[mpuvdd]

Running a basic contour ramp around the rectangular portion of a part results in one of two results when ran on our Fanuc Onsrud router:

 

A. It ramps perfectly and cuts a rectangle with consistent 200 ipm feed rate

B. It ramps with the first leg being a rapid move and the rest of the tool path being normal G01 F200. (See highlighted code)

This happens on some parts but not all making me think the problem is driven by a geometry attribute. Any ideas?

MCAM 2018

Ill upload a zip2go when I get a chance.

Thanks,

 

Seth

[Leon82]

What do the linking parameters say? Double check the top of stock and feed plane

[mpuvdd]

Thanks Leon.

Clearance is off. Retract is off.

Feed plane: 1.0 Absolute

Top of Stock: 0.75 Absolute

Depth: 0.005 Absolute

 

15 hours ago, Leon82 said:

What do the linking parameters say? Double check the top of stock and feed plane

 

[Grimes]

your linking parameters page is the problem. you must be fairly new to mastercam, which is fine. but you should look at the lines going to the part in the linking parameters page. Top of stock, and Depth are ok, Feed plane as far as ive used is always in incremental, a bit above the top of stock. you should be using Clearance anything above the top of stock, Retract isnt required.

[mpuvdd]

Grimes,

 

I am new and learning. I’ll give it a try tomorrow. Thank you!

 

Seth

[JoshC]

if your new heres some free online training courses that may interest you, they are based off a newer version than what your using however most of the info on paths like that contour should be exactly the same. 

https://signup.mastercam.com/free-mastercam-training

just wanted to share this since you may not know that free training is available through mastercam

 

[huskermcdoogle]

I think everyone zipped past it.  But if you read the code the first feed move is actually the arc move, it should be the first Z move where the F25. is called out (missing a G01).  My bet is it is actually a post issue, nothing to do with his mcam file.  The null toolchange position line likely isn't updating gcode to 0 likely commented in with "" and therefore modality thinks it is in G1 already... which it isn't.  Hence when the value changes to 3 for the first arc move it outputs a G03.  Does it do this any time you have two operations in a row with the same tool?  Quick fix/test would be to check the force tool change on the tool page and see if the behavior is corrected when coming in from a fresh "toolchange".

[Grimes]

On 10/10/2022 at 7:07 PM, huskermcdoogle said:

I think everyone zipped past it.  But if you read the code the first feed move is actually the arc move, it should be the first Z move where the F25. is called out (missing a G01).  My bet is it is actually a post issue, nothing to do with his mcam file.  The null toolchange position line likely isn't updating gcode to 0 likely commented in with "" and therefore modality thinks it is in G1 already... which it isn't.  Hence when the value changes to 3 for the first arc move it outputs a G03.  Does it do this any time you have two operations in a row with the same tool?  Quick fix/test would be to check the force tool change on the tool page and see if the behavior is corrected when coming in from a fresh "toolchange".

ya husker, i wanna throw this into my computer tomorrow and see what it posts.

[mpuvdd]

I'm curious to see what you find. I am still trying to make sense of it all. It seems that using Grime's first recommendation (add clearance and set feed plane to incremental) helped somewhat. Still, there are several bits of code missing a switch to G01. I tried the "force tool change" and did not notice any difference.

I'll have a better update tonight on what's going on and may upload another file as well.

Thanks thus far! You all have given me some hope!

[huskermcdoogle]

Upload a zip to go with your post in it, or shoot me a pm and I'd be glad to take a look at it.