At 05:48 PM 4/4/2008, you wrote: >I wounder if you could have an .ini file for each job which calls out a >matching .tbl file. This way, you can have as many total tools as you >want as long as any one job doesn't use more that 53(?) tools. > >(Agenda bump: If someone happens to be in the tool code anyway, maybe we >could earmark an on-the-fly tool (wear) offset?) >-- >Kirk Wallace (California, USA >http://www.wallacecompany.com/machine_shop/ >Hardinge HNC lathe, >Bridgeport mill conversion, doing XY now, >Zubal lathe conversion pending >Craftsman AA 109 restoration)
I think it would be best to follow industry and make the tool offsets availiable to macro use as variables both as read and write. On the controls I have used the offsets start at #2000 or #10000 or #13000. When the offsets have a length, length wear, radus/dia., and wear values it is know as Type II offsets. When they start a 2000 you only have 200 offsets. #2001 Length offsets | #2201 Length wear offsets | #2401 Rad/Dia offsets | #2601 Rad/Dia wear offsets If they start at 10000 you can have 1000 offsets. #10001 Length offsets | #11001 Length wear offsets | #12000 There is a break here #16001 Rad/Dia offsets | #17001 Rad/Dia wear offsets | #18000 It should be possible to change an offset from the control while a program is running or at least while it is stopped (feed hold or single step), the new offset would take effect at least at the next G43/44 for length G41/42 for radius comp if hot the next block. __________ Andre' B. Clear Lake, Wi. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. 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
