Help required producing usable Gcode files for CNC engraver

[he1957]

Sounds like what you are doing is lots of fun and interesting at the same time. The sample I posted above was simply an example tool-path simulation (image) of the NC code that "drew" it (the NC code).

For such projects, where you have (as shown) one operation to perform the task needed (route excess copper to get tracks) then a different operation (perhaps with a different tool) to perform another (drill holes) and so-forth. The machine/software should be quite capable of doing this. You use different operations.

For example, I posted a pocket operation as described above. I would then create a drill operation using the pin (holes). These are shown as circles in the drawing but for a fixed operation such as it is, point entities would also work because the operation is a drill cycle using a particular bit size (perhaps 0.6 mm) at their co-ordinates, so all the generated code needs to do is drill holes at the point co-ordinates.

The same copper traces could be produced by routing a contour around the outside edges of the "traces", leaving both the traces and the surrounding copper as "islands" that could also be used as ground-plane shielding (or even heat-sink assist or mounting pads). It's a matter of what works best for your intent.

The various operation steps are broken into sections that can be in the same file with a tool change or as separate (manual) files with tool change.

In the NC file, look for the "ToolChangeOrg" lines. These represent the start of the 3 operations and could be saved/loaded as three separate files. To make it 3 files, copy the "Header" and "EndOfFile" blocks and place the code from the "ToolChange" to the comment just before the next ToolChange between the Header and EndOfFile and save the files.

The additional comments (between parenthesis "()") can be ignored/removed. I setup my PostProcessor to give this to help me follow/debug code if I need to. (Basically, its tells me about Before and After FirstFeed and LastFeed moves (BFFM, ALFM)).

I constructed it this way so you can see the specific operations combined as a single file. A machine with tool-change processing will pause between the operations. If your machine does not understand tool change then it might blindly run the code (or error) using the tool currently mounted which could break the tool.

Yes, there is a lot to it all, but it starts to fall into place. It's about thinking how would you do it yourself and then telling the machine (CNC machines are about as smart as a house brick).

[mactec54]

here is the CadBam file I used to generate the gcode appended to have a .txt extension (the only way I could get it to attach). You will have to rename it as a .cb file for it to work of course, but you will see that it has three items of text

Thanks for the help

Le

G-code is only text it can stay in text and run in the machine control, some controls require different extensions, but most will run with the text extension

[lesthegringo]

Guys, I have been adding circles as my drill points in Qcad, whereas I think that what I should have been doing is adding a point, but I'm struggling on how to do that - any ideas?

Cheers

Les

[he1957]

Guys, I have been adding circles as my drill points in Qcad, whereas I think that what I should have been doing is adding a point, but I'm struggling on how to do that - any ideas?

Cheers

Les

QCad User Reference Manual - Points

I don't use QCAD but it looks interesting.

I use SimplyCam for most works. Not only can you draw your parts but you can generate G-Code tool paths for many targets (see above), run a speed-controlled simulator (as well as single step), view your objects in a 3D presentation. You can also import G-Code to get it to draw what the object looks like via the simulator.

It also has a GRBL control inbuilt.