WOOOOOOOOOOOOOO HOOOOOOOOOOOOOO
    Thanks guys.  I now have it punching out perfect code for reversing
tension-compression tappers, tapmatic
tappers, and rigid tapping.  I sure appreciate all your help.  Here is a
copy of the .tmp for anyone that wants it.

By the way, where are the jos(xxxx) type fields listed so I can include them
on my printouts.
I want to include the .jof Job notes and Tool notes in my program, but am
not sure of the field names.  Is there a list?
Thanks again
Jon

----- Original Message -----
From: "Lauzus, Frederick" <[EMAIL PROTECTED]>
To: "Jon Baker" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, October 12, 2000 9:52 AM
Subject: RE: [mfg-smartcam] Templates


> I'm just as confused as you are. #CYCLE should automatically be set to the
> correct value form the planner. You can however access the active step in
> the planner from the template file using the jos data tags. the data tag
for
> cycle is:
>
>     jos(cycle)
>
> You could try to force it to update by
>
>     #EVAL(#CYCLE=jos(cycle))
>
> but you shouldn't need to.
>
> Could you post your template file? There must be something else going on
> that I can't see.
>
>
> =============================================
>  Fred Lauzus, CAM Programming Coordinator
>  High Steel Structures, Incorporated
>  mailto:[EMAIL PROTECTED] http://www.highsteel.com
> =============================================
>
> -----Original Message-----
> From: Jon Baker [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 12, 2000 12:20 PM
> To: [EMAIL PROTECTED]
> Subject: [mfg-smartcam] Templates
>
>
> I am have a confusion on my .tmp logic.  This is an example of the
problem.
> At line 1, the file hasn't updated the #CYCLE value so it comes up as
value
> 0 each time.  BUT... when it then gets to line 2, it does pull up the
> correct #CYCLE value for the tool as stated in the.jof.  Then, on line 3,
it
> stays as the same value as line 2 since it is modal.  How do I force line
1
> to look at the .jof of the current tool and update its value prior to
being
> called out in the machine cycle
>
>
> line 1    #CYCLE
> line 2    #ABSI  #CYCLE  #RTNLVL  X#XPOS  Y#YPOS  Z#ZDPTH R#V5 F#V6
S#SPEED
> line 3    #CYCLE
>
> Thanks to all you guys that know so much more than me
> Jon
>
>

Attachment: Fadalnew.tmp
Description: Binary data

Reply via email to