Closed GoogleCodeExporter closed 8 years ago
I have been swaying backwards and forwards between suggesting the re-use of the
'locating' operation and adding a separate 'optional stop' operation.
We have a 'locating' operation that rapidly moves to a x,y,z coordinate and then
issues the M0 command. The original idea was to allow me to run a drilling
cycle and
then base a locating operation on the drilling cycle's locations. When it
moved to
each drilled hole it would issue the M0 command and allow me to use my tapping
chuck
manually. I then pressed 's' to re-start and it would move to the next hole and
pause again.
If we were to add an 'optional stop' operation, I would expect to want it to
move to
a some location before pausing so that the cutting tool was 'out of the way'.
I suppose the difference here is that the locating operation takes the
coordinates
for the rapid movement from graphics objects in the same way as the drilling
operation does. These coordinates are also within the realm of the current
coordinate system (G54, G55 etc.)
Would it be enough to add an extra property to the 'locating' operation that allowed
the user to enter a 'safe coordinate' in the operation's property window rather
than
looking for graphics objects? It could interpret this coordinate as a 'machine'
coordinate (G53)
Is the locating operation enough or is the functionality slightly different?
I would be happy to implement it. I just wanted to get the requirements clear.
Original comment by David.Ni...@gmail.com
on 8 May 2010 at 10:42
I wasn't aware of the locating operation- let me try that out first before we do
anything about a separate M0. I can probably make something work in my
postprocessor
with that.
Thanks,
Dan
Original comment by ddfalck2...@yahoo.com
on 9 May 2010 at 12:03
The locating operation works for me. In fact, I think it's perfect for what I
want to
do.
Thanks,
Dan
Original comment by ddfalck2...@yahoo.com
on 9 May 2010 at 7:18
Closed.
Original comment by David.Ni...@gmail.com
on 10 May 2010 at 10:50
Original issue reported on code.google.com by
ddfalck2...@yahoo.com
on 8 May 2010 at 5:41