Fred,
 I would like to take a minute to thank you for giving us so much valuable
information. I have learned much from your posts as well as the many others who
post messages in here.
Thanks Fred and All,
Michael

"Lauzus, Frederick" wrote:

> To access the active step number in the template file you need to use the
> jos data tags (found in the customization guide). The data tags can be used
> to access information but cannot output information on their own. To output
> the values you need to assign them to a template variable. Here are 2
> examples of how to do this.
>
> This first example creates a custom user defined variable #step in the
> @DECLARE section of the template file (you may need to add this section).
> The value of this variable is then defined in the template sections where
> the desired value (step numbers) may change. For the step numbers this would
> be in the @START, @TOOLCHG and @STEPCHG if used. The variable can then be
> used to output information in the same manner as any system variable.
>
> @DECLARE
> #INT #step
>
> @START
> #EVAL(#step=jos(step_num))
> N#step
> -  or -
> #OFFBLKN#step
> #ONBLK
>
> @TOOLCHG
> #EVAL(#step=jos(step_num))
> N#step
> -  or -
> #OFFBLKN#step
> #ONBLK
>
> @STEPCHG
> #EVAL(#step=jos(step_num))
> N#step
> -  or -
> #OFFBLKN#step
> #ONBLK
>
> This second example is more specific to your question. Instead of creating a
> custom user defined variable, it changes the value of the system variable
> that contains the current block number #BLK. The value of this variable is
> then re-defined in the template sections where the desired value (step
> numbers) may change. Again this would be the @START, @TOOLCHG and @STEPCHG
> sections. The next block number output would then reflect the change. In
> this case, the #EVAL statement would have to be placed in the line
> immediately before the desired block number change.
>
> @START
> %
> #ONBLK G40 G17 G80
>  G91 G28 Z0
> #EVAL(#BLK=jos(step_num))
>  T#TOOL M6(#TDESC)
>  G90 X#XPOS Y#YPOS M08
>  G43 Z#ZPOS H#LOFF
>
> @TOOLCHG
>  G40 G80 MO9
>  G91 G28 Z0
> #EVAL(#BLK=jos(step_num))
>  T#TOOL M6(#TDESC)
>  G90 X#XPOS Y#YPOS M08
>  G43 Z#ZPOS H#LOFF
>
> @STEPCHG
> #EVAL(#BLK=jos(step_num))
> =============================================
>  Fred Lauzus, CAM Programming Coordinator
>  High Steel Structures, Incorporated
>   mailto:[EMAIL PROTECTED]  http://www.highsteel.com
> =============================================
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 15, 2000 5:24 PM
> To: Smartcam Tech
> Subject: [mfg-smartcam] Step number in TMP file
>
> Hello,
>
> Is there any way to access the step number with the tmp file? I would like
> my "N" numbers in my nc code to
> reflect the step number in the job plan.
>
>
>
> Tom Cox
> [EMAIL PROTECTED]
>
> ======================================================================
> To find out more about this mailing list including how to unsubscribe,
> send the message "info mfg-smartcam" to [EMAIL PROTECTED]
> ======================================================================

--
 Visit us at http://www.microsystemsgeorgia.com/toc.htm
  Smartcam Support Repository and Rhino Modeling for CNC Milling


======================================================================
To find out more about this mailing list including how to unsubscribe,
send the message "info mfg-smartcam" to [EMAIL PROTECTED]
======================================================================

Reply via email to