Aced SNF
Aced SNF
Aced SNF
(ACE_SNF.MA)
(Versions - FWP 3.1.x.x/3.2.x.x rel 2.0.4 & FWP 7.0.x.x rel 7.0.4 & FWP 7.1/7.2/7.3 rel 6.0.4 & FWP 8.0.x.x rel 8.0.4 & FWP 9.0.x.x rel 9.0.4 &
FWP 10.0.x.x rel 10.0.4 & FWP 11.0.x.x rel 11.0.4 & FWP 12.0.x.x rel 12.0.4)
The steel detailing neutral file (SDNF) import application can be utilized to read SNDF files (version 2). SDNF files
created by FrameWorks or any other application that writes the SDNF (version 2) format can be imported. A copy of
the SDNF (version 2) specification and a sample SDNF file, ACE.SNF, is included toward the end of this document.
The SDNF (version 2) format supports linear & arc members (tapered or non-tapered) and plate elements, which are
placed as solids. This application does not support the version 3 SDNF format (FWP 7.1.x.x & FWP 7.2.x.x) as
Intergraph provides software to read version 3
SDNF. If a SDNF version 3 file is encountered,
a message is displayed.
The following information is carried for each
linear member: section size, type, class, status,
name, end points, end offsets, cross section
offsets, cutbacks, grade, orientation vector,
rotation, reflect & mirror status and cardinal
point. The following information is carried for
each arc member: section size, type, class,
status, name, end points, center point, start
angle, sweep angle, normal vector, end offsets,
cross section offsets, cutbacks, grade,
Steel Detailing Neutral File Import - Dialog Box
orientation vector, rotation, reflect & mirror
status and cardinal point. The following information is carried for each plate: name, class, grade, thickness, and
shape vertices.
This application provides several features and options to enhance handling of SDNF files. The most significant
feature is the missing section and section substitution capabilities. If any
sections are not found when a SDNF file is processed, the option is given to
write an ASCII file (shown left) that will contain the names of the missing
sections. This missing sections file (named anything.MIS) can be easily
converted into a section substitution file (named anything.SEC). The
application has the ability to substitute for missing members, substitute all
members or substitute no members. Thus when translating from a CAD
system to FrameWorks and different section naming conventions are utilized the .MIS and .SEC files can be
effectively utilized to properly place all members. To do this first run the verify command and produce a .MIS file.
Next edit the .MIS file and create a .SEC file (.MIS and .SEC file details are discussed later in this document).
Finally run the import and select substitute missing members.
The last feature involves naming of linear members & plates. Three naming options are available. First the linear
member & plate name specified in the SDNF file may be utilized (default option). However two additional naming
options exist. In the second option, new names can be generated at placement time. Under this option, all
components for a given member type (member or plate) are given the a name by
concatenating a sequence number to a prefix (i.e. mem or pla). Finally, FrameWorks
normal naming for individual components (autoname) may be specified.
Naming Option Button
When the verify mode is invoked, the verify dialog box shown below left will appear.
If the file is processed the import information dialog box shown above right will appear.
The SDNF import application can be extremely useful in converting structural models from one modeling
system to another. Models from any 3D modeling system that writes SDNF format files can be translated to
FrameWorks. The process is simple, first using the original CAD application write a SDNF file and then
utilizing this application import the SDNF file into a FrameWorks model. The subsequent FrameWorks models
can be used for interference checking, design review or drawing generation.
LOG FILES
All applications can write log files if the environment variable ACE_DUMP is set to 1. There have been reports that
some sites lock the C root drive and under certain conditions a locked C drive can cause a system fault 5.
This application will produce a log file (default c:\ace_snf.log )which will contain: Packet 00 information,
information on linear members placed, information on plate elements placed, error information and summary
placement information. This particular application will ALWAYS WRITE to a log file. This application WILL
FAIL with a locked C drive. The environment variable ACE_LOG_PATH must be utilized for this application if the
C drive is locked.
All applications have been modified to warn of a locked drive/file and then gracefully exit. All applications now look
for the environment variable ACE_LOG_PATH. If it is found, that is the directory where the log files will be placed.
If the directory is locked or non-existent or if file is locked a warning will be given and the C drive will be tried. If it
is locked or the file is locked a warning will be given and application will gracefully exit.
Usage of the variable ACE_LOG_PATH to control log file locations is similar to ACE_DEF_PATH to control DEF files.
However there is one very important difference: ACE_LOG_PATH should NEVER point to a network drive (this is
highly recommended for ACE_DEF_PATH). Everyone writes to the same named log file and if they are on a network
drive there will be bad consequences. ALWAYS point ACE_LOG_PATH to a local drive (perhaps a temp off C root).
ACESEA 1998-2013
SDNF Files
The SDNF Import application will by default look for *.SNF files in the c:\ directory. A lookup dialog box is
utilized to located section substitution files. Note that SDNF files have a .SNF extension. The initial search
directory for the SDNF file (.SNF file) can be specified with the following environment variable:
ACE_SDNF_FILE (such as: ACE_SDNF_FILE=f:/sdnf_files/). The following section provides the
specification for version 2 SDNF files.
ACESEA 1998-2013
Format Specifiers:
FP
I
Cnn -
fixed -
With the exception of the fixed format records, the data may start in any column of the record. An example record follows each record
format description, and is shown in italics.
Comment Cards:
Comment cards may be inserted anywhere in the input file, provided that the record begin with the "#" character in the first field.
Format:
#comment
This is a comment record
ACESEA 1998-2013
Record 7:
Revision Number, Issue Code
Format:
I; C64
18 "Issue Code"
Record 8:
Design Code
Format:
C80
"Design Code Name"
Record 9:
Format:
2
Record 10 on:
'n' Load Combination record, where 'n' is from Record 9
Loading #, Loading type (0=load case, 1= load combination ), Description
Format:
I; I; C64
1 1 "Live and Wind loads"
ACESEA 1998-2013
Packet Header
fixed
Record 2:
Format:
"feet"
Record 3 on:
Each linear member is represented by 6 records which follow:
(total of 6*n records, where 'n' is number of members from Record 2 above)
Linear Member Record 1:
Member ID, Cardinal Point, Status, Class, Type, Piece Mark,
Revision Number
Format:
I; I; I; I; C24; C24; I
00100040 8 0 1 "Beam" "B_101_FL1" 14
Linear Member Record 2:
Section Size, Grade, Rotation, Mirror X axis, Mirror Y axis
Format:
C32; C24: FP, I, I
W12x50"
"A36" 90.0 0 0
Linear Member Record 3:
Orientation Vector; Start, End Coordinates; Start, End Cutbacks
Format:
3 FP; 3 FP; 3 FP; 2 FP
0 0 1.0 10 0 72.75 10 12.5 72.75 0 0
Linear Member Record 4:
X, Y Cross-section offsets
Format:
2FP
0 -.25
Linear Member Record 5:
X, Y, Z Offsets Start; X, Y, Z Offsets End
Format:
6 FP
0 0 0 0 0 -1.0
Linear member Record 6:
Releases - End 1 Tx, Ty, Tz, Rx, Ry, Rz; End 2 Tx, Ty, Tz, Rx, Ry, Rz
Format:
12 I
000011 000011
ACESEA 1998-2013
Packet Header
fixed
Record 2:
Format:
"feet"
Record 3 on:
Each plate is represented by a variable number of records which follow:
Plate Record 1:
Plate ID, Connect Point, Status, Class, Type
Format:
I; I; I; I; C24
02600005 1 0 1 "slab"
Note: Connect point refers to plate position relative to the plane defined by plate
coordinates.
Connect point:
0 = by center
1 = positive face
-1 = negative face
Plate Record 2:
Piece Mark, Grade, thickness, number of vertices
Format:
C24; C24; FP; I
"Plate GP_78" "A36" 1.125 6
The plate geometry is represented on 'n' records, where 'n' is the number of vertices from Plate
Record 2 above. Each record contains the X, Y, Z coordinates of a vertex.
Plate Geometry Record: X, Y, Z coordinates
Format:
3FP
22.763 8.475 10
ACESEA 1998-2013
Packet Header
fixed
Record 2:
Format:
"feet"
Record 3 on:
Each member loading is represented by a variable number of records which follow:
Member Loading Record 1:
Member ID, Number or loadings (for this member)
Format:
I; I
00100040
3
The loads for each member are represented on '3*n' records which follow, where 'n' is the number
of loadings from Member Loading Record 1 above.
Load Record 1: Loading number, Description
Format:
I; C64
1 "Equipment loads"
Load Record 2: Member Forces - Start (end 1)
Format:
6 FP (Axial Force, Shear Y, Shear Z, Moment Y, Moment Z, Torsion)
-3.762 14.8 4.1 .03 -77.23 3.17
Load Record 3:
Member Forces - End (end 2)
Format:
6FP (Axial Force, Shear Y, Shear Z, Moment Y, Moment Z, Torsion)
-3.762 11.3 -8.334 5.4 -14.7 8.64
Note: Member ends are defined by the order of coordinates in Packet 10.
ACESEA 1998-2013
Packet Header
fixed
Record 2:
Format:
628
Record 3 on:
Each connection detail is represented by a record as follows:
Connection Record: Detail Number, Member number, Member End #
(1 = Start, 2 = End), Connection Detail
Format:
I; I; I; C50
177 14 1
"End 1 detail information"
ACESEA 1998-2013
10
ACESEA 1998-2013
11
ACESEA 1998-2013
12