Any issues like this needs to be posted on the Mastercam forums

I get this when I try to run MCam 2018. I did try to reinstall, but same problem.

You will need to post this on the official beta forums.

Is it missing or am I just blind? Cimco has it.

Select File -> Options

Eric,

The bool conventional maps to a checkbox on the UI. The overrides are values set from the UI and whether the imported operations have depth or we are using the depth of the current drawing. You can set these to hard coded values while testing your code.

Mick

Mick,

 

I'm trying to use this snippet to reverse toolpaths after mirroring geometry. I'm missing some basic stuff though:

 

• How is the boolean(?) <conventional> assigned? (line 801 in the screenshot)
• How are the classes(?) <definition> and <overrides> initiated? (lines 814, 817)

 

I will be happy to do some homework on this, but a little nudge in the right direction could sure help.

Thanks.

The NET-Hook will run in X9 and 2017 as is, there are no specific dependencies. 

I can not get it to work.in X9. Run user application view fit.dll - result = invalid user application.

 

Thanks anyway

Did you unzip to a temp folder then copy to the chooks folder? If not the files will become blocked and wont run. Copy them out to a temp folder and right click each file and make sure they are unblocked, then copy them back.

Make sure that when you extract the files you do so in a temp folder before copying to the Mastercam CHooks folder because the files will be blocked and will not function.

Having said that I was able to created a new toolbar and add the functions as expected. Please see the attached image.

This is the best add on to mastercam and I have been using it from the mastercam x version.

 

I need help getting the add on to work for version X9. 

 

Thank you.

A quick and easy way is to filter out what objects (textbox, labels) to display based upon the string name contained in the tool description field. While this might not be the most robust method it is certainly viable.

From within the subreport add the detail format event from the object drop down and then add a little C# code. 

Simple test for the word "FACE MILL" (case sensitive)  returns true or false, based upon the result hide or show the controls.

The result:

I got word from the developer that this functionality is currently under investigation due to the differences in graphics interaction between Mastercam and Mastercam for SolidWorks. I believe that there is a SolidWorks function under View:screen capture but I am not entirely sure if that is at all helpful.

I am not too familiar with McfSW so I will look into it and get back to you.

Are you on a 4k monitor by chance? You should be able to see it as shown below.

Capture Icon missing:

 

The Camera icon, which I have seen in other posts, in the lower left corner of the Setup Sheet popup is missing in my window.

 

I would like to use the Capture feature; is there a setting I'm missing?

 

Thanks! 

Eric,

You're welcome. Any questions or issues feel free to reply to this thread.

David,

What version of Mastercam?

I was trying to create a point entity (PointGeometry Object) but i encounter an error in IDE. Object instanciation is correct but i can't commit it to database.

        Dim pointPerpGeo As New PointGeometry(New Point3D(pointPerp.x, pointPerp.y, pointPerp.z))

        pointPerpGeo.Commit()

Here is the error message from Visual Studio:

'Commit' has a return type that is not supported or parameter types that are not supported.

 

Any idea?

Attached is an example NET-Hook project that shows how to rename tool path groups and nci name.

Basically, run the NET-Hook, use the current drawing or prompt for one if there is none, prompt for a name, rename all tool path groups with the name and set the nci for each operation using the same name. 

Hope-fully this will help. If you are interested in writing your own NET-Hooks go to mastercam.com 3rd Party Developers section and down load the appropriate getting stated guide.

Source attached and NET-Hook attached.

NOTE 1: Extract NET-Hook to a temp folder before copying to Mastercam or it will be blocked.

NOTE 2: Not all operation types are support in the .NET API

Run NET-Hook - RenameToolGroups.dll

Select Drawing

Name prompt

Result

Post

Code - Main Entry Point

Set Name

Check drawing

Get Groups

Source_RenameToolGroups.zip

NET-Hook.zip

I'm quite sure we have done this in the past with a NET-Hook. I'll take a look tomorrow and see what I can find.

Crnko,

Could you give us a snippet of some code or more context in regards to the work flow, I am not entirely sure what you are after, thanks.

You need to create an instance of the FileSystemObject. Depending on what version of Mastercam you are running there is a code snippet for it in the editor. Type FSO and hit the tab key to generate the declaration as shown in the image.

Jason you should contact tech support or post on our official forums because your post here will likely be missed.

Roger,

Its there  you just need to add it to the Ribbon.

BenK,

We use Beyond Compare in house, to ignore block numbers just add a regular expression to filter them out and set ignore minor differences if you want them completely hidden.

That's what I use as well. Its a great compare tool but it still needs a few things in my opinion. I'm still trying to figure out how to have it ignore block numbers. 

 

 

 

 

I agree that Cimco could use a little work on the compare function. It has trouble when you get a lot of differences and basically gives up and marks everything as different. I still use it for the simple compares but when it gets more complex I move to Beyond compare. With that said I could understand if this wasn't their focus and it wouldn't bother me one bit if they didn't touch it. When I run across some specific issues I will send them to you. 

James,

What version of Mastercam are you using? Are you open to VB.NET or does it have to be VBScript?

If you are looking for NET-Hook project examples you can find them at http://www.masterchttps://my.mastercam.com/Communities/3rd-Party-Developers/NET-Hook-Downloads

If you have any specific requests please let us know.

You did copy both the DLL and FT to the chooks folder and edit your script to match the application name and function name? It should work.

Anyway, if you are looking into VB.NET NET-Hooks grab the free Visual Studio Community Edition and then the Intro doc and examples off Mastercam.

No Go - no error just nada. Level manager still does not show the levels and if I move geometry to a level it does not move either.

 

Thanks anyway Mick.

I think I'm going to force myself to move to the .net stuff. Too bad as the VBA is a real quick way for our shop to have a lot of little things automated.

The VBScript API is no longer in active development as we encourage users to move to NET-Hooks, typically VB.NET as the syntax is very similiar to VBScript. Having said that there is a bug with the Levels Manager where it does not receive update notification when changes are made via the VBScript API even though your level names have actually been set they are just not visible.

I did create a simple VB.NET NET-Hook that you can call from your script to update the display, I have attached the release NET-Hook, NET-Hook source and a screen shot of the script I used to test.

Unzip the NET-Hook and FT file to a temp folder away from your Program Files folder, right click each file to make sure they are not blocked, then copy them both to your Mastercam chooks folder. Update you script as shown above to call into the NET-Hook and run the Level Manager refresh method.

Any issues just let me know.

EDIT:

The way the script knows what to call is set in the NET-Hooks FT file, the Application (needs to be unique), in this case "__LevelManagerRefresh__" and the function entry point to call (set to HIDDEN so that it does not show in customize) "RefreshLevelManager"

LevelManagerRefeshNETHook.zip

LevelManagerRefreshSource.zip

Karl,

I'll be honest and say that I have not done anything with VBScript in a long time, I'll take a look at this in the morning.