Advanced Search

Look in the Integrator Manual in the axis section of configuring EMC.

John

Hi Anders,

I think it was Brad (sliptonic on IRC) that did the spider. He's got a cnc router set up for doing a lot of fun wood projects for his family and friends. That's one of the things that I love about this sort of thing- you can amaze your family and friends with awesome work.
I see your code unleashing a wave of creativity that hasn't been seen before in the open source cadcam world. I know that it could be used for all sorts of things- guitar parts, surfboards, jewelry...
I especially like the fact that you and Dan Heeks are working together on this. Dan's 'Attach' machining operation is especially powerful in combination with your code.

Thanks for all the hard work with this.

Dan

Hi Dan F,
It's nice to see that someone actually uses OCL. The foam spider on your blog may have been the very first part anyone has ever cut with this code!

Once the basic routines for cutter-location (drop-cutter which is done, and push-cutter which I am working on slowly) are done, as well as offsetting and a few other things are in place I think there is potential for a lot of different things. For hacking, the closer you can go and take a peek at the low-level functions in the python-code the better.

I've really only been visualizing things with VTK so far, but as heeksCNC improves I might switch to developing OCL under it.
Ofcourse OCL is not tied to HeeksCNC and anyone could come up with another GUI if they wanted (Coin3D, VTK, etc. etc.)

I am very slowly working on a lathe project, and if/when that machine starts making chips later this year then I will take a look at 2D lathe operations. These should not be so different from the 2D offset or waterline ideas/algorithms which are needed for 3-axis milling anyway.


Anders

Hi!
I need to compensate X axes. Can anybody help me to show the example of this file?
In Integration Manual there is only menthioned of this file, no example

Anders,
Thank you so much for doing this. I've been using the HeeksCNC implemented version of your software and I am very impressed.
Dan Heeks also set up the 'Attach' machining operation to your libs and now we have some really interesting options for machining surfaces and machining on surfaces.

Thanks,
Dan

a status update on what has been going on lately.

The drop-cutter algorithm has been optmized a bit, and the Toroidal/Filleted endmill case, which is the hard one computationally, has been improved.
OpenCAMLib now supports cylindrical, spherical, toroidal, and conical tools. A CoumpoundCutter class can combine these shapes to produce e.g. an APT-style cutter (cone at the center, toroid in the middle, and then another cone).
There is a cutter.offsetCutter() function which returns an offset-cutter for producing stock-to-leave paths.

There is a simple CL-point filter which detects collinear points and removes them. This example shows the raw CL-points close to the surface and the filtered ones offset upwards:
www.anderswallin.net/wp-content/uploads/2010/07/line-filter.png
a good addition to this filter would be an algorithm that detects circular arcs for output as G2/G3 moves in G-code.

There is an experimental octree-based cutting simulation:

and

building the octree which represents the cutter-swept-volume for each G1 move at a reasonable resolution takes about 3s on my machine, so that is the bottleneck now. I have not looked at all at optimizing how the octree is rendered (now all faces of all cubes are rendered, which is slow).
If these problems can be overcome this can be the basis for a very general cutting simulator. 4/5-axis, undercuts, lathe-ops, and arbitrary cutter shapes are in principle possible.

I would like to work on waterline or z-slice toolpaths next, similar to this picture:
www.grzsoftware.com/nimage/waterline.png
This will again be based on a triangulated surface and "sampling" or calculation of a number of valid cutter-locations which then are linked together into a toolpath.


Anders

The Exception was caused by an error in the Gtk2 Widgetset, This was fixed in the latest source.
Wrote yesterday the 3D Preview for mocca, so a Full 3D preview of the milled part is available now.
Source and binary will be updated end of this week,

regards, Thomas

Hi deadalus

I'm a newbee with mastercam but I'm running quite succesfull a X4 MU2 version. with a 3-axis EMC

I'll attach you some files....

Until now my problem is related to G28 or generaly sppeking I'm not yet able to have comletley automated "homing"

I have to delete the G28 lines.... And home by hand...
For the future aim is to have an "probing installation" that alowas unchanged code...

Hope this helps you a bit

Mike

Hello,

Try looking here.
www.linuxcnc.org/docview/html//gcode_main.html#r3_7

Rick G

Hello,

What you probably want to use is o<filename> to call an external ngc file. This should work in 2.4.x, nor sure it was working properly in 2.3.x

You can use M101 etc. to run external programs.

Rick G

Hi,
i'am trying with no success to call a small program with M1XX code in MDI. I have build a file:

M101

---

G90
G0X0Y0
exit 0

---

M code link work well, but nothing happen.
Can i call g-codes in M1XX soubroutine?

Thanks,
Michele

hi thom
for for updating moca, and also a English translation, i see there are still some areas to be translated, like on tool edit window etc.

also when i go to MDI window, i still get the error as above,

running from command line gives me this print out
hope this helps, robert

$ emc
EMC2 - 2.4.1
Machine configuration directory is '/home/superslant2/emc2/configs/sim'
Machine configuration file is 'axis_mm.ini'
Starting EMC2...
Mocca starts with correct version EMC2-2.4.1
Library loaded from: /usr/lib/
mocca reads from :/home/superslant2/emc2/configs/sim/
Default NML- File: /usr/share/emc/emc.nml
Setup is metric
Config directory = "/home/superslant2/skins/default_en/"
"index" in tool config is out of range
Added Script: test ,File: test.nc
Hal component "mocca" loaded.
[WARNING] Out of OEM specific VK codes, changing to unassigned
[WARNING] Out of unassigned VK codes, assigning $FF
Reading layout from /home/superslant2/skins/default_en/mocca.xml
Reading layout from /home/superslant2/skins/default_en/jog.xml
No Jog-Increments set in config-file
Using default configuration
Reading layout from /home/superslant2/skins/default_en/mdi.xml
Reading layout from /home/superslant2/skins/default_en/run.xml
Canon Offsets: 0.00 0.00 0.00
TApplication.HandleException Access violation
Stack trace:
$0114906E
$081C543C
$08115B5B
$08114DCA
$080EE34C
$080EDF45
$080EEF1A
$080EE415
$0805D011
$08062292
$08063369
$080EDF45
$080E925A
$0806288D
$080EC9FD
$080EFDBB
$081D9EDA
Shutting down and cleaning up EMC2...
Cleanup done
superslant2@superslant2-2:~$

Might have been a time out or something...

John

There was something wrong in the english versions of mocca, this was fixed in the latest binary.
We have now the english config and layout files available. So please take a look at the project homepage at googlecode. mocca.pdf is the documentation in english, still missing a lot but at least some documentation

The gtk2 OpenGl problems are gone... mocca now works on any linux with a installed Gtk2.
Pleas do NOT use mocca for lathes, it was not tested on real lathes, just on milling machines.

regards, Thomas

Hey, I wrote like three paragraphs and then something ate my session.

I'll tell more about the project this weekend. I'll also take a look at that post and go through some of the documentation.