All,

Once again, the value belonging to this group of SmartCAM users (and
Developer) makes itself known. While I may never need to use the SECNAME and
SECNUM values, it's amazing to me just how much knowledge is out there that
we all have access to.

A million thanks to Fred and Gregg for the information on SECNAME and SECNUM
and to all the rest of you who share your knowledge and secrets with this
group. You make our SmartCAM life just that  much easier.

And once again, I curse SDRC for killing off a wonderful product. I dread
the day when I have to switch to a new CAM system, because you all might not
be there to help with my problems.

Sincerely,

Dave Coupar

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Gregg Olson
Sent: Friday, August 25, 2000 4:28 PM
To: Lauzus, Frederick
Cc: Smartcam (E-mail)
Subject: Re: [mfg-smartcam] SECTION NUMBERS


Fred,

Here's a few missing pieces.  Plus more detail than you may care to know.

19=@FXDCAN  (**** legacy)
27=@SPEEDS (* lookup table)
35=@WAIT  (*** valid section)
39=@CYCLCHG (** #SECNUM not set to this)
57=@COOLANT (* lookup table)
58=@CYCLE (* lookup table)
59=@NURBS (*** valid section)

* lookup tables are handled through the var processing subsystem (not
section
processing which calls @CYCLCHG and assigns #SECNUM), therefore their access
through normal var processing doesn't cause @CYCLCHG to be called; you would
get
these values if you called the table manually (#CALL(COOLANT)) which would
invoke
the section processing and output the contents of the table to your code
file

** since one of the purposes of @CYCLCHG is to set #SECNUM it is excluded

*** the values for @WAIT and @NURBS should be assigned and testable in
@CYCLCHG

**** legacy no longer called by the system

--gregg

"Lauzus, Frederick" wrote:

> Attached is a zipped Word 97 document with my personal list of template
> words as well as their known values that I have accumulated over the
years.
> This includes the values for #SECNUM. You will notice there are some
> sections that do not appear to generate a section number, as well as some
> section numbers that appear to have no section assigned. I'm sharing my
list
> with you and the group with the hope that if someone finds any of these
> missing pieces that they will in turn share their discovery with us.
>
> =============================================
>  Fred Lauzus, CAM Programming Coordinator
>  High Steel Structures, Incorporated
>  mailto:[EMAIL PROTECTED] http://www.highsteel.com
> =============================================
>
> -----Original Message-----
> From: Joe Geraci [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 25, 2000 8:59 AM
> To: Smartcam (E-mail)
> Subject: [mfg-smartcam] SECTION NUMBERS
>
> Hello Everyone,
>
> Does anyone have a list of section numbers (#secname) with their
> corresponding section names (#secname) ?
>
> Thanks,
>
> J.G.
>
> ======================================================================
> To find out more about this mailing list including how to unsubscribe,
> send the message "info mfg-smartcam" to [EMAIL PROTECTED]
> ======================================================================
>
>   ------------------------------------------------------------------------
>                       Name: List.zip
>    List.zip           Type: Zip Compressed Data
(application/x-zip-compressed)
>                   Encoding: base64
>            Download Status: Not downloaded with message

--

Gregg Olson
Development Manager
SDRC CAM Products


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

======================================================================
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