Chris, in file labels.ngc, line 1: Olabels sub Should be: O<labels> sub and: Olabels endsub Should be O<labels> endsub
This syntax error should also be corrected in the other files. regards, Jan On Wed, Sep 30, 2009 at 18:00, Chris Epicier <[email protected]> wrote: > > > > Dear Stephen > >> >>Check this chapter in the manual: >> >>http://linuxcnc.org/docs/2.3/html/gcode_main.html#r3_7 >> >>Regards, Jan > > I did, but I just cannot get it to work. I have 5 files: > > [master.ngc] > O<labels> call > O<internal_contours> call > O<external_contours_rough> call > O<external_contours_finish> call > G53 G0 X0Y0Z0 > [end of master.ngc] > > > [labels.ngc] > Olabels sub > N0G20M6T2 > .... > N868M09 > N869M30 > Olabels endsub > M2 > [end of labels.ngc] > > [internal_contours.ngc] > Ointernal_contours sub > N0G20M6T2 > .... > N868M09 > N869M30 > Ointernal_contours endsub > M2 > [end of internal_contours.ngc] > > [external_contours_rough.ngc] > Oexternal_contours_rough sub > N0G20M6T2 > .... > N868M09 > N869M30 > Oexternal_contours_rough endsub > M2 > [end of external_contours_rough.ngc] > > [external_contours_finish.ngc] > Oexternal_contours_finish sub > N0G20M6T2 > .... > N868M09 > N869M30 > Oexternal_contours_finish endsub > M2 > [end of external_contours_finish.ngc] > > > All files are in the same directory. I believe I got the > master file about right. What I doubt there is if the homing > sequence is correct but that's not a showstopper. > > In [labels.ngc] and all the other sub files, I doubt > the missing line numbering. My programming experience tells > me, either it has to be ther or totally omitted. > > If I load master ngc in axis, I get no errormessage. when I > run the file I get "Bad Number Format". > > I am lost now. What's wrong and where, any help is greatly > appreciated. > > greets > > chris >> >> >> >> >> >> > >> >> > >> >> > > >> > >> >======================================================================= >> > >3.7 Calling Files >> > > >> > >To call a file name the file the same as your call >> and >> > include a sub and endsub. The file must be in the >> directory >> > pointed to by PROGRAM_PREFIX >> > > >> > > o<myfile> call (a named file) >> > > >> > >or >> > > >> > > o123 call (a number file) >> > > >> > >In the called file include the oxxx sub and endsub >> and >> > the file must be a valid file >> > > >> > > myfile.ngc >> > > o<myfile> sub >> > > ... >> > > o<myfile> endsub >> > > M2 >> > >================================================ >> > > >> > >If I interprete that correctly, I shoud be able to >> do >> > this: >> > > >> > >Let's assume I have these files: >> > >engrave.ngc, bevel.ngc, inner.ngc, outer. ngc, >> home.ngc >> > >> > > >> > >I so, I woul generate another file, let's call it >> > master.ngc with about te following content: >> > > >> > > >> > >omaster.ngc call engrave.ngc >> > >omaster.ngc call home.ngc >> > >omaster.ngc call bevel.ngc >> > >omaster.ngc call home.ngc >> > >omaster.ngc call inner.ngc >> > >omaster.ngc call home.ngc >> > >omaster.ngc call outer. ngc >> > >omaster.ngc call home.ngc >> > > >> > >However that fails, why? >> > > >> > > >> > I haven't tried it, but one thing to note is that the >> > <> are necessary >> > around a named O-word or parameter. >> > >> > Also, the manual might be a little unclear since it >> looks >> > like the text >> > in parentheses is part of the command. I think what >> > the instructions >> > are trying to say is that the master file should do a >> call >> > with the name >> > of the subroutine file: >> > O<engrave> call >> > O<home> call >> > ... >> > >> > And the subroutine files should be like this: >> > engrave.ngc: >> > O<engrave> sub >> > (your engraving G-code goes here) >> > ... >> > O<engrave> endsub >> > M2 >> > >> > home.ngc: >> > O<home> sub >> > (your homing g-code goes here) >> > ... >> > O<home> endsub >> > M2 >> > >> > Etc. >> > >> > Try it and let us know if it works this way. >> > >> > - Steve >> > >> > >> >> >> >> > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
