My dad has a PlasmaCAM brand plasma cutting table. We haven’t had this machine in operation for quite some time. I know we had to use PlasmaCam’s DesignEdge software when it was in operation. To say that program was horrible would be an understatement. I contacted the company…their customer service is horrible (at least it used to be). At the time, they said we could NOT use ANY other software that it was specific for PlasmaCAM. Anyway, I have been using Lightburn since April because I purchased an XTOOL hobby laser, and now I have upgraded to an OMTech CO2 Laser. This has sparked my interest to think about firing up the PlasmaCAM again just because I don’t want any limitations to what I can create.
What relevant information would I need to be able to understand if Lightburn would be a supported software for this machine?
Would I need to change the controller?
I do know the PlasmaCAM machine has the same basic concepts as the XTOOL and OMTech. X and Y axis as well as Z. PlasmaCAM uses the DXF files and I am sure it would not support Images, but other than that, I feel that the Lightburn Software would be the best thing since sliced bread for this machine!
If the PlasmaCAM software can import g-code to run, then that might be the most expedient way to try to get this to work.
Be aware that in its current state LightBurn isn’t tailored to suit Plasma cutting operations. Having said that, some enterprising folks have indeed been able to get this to work sometimes with having to tweak the g-code coming out LightBurn before sending to the Plasma cutter.
A new feature set to release in 1.5.00 will allow for more customized g-code processing which could help facilitate this.
Therein lies the rub: LightBurn has no concept of things like torch height, arc firing, and all the vital controls required to light the fire and keep it burning.
With that in mind, you’d probably end up replacing whatever controller is in the thing with a more-or-less standard GRBL or LinuxCNC controller. Because it must run in a decidedly hostile environment, the casual approach of just dropping an Arduino into the chassis won’t work: EMI radiating from the first arc will stun the microcontroller.
So, while it can be done, it will be a major learning experience; nothing wrong with that, but don’t go into it expecting a trivial upgrade.
LightBurn is probably the wrong hammer for the design-to-G-code job, at least in its current state. The upcoming CNC-ish version may be more easily adapted, but much of the plasma arc control must be built into the machine controller, which does not come as a standard capability. In any event, LightBurn must produce the specific G-Code required by the controller.
Studying the LinuxCNC writeup on plasma cutter control should give you an idea of what’s in your future:
But that said, I’ve been using LB on my plasma table for 2 years now. It’s been a journey but with a lot of success and learning along the way. The first year there were constant improvements in process and workflow as it concerns CAD and CAM with LB, and in plasma table setup as it concerns making a standalone THC behave well with my grbl controller (or any controller for that matter). I’m happy to say that for the past year its been turn and burn with all systems staying pretty stable.
I’m excited about LBs direction to support Generic GCode going forward, I’ve explored it in the 1.5 beta and its very promising. But in the meantime…
My use case is perhaps similar to yours in that I have CNC laser, plasma, but also milling. Currently I use LB ga release (1.4.03) as CAD for all 3 processes and of course CAM for laser. For plasma and 2.5D milling I use SheetCAM, exporting .svg from LB into SC. The CAD/CAM iteration workflow takes seconds.
I googled PlamaCAM in plasmaspider.com and found that some folks do import gcode into it’s controller. SheetCAM has a post processor (.scpost) for it also, so I tried it. Note that these .scpost s that ship with SC are written buy anyone, and many are not fully tested, as is this case of plasmacam.scpost. However, with a few edits, it generates gcode but I have no idea if its compatible with PlasmaCAM. According the header comments in plasmacam.scpost, PlasmaCAMs controller apparently handles some amount of Z management as it pertains to pierce height, cut height, pierce delay, THC, etc, but in current state the .scpost is absent the the torch fire command M3, M4, or other but can be added easily. Gcode it generated is posted here. Again, you can get as elaborate or as simple as you like with .scposts and gcode production.
The gcode in this example is super simple, and for a job cutting 100mm square and circle.