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.

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.

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.

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.

Thanks. I'll give it a shot. Matt.

Yes X6 64 Bit.

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.

Thank-you.

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 used to use Quadrants with this controller. I found sometimes if the arc didn't start and/or finish at 0-90-180-270 then it cut funny and end up scrapping the part.

In the past I had a macro I would use to set the tool height. I would bring the tool down to the top of a '123' block, then go to program 08000 and press the start button. This would input the machine Z value plus 2.0" (a variable that was previously set and could be changed) into the height offset for that tool. This would effectively set the tool to the top of the table. Then it would retract the machine to the home position. I'm sure a macro like this could also be used to clear the D value at the same time. Matt.

I'd think if you are on private property then it is. But no one has complained about it, and some have actually praised it.

Smoking hasn't been allowed inside the workplace here for years. The place I work for took it one step further and banned smoking on the property at all. Down to the sidewalk they go. They are not even supposed to light up in their car in the parking lot, and this applies to any sub trades working on the properly also.

Are you changing the colour of Entities (IE wireframe, surfaces) or Solids? If Solids you need to go into the Solids tab (top of the toolpath manager), right click on the solid and click on Clear face and feature colours or something to that effect (the one at the bottom! sorry, I don't have Mastercam in front of me at the moment). Then the entire model will take on the colour you have selected as per your process in your post.

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

You could "Save As" your first file as a different file name, then import your second part model into that mcx file on a different level. Then you can back plot each toolpath 1 by 1 and as you do this reselect your geometry using the new model. Once you have gone through all the toolpaths and verified that each toolpath is attached to the correct feature (using backplot, verify to Solid model, STL Compare etc) you can delete the first model from the current file and you are done. Matt.

Thank-you. I do appreciate it. However, to be fair, I wasn't looking for a freebie. We were willing to pay our co-op student to do this, and he was asking for help on how to accomplish this on Emastercam which I recommended to him as a great resource, however he quickly determined it was beyond his capabilities and informed us of this. I did also make this request to my re-seller and have yet to receive a response, possibly because they saw it being taken care of here. Thanks again. Enjoy your weekend. Matt.

Hi Roger. Thanks for doing this script. Matt L is our co-op student here this term and I had asked him if he could do something up like this as he said he had some VB programming experience. I'm glad you were able to help out with this (ie. do it for him :-) ) I've had script linker installed and now this chook is working as I had hope, saving the file in the proper directory. There are a couple of additions that would make it better if possible: 1. To save the chance of overwriting an existing file, could it check the directory that it is writing to see if a file by the same name already exists, and if so give us the option of over writing or not, or ask for a new filename? I'm sure this won't happen a lot but I could see it biting someone down the road. 2. My "template" that I use already has a machine group and a toolpath group with the name "template-1" and "template-op10" respectively. Could these be change to replace the word "template" with the filename of the MCX-5 file? Thanks again for all your help on this. It should save me a good chunk of time and help to standardize where we all save our files. Matt.

Right now we use File Merge/Pattern to import a SLDPRT file into a "template" file that has some standard tools and operations defined. When we do that we need to "Save As" and pick up the filename of the imported file because the imported file maintains the name of the file it was imported to, in this case "template.mcx-5". The machine group name and template name are then changed from "template-1" and "template-op10" respectively to match the name of the part file. We are just looking to automate this process to save repeating this process for each part we program and to standardize to make sure the the mcx-5 files are going into a certain subdirectory of the directory where the SLDPRT file is.

Thanks everyone. I'll see about getting MU1 installed and hopefully I won't see this again.

Have you had this happen again? I'm experiencing a similar issue.

Good morning all. I'm looking for advice on machining a CAM on a turned part on a Haas ST20 with C Axis. I've uploaded the file M057055.MCX-5 to the FTP Site under the X5_Files directory. I've tried a bunch of different tool paths but none worked well for me. Multi Axis Rotary worked the best but the backplotted output didn't match the posted output. I have IHS looking at my post but it will be a few days before they get back to me. In the meantime I'm looking for other alternatives. I've tried C-Axis contour and transform the toolpath. In backplot it seems to cut off the highest lobe on the part. Also the posted code seems to back track on itself. I've tried three 3d surface parallel toolpaths with c axis substitution, rotating my planes 120 degrees each time to get all the way around but it gives me errors about y axis moves. I thought this might be my best bet to get it off the machine even if the cycle time is longer but with the y axis errors I can't even get proper post output (no axis moves). I know most of my issues seem to be related to the post output which is being looked at, but I'm just there wondering if there are any work arounds that might do the trick this time. Thanks, Matt.

Canada bound eh....I'm hoping to go to CMTS this year. It's been a few years since I've gotten out to it.

Our Haas alarmed out also from all the text in the header. I narrowed it down to the path and filename of the mcx file. There can be too many characters on that line which the machine doesn't like. The solution to keep the text at the header and still get it into the machine without an alarm is to eliminate the "*smcpath$," from this line: sopen_prn, sspace, "MCX FILE - ", *smcpath$, *smcname$, *smcext$, sspace, sclose_prn, e$ This may also be a problem for you in the line that displays the path and name of the NC file. Yours doesn't look too long. Mine always posts to a USB stick so it's never too long. Matt.

We have the tool change on startup disabled so I'm unsure what happens in this situation. It seems to move to that position whatever I do for a tool change, M06, ATC FWD, all the probe macros since I'm sure they are using M06. I might try it out one day, but for the moment I'm just going to leave the tool change on startup disabled.