Knowledge Base Articles
Differences in Simulation Between BobCAD and NC Editor
One of the most popular questions about the simulation in NC Editor is “Why do I need it when I already can simulate my program in BobCAD?” This article will go through the differences between what is happening in the simulation of BobCAD versus NC Editor.
Pic. 1 - Simulating an Example Part File in BobCAD
Simulating in BobCAD-CAM:
The BobCAD simulation is a quick tool to view how a part will be cut when the current toolpath in the CAM Tree is being ran. Due to the factor that the “Post” function is not required to be used prior to running the simulation, the simulator in BobCAD will only simulate out the toolpath that has been created by the user as opposed to the actual G-Code that will be sent to the machine. Since most of the post processor that are available at bobcadsupport.com and that are installed when initially installing the software have been tested on several customer’s computer they should be perfectly formatted for the specific controller that they are made for. If a post processor however does have any formatting error then the simulator will not be able to recognize this issue due to it not simulating the G-Code.
Pic. 2 - Simulating an Example Part File in NC Editor
Simulating in the NC Editor:
Attached above is the exact same part file in Picture 1, but instead of being simulated in BobCAD it was simulated in NC Editor. As described above the basic flow chart of BobCAD would be to design a model, create toolpath, simulate in BobCAD, and then use the post processor to convert the toolpath into G-Code. Due to the factor that the simulator in BobCAD will only show the toolpath, it is unable to show issues that are in the post processor since they are further down the flow chart.
The part shown in picture 2 shows the aftermath of a drilling feature where the post told the tool to return to the feed plane instead of the rapid plane (G98 versus G99). Due to the factor that the simulator in BobCAD assumes that the tool will return to rapid plane during a drilling cycle it was unable to catch the crash before posting out the code and sending it to the machine as shown in Picture 1. The main difference is that NC Editor receives the G-Code, stock, machine setup, and tooling information from BobCAD and will simulate out the same G Code that a machine will receive to run this program. Since the NC Editor simulates out the code that was from the post processor it was able to catch the Drilling crash before it got sent to the machine.
NOTE: 99% of the time the simulator and NC Editor should both show the same exact part at the end of the simulator. Primarily the only time there will be differences are when there are issues with the post processor (which are strenuously tested before getting to customers).
If you need further assistance, please contact our support team at (727) 489 – 0003 or [email protected]