'Simulate with CAMotics' plugin

[Bob La Londe]

I don't use (well haven't mostly) conical cutters and v cutters almost never, so that doesn't affect me much, but I have to say the way it is now is nice.

I just turn on the operations I want and simulate with Camotics.  Depending on the complexity a few minutes later I have a rough cut proof on screen.  Since I tend to use CamBam on my right side monitor its really convenient because Camotics opens up on the left side monitor. 

This is a nice plugin and the bug fix on the spaces in file path was just icing on top. 

[jk]

Version 1.4 has arrived - fix for the diameter of conical tools. Hopefully this time would be ok )
First post updated.

[michel]

Hi,

I installed that plugin and when running a silulation of a part for testing I get this error . What can be the issue here ?



regards
Michel

[dave benson]

I've had a chance to use the plug today, and have done a fair bit of simulating (with lots of different files)
and find It's very handy.
Dave

[Bob La Londe]

The big thing for me is between the plug-in and the Camotics software its now very very easy to use.  I've used Camotics off and on for a while now, but this plug-in really makes it pop.  

I know.  I know.  I am starting to sound like a fanboy.  I'm really not.  So far the latest rendition seems to work and its easy to use. 

[jk]

I installed that plugin and when running a silulation of a part for testing I get this error . What can be the issue here ?

Something wrong with the generated g-code file, I think.
Show the first lines of it for investigation )

[dh42]

Topics merged

++
David

[michel]

here is the created g-code

[dh42]

Hello Michel

I have a look on your Gcode ; the pb is that there is a lot of Gcode that Camotics do not understand like:

G60, M51, M20, M83, M28, M29 ... etc

Use a more standard post pro (Like Mach3) to do the simulation, then switch to your Ranc232 postpro to generate the 'real' Gcode for the machine.

++
David

[jk]

Michel, CAMotics screams on a first line because of 'percent sign' start of program marker it do not understand.
You should switch to a standard preprocessor for simulation as dh42 suggests.

[EddyCurrent]

In addition to what David said, I had to delete %11 in line 1 before Camotics would even attempt to run it.

Ha jk, you posted the same time as me 

[michel]

Hi All,

My opinion is that a simulation has to be a close representation of the actual reel milling after . So it is a kind of evaluation of your g-code output. If I have to use another processor like the mach 3 for example then any evaluation  of your reel output is gone and then this is just becoming a visual on screen with no added value.

If camotics can't handle the output I have for my machine then it is useless for me . Perhaps it can be achieved to get another processor to output a similar g-code that leaves out the bugging parts of it.

I must say that I was hoping to use this when I had to mill a unsual part to be sure of the result but until today CB did not give me any reason to simulate as it works very well. The program has never let me down yet ;-)

It would have been a nice addition in some situations.

[pixelmaker]

michel,
if you have a controller that needs a G91.1 the toolpathes are the same in a controller that need G91.
You have to configure a pp that work with a simulation software. If same commands have different numbers does not matter. That's always the same.
It is the same with the simulation of mach3 code in CutViewer. The original code don´t work and you use a different, but always the same, post processor for simulation.

ralf

[dh42]

Hello,

Your Gcode works as is on CutViewer Mill, just need to define stock and tools (but it can also be defined in the PP and passed automatically by CB, so you don't need to define it yourself in CV).

If CV don't understand a code, it skip it, where Camotics give an error.

++
David

[Bob La Londe]

This plug in so saved me some destroyed parts today.  

I was just playing but it did the trick.