NativeCAM is Features renamed

FernV wrote:
Hi Karl,
This may be just the error I was looking for. Nice if you succeed and have a po file.

Hi Fern,
in addition, in ncam.py after line 2208 you should add
self.builder.set_translation_domain('ncam')
otherwise the glade file entries do not get translated. Stupidly enough I was using
an outdated pygtk version before I got the translation stuff to work. 2.24 is fine.
Once I have a german version completed, I will send it to you if you like. I'll have to clone
your new version before that, though.
Best regards,
Karl

cncnoob1979 wrote: ...The part is not trashed however I'm trying to figure out why my 1/2in end-mill went outside of the planned trajectory. As you can see in the pictures I tried clockwise and counter-clockwise. I stopped the machine before any major damage.

I waited until the end-mill was done with the ramp in, the ran the table up to match the required depth I needed. After the ramp the machine stayed in the .75 inch constraints.

The machine would start to ramp in about .25in outside the planned cut. However I do not see that in gremlin.

I have not experienced this before. Is this a result of linuxcnc or NativeCam? Any ideas? Or ---- Did I do it to myself and not realize my mistake?

Hi

Using a pre-release version instead of a stable one is always risky but it is not the problem

In fact there is no problem with the pre-release version or NativeCAM in your case but some params not set properly.
First a few explanation : every shape you mill ends with a G40 (same for plasma), so it means it always starts with a G40 condition and when milling inside or outside, it will compute a pre-entry point at a distance which is off the start point by 0.501 X tool radius hence "about .25in outside the planned cut" then it will move in an arc to the entry point with a condition of G41 or G42. (The 0.501 factor makes it look like a straight line but it is the same formula in plasma where the factor is higher for a larger arc when firing the torch). This movement is always done at "cut start" + 'Workpiece/Milling params/Rapid to Z' + 'Workpiece/Milling params/Z clear', then moves down at G0 feed to "cut start" + 'Workpiece/Milling params/Rapid to Z' then to "cut start" at "Tool Change/Feed and speed/Vertical" feed. You can see this in simulation and the code is in lead_in.ngc and material.cfg

In your case, since you started at the high side of material, you could have increase params "Workpiece/Milling params/Rapid to Z" and/or "Workpiece/Milling params/Z clear" and/or "cut start". (If someone suggest a better name for those params, I will change it)
Experiment before running.
Increasing "cut start" would be sufficient I think

Another solution would be to rotate the circle 180° so it starts on the low side but it will take a big bite at the first half. I do not recommend this.

Hope this help.

Best regards
Fern

Hi Fern,

I just got Native Cam up and going thanks to some outside help. It looks like a useful tool.
So far without watching any videos I've figured out how to use it I think.

Thanks
JT

I've been using NativeCAM for a while now, and it's been very useful; the only thing it didn't offer that my old conversational control did was Helical moves, so I've written a quick sub for it - As usual with these things it's had little testing and probably too little sanity testing for its input - therefore use at your own risk! it's been fine for me, but YMMV!

(Strip the .txt from the cfg file and put the ngc in a folder LinuxCNC can see)



[Updated the ngc file - Realised I uploaded an older version with a few bugs]

[The running product]

orpheus wrote: ... I've written a quick sub for it - I've used it a few times today for some threadmilling I'd been putting off, and it's worked for both single-point and multi-toothed cutters. As usual with these things it's had little testing and probably too little sanity testing for its input - therefore use at your own risk! it's been fine for me, but YMMV!

Hi orpheus

Very well done, I will sure give it some serious tests if I can find the right cutter for it. And I will sure include it before long.

Best regards
Fern

orpheus wrote: ... therefore use at your own risk! it's been fine for me, but YMMV!

Hi orpheus,

You have done a fantastic job on this one and I am preparing to include it in the package.

Changes I will do

• rename it 'Thread Milling' (I think it is the purpose, right?)
• give the option to select metric or imperial no matter the mill setup
• imperial will be TPI which is standard
• move the cutter params to 'Tool Change' and add usage for threading, this will prevent wrong usage of the cutter
• I do not think I will buy a cutter to try it, so users should be warned

If you think of something else, let it be known

Best regards
Fern

p.s. : 'orpheus' or just Philip may be strange in the contributors list