Out put format and motion controller

I am considering purchasing Light Burn, I currently have a “Digital Wood Carver 2440” with laser attachment. This machine uses Planet CNC for motion control and Vetric Aspire CAD/Cam which Will Light Burn direct connect to Planet CNC (excepts g-code and imports/ export .DFX . .tap and most all other cam formats)
Is Light Burn compatible with this or will export files as .DFX or .STL. .DWG .TAP
I COPIED THE FOLLOWING FROM PLANET CNC PAGE
"PlanetCNC TNG is a motion control hardware and software intended for control of CNC machines. As a standard, g-code is used as native programming language.

PlanetCNC TNG software processes gcode program and sends series of commands to motion controller. Controller interprets these commands and arranges coordinated machine motion.

Gcodes
G-code commands can be divided into multiple groups which differ from one another based on functionality and intended use.

Single G-code line, aka block, can include commands for modal state configuration, machine motion, program control and data manipulation, or peripheral control.
PlanetCNC TNG supports also gcode functions, expression functions, parameters, operators etc…"

The easiest way would be to download a trial version and test if your machine can work with LightBurn. The trial version works without restrictions for 4 weeks (I think). You can also dig here the forum for a grain of gold, it could be that there are others who are already running with your coveted setup or something similar.

1 Like

Thank you very much

If you have any examples of GCode for that machine that drive a laser, I could tell you if there’s a profile in LightBurn that would work.

sorry Oz hereis a copy of the post precessors used for the “Digital Wood Carver”
C.N.C. using Vetric Aspire and Planet CNC
this is for the Aspire laser out put i will send others pp if needed this is long

+================================================
+                                                
+ G Code - Vectric machine output configuration file   
+                                                
+================================================
+                                                
+ History                                        
+                                                
+ Who      When       What                         
+ ======== ========== ===========================
+
+================================================

POST_NAME = "Digital Wood Carver Laser Picture (inch)(*.tap)"

FILE_EXTENSION = "tap"

UNITS = "INCHES"

DIRECT_OUTPUT = ""

SUBSTITUTE = "({)}"

LASER_SUPPORT = "YES"

+------------------------------------------------
+    Line terminating characters                 

VAR X_POSITION = [X|A| X|1.4]+------------------------------------------------

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 POWER = [P|A|S|1.0|1.0]
VAR SPINDLE_SPEED = [S|A|S|1.0]
VAR CUT_RATE    = [FC|C|F|1.1]
VAR PLUNGE_RATE = [FP|C|F|1.1]
VAR Y_POSITION = [Y|A| Y|1.4]
VAR Z_POSITION = [Z|A| 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 DWELL_TIME = [DWELL|A|P|1.2]
+================================================
+                                                
+    Block definitions for toolpath output       
+                                                
+================================================

+---------------------------------------------------
+  Commands output at the start of the file
+---------------------------------------------------

begin HEADER

"//|-----------------------------------------"
"//--FILE DETAILS"
"//-- [TP_FILENAME] "
"//-- File created: [DATE] - [TIME]"
"//-- Material Size"
"//--(X= [XLENGTH], Y= [YLENGTH], Z= [ZLENGTH])--"
"//-- Z Zero Position = [Z_ORIGIN]"
"//-- XY Datum Position = [XY_ORIGIN]"
"//--(XY Origin Position  = X:[X_ORIGIN_POS], Y:[Y_ORIGIN_POS])--"
"//-- Home Start Position"
"//--(X = [XH] Y = [YH] Z = [ZH])--" 
"//-- Safe Rapid Z Above Material = [SAFEZ]"
"//--([FILE_NOTES])--'"
"//-- Toolpaths used in this file:"
"//--([TOOLPATHS_OUTPUT])--"
"//--Number of tools used in this file: "
"//--([TOOLS_USED])--"
"//|---------------------------------------"
"//         |--BEGIN JOB--|"
"//                                        "
"//|---------------------------------------"
"//| Toolpath:- '[TOOLPATH_NAME]'    "
"//| Tool: -    '[TOOLNAME]'         "
"//|---------------------------------------"

"G90"
"G20"
"[FC]"
"G00 [ZH]"

"S0"


+---------------------------------------------------
+  Commands output for rapid moves 
+---------------------------------------------------

begin RAPID_MOVE

"S0"
"G00[X][Y][Z]"


+---------------------------------------------------
+  Commands output for the plunge move
+---------------------------------------------------

begin PLUNGE_MOVE
"G00[X][Y][Z]"


+ ---------------------------------------------------
+  Commands output for Retract Moves
+ ---------------------------------------------------
begin RETRACT_MOVE

"[S]"
"[P]"

+---------------------------------------------------
+  Commands output for the first feed rate move
+---------------------------------------------------

begin FIRST_FEED_MOVE

"[FC]"
"[P]"
"G01[X][Y][Z]"


+---------------------------------------------------
+  Commands output for feed rate moves
+---------------------------------------------------

begin FEED_MOVE

"G01[X][Y][Z]"

+---------------------------------------------------
+  Commands output for the first clockwise arc move
+---------------------------------------------------

begin FIRST_CW_ARC_MOVE

"[FC]"
"[P]"
"G02[X][Y][I][J]"


+---------------------------------------------------
+  Commands output for clockwise arc  move
+---------------------------------------------------

begin CW_ARC_MOVE

"G02[X][Y][I][J]"


+---------------------------------------------------
+  Commands output for the first counterclockwise arc move
+---------------------------------------------------

begin FIRST_CCW_ARC_MOVE

"[FC]"
"[P]"
"G03[X][Y][I][J]"


+---------------------------------------------------
+  Commands output for counterclockwise arc  move
+---------------------------------------------------

begin CCW_ARC_MOVE

"G03[X][Y][I][J]"

+---------------------------------------------------
+  Commands output for a new segment - toolpath
+---------------------------------------------------

begin NEW_SEGMENT
"//|---------------------------------------"
"//|  Toolpath:- '[TOOLPATH_NAME]'    "
"//| Tool: -     '[TOOLNAME]'         "
"//|---------------------------------------"


+---------------------------------------------
+  Commands output for a dwell move
+---------------------------------------------

begin DWELL_MOVE

"G04 [DWELL]"

+---------------------------------------------------
+  Commands output when the jet is turned on
+---------------------------------------------------

begin JET_TOOL_ON

"M3"
"[P]"



+---------------------------------------------------
+  Commands output when the jet is turned off
+---------------------------------------------------

begin JET_TOOL_OFF

""

+---------------------------------------------------
+  Commands output when the jet power is changed
+---------------------------------------------------

begin JET_TOOL_POWER
"[P]"

+---------------------------------------------------
+  Commands output at the end of the file
+---------------------------------------------------

begin FOOTER

"S0"
"G00 [ZH]"
"M5"
"G00 [XH] [YH]"
"M02"

Do you have an example of the GCode produced by this? It would be easier if I had an example as well.

This file was generate in aspire, saved has the pic laser post processor and opened in planet cnc. This is a copy of the g-code exported from Planet CNC and copied into note pad and then pasted. the machine was not connect (could not zero) but xyz can be edited that should not effect
I greatly Appreciate your assistance
if you nned the entire g code i can send that

//|-----------------------------------------
//–FILE DETAILS
//-- S_Monogram_laser
//-- File created: Friday January 01 2021 - 04:32 AM
//-- Material Size
//–(X= 11.000, Y= 8.500, Z= 0.750)–
//-- Z Zero Position = Material Surface
//-- XY Datum Position = Bottom Left Corner
//–(XY Origin Position = X:0.000, Y:0.000)–
//-- Home Start Position
//–(X = X0.0000 Y = Y0.0000 Z = Z1.8000)–
//-- Safe Rapid Z Above Material = 0.200
//–()–’
//-- Toolpaths used in this file:
//–(Laser Cut 1)–
//–Number of tools used in this file:
//–(1 = Laser Cutter 6W {0.015"})–
//|---------------------------------------
// |–BEGIN JOB–|
//
//|---------------------------------------
//| Toolpath:- ‘Laser Cut 1’
//| Tool: - ‘Laser Cutter 6W {0.015"}’
//|---------------------------------------
G90
G20
F2700.0
G00 Z1.8000
S0
S0
G00 X9.5996 Y1.7443 Z0.2000
G00 X9.5996 Y1.7443 Z0.0000
M3
S0
S85

S85
G01 X9.9439 Y2.1135 Z0.0000
G01 X9.9567 Y2.1290 Z0.0000
G01 X9.9899 Y2.1702 Z0.0000
G01 X10.0225 Y2.2117 Z0.0000
G01 X10.0544 Y2.2535 Z0.0000
G01 X10.0829 Y2.2919 Z0.0000
G01 X9.4242 Y1.5856 Z0.0000


I CUT OUT A MAJORITY THE END CODE IS

S0
S0
G00 Z1.8000
M5
G00 X0.0000 Y0.0000
M02

There’s a good chance that the GRBL-M3 device in LightBurn will produce code that’s compatible, or very close to it. The comments in your file use // to denote them, but GRBL uses semi-colons, so you’d likely need to change that, but everything else looks ok.

Your file shows S85 - what power level does that correspond to? IE, is that 85% power?

Thank You, for your assistance I will attemp to change the // in the comment section. I did find the following .pdf files in Planet CNC doc folder her is a copy/past of the 2 files this may help as well i did have to cut out amajarity due to charector limit in post if need i can e mail the .pdf file my email is wstevesivell@gmail.com
the first is the"API" manual and second is the Gcode manual

API Reference
2019/11/08
Note:

  • all functions use CDECL calling convention.
  • some commands can be called using named pipe \.\pipe\PlanetCNC
  • use one of Run commands to start new TNG process. If API is calling existing TNG process then it
    will internally use pipes for interprocess communication.
    Memory
    FreeString
    Declaration: void FreeString(char* str);
    Frees previously allocated string.
    FreeStringW
    Declaration: void FreeStringW(wchar_t* strw);
    Frees previously allocated widestring.
    Callback
    SetInitialiseCB
    Declaration: void SetInitialiseCB(__InitialiseCB cb);
    Callback is called when TNG is initialed and ready to use (parameter value ‘1’) and when TNG is
    shutdown and no longer available (parameter value ‘0’).
    Prototype __InitialiseCB is defined as:
    t
    .

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.