This is probably an easy one that I’m just drawing a blank on, but can anybody help me resolve this? Here’s a screenshot.
Try navigating to the4 file location that the error is telling you to go to. See if the file is located in that folder. If it is, Make a copy of it and move it to your Desktop and try and open the file in BobCAD from that location.
If it isn’t in that folder then it may be referencing that incorrect location.
Thank you. That worked. Seems to be fine now.
So today’s new error is a missing “MachSim.CL” file when I try to run the mill simulation. Any ideas? Thank you.
The mach Sim folder is your Machine Folder.
Right Click on Milling Tools inside your CAM Tree under CAM Part. Then go down to Part and then Current Settings. Go to the tab on the left that says Posting. Under the NC filepath. Make sure that the location is set to match the location below.
C:\BobCAD-CAM Data\BobCAD-CAM V25\NC\Mill
If that works, Make the same change as above except when you Right Click on Milling Tools go to Default and then Current Settings, not Part.
If that doesn’t work, then try Changing your machine by Right Clicking on Milling Tools inside your CAM Tree under CAM Part. Then go down to Part and then Current Settings.
When it opens go to the Tab on the left that says Machine Parameters. Tyr selecting one of the bobCAD Machines like the BC_3X_Mill. and then click on the Posting tab on the left and select your Post from the Post Processor box.
Let me know if any of that helps.
I tried your suggestions to no success. Should I be able to see the MachSim.cl file in Windows Explorer file tree? I can’t find one anywhere.
The MachSIM files are the machines that are used when Simulating. They can be found here:
C:\BobCAD-CAM Data\BobCAD-CAM V25\MachSim
Make sure that the machine you have selected in the Current Settings actually exists inside that folder.
I have selected the standard bc_3x_mill and it won’t simulate. It won’t simulate no matter what machine I choose. With all these problems, I’m starting to think the installation was botched thanks to our “trusty” I.T. guy.
Found the problem. I had to set the properties of the launch icon to “Run as administrator.” Works fine now.
You must be logged in to reply to this topic.