Tool list format ( output using output_tool_list variable )************* (MTOOL T1 S1 D0.25 C0. % O0100 (PROGRAM NUMBER) (PROGRAM NAME - POST GUIDE - LESSON 1.NC) (POST - BC_3X_MILL 3-AXIS GENERIC FANUC) (DATE - FRI. These comments tell us which Post Blocks are responsible for the output we are seeing in the NC code. Notice now the extra entries for the Debugging comments. Open the Gcode in your text editor and I recommend you tile the two windows so you can see the post processor output(Gcode) and the post processor file itself at the same time as shown in the image below. Run the post processor to generate the gcode. It will help us locate what Post Block is outputting the lines of code we wish to modify. Change the “ debug_off ” variable to “ debug_on ” and save the file. (We recommend using Notepad ++ for this as it is a no cost text editor that works well). Open the post processor file in your text editor. Y-2.5 Z-0.375 元.5 W2.5 H0.375) (END PREDATOR NC HEADER)įor the 1st modification we will alter the header to remove the following items and then we will add some new information. ) (TIME - 04:36PM) (BEGIN PREDATOR NC HEADER) (COORD_SYS 1=X0 Y0 Z0) (MTOOL T1 S1 D0.25 C0. The start of the NC program is referred to as the “Header” and below you can see an example of the default header output. All drilling canned cycles supported by the software and the machine.Profile Milling with and without machine cutter compensation.It is important when creating, customizing, or modifying post processors that you test all machining scenarios to ensure the post processor is working fully on the machine tool. Each feature contains multiple operations to complete the part. This test file includes multiple machining features. Machine File: BC_3x_Mill Post Processor: BC_3x_Mill.BCPst Part File: Post Guide – Lesson 1.bbcd
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |