MacOs Version 15.6.1
Qcad CAM Pro Version: 3.32.5.0
Arcdroid Post Processors installed
I’ve started to use my new Arcdroid and understand the built in trace programs and UI. I am now starting to program using QCad/Cam. I know how to design in CAD already. I have a few questions about the use of CAM software for someone who has never used it.
Will the CAM export file (g code) override the values I put into the Arcdroid.. (ie. Z offset, ker, etc)? I am pretty sure it does, but dont know 100%
Tools:
I think I need to create a tool around the Plasma cutter.
If I need to create new tool in qcad, should I create a new tool for each media and thickness around amperage, speed etc? For example 1/8”, 3/16”, 1/4” steel…aluminum… stainless etc?
Any help would be appreciated, I have my settings in a spreadsheet already
CAM SET UP with Plasma cutter
Moderator: andrew
Forum rules
Always indicate your operating system and QCAD version.
Indicate the post processor used.
Attach drawing files and screenshots.
Post one question per topic.
Always indicate your operating system and QCAD version.
Indicate the post processor used.
Attach drawing files and screenshots.
Post one question per topic.
-
tiger351w
- Newbie Member
- Posts: 3
- Joined: Wed Dec 24, 2025 7:33 am
- Location: SF Bay Area
-
CVH
- Premier Member
- Posts: 5024
- Joined: Wed Sep 27, 2017 4:17 pm
Re: CAM SET UP with Plasma cutter
Hi,
A Plasma cutter is still something different than a milling router or using that with a laser module.
Common is that they all move in XY and in Z.
Plasma typically 'touches off' and then retracts a bit.
Height is then constantly adapted depending measured arc parameters.
This last part is fully up to the Plasma driver with a closed loop algorithm and some settings by parameters or knobs.
I have a copy of the post processor is front of me.
It is directly based on GCodeBase.js.
Meaning that all things define in the most standard G-Code exporter are used unless overruled by ArcDroidMM.js for example.
Overall power (amps) and FEED is of course depending on the material to cut.
More power, bigger nozzles, ... make a bigger hole and then the offset to the required contour matters.
It's a pity that Laser or Plasma don't get new Profile dialogs ... It's the milling Profile dialog that is molded to suit the needs.
In Laser machining I remember that milling rotational SPEED is being (mis-) used as Laser POWER.
ArcDroidMM.js:
Tooltype 'Mill' is simply replaced by 'Plasma' ... Textual.
In the CamProfileToolpathDialog:
- CamSpindleSpeed and associated are set invisible.
- Whole the CuttingDepths_Group is set invisible.
- CamPlungeRate is set invisible.
In the CamToolDialog:
- CamSpindleSpeed and associated are set invisible.
- CamPlungeRate is set invisible.
I have to admit that not everything is fully understood ...
... But I see the initialization of a LayerDialog.
I guess that Plasma parameters depends on layer properties. (Custom Properties as key-value pairs)
Probably meaning that things drawn on Layer X use different settings than those drawn on Layer Y.
Perhaps ArcDroid documentation explains that further.
Continuing with the same assumptions:
In QCAD/CAM you can generate a Template drawing.
This would normally include tool types and their specifics for milling.
It can include a layer with a rectangle of your work-area.
And that can also include layers with predefined custom properties ... Properties for Plasma in this case.
Then it would be the question of placing shapes to cut on the intended layer before creating a profile.
It is also possible that a drop-down on the Layer Dialog is expandable and that (new) content is saved persistent.
Hoping this helps and that it is somewhat assumed correctly.
Report back with success or failure.
Regards,
CVH
A Plasma cutter is still something different than a milling router or using that with a laser module.
Common is that they all move in XY and in Z.
Plasma typically 'touches off' and then retracts a bit.
Height is then constantly adapted depending measured arc parameters.
This last part is fully up to the Plasma driver with a closed loop algorithm and some settings by parameters or knobs.
I have a copy of the post processor is front of me.
It is directly based on GCodeBase.js.
Meaning that all things define in the most standard G-Code exporter are used unless overruled by ArcDroidMM.js for example.
Overall power (amps) and FEED is of course depending on the material to cut.
More power, bigger nozzles, ... make a bigger hole and then the offset to the required contour matters.
It's a pity that Laser or Plasma don't get new Profile dialogs ... It's the milling Profile dialog that is molded to suit the needs.
In Laser machining I remember that milling rotational SPEED is being (mis-) used as Laser POWER.
ArcDroidMM.js:
Tooltype 'Mill' is simply replaced by 'Plasma' ... Textual.
In the CamProfileToolpathDialog:
- CamSpindleSpeed and associated are set invisible.
- Whole the CuttingDepths_Group is set invisible.
- CamPlungeRate is set invisible.
In the CamToolDialog:
- CamSpindleSpeed and associated are set invisible.
- CamPlungeRate is set invisible.
I have to admit that not everything is fully understood ...
... But I see the initialization of a LayerDialog.
I guess that Plasma parameters depends on layer properties. (Custom Properties as key-value pairs)
Probably meaning that things drawn on Layer X use different settings than those drawn on Layer Y.
Perhaps ArcDroid documentation explains that further.
Continuing with the same assumptions:
In QCAD/CAM you can generate a Template drawing.
This would normally include tool types and their specifics for milling.
It can include a layer with a rectangle of your work-area.
And that can also include layers with predefined custom properties ... Properties for Plasma in this case.
Then it would be the question of placing shapes to cut on the intended layer before creating a profile.
It is also possible that a drop-down on the Layer Dialog is expandable and that (new) content is saved persistent.
Hoping this helps and that it is somewhat assumed correctly.
Report back with success or failure.
Regards,
CVH