Roland Jollivet pravi: > 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...) > > > I'm not shure what you mean. The problem to handle this is that switch is limit switch too. So any code moving axis can't reach that switch as soft limit is trigered before. If I override soft limit then switch act as limit and triger hard limit.. So the only rehular way is while homming.
------------------------------------------------------------------------------ Download Intel® 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
