> Message: 2 > Date: Mon, 15 Jul 2013 01:24:21 +0200 > From: Michael Haberler <[email protected]> > Subject: Re: [Emc-developers] discuss: Why do we have MAN, MDI and > AUTO modes. > To: EMC developers <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > Am 15.07.2013 um 00:59 schrieb Stuart Stevenson <[email protected]>: > > > Gentlemen, > > I remember the good old days when I learned to run the cnc controls > Fanuc > > 5T and GE 1050 mill control. > > I could be running in AUTO mode. Hit single block to stop the program > > processing at the end of the currently processing block. Switch to MDI to > > input a control command OR MAN/STEP to do some thing with the machine. As > > long as I did not hit the reset button I could switch back to AUTO, hit > > cycle start and the machine would take off as if I had done nothing in > MDI > > or MAN. > > Could you summarize which kinds of changes are possible when switching > from AUTO to MAN (or MDI a bit) AND which remain in force when you cycle > start? (because that's a hard case) > > example: machine position - does it revert to where it left off? what for > offset changes? tool diameter? >
At the end of a block - single step operation where you must hit cycle start to run each line of the program. (This is much different than hitting feed hold) The axis motion follows the operator input. The machine state remains the same unless changed by the operator. With MDI the operator is able to change the state of the control with commands just as if the control was running in SINGLE STEP AUTO. Every control command is available to the MDI input. If you want to change a tool then MDI would allow that. You had better make sure you match the TLO to the tool as you choose or bad things will happen. CRC changes are allowed. Essentially, anything programmable is available by MDI. The controls read from a paper tape. The is queued in the reader waiting for the next AUTO line request. The control interprets the next line on the paper tape using the state of the machine control when AUTO is selected. This goes well providing the operator has used MDI and MAN to prepare the machine and control for the next AUTO line. Operator competence and care is paramount. > > > It was not unheard of for the operator to change a modal command or > > position the machine incorrectly and when the cycle start button was > pushed > > the machine would do something unexpected but that was the operator's > fault > > not the machine. > > This was very convenient for a competent operator. > > I believe many machines function in this manner today. > > > > Another 'feature' I have found hardly useful is to be able to hit feed > > hold, switch to MAN, move the machine to change a broken tool, reset the > > TLO, switch back to AUTO, hit cycle start to restart where the machine > was > > put in feed hold. When they first put this in the controls I thought this > > would be very cool. I found I used it so seldom I did not learn to use it > > at all. If you are watching the machine process properly you will be able > > to change tools prior to tool breakage in almost all cases. > > which operations are important to have during feedhold? (that's another > hard case) > Here my understanding is not as clear as this is a 'feature' is did not like nor use. During a cut the need for a tool change becomes apparent. The operator pushed the feed hold button to stop motion processing. The spindle (tool or workpiece) will need to stop somehow. The stop point will need to be remembered. Operator intervention will move the machine to separate the tool and workpiece. The stop point will need to be remembered. Multiple operator moves and stop points may need to be remembered depending on the process. If grooving with an ID bar or back ID trepanning a complex set of remembered points may be in order. The machine is moved to allow a tool/insert change. The machine is moved to allow reset of tool offset per the new tool dimensions (if necessary) The operator then positions the machine for restart. Restart mode causes the machine to retrace the remembered points in reverse order to position the machine to resume program operation. The first remembered point (the last in the restart operation) is approached at the programmed feed rate. If this is done I would suggest a graphic representation of the remembered points. On the controls I ran it was not clear if you had caused the control to remember a point or not. This led to sphincter exercise. > > > > > I did run a machine once, I don't remember the control, that I could > change > > the TLO or Work Piece Coordinates and the machine would complete the > > currently processing block as prior but the next block would incorporate > > the changes I had made. I DID LIKE THIS. > > that's a good case for delaying binding offsets and TLO to motion time, > this is done way too early now which is why this doesnt work > > for this to reliably work we need a reliable motion ID first (which must > be a guaranteed-to-be-unique wrt line source context); the current one > isnt, I'm rather sure it is possible by appropriate choice of linenumbers > of subroutine definition and call statement to generate motions from two > blocks which have the same motion id > > > it is back to square one: we must fix the known-to-be-broken fundamentals > first or we'll never get beyond patching around > > -m > > > > > thanks > > Stuart > > > > > > > Thanks Stuart -- Addressee is the intended audience. If you are not the addressee then my consent is not given for you to read this email furthermore it is my wish you would close this without saving or reading, and cease and desist from saving or opening my private correspondence. Thank you for honoring my wish. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
