Kirk Wallace wrote: > On Sun, 2009-05-03 at 07:04 -0500, Ray Henry wrote: > >> On Sun, 2009-05-03 at 09:56 +0100, robert wrote: >> >>> this is a shame if emc does not store current tool into a paramiter >>> looks like i need to keep a perm record in plc some how then. >>> >> You could use a parameter in the var file to keep track of current tool >> number. This ability has been a part of the EMC for all the years I've >> been hanging around it. IMO this is more a user interface issue than it >> is a core EMC problem. >> > > Parameter as in .var file or with g-code #? > i just asked on IRC about the var file, cradek said you cant realy do it and looking through the docs i cant see any ref to setting a parameter in atxt file from hal, unless one makes there own hal comp file > I did a little more research, I think iocontrol.0.tool-number and > iocontrol.0.tool-prep-number will work. Using a sim config and Hal > Meter, it looks like tool-prep-number changes on the completion of the > Tx word, and the tool-number changes on the completion of the M6 word. I > suspect they where designed to work that way :). i can see why, as on a random access changer, u would call the tool, wait for the carousel to get that tool ready and in position, normaly while running and cutter metal then issue the m06 commad > So tool prepare-prepared can stay tied together (logical short circuit). Then > the change-changed loop could be opened to insert a script that checks > iocontrol.0.tool-number, checks the carousel encoder and insures they > match, invoke a tool removal, read iocontrol.0.tool-prep-number, move > the carousel to the prep-number, move the tool from the carousel to the > spindle, set tool-changed to true. > > Other parts of the script could be made to clean the tool taper, verify > the tool is seated properly, verify the changer arm is in the proper > positions, time-out if any procedure takes too long, check for adequate > air pressure if needed, check for proper sensor operation, etc. > yep this is pritty much what i have written out in a quick classicladder sketch, obvisly adding things and sequencs as needed for setup like spindle orientation. thanks for taking time to confirm this > One problem might be that EMC2 seems to start with > iocontrol.0.tool-number = 0, and iocontrol.0.tool-prep-number = -1, so > an init script may be needed to read the carousel encoder, or maybe > better, require the operator to check or set the carousel, spindle and > tool status at start up. > > yes this shame if theiocontrol.0.tool-number was set as a paramiter and stayed from last sesion etc we could just read it right in at start. i dont see anyway to set tool-number from mdi etc i was hoping M61 would of done it but it didt
iocontrol.0.tool-number get sets after the first complete M06 i belive as i dont have any encoder etc or anyway to know where i am on the carousel as it is , so #1 option setup a way to set a preset count and keep track where we are from session to session #2 take the changer apart and find a place to fit an encoder of sorts to read in each pocket number/posision i dont realy want to rely on the operator to setup carousel each time, and ever morning etc it might get a bit tedius also > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.325 / Virus Database: 270.12.15/2093 - Release Date: 05/02/09 > 14:23:00 > > ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
