mGcodeGenerator

hi. I am the author of mGcodeGeneratora
wiki.linuxcnc.org/cgi-bin/emcinfo.pl?GcodeGenerator
this is a cam-type program.
audience of this program is quite small
cnc, emc2, blender user
probably talking about twelve users in the world
you have any comments or suggestions to the program?
that allowed me to create something more useful.

This looks interesting. Keep us informed on your progress.

Dan

Hi yoyoek1,

it looks a lot like the program, thank you for sharing.

T'on can make several small cuts?


Scalaire

scalaire wrote:

can make several small cuts?

yes.
you need only make some edges where to cut.

example.
draw needed cuts in your favourite cad software, save it as a dxf file, import it to blender and generate gcode as a 2d 2.5d gcode.
it will automatic recognise elements to cut and make work path quite optimise.
important is to make join duplications of vertex.

Perfect... thanks a lot... that is exactly what i was locking for... Now i can mill and reprap all directly out of blender

The mGcodeGenerator appears to be a fantastic tool, but I can not figure out how to save the g-code file! When I try selecting a file to save it, it doesn't save the file. Also, I have a bit of difficulty with units- Blender isn't all that helpful when trying to dimension objects- I drew the object in another application and imported the mesh into blender, and now I haven't the slightest idea how big it is!

in blender there is a "transform properties" in object mode / menu object / transform properties
dimX dimY dimZ
I some times use it to correct dimensions after import.

about saving
if you use windows I have no idea
when you use linux script save's file in defined path / file.ngc in input in group "Save as ..."
steps are:
- set or use defined path (no error handler for non existing target directory. make sure that the target directory exists)
- make your gcode
done

I hope that tips helps. if not write.

sorry for my EN

Thanks for the hint on resetting dimensions- that should do the trick.

As to saving the g-code, my experience is that it is pretty hit and miss. I am using Ubuntu 10.04, and when I leave the default file (which is, I believe, "/tmp/myGcode.npg/", the app seems to save the g-code randomly. I did notice on one case after generation, I got a "pop up" with the file name shown, and clicking on that resulted in saving the file. I can work with the default setting, but would like to understand more about the save feature, because generating the code does not always result in automatically saving the file (there may be some issue with over writing the existing file, when I have to adjust settings...).

This is a great script- ultimately, my goal is to apply EMC2 to a home-built 3D printer. I would rather use Salome for graphics (much easier to use than Blender!), but I like the idea of a single-step process to generate g-code...

ok I think I know where I explain it wrong :/

small steps one more time my english is weak

group "save as.. " is really a place where you define a file where to save result of baking
if default is "/tmp/myGcode.npg/" with "/" on end it is my mistake there should be no "/" on end!
enter there a /tmp/myGcode.npg
click bake and in /tmp folder you will have a file myGcode.npg with result
if you want next file (different) just change file name for exaple
/tmp/myGcode2.npg
/tmp/myGcode3.npg
and so one

now it is explain more correct ?
if not write I will try to help! some how