SFA

rarely does anything get by easystone that makes the machine flinch. Today it missed a Y limit with a tool. It is not uncommon for me to run parts up to within a 1/4 inch or so of the limit. When I told it to write the code it did not error out.

When I check the run time it errored out with like a 4'' Y axis over run.

Being the optimist (and because I checked the limit before I did the whole slab setup) I decided to believe the code generator and not the run time generator.

Guess which one was accurate? First time I've ever gotten mislead by easystone on this.......

Oh well. Just run everything else on the table and then shift the part 4 inches and run it.

Just curious did the machine try to cut it and reach the limit or did it just give you a software limit switch error and not try and cut it

The machine cut the first half of the part, and then stopped mid Bullnose breaker and gave me the error. Usually easystone will giv e me the software error and I can adjust prior to starting

Chris,

Two potential contributors:

The configurable limits in Easy Stone must precisely match the software limits and protected zones on the CNC.
(Table dimensions and relative location together with the *.ppm file axis descriptions for your machine)

There's no magic to it, the tool center is mathematically in or out.

Manually jogging the machine to its +/- limit for each axis is a simple way to get the numbers if you don't know where to look in the control. (cancel active tool offsets and part origins first, go slow when near the limits to avoid "coasting errors" in the axis position display.)

Otherwise, if the tool radius is larger at the CNC than in the software, the tool center could end up out of bounds only at the machine.

This is another example of why the tool information in the software should accurately reflect the values at the machine (or err on the conservative side).

Sometimes the limits on the machine can be cautiously tweeked to give you a little more space if it is determined beyond doubt that no risk of collision or damage will be introduced with the modification.

S

Just checked and the diameters are good at the machine and in ES.

What was curious as to why it errored out on the time generator but not on the normal code generator (forgive the home made lexicon).

Just finished the part so no big deal just curious.

Easy Stone can generate a log file to help determine where its choking.

Let us know if you want to look into it.

I didn't know there was another way to check it other then the simulator. I didn't know the code generator warned you.

Chris,

Just as Steve has said the limits on the machine must match what's in Easystone's .ppm file. Also you have several options for debugging or logging in Easytone. It's in the General section under file - configuration, but be warned anything over the debug lvl 2 setting will cause the code generation to become significantly longer in the time it takes to generate it. I showed it to you back in March when I was there, so it should only be used to find the issue and then turn it off. Ask myself or Steve and we can walk you through it. Ask Jerry if he want's to look at your configuration or not. I suggest that at the minimum you get it looked at. But Steve is also right in that the tool database must also match exactly what's on the actual machine in order for the software to flag any possible alarms and not skip them.

Just as a point of information to any new people on the board.

I love Easystone.

The lied part of the title to this thread was very tongue in cheek. Just wanted to make sure any body wandering thru here at a later dates understands.

Chris, In MDI mode key in GG52XYZ and let your machine move to its machine home. Now turn your feedrate knob to 0% so the machine cannot move. Now hold down the X, Y, and Z plus and minus buttons and record the value in the distance to go window on the controls. Then give me a call while your near your programming software.

Jerry

will do.