Just poking in here, but why not use comma delineators. Then you can by default have, say, 16 parameters per tool, most unused for now, but allows expansion of parameters at any stage. So each line would look something like;
1, T1, P1, D0.125000, Z+0.511000 , , , , , , , , , , , , ;1/8 end mill It also allows users to personalise things. One might also want to keep flute length, flute number and other parameters in there so it's all in one one place. Cross-referencing charts is a pain. One can still use a prefferred editor or spreadsheet to break the colums up and help edit. Roland 2010/1/6 Erik Christiansen <dva...@internode.on.net> > On Tue, Jan 05, 2010 at 10:18:59PM -0600, Chris Radek wrote: > > > > Here is what the new tool table format looks like: > > > > > http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=configs/sim/sim.tbl;hb=tlo_all_axes > > Now that looks very business-like. > > > You can see tool number, pocket, diameter, Z offset, comment. > > Yes, you need comments. (Well, I do anyway.) > > > A lathe would have some more words for each tool. A two-turret > > lathe might have some tools with Z and some with W, etc etc. > > > > This removes a lot of the mess we currently have where every feature > > change that touches the tool table has to either keep the number and > > order of columns the same, or break everyone's tool tables. > > > > For wear offsets I'm not sure what we'd want. One idea that comes > > to mind is to have a second tool table for those. It could have > > tool numbers and offsets but not pocket numbers or orientations. > > Could it perhaps be handled by optional parameters in Michael's new > table format? In the past, I've handled such parsing variability with > lex & yacc, and a suitable BNF grammar [1]. Using such tools makes it > easy for the parser to accommodate evolution of the table format over > time. But maybe Michael has it all wrapped up. (I'll figure out how to > use git, and take a peek at his branch. I'm not sure whether my > familiarity with CVS is a help or a hindrance. I know that was a pain > until I learnt to think its way.) > > [1] A listed grammar also answers any user question along the lines of > "Is this legit syntax?" > > Erik > > -- > The world is full of willing people, some willing to work, the rest > willing to let them. > -- Robert Frost > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
