Tape splitting ?
15 Jun 2014 10:52 #47978
by rmattioda
Tape splitting ? was created by rmattioda
Is there a way to split large designs into smaller runs, I am using Aspire.
I have heard about a tape splitting post processor, does linux do this
I have heard about a tape splitting post processor, does linux do this
Please Log in or Create an account to join the conversation.
15 Jun 2014 11:08 #47979
by jmelson
Replied by jmelson on topic Tape splitting ?
G-code is just plain, human readable text. Any text editor that can handle large files should be
able to split a G-code file into pieces. You select the optimum place to make the split.
Jon
able to split a G-code file into pieces. You select the optimum place to make the split.
Jon
Please Log in or Create an account to join the conversation.
15 Jun 2014 15:30 #47982
by ArcEye
I haven't heard about them for years. Originally they were to overcome the limited memory of controllers, by feeding long programs in pieces the controller could read and store.
Typically, the program would be broken where a toolchange occured, or another instance where there was a full retraction from the workpiece and cutter compensation removed etc.
As Jon says you can do it by hand quite easily, you just need header and footer code to paste in whenever you make a split.
How human readable the output from your CAM program is, is another matter.
For some reason none of them space parameters and everything is just crushed together in one line
N168G3X12.456Y24.874I23.5J0F34.678 for instance
regards
Replied by ArcEye on topic Tape splitting ?
I have heard about a tape splitting post processor
I haven't heard about them for years. Originally they were to overcome the limited memory of controllers, by feeding long programs in pieces the controller could read and store.
Typically, the program would be broken where a toolchange occured, or another instance where there was a full retraction from the workpiece and cutter compensation removed etc.
As Jon says you can do it by hand quite easily, you just need header and footer code to paste in whenever you make a split.
How human readable the output from your CAM program is, is another matter.
For some reason none of them space parameters and everything is just crushed together in one line
N168G3X12.456Y24.874I23.5J0F34.678 for instance
regards
Please Log in or Create an account to join the conversation.
15 Jun 2014 16:54 #47984
by cncbasher
Replied by cncbasher on topic Tape splitting ?
aspire will split code into parts , or even based on tool numbers . just take time to set everything up , and if need be set up phantom tools
with the same information , and select the order you wish to cut and base your length on the code as you go .
it just takes a little thought , and understanding as to what is happening , rather than just load the code and post process it , and accept the outcome
take your time to understand what aspire is doing , and it will all become clear .
with the same information , and select the order you wish to cut and base your length on the code as you go .
it just takes a little thought , and understanding as to what is happening , rather than just load the code and post process it , and accept the outcome
take your time to understand what aspire is doing , and it will all become clear .
Please Log in or Create an account to join the conversation.
18 Jun 2014 23:47 - 19 Jun 2014 01:41 #48077
by rmattioda
Replied by rmattioda on topic Tape splitting ?
Going to give this PP a try tonight, it batches the files into however many lines of code you desire.
this comes from the Vectric PP guide in the manual
opinions?
this comes from the Vectric PP guide in the manual
opinions?
Last edit: 19 Jun 2014 01:41 by rmattioda.
Please Log in or Create an account to join the conversation.
19 Jun 2014 01:42 - 19 Jun 2014 03:33 #48080
by rmattioda
Replied by rmattioda on topic Tape splitting ?
+================================================
+
+ Emc2 - Vectric machine output configuration file
+
+================================================
+
+ History
+
+ Who When What
+ ======== ========== ===========================
+ Tony 02/08/2005 Written
+ Pieter 20/06/2008 adapted for EMC2, begin + end
+ its uses M7 to start coolant/vacu-cleaner
+ Mark 28/06/2008 Added Arcs and new segment section.
+ Mark 11/08/2008 Inch version.
+================================================
POST_NAME = "EMC2 -G61 NO TOOL SPLIT Arcs(inch)(*.ngc)"
FILE_EXTENSION = "ngc"
UNITS = "INCHES"
+------------------------------------------------
+ Line terminating characters
+------------------------------------------------
LINE_ENDING = "[13][10]"
+------------------------------------------------
+ Block numbering
+------------------------------------------------
LINE_NUMBER_START = 0
LINE_NUMBER_INCREMENT = 10
LINE_NUMBER_MAXIMUM = 999999
+================================================
+
+ Formating for variables
+
+================================================
VAR LINE_NUMBER = [N|A|N|1.0]
VAR SPINDLE_SPEED = [S|A|S|1.0]
VAR FEED_RATE = [F|C|F|1.1]
VAR X_POSITION = [X|C|X|1.4]
VAR Y_POSITION = [Y|C|Y|1.4]
VAR Z_POSITION = [Z|C|Z|1.4]
VAR ARC_CENTRE_I_INC_POSITION = [I|A|I|1.4]
VAR ARC_CENTRE_J_INC_POSITION = [J|A|J|1.4]
VAR X_HOME_POSITION = [XH|A|X|1.4]
VAR Y_HOME_POSITION = [YH|A|Y|1.4]
VAR Z_HOME_POSITION = [ZH|A|Z|1.4]
VAR SAFE_Z_HEIGHT = [SAFEZ|A|Z|1.4]
TAPE_SPLITTING = 75000 100 "%s_%d.ngc"1 "YES"
+================================================
+
+ Block definitions for toolpath output
+
+================================================
+---------------------------------------------------
+ Commands output at the start of the file
+---------------------------------------------------
begin HEADER
"%"
"G20 G40 G49 G61"
"G17"
"M7"
"G0[ZH]"
"G0[XH][YH][S]M3"
+---------------------------------------------------
+ Commands output for rapid moves
+---------------------------------------------------
begin RAPID_MOVE
"G0[X][Y][Z]"
+---------------------------------------------------
+ Commands output for the first feed rate move
+---------------------------------------------------
begin FIRST_FEED_MOVE
"G1[X][Y][Z][F]"
+---------------------------------------------------
+ Commands output for feed rate moves
+---------------------------------------------------
begin FEED_MOVE
"[X][Y][Z]"
+---------------------------------------------------
+ Commands output for the first clockwise arc move
+---------------------------------------------------
begin FIRST_CW_ARC_MOVE
"G2[X][Y][I][J][F]"
+---------------------------------------------------
+ Commands output for clockwise arc move
+---------------------------------------------------
begin CW_ARC_MOVE
"G2[X][Y][I][J]"
+---------------------------------------------------
+ Commands output for the first counterclockwise arc move
+---------------------------------------------------
begin FIRST_CCW_ARC_MOVE
"G3[X][Y][I][J][F]"
+---------------------------------------------------
+ Commands output for counterclockwise arc move
+---------------------------------------------------
begin CCW_ARC_MOVE
"G3[X][Y][I][J]"
+---------------------------------------------------
+ Commands output for a new segment - toolpath
+ with same toolnumber but maybe different feedrates
+---------------------------------------------------
begin NEW_SEGMENT
"[S]M03"
+---------------------------------------------------
+ Commands output at the end of the file
+---------------------------------------------------
begin FOOTER
"G0[ZH]"
"G0[XH][YH]"
"M2"
"%"
Last edit: 19 Jun 2014 03:33 by BigJohnT. Reason: add code tags
Please Log in or Create an account to join the conversation.
Time to create page: 0.066 seconds