Alex Joni pravi:
>>>> - what is allowed during a pause? everything? only jogging? some MDI?
>>>> all
>>>> g-codes? running subprograms?
>>>>
>>> My first thought was jog-only, but then I realised you need to be able
>>> to touch-off.
>>> And possibly switch to a different tool (MDI) or run an automated
>>> measure and touch-off (subprogram) and then the size of the task of
>>> even speccing this becomes clearer.
>>>
>> Jog only and be able to switch spindle and coolant on/off and touch off
>> a tool.
>>
>
> see.. this is where differences of oppinion appear (which is by itself a
> very good thing, but takes a lot of time to decide upon something)..
> Wasting programmers time to write a spec is not really useful, that's the
> only reason why this hasn't been implemented yet.
>
> Decide upon a spec, and I'm sure it'll (quickly) get implemented.
>
>
>> Any other bells, whistles and toolchanges should be programmed in the
>> code in the first place.
>>
>> It shouldn't work within canned cycles or subroutines either. It doesn't
>> on the commercial controllers I've used, and therefore don't see why
>> that should be used as an excuse not to implement it.
>>
>
> this is a very useful datapoint, together with info what the controllers
> were (make, type and version).
> even collecting information like this in a central point will get things
> going
>
> I started a wiki page on this topic, hopefully everyone who has a saying
> about it will contribute to it [1]
> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?ManualWhilePaused
>
> Regards,
> Alex
>
>
Hello...
I think that simplest and best way to solve that problem is to leave
choice to users.
It's needs just 4 line in machine INI file. If none applied then
standard behaviour (all dissabled)
M0_ENABLE = jog, mdi, subs, SpindleCtl, CollantCtl, TouchOff .. .. ..
#or if that's hard then use sum of numbers 1=jog 2=mdi 4=subs 8=SpindleCtl
M1_ENABLE = parameters same as M0
M6_ENABLE = ..same as M0/M1 parameters
ON_PAUSE_MODE_ENABLE =...same
This shouldn't be hard to realize. Of course if you do something out of
program then be careful to not break/crash your tools. Do not complicate
here.
I think that just remembering position/plane/fixture where was is
enougth. so for example.
1. I think :D that tool as dull so I press pause
2. Machine saves position/plane/fixture... modes...
3. I jog out of work and resharpen/change tool (collet using)
4. I made new TouchOf of Z axis as tool height can be different
5. I pres continue
machine restores plane/fixtures (in that examples nothing changed
here) - nothing moves yet
machine restore initial position as saved in step 2. But using
priority of axes (can be same as homing sequence or some else specified
in ini)
so for mill for example assume that user leave tool high enought
(Z) axis to be safe or to move on top position
after that XY can move simultaneous to saved position (step 2)
after that Z axis goes to the saved position
and voila - safe restart.
To much?
Slavko.
------------------------------------------------------------------------------
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
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
