This is probably a bit of a dumb question. Is the process for running a file manually, without the ATC, just using the non ATC post processor and saving it in the root of the USB? I purchased a 3D printed QCW mount for the ATC and subsequently ran the spindle into it while trying to run a program. I had done all the load testing etc, it was some issue with soft limits and when I cleared the error, the spindle ran into the toolsetter and broke the mount. So until I get that fixed, I need to run in manual mode and just want to make sure I understand the process.
You don’t mention which CAD/CAM you’re using, but in Vectric, I select the checkboxes for all of the files that use the same tool, and then under “Save Tools”, I select “Visible Toolpaths to One File”. Make sure that the toolpaths are in the order you want to run them on the list, you can move them up and down. For example, I generally run interior cutouts before cutting the outside part profile to reduce strain on the material.
Because the software uses a default generic title when batching toolpaths, I usually append a reminder on the end of the saved toolpath, e.g. “E25” if I specify a 1/4-inch email for the toolpaths that I’ve batched. When the toolpath has completed, change manually (horrors!) to the next tool, load the next batch file, and off you go.
Other programs probably include a similar workflow.
How I wish there were an ATC for the BB controller!
1 Like
I probably didn’t explain things well enough. First of all, I am using Vectric. With that said, I am familiar with how all the tool path settings work. I am wondering if I just need to use the non ATC Onefinity post processor to run the machine manually and then save the tool path files in the root directory instead of the ATC subroutine folder.
1 Like
If you’re using the subroutines then set the tool number to 5 (or whatever number you designated as your manual tool change tool number in the web UI). When you run your file it should prompt you to load the bit and proceed as normal.
If you want to totally bypass RapidChange and the subroutines then I would setup the tool you want to use in the Masso tool library using some other tool number not assigned to the pockets or the manual tool change pocket you have assigned in the web UI. You can go to the Masso tool library and open that tool number and hit the 2 buttons to manually load the tool and then zero it. I would think you’d need the regular non Rapidchange version of the post processor when exporting the file you want to run from Vectric.
2 Likes
is there a rapid change post processor?
if you’re running the ATC using the subroutines then you should use the RapidChange post processor. If you’re using native Masso integration you would use the regular post processor.
2 Likes
ok i downloaded the rapidchange PP and resave the tool paths with the seemingly correct PP from rapid showing when i saved the tool paths brought it to the masso tried to load the program and it told me it could not find the sub program.WTH?
Looks as if neither one works. I ran the tool changer test fine but it will not change tools whatsoever. Getting close to saying to hell with it and selling it off. Never had one before and things ran fine.
FWIW I had much better success using the native Masso integration. There are trade offs but IMO it’s a lot more user friendly. You may want to give it a try before giving up. The setup process is documented on here in another thread
2 Likes