You could implement a similar function using a contrived method, that is not
part of the G28 command or other homing function.

Basically you would have a subroutine to deliberately move the machine to
the home switches and write the x,y,z values to file as the switches are
crossed. Assuming they should be  0,0,0, the new, 'wrong' values might be
0,3,0. Then a program outside EMC could interrogate the file data. It might
also be time stamped. The routine would then have to move back to resume
machining.

So depending on how critical your project is, you could use a text or other
editor to insert this gcode as a call function every 500 lines, or 1000
lines, or maybe after every tool change, into your gcode before you run the
file.

I don't know how difficult it would be to implement this using EMC.
When I worked with an Emco mill(stepper), some programs ran for more than
24hrs. I wanted to insert a 'home' call at the start of every new pass. If a
few steps were somehow lost, at least one would be starting with a 'clean
slate', and not have an incremental error. But it could not be done.

Roland
PS (now I'll wait to get shot to pieces by the gurus...)



On 9 April 2010 18:42, Slavko Kocjancic <[email protected]> wrote:

> Jon Elson pravi:
> > The problem with the homing report is the destruction of data.  When the
> > home position is found, the machine position count is set to zero (or
> > whatever the HOME_OFFSET value is).  So, the old home position is
> > destroyed by that operation.
> >
> >
>
> Just that. Before writing that HOME_OFFSET just read previous value and
> show difference. But doesn't work! The destruction of data is done
> earlyer too! That's is done to screw_comp file come at right position!
> So isn't simple as I think.
>
> Slavko.
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to