Importing SLDPRT into MCX-5

[Matthew]

I tried it out this morning and it works great! It is exactly what I was looking for! Thanks again for doing this.

 

Matt.

[Matthew]

Hello all.

 

I've upgraded to X6 and installed this script. Almost everything works great, except that it saves the file as a .MCX-5 file.

 

What would it take to get this updated to save as a MCX-6 file? Or allow for a custom extension to be saved in the registry?

 

Thanks,

 

Matt.

[Roger Martin from CNC Software]

Matt

I'll take a look at this next week when I'm back in the office.

[Matthew]

Thank-you.

[NOTW Programmer]

Hello all.

 

I've upgraded to X6 and installed this script. Almost everything works great, except that it saves the file as a .MCX-5 file.

 

What would it take to get this updated to save as a MCX-6 file? Or allow for a custom extension to be saved in the registry?

 

Thanks,

 

Matt.

I've got some experience coding, I have done some work in access and VB.

 

Roger would this be the portion to change.

                
if (result)
               {                      
                   filename = Path.ChangeExtension(filename, ".MCX-5");<------------- change to ".MCX-6"                                      
                   // Tell Mastercam to save it as...
                   if (Mastercam.IO.FileManager.SaveAs(filename))

[Roger Martin from CNC Software]

The new MergeSLDPRT2MCX for X6 is available in the ZIP attached to this posting.

Please see the PDF in the MergeSLDPRT2MCX-6.ZIP for details on what this AddOn does.

 

Greyman,

I believe that the code snippet in the earlier posts is a bit out of date, but...

Yes, that would be one place in the code where MCX-5 needs to be changed to MCX-6.

There are a about 4-5 more occurrences that you'd need to upstate -

a few for the SaveAs dialog tile and filter and in a couple comments.

MergeSLDPRT2MCX-6.zip

[Matthew]

Hi Roger.

 

I'm encountering an error. It's giving me a .NET Library Error - Fucntion not found in Assembly CHOOKS\MERGESLDPRT2MCX.DLL

 

Do you have any suggestions?

 

Thanks,

 

Matt.

[Roger Martin from CNC Software]

Are you running X6 ?

[Matthew]

Yes X6 64 Bit.

[Roger Martin from CNC Software]

Very strange...

I know that I tested it (I'm also running Win-7 64-bit).

I've replaced the ZIP with the rebuilt (working) CHook in the post above ^^^

[Matthew]

Thanks. I'll give it a shot.

 

Matt.

[Matthew]

Hi Roger.

 

I'm still getting the same error with this. I'm not entirely sure it's the chook but I'm not sure how to fix it.

 

When I run the application from the toolbar, which is a "Mastercam X" logo now and not a "Solidworks" Logo, it gives me a .NET Library Error - Function not found in Assembly chooks/mergesldprt2mcx.dll.

 

I tried running it from the settings menu - Run User Application and get an Open Error - Unknown file type.

 

Any thoughts on how to fix this?

 

Thanks,

 

Matt.

[Roger Martin from CNC Software]

Matt,

 

Sorry - Haven't a clue.

 

I re-downloaded the ZIP from the post above and ...

Extracted all of the files into the Program Files\mcamx6\Chooks folder.

Started X6-MU2 (The MU would not make any difference here).

Setting-Customize - Category Files.

Selected the SW icon and dragged it to a toolbar

And it runs just fine.

[Matthew]

Do I have to do anything with script linker? The fact that it is showing the "X" logo does this mean anything? Maybe I'll delete the files and remove the button from the toolbar and try from scratch again.

 

Thanks Roger.

 

Matt.

[Matthew]

I deleted the files I had, I deleted the registry entries under X6 for the Merge sldprt chook, rebooted my computer, added the merge sldprt chook to the directory in programs files\mcamx6\chooks, opened up mcamx6 and it showed under settings-customize-file menu as a mcamx "X" logo. If I drag that to the tool bar and run it I get the same error I described above.

 

Matt.

[Matthew]

I just replaced it with the original x5 version of mergesldprt2mcx, which worked when I first installed Mcamx6 except for saving it as an MCX5 file, and that doesn't work either.

 

I'm at a loss and don't know what else to try. I'm open to any suggestions. I don't believe this is an issue with your script.

 

Matt.

[Roger Martin from CNC Software]

The only difference in the X6 version of this NETHook vs. the X5 is ->

I changed the file type to MCX-6 and for an X6 NETHook you build it with Visual Studio 2010 and it targets the .NET Framework v4

And you should have that, as it's a prerequisite for X6 (the X6 installer will make sure of that before it installed X6).

[Matthew]

When I first installed X6 I used the X5 version of this chook and it worked. When you updated the chook for X6 replaced the X5 one with the new one and it didn't work. I tried going back to the X5 version of the chook and it doesn't work anymore either. Do I need to try removing Mastercam and reinstalling?

 

Matt.

[Roger Martin from CNC Software]

Matt,

 

Try removing Mastercam and re-installing...

 

Rarely the solution despite what you may read.

 

email me (sdk <at> mastercam <dot> com) with an address that allows for sending Zipped attachments.

I'll shoot you a DLL (or two) to try.

[Christie]

On 8/20/2012 at 8:22 AM, Roger Martin from CNC Software said:

Matt,

 

Try removing Mastercam and re-installing...

 

Rarely the solution despite what you may read.

 

email me (sdk <at> mastercam <dot> com) with an address that allows for sending Zipped attachments.

I'll shoot you a DLL (or two) to try.

Hey Roger, sorry to resurrect a decade old post but I'm hoping you are still able to answer a question.

This C-hook has been working great for the last 2 versions of Mastercam I've been on (2019 and 2022). It has always renamed level 1 from "part" to the name of the sldprt file we are merging.

Since updating however, it just renames it to one of the features in the Solidworks feature tree such as "Chamfer #3" or "M4 x 0.7".

Any input as to why this might happen? I'm not sure if this is related to the c-hook or if it's due to a change in the way our feature trees are displayed.

[byte]

1 hour ago, Christie said:

Hey Roger, sorry to resurrect a decade old post but I'm hoping you are still able to answer a question.

This C-hook has been working great for the last 2 versions of Mastercam I've been on (2019 and 2022). It has always renamed level 1 from "part" to the name of the sldprt file we are merging.

Since updating however, it just renames it to one of the features in the Solidworks feature tree such as "Chamfer #3" or "M4 x 0.7".

Any input as to why this might happen? I'm not sure if this is related to the c-hook or if it's due to a change in the way our feature trees are displayed.

Hi Christie,

Fyi, Roger retired,

if you need to enforce the level naming after import, you could iterate through the list of imported levels and rename them to the desired name using this function 

DllImpExp bool set_levname (
    int lvl_no,
    TCHAR *new_level_name);
 

you can always reach out to the sdk team <sdk>at<mastercam>dot<com>