G71

Hi Andy,
I am game to put the two together.
I have your G71 typeII python remap running.
I made some slight modifications and added G41/G42 cutter compensation to the python remap using some ugly hacks.
Computed the Z axis offset for each cut using trignometry. It is rudimentary and I would like to implement it inside rs274 so that we can use G41G42 compensation from the C++ code directly.
I also have the benporter/G71 running. I see how he has made the profile using profile and endprofile keywords.
Can you guide /review any changes to be made.
-automata

Hi Andy, Partik T,

Any ideas on how to compute the roughing finish pass with thickness specified by I,K.
I checked benporter patch and because of monotonic requirement on the profile for both X and Z axes, the roughing finish pass will not eat up any profile segments.
Any ideas on how to handle same for non monotonic passes.
-automata

I don't entirely understand the question but:
Could you add the offsets to the tool geometry before passing the data to the radius compensation code?

I did it all from scratch, including the maths. So I have not investigated which parts of the existing code that can be combined and reused

Being able to use the existing radius comp code (so that it is only done in one place, and consistently) is the only real reason to use C-code rather than the Python remap.

Hi Patrik T,

1. How come you first rounded out there corners with Q word? Any reason for that?
2. Did you try the finish pass with very large value of the offset?
3. If you offset a semicircle with different values in X and Z does the offset curve still remain a part of a circle?
4. How did you calculate which of the offsetted curves in a valley that would result in a self intersecting offset curve. Would a self intersecting offset curve be allowed in your method? If not , how do you remove the self intersecting portions?
-automata