I might be able to answer a couple of those questions, although full disclosure, I don't have a cutter, and only have learned what I know by trial and error with Inkscape and a simulator, and trying to help others who are lost with those extensions. It seems the Russian forum does no longer provide support for these extensions (unless they have resumed in the last few months, I haven't looked lately).
(Note that I realize you've already figured out a lot of this. But since you wrote it up as a tutorial, I thought I'd fill in some blanks, for others who may be reading this, who may not have gotten that far yet.)
If you're in touch with, or can get in touch with a local makerspace or fablab, those seem to be the best places to get support. Well, at least with their own machines. But they might be able to help with the Inkscape extensions too.
I do know of a couple of tutorials, but they aren't very comprehensive. But they still might provide some clues.
https://www.norwegiancreations.com/2015/08/an-intro-to-g-code-and-how-to-generate-it-using-inkscape/ https://www.shapeoko.com/wiki/index.php/User:BHSPitMonkey/Inkscape_and_Gcodetools_TutorialI would urge folks to study the documentation for their particular machine. That can be very, very important, as far as I've been able to learn. I think some of the options in these extensions are specific to the hardware.
As far as I know, no matter which specific type of gcode or specific type of cutting you're going to use, you should start with these, in this order. Be sure to read every bit of info in all the dialogs, because they do provide clues.
1 -- Orientation Points (this appears to set up and orient the work space both on Inkscape canvas and whatever material you're cutting)
2 -- Tools Library (adds information about the particular tool you want to use, to the work space info)
3 -- Whatever specific type of cutting you want to do: Area, DXF Points, Engraving, Graffiti, Lathe, Prepare for Plasma
4 -- Most of those provide a Path to Gcode tab. But if they don't, then the Path the Gcode extension is the last step.
This is just kind of an odd observation. I'm not sure if it would be considered a bug, or if there is some purpose for it. Also, I've only been testing (today) with the Area extension, so maybe this does not happen with the others?? I haven't noticed it in the past, but it could be happening with all of them, and it was just contributing to my confusion in the past??
Anyway, it seems to depend which tab you have open at the moment when you click Apply, as to what is drawn on the Inkscape canvas. As far as I can tell, it does not affect the gcode itself (although if I looked at the code, I would not understand it anyway). Well, I guess it's more of an assumption.
For example, if I'm on the Area tab, when I click Apply, it shows the cutting lines. Like if I have a square or circle selected for what I want to etch out, then it shows the concentric circles or squares (or if it were a triangle, concentric triangles, etc.). But if I'm on the Fill Area tab, and I have Spiral or ZigZag selected for the Fill Method, it draws spiral or zigzag. If I have the Path to Gcode tab open, it only draws the outer shape (blue and black segments with tiny arrows).
Although I have in the past, today I didn't try using a simulator. So I can't address your comments about how the job was running with various options. (Already invested too much time trying to learn about biarc interpolation
)
Now let's see if I can answer any of your specific questions. (don't hold your breath, haha)
1 -- Biarc Interpolation Tolerance
The short answer is that I don't know for sure what this setting is, or does. The long answer, I've just spent about an hour, trying to learn what a "biarc" is, and what "biarc interpolation" is, and trying with Inkscape using various different settings for that option. I can't see any obvious difference between using 0.1, 1.0 or 10.0 (and only 0 to 10.0 are allowed). Not any difference on the canvas - I did not look at the actual gcode (which I don't have a prayer of understanding anyway).
As far as I've been able to learn (and there's a
lot of assumption going on, and a good chance I may not have learned correctly), the author is being very, very specific in differentiating between "interpolation" and "approximation". I think for most intents and purposes, the approximation he refers to
is the interpolation (or vice versa, at least as I think I understand it).
When the instruction says the path will be split, I think he means the 2 arcs will be split from 1 curve into 2 arc-curves which meet at the same point. Again, stressing that I'm faaarrrr outside my comfort zone with this.
So with my current understanding, I think you would not know they were split, unless you have the machine set to stop cutting at the end of a path. And you were watching, and you knew (or suspected) where the path was split in the first place.
2 -- I think the Cutting Order has more to do with how the gcode is written, than how the material is cut. Or it might need to be set a certain way for your particular machine. But again, I'm not really sure. Be sure to consult the documentation for your machine.
I'm pretty sure the color options for the depth function are needed for some machines and not for others, although again, I'm not positive about that.
d = depth defined by orientation points, Tried orientation on each level.
I would suggest not using more than one layer, for your first try. Start simple!
s = Surface defined by orientation points. This one just runs never stops
I'm not sure what you mean by running and never stopping. You mean the CNC? By the title for that field "Depth function" and because it's somewhat of a long field, it makes me wonder of there is some short bit of code or something, that needs to be written there, to define the depth - not just "d" or "s" or "c". I don't know, maybe you already figured that out?
I have no clue what "Sort Paths to reduce rapid distance" means.
EXTENTIONS/ GCODETOOLS/ OPTIONS
1) Scale along Z axes: Presented with 1.0 to 100,000.0 the last four digits do not cycle
2) Offset along Z axes: Presented with 0.0 to 100,000.0 the last four digits do not cycle.
I don't know what you mean by "do not cycle". But I would keep the scale at 1.0, and the offset at 0, unless you're doing something "fancy" and you know what you're doing.
I'm not positive what "minimum arc radius" is, but I would guess it's the point at which you don't want the machine to try and make an arc, and just make a corner instead.
Get additional comments from object properties.
I assume this adds text to Gcode for clarity?
That would be my guess as well.
Z safe height for G00 move over blank: starts at 1.0 to -1000.0000 only first digit cycles pass the dicmal point. I have been using 0.5 but the CNC has been traveling all the way to the top 30 sec up 30 sec down between cuts or lines. I'm drawing before I cut.
So you're saying that your machine is not respecting what you set for the safe height? I wonder if some other setting is overriding it. Like maybe that Z Scale setting, and/or other?
Generate log file. Log what a file to tell what was in the last one you made?
The log file is different from the gcode (NGC). It just tells each step that was taken along the way. It looks like it documents node coordinates and all the options you had selected. I guess it just remembers all the details for you, because as soon as you change the options in the dialogs, the last job you did is essentially erased.
Although to be honest, I would not be able to look at it, and reset my canvas, or reset the dialogs. And I'm not sure if there would be a way to apply the file to somehow automatically reset that job. But I would probably still save the file, just in case I might find a way to use it.
Full path to log file. And where you store it. Is this Duplication and wasted space?
No, I don't see it that way. The option to save a log file is just a checkbox. I guess if you did not fill in the directory field, Inkscape probably puts it in some default location, and gives it some generic and/or random name.
This plug-in calculates Gcode for paths using circular interpolation or linear motion when needed. Is that when the R shows up?
Not sure about the "R". But doesn't the "circular interpolation" refers to that biarc interpolation setting?
Well, I know there weren't very many definitive answers in all that. But at least so far, I haven't come across many people who really have many definitive answers about those extensions. So I feel like if we can all kind of pitch in with bits an pieces, we can help each other
