8 hours ago, Aaron Eberhard said:

Another way to do this is to use Convert to 5 axis, then use a Feed control Zone on the inside pockets to slow it down.  It'll work volumetrically, so any changes to the input toolpaths will be instantly updated.    I can grab a video tomorrow if it would be helpful.

That sounds awesome!

17 minutes ago, Colin Gilchrist said:

Change-at-Point is the best solution, because those changes are attached to the "chain", so the changes can be made in the Chaining Manager, and the modifications "stick" through regeneration.

Absolutely, I hadn't noticed that as an option until @bird2010 pointed it out, Every time I start to think I've got a pretty good understanding of MC's capabilities, I'm reminded of why my tag is what it is.

1 hour ago, Jake L said:

If you use the up/down arrows next to Position > Pass it will cycle thru each depth cut. If you want to change the feed on more than one depth cut you have to do each depth or "pass" individually.

Also keep in mind using toolpath editor will lock the toolpath. If the toolpath needs to be regenerated you will need to manually make all of the changes again after regenerating. This is why I only use toolpath editor when really necessary.

Edit: pic for clarity

Thanks, this was what I asked for & it works well.

38 minutes ago, bird2010 said:

If you are using 2D contour, you want to change the partial path feed rate to apply the change to all depths
"Maybe" Toolpath editor is not a faster way
You can try using the "change at point" function

This is even better! Thank you very much!

3 hours ago, GoetzInd said:

G, the universe was telling you that you needed to take a day off! 

To which G replied "Hold my beer"

47 minutes ago, JParis said:

You have "Point" & "Pass"....Point will take you along an entire Z level of the cut......when you get the top, change Pass so that you can get the points along the next Pass and so on if you have multiple depths of cut

I don't understand this at all. When I select Toolpath editor it opens this dialog:

Then, when I select Edit Point, this dialog opens:

How do I apply changes to all depths? I know I can select Section and, after clicking the green check, it will prompt me to choose the end point of my feedrate change. But it will only apply it to the first depth, and that's the rub that's got me flummoxed.

I have a contour path, with depth cuts, that I'm trying to change feed speeds in a section of the path, using Toolpath editor. I can't figure out how to apply the feed changes to both depths of cut.

Can anyone provide some direction for me?

Here's a link to benchmarks for your CPU

https://www.cpubenchmark.net/cpu.php?id=4692&cpu=Intel+Core+i7-12700F

2 hours ago, Mick George said:

Ah yes 2022 was kind of a preview so you can go ahead and create the folder in Shared and use that. You should find some samples online, you can also take a look at the NET-Hook samples as they both use the same API.

The inbuilt script editor isn't in 2022 though, correct? Can it be added?

13 minutes ago, Mick George said:

There is a NET-Script folder in Shared that you can use, there should be a few sample scripts in there also.

Hmm, there's a NET-Script folder in 2023 but not 2022. We are not moving to 2023 or 2024 due to issues that adversely effect our programming, mostly issues with viewsheets.

So, I guess we'll just try to figure out the VBScripts. I'm going to try putting the script in the shared VB folder & see if that works.

1 hour ago, Mick George said:

NET-Scripts are replacement for VBScript. I believe NET-Script was first added to Mastercam 2022.

VBScript is deprecated and will be removed completely from Mastercam 2025.

NET-Scripts use the same API as NET-Hooks but can be created using the inbuilt script editor.

There are several short video introductions to NET-Script on the Mastercam forums.

 

Thank Mick. I've watched a few of the videos on the Mastercam site, but I haven't run across any that let me know what folders to put the scrips into. I'll probably be using both the VBScript, for older files (we don't uprev proven files here), and NET-Scripts for our 2022 & newer files.

54 minutes ago, So not a Guru said:

I'm trying to learn how to use the 2017, that is a 2018 app, veiwsheets example, the overview says to install to the default Mastercam location, but it doesn't say where that is. Am I supposed to unzip the file into a specific folder, like the shared VB folder?

I see that the NET-Scripts appears to be a prefered add-on method, what folder should I locate these examples?

3 minutes ago, So not a Guru said:

I see that the NET-Scripts appears to be a prefered add-on method, what folder should I locate these examples?

How do I get the NET Script add in?

I'm trying to learn how to use the 2017, that is a 2018 app, veiwsheets example, the overview says to install to the default Mastercam location, but it doesn't say where that is. Am I supposed to unzip the file into a specific folder, like the shared VB folder?

7 minutes ago, So not a Guru said:

Once I've opened Visual studio, in administer mode, and downloaded a C# example from the Mastercam site, how do I open the project? Do I need to unzip the example into a specific folder? Or do I just unzip it wherever I like & open the folder from there?

NM, I found the instructions.

21 hours ago, byte said:

Yes you can use visual studio, the csharp project from the visual studio marketplace would be good for that

Once I've opened Visual studio, in administer mode, and downloaded a C# example from the Mastercam site, how do I open the project? Do I need to unzip the example into a specific folder? Or do I just unzip it wherever I like & open the folder from there?

19 hours ago, byte said:

Yes you can use visual studio, the csharp project from the visual studio marketplace would be good for that

Thanks, I'll try playing with it.

5 hours ago, byte said:

Sure viewsheets are accessible through the nethook api, I made an app a long time ago that store views heets in the toopath Manager window

Can I do this using Visual Studio?

Just now, So not a Guru said:

Can I do this using Visual Studio?

Or is this something done in Mastercam, like a chook?

Is it possible to create a dialog box that has the viewsheets in it? I have files that can have 70+ viewsheets & it can take quite a while to scroll back & forth between them.

7 hours ago, Aaron Eberhard said:

At my failed attempt to buy out a machine shop a few years ago, the old school owner very smugly showed me how much more efficient it was for him to spend 4+ hours grinding a tool to cut a small feature on the lathe instead of "wasting" $100 to just buy it off the shelf from Micro100...   That was a valuable lesson, just not the one he thought it was teaching...

Throwing away dollars to save dimes, doesn't sound as efficient as he believes!

6 minutes ago, cncappsjames said:

Only ever had to grind drills, corner radii, and a few form tools. I'd say the VAST majority of guys that can do that now have gray hair or no hair.

Generic carbide tools today are so inexpensive it's cost prohibitive for machinists to grind their own tools from scratch any more. IMHO of course.

My experience is exactly the same. I've also made a lot of custom form tools from tool steel flat stock, mounted into fly cutters.

But it's been many, may moons since that was required of me.

On 1/10/2024 at 3:31 PM, Metals and materials said:

Just curious to how those endmills and cutters etc etc  are manufactured and where. 

Another video

On 1/11/2024 at 10:25 AM, Metals and materials said:

Interesting! They are grinded. Wait so like these Kennametal's or Harvey grind those tools in hundreds of thousands of quantities?

 

Rob, at QC, says the line auto Z will be returned to default unchecked in 2025. So that's a plus.

And the response to the line issue.

Hi Zeke.

That is working as it should.
Because Create -> line is a function, Mastercam does not save any settings in that, or any function.
For example, if you create an arc, or a rectangle, and then shut down Mastercam, when you restart Mastercam, the dimensions you entered for the arc, or rectangle in the first session do not reappear in the restarted session.

So, since it was always unchecked in previous versions, it now being checked, as the default, is "...working as it should.".

What an unmitigated crock of sh*t.

Here is the response for the undo disappearing feature.

Hi Zeke,
This is a known issue and is logged ad D-53659.
I will add you name to the defect.
In the steps to reproduce the defect, if you press UNDO a second time, the geometry will come back.

Ok, I've submitted both to QC.