Gene Heskett wrote: >> >> Thanks very much for this pointer. I've got the 10-min demo version, >> went through the scripts, manually got a dxf file mocked up and sure >> enough -- the "gcode_angle" script is correctly generating G2/G3 arc >> moves. >> > > Which would be very nice, but did you note the asking price for this little > add-on? That 149 EUR translates to something that WILL make a dent in my SSI > check. > > Um...well, I bought a license for Qcad, mainly because I do need a good, working CAD...and since I do most of the work in Qcad, I just do my drawing, then my toolpaths, pop over to CE, do the "CAM Export" real quick.
Qcad is worth paying for, but CE has some quirks with its CAM capability. I'm using the CE demo version for now, and I am currently working on a 'smarter' dxf-to-gcode program. >> I'm still not fond of Qcad for doing simple things -- it's UI and work >> style doesn't make sense to me, but I'm sure it works for most people. >> I have no problem digging in and grokking it for more complex stuff in >> the future, I was just hoping to use a more simple drawing program for >> the simple parts I want to mill, and build a toolchain from there to >> g-code that still allows me to use G41/G42 tool comp. >> > > I'm getting the impression the QCad and CAM Expert are older code, there is > no > mention of the ubuntu distribution compatibility on the ordering pages. > > I normally use Debian, but I'll take my binary tar-zip of Qcad over to the EMC computer this evening and see if everything is kosher. I don't expect it'll have any problems. >> But, I'm probably reaching the point of diminishing returns, and should >> just buy Qcad/CamExpert, buck up to the learning curve, and mill my >> damned parts! 8^)= >> > > I think we'd all like to do that. :-) > > Has anyone here made use of gCAD3D? It looks fairly capable to my easily > impressed eye, and can save in at least half a dozen formats, including .dxf. > > Is there a FOSS .dxf to semi usable .ngc convertor utility around? > > >> There's Gcam [http://gcam.js.cx/index.php/Main_Page], which I have tried and think it could become very good. It uses it's own file format, but I think it would be relative easy to make a dxf->gcam conversion script. Gcam outputs proper arcs/circles, has a voxel preview of your work, a 3d/2d view of your toolpath, and lets you work in terms of pocket/extrusion boundaries and drill holes. There are some (IMHO) slightly awkward constraints on how you can create geometry, but it's still a very good diamond in the rough. Since you guys seem interested in the whole approach, here's the way I've gone about it: Starting with Qcad, I make my drawing, either starting with a picture to trace, my handwritten sketches, or I simply play with the geometry to get it right. I make use of mulitple layers for diffent parts, different heights, or even 'scratchpad' layers for tracing and working things out (I'm influenced by my earlier experience with hand drafting). Once I've broken down my part into stages, I create toolpaths on separate layers. One of the main reasons I finally paid for Qcad was the new polyline feature they added - creating polylines from existing chains of arcs and lines. (Sadly, this did not work properly when I first tried it. I immediately filed a complaint with ribbonsoft...and less than a day later, they had it working properly, with an update available for download. Yahoo!) I make parallel offsets of my part outlines, using the polylines. It's not perfect yet, and I've been trying to figure out how to make a repeatable error so I can show ribbonsoft - but usually, it works fine. Qcad is mouse-centric, with the ctrl, shift, and alt keys allowing rapid scroll/pan/zooming with the mouse wheel - and all functions are traversed using the menu on the left, and right click backs out of any function. After creating toolpaths, I save, I pop over to CAMexpert, open the file, and export. Since the sorting and optimization in CE needs work, unless I'm doing simple stuff I usually plan everything - I make all my toolpaths continuous chains, using a "rapid" layer with lines for G0 moves. You can manually choose your toolpath, where I pick the starting point....once it's chosen, I hide the "rapid" layer, and now all my rapid moves really are so. Lately I've discovered the "useful-subroutines.ngc" with EMC, and have been using O100 functions, using Qcad as reference while I hand-write the gcode file. Many thanks to Chris Radek! As far as using tool-comp, it shouldn't be too hard with Qcad/CE - you just have to draw it, and then edit the gcode file to put the cutter comp codes in the right places. Second-to-last, I keep a version of EMC compiled on my desktop for --simulation-only, to preview my codes (Many thanks to all you guys :) I've been looking at gdepth [http://axis.unpy.net/01169521961], but haven't tried it yet. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
