My machine does not offset / compensate the tool radius even though I'm choosing to cut outside or inside in QCAD/CAM.
Tool radius compensation
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.
Tool radius compensation
From a QCAD/CAM user:
Re: Tool radius compensation
You might be using a post processor which uses G41/G42 for tool radius compensation. This means that QCAD/CAM exports the contour data at its desired size and the machine controller computes the tool radius offset, not QCAD/CAM.
However, not every controller supports G41/G42. Please refer to your controller manual to find out if yours does. Otherwise, you would have to use a different post processor which exports computed offsets (e.g. "G-Code (Offset) [mm]"). In this case, QCAD/CAM computes the required offset.
However, not every controller supports G41/G42. Please refer to your controller manual to find out if yours does. Otherwise, you would have to use a different post processor which exports computed offsets (e.g. "G-Code (Offset) [mm]"). In this case, QCAD/CAM computes the required offset.
Re: Tool radius compensation
@ Andrew,
in my case, in the dialog box for tooling, practically I wrote 2mm as depth before generating , when I double checked after generating the depth is in the programme reads 4mm , before I even involve the controller.
in my case, in the dialog box for tooling, practically I wrote 2mm as depth before generating , when I double checked after generating the depth is in the programme reads 4mm , before I even involve the controller.
Re: Tool radius compensation
Please attach your DXF file as this contains all the data we need to help you efficiently, thanks.
Re: Tool radius compensation
HI, Andrew , Tool compensation
find attached dxf 1025
find attached dxf 1025
- Attachments
-
- 1025PANEL.nc
- (553 Bytes) Downloaded 401 times
-
- PANEL1025.dxf
- (140.67 KiB) Downloaded 416 times
Re: Tool radius compensation
Your Z levels are configured as follows:
- The safety level is Z=0. This is where the tool moves to in rapid mode.
- Your material starts at Z=-5
- The ultimate cutting depth is Z=-16
- You are cutting in two passes, first pass at Z=-10.5, second pass at Z=-16.
Looking at the G-Code file, I can see those Z values.
Note that usually the material starts at Z=0, your safety level would be at perhaps Z=2 and your cutting depth for example Z=-11 with the first pass at Z=-5.5 and second pass at Z=-11. However, your configuration can make sense depending on your use case.
I cannot see the depth "2" as you indicated nor the depth "4" you mentioned being generated. Can you please double-check?
I hope that helps.
This means that:- The safety level is Z=0. This is where the tool moves to in rapid mode.
- Your material starts at Z=-5
- The ultimate cutting depth is Z=-16
- You are cutting in two passes, first pass at Z=-10.5, second pass at Z=-16.
Looking at the G-Code file, I can see those Z values.
Note that usually the material starts at Z=0, your safety level would be at perhaps Z=2 and your cutting depth for example Z=-11 with the first pass at Z=-5.5 and second pass at Z=-11. However, your configuration can make sense depending on your use case.
I cannot see the depth "2" as you indicated nor the depth "4" you mentioned being generated. Can you please double-check?
I hope that helps.
Re: Tool radius compensation
@ Andrew,
I managed to sort out the issue of 5mm less on my work,
like you mentioned some machines are not compatible with G41/42 , like mine now am using Gcode offset mm, now the machine is producing excellent work its now 100% accurate thanks for the support .
I managed to sort out the issue of 5mm less on my work,
like you mentioned some machines are not compatible with G41/42 , like mine now am using Gcode offset mm, now the machine is producing excellent work its now 100% accurate thanks for the support .
Re: Beziers, QCAD PROFFESSIONAL
@ANDREW,
Attached is a map of Africa, i imported that shape into QCAD, i want to cut it as it is , after imPorting ,the shape is always associated with many tiny squares , so when i generate the toolpath it takes too long, sometimes it fails to produce the NC programme after importing how do i get a sm
ooth shape without beziers/ tiny squares in QCAD.
Regards,
Collen ,CNC TECHNICIAN
Attached is a map of Africa, i imported that shape into QCAD, i want to cut it as it is , after imPorting ,the shape is always associated with many tiny squares , so when i generate the toolpath it takes too long, sometimes it fails to produce the NC programme after importing how do i get a sm
ooth shape without beziers/ tiny squares in QCAD.
Regards,
Collen ,CNC TECHNICIAN
- Attachments
-
- Africa-outline-map.jpg (35.64 KiB) Viewed 8845 times
Re: Tool radius compensation
Hi,
I would have started a new topic about this.
An example file would always be handy ....
There is no easy answer, all depends on how large the shape is and how acurate it must be.
If one explode a spline with a huge reference count or many beziers, there will be even more reference points.
Eventually I used FlexPainter to make a global polyline offset at distinct intervals.
As Pro user select the single contour and type FP (Painter = 1_OrthoPointGlobal)
+ A few manual corrections of course
Regards,
CVH
I would have started a new topic about this.
An example file would always be handy ....
You probably mean reference point indicators when the shape is selected ....
Been there, done that, as engraver, coin-size.
There is no easy answer, all depends on how large the shape is and how acurate it must be.
If one explode a spline with a huge reference count or many beziers, there will be even more reference points.
Eventually I used FlexPainter to make a global polyline offset at distinct intervals.
As Pro user select the single contour and type FP (Painter = 1_OrthoPointGlobal)
+ A few manual corrections of course
Regards,
CVH