Speaking of which, I've noticed that in multi-file programs variables set in one file do not commute to subsequent files. That is: values set in one file don't propogate beyond that file. This seems kinda strange since the docs seem to indicate that each file bounded by "%"'s concatenate into one large program. If that's so then the g-code interpreter should have no idea about file boundries and variable values set in one file should continue over all files. If variables are intended by the authors to *not* propogate over sperate files then its seems to me that *modes* should not propogate over seperate files either, but they clearly do (modes propogate).
Robert W. Jon Elson wrote: >Stuart Stevenson wrote: > > >>Gentlemen, >> Has there been a good procedure developed for starting in the >>middle of a program? >> >> >This is too well hidden. Assuming you are using the Axis GUI, >you scroll down to the line you want to start from, using the >mouse buttons on the G-code window. You click to highlight that >line, and then in the File pull down (I think) is a "start from >line" entry. Click on that, then hit "r" and it will run >quickly through the code to get to the right position and modes >at the beginning of the selected block. BUT, it won't start the >spindle! If you don't have a manual spindle override, you are >pretty sunk until this BUG is fixed. Starting the spindle with >F9 and then doing the Run will just turn the spindle off. > >Please excuse, I'm going into <rant on> >Clearly, the spindle is a modal operation, just like G41 or G17, >and so if the G-code starts the spindle in the first couple >lines, it should be running when the line to start from is >performed. In all machining operations, you'd want the spindle >to be started before beginning a cutting operation. If somebody >used M03 and M05 to turn a plasma cutter or laser on and off, >then these would be scattered all through the code, and >presumably the operator would know to start on a line where the >device was off. This all combines with spindle speed, and maybe >even gear changes, so it might get a bit more complex. But, >these are clearly modal functions, and so if you are preserving >the state of all the other modal settings, spindle on/off and >speed should be handled as well. ><rant off> > >Jon > >------------------------------------------------------------------------- >This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >Don't miss this year's exciting event. There's still time to save $100. >Use priority code J8TL2D2. >http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >_______________________________________________ >Emc-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/emc-users > > > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
