Anfang der weitergeleiteten E-Mail:

> Von: robert <[email protected]>
> Datum: 28. Dezember 2010 23:28:03 MEZ
> An: [email protected]
> Betreff: Re: [Emc-developers] Revising the toolchanger protocol -     
> requirements
> 
> 
>> So lets assume the tool change process resulted in an error, or a TC abort 
>> button was pressed.
>> 
>> What would you expect to happen in EMC?
> i think EMC should react in a safe and predictable way like it does with all 
> error codes to date.
> a program stop/abourt is nice that then places EMC back into manual mode with 
> a error up saying tool change abourted or something
> as from looking at it i dont think machine needs to be placed into a machine 
> off state for this error.
> this would allow the user to then use a PYVCP panel, or real buttons or even 
> Mcodes to get out of the error or move the machine etc, as some machines need 
> to move the Z axis up to do a tool change
> 
> our CNCs have an array of Mcodes built in that will let you do a tool change 
> sequence from start to finish, and u can issue these only from a MDI command. 
> so this lets you reset the tool arm or carousel, then u can search the 
> program for the tool change location and run from that line ...
> 
> some machines i have used have had a secrute switch behind the panel that 
> lets you move one station at a time on the turret as this was on a lathe. did 
> the turret up and next station with switch on, and off it did a lockdown, 
> again u had to be in a set mode for this to work.
> but this is more to the intergrator i feel, the same way i think EMC will 
> recived a tool change abourt signal..
> 
> 
>> What I can imagine is passing through more information to the EMC level, 
>> namely wether it was a tool-prepare or a change, what the tool/pocket number 
>> was, and how it was aborted (user, machine). That could be passed to say an 
>> Axis message describing what happened. But other than that, the tools at 
>> hand at this point are really what I described in the previous paragraph.
> tool prep error would be handy so on a random, if u cant find a tool # for 
> what ever reason u can abourt safly before a m06 is even throught about.
> but here do you want to abourt the program? as on a random u will be down in 
> the job running Gcode, while getting the next tool ready.
> 
> so maybe abourt at the m06 command using the same tool-about path as above 
> but a error message that says tool-prep error
>>> what todo with a changed or not changed tool number state is tricky
>>> some controls i'v seen asume it has change the tool from pocket to the 
>>> spindle,  i think you have to say, what does someone do in a power cut 
>>> while in a tool change right now?! answer is problem same for here...
>>> other dont and still think the old tool is there.
>> Ok, that sounds exotic, but I could imagine that EMC dealt with powerfail in 
>> a more configurable way beyond just restarting in e-stop mode; for instance, 
>> trying to save essential machine state if a powerdown is pending, and deal 
>> with it in a controllable way if power comes back up. Linux has fairly basic 
>> support for dealing with powerfail and recovery in a controlled way provided 
>> there's some power backup to at least permit a controlled shutdown, and that 
>> mechanism could be built upon.
>> 
> what i ment here was what does machine do on a power stop or estop not how 
> does EMC or linux machine react turning off is fine what whats machine do in 
> a tool change.. the user has to power back up and reset the tool changer or 
> what ever i know but its same route he/she has to take as to what the 
> tool-abourt is going to do in away.. this is how i ment this to come over.


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to