Export SDNF

Export to SDNF Page 1 of 19
Structural Design User Guide
SDNF Export/Import : Export to SDNF
Export to SDNF
Exports a steel structure to a SDNF file.
Target Information
Click Target Information to display the Export Target Information window which contains information about
the 3D steel detailing package to which the SDNF file is being transferred.
https://help.aveva.com/AVEVA_Everything3D/2.1.0.22/SDUVPDMS/OSUG3.11.02.... 16/12/2019
The interface requires at least two external mapping tables for each Target Package in order to check that the
Target Package can accept the data. It also may use the Profile Orientation and/or the Unicode mapping
tables if necessary. The mapping tables are for the Profiles, Materials and for mapping the Profile Orientations
between AVEVA E3D™ and the neutral file. The Unicode mapping table is to translate AVEVA E3D™
Unicode strings into ASCII strings. The file arrangement on the system and required format is explained.
Refer to Customise SDNF for further information. The interface also needs to know where the external
mapping files are located on the computer network. For this, internal mapping tables are required. The
configuration and location of files is explained. Refer to Internal Mapping Files for further information.
For example you may have a generic set of mapping tables to map between AVEVA E3D™ and SDNF for a
particular steel fabricator, or you may have a similar set for each 3D steel detailing package.
The current file settings are indicated on the Export Target Information window. Changing the Target
Package by using the Target Package drop-down list on the right-hand side of the window may cause the text
to change giving the full path names of the respective files. Do not be concerned that the path name may be
truncated by the insertion of the ellipsis (…): it is modified only for display purposes on the window.
The system also checks that these files are compatible with the Target Package by checking only the
identification line at the top of each mapping table. The format of the mapping files is detailed. Refer to
External Mapping Files for further information.
The two main options are, Auto and Manual which are activated by selecting the appropriate option button.
Auto causes the interface to select automatically the mapping tables for the Target Package indicated by the
Target Package drop-down list on the right hand side of the window, according to the system configuration
files. The files selected are dependent upon how you have configured the internal mapping files.
Manual activates other option buttons, which are greyed out for the Auto option. Selecting this option
changes the display of the window. For example:
You can select the file type using the Profiles, Materials, Orient'n or Unicode radio buttons and input the full
path name of the file in the data entry area. You can also include system environment variables in the path
name as long as they are in the proper AVEVA E3D™ format, for example, %ENVVAR% being the AVEVA
E3D™ representation of the ENVVAR environment variable.
Press Enter, the interface checks for the existence of the file and compatibility with the Target Package
indicated by the Package drop-down list.
Note: The check is only that the file applies to the Target Package and not that it is a correct file type or
format.
You can choose by hand which mapping file to use either by inputting its name in the text data entry field, or
by using the Browse option to display a File Browser. You can use this browser to search for the relevant
mapping file.
Once you have input all the correct data on the Export Target Information window, click OK and the
interface variables are updated. Click Cancel to close the window, leaving the original interface variables
unchanged.
Error and Log File Messages
Internal error Internal lists are not in step.
Cannot find suitable Internal mapping files not found.

internal mapping list
Suitable Mapping Table File Mapping table found is not for the correct Target
not found Package, or it does not exist.
Not a suitable Mapping Incorrect format of file, or empty file, or wrong Target
Table File Package.
Bad Map File Mapping file is not correct format. Possibly it is from
another operating system.
Error on SDNF File You have input incorrect data on the file browser.
Browser form
Export/Import different SDNF Format

The interface can read SDNF files to both version 2 and version 3 of the format (but it will write to only version
3). The format is described elsewhere. Principally in version three files, there are many more records attached
to each linear member and the method of plate definition has changed. The interface does use some of this
new information, principally the date and times of creation and modification.
Export Information
Click Export Information to display the Export Information window which contains information about the
export process.
You can either type the full path name of the output file, or click Browse to display a File Browser. The
interface checks that the file exists and if it does, you are asked whether to overwrite it. If the file does exist
and you want to overwrite it, the file mode beside Browse changes from WRITE to OVERWRITE. The output
file is rechecked for write/overwrite status during the actual Export process because you can perform Exports
repeatedly without changing the output file name.
Note: If you do not input the full path name and just a plain file name, the output file is created in the folder
which started AVEVA E3D™. You can also include system environment variables in the path name as
long as they are in the correct AVEVA E3D™ format, for example, %ENVVAR% being the AVEVA
E3D™ representation of the ENVVAR environment variable.
The SDNF file may have several sections: a header, Packet 00; a set of Linear Members, Packet 10; a set of
Plates, Packet 20 and their holes (Packet 22); a set of Connection Details, Packet 40, and a set of Arc
Members (Packet 60). The header is compulsory: any other Packets are optional.
Selecting the information to be contained in Packet 00 is performed by navigating to, or below, the relevant
AVEVA E3D™ SITE, ZONE or STRU element which contains the required header information. Open the
Members list window on the main Export window. When at, or below, the correct element, click Use CE on
this window, the source text indicates from where the interface gets the information. If there is not enough
space on the window the element's reference number is output rather than its name.
To view the information contained by the chosen header element, click Inspect to display the Export File
Header Details window.
At first the entry fields are greyed out but you can read the contents. To modify the contents of the fields click
Edit on the Export File Header Details window and the fields become active and allow you to input any
revised data. Click Apply and the data is transferred back to the chosen header object, overwriting the
original data. Click Cancel to leave all the data unchanged.
The Previous Revision and Transfer information, if changed, is transferred not to the header object but to the
Configuration Site for the specific current MDB/user combination. During Export or Import AVEVA SDNF
inspects all the available Configuration Sites in order to elucidate the most recent Transfer letter and Revision
number. The information is then stored in the site for the current user and allows for multi-user access to the
databases.
Using the toggles on the Export Information window, you can select whether to export Packet 10 (Straight),
Packet 60 (Curved) or Packet 20 (Plates) with the option of their holes, Packet 22 (Holes). You cannot
output Packet 40 (End Connections) without outputting either Packet 10 (Straight) or Packet 60 (Curved). If
you want neither Packet 10 nor Packet 60, the sub-options, Members only and Members + End
Connections are inactivated and greyed out. Similarly, one cannot output Packet 22 (Holes) without
outputting Packet 20 (Plates). You are able to export Plates without their holes.
The interface checks that you are attempting to Export something and outputs a message accordingly.
Once all the correct data has been input on the Export Information window, click OK and the interface
variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Export file already exists File exists, you receive the option to overwrite it.
Wrong place in database You are most likely at the WORLD element in the
database.
Illegal Transfer letter You can only use transfer letters between A and Z.
Nothing to export You have deselected both the Linear Members and
Plates options.
Cannot decrement Transfer You cannot decrease the Transfer letter, only
letter increment it.
Run Information
Click Run Information to display the Export window which allows you to view the Log File after the export
process is complete and select the Log File? check box.
Click either the Brief or Verbose radio buttons to choose which format messages are displayed.
The Test Run? option allows you to suppress the updating of all the Export flags, allowing you to check if
Export of the model will be successful. You may find that the Profile or Material mapping files are not quite up
to date which might cause a failure in the Export process. Therefore, you can select this option to define this
as a test run.
After the Export process has completed, Test Run? is reset to false. You are then forced to state categorically
each time the model is Exported that the run is a trial.
Once all the correct data has been input on the Run Information window, click OK and the interface variables
are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Members and Export List

The Members part allows you to navigate around the database hierarchy.
Though AVEVA E3D™ will create only GENSEC elements, old models might still contain SCTNs as well. The
interface will still find SCTNs and export them. If a model is being imported and there are pre-existing SCTNs,
these will be preserved, but all new members will be created as GENSECs.
You must input the elements to be exported, but need not select only SCTNs, GENSECs or PANEs. The
interface locates all SCTNs, GENSECs and PANEs contained in, or implied by, the Export list. If you add
something to the Export list and the item display in the 3D view it is highlighted and its colour changes. The
Export list is managed such that duplicate elements are removed and that items are exported only once.
Note: Partial model transfers are supported by the interface, however, you must be aware of how the Import
process handles partial model transfers. Refer to Comparison and Merge Processes for further
information.
There are several methods of adding elements to the Export list.
Add CE adds the current element to the list and implies all items below the current element in the database
hierarchy. The WORL can not be added to the list.
The Add by Pick option allows you to select an item from the 3Dview. It is similar to other pick functions.
Selecting this option brings up a Status window and puts you into a mode where an item from the 3D view
can be picked. You can also pick a sequence of items in succession to add to the Export list. Press the ESC
key when complete. If you do not want to continue, press the ESC key.
Add Structure attempts to climb to the Structure owning the current element and add that to the Export list. A
warning message displays if there isn't an owning Structure.
There is also a set of methods by which you can remove items from the Export list. These options work only
on entries in the Export list, rather than in the model. As with adding to the Export list, when items are
removed from the Export list, the highlight is removed from the item or items and they are returned to the
default colours as defined by this interface.
Note: The colour may be different from the colour in which it may have originally been added to the Drawlist.
Remove CE looks for the name of the current element in the list and removes it if present.
Remove by Pick allows you to select something from the 3D view and, if it is present in the Export list, the
name is removed. As with the Add by Pick option, you can select a series of items to remove from the Export
list until the ESC key is pressed.
Remove Selected is a means by which the item selected in the Export list is subsequently removed. Select
the item first in the list, then click Remove Selected.
Clear just removes everything from the list.
You may find that items that display in the Export list do not exist, or have been renamed. The Export process
determines all the valid entries in the Export list and prepares the data accordingly. Clearing the list, or
removing individual items is performed as expected.
Can't export the WORLD You cannot export the WORLD
No owning Structure Cannot climb to Structure element from current

location in database.
Cancel closes the AVEVA SDNF Export window.

Export executes the Export process. As it proceeds you are kept informed of the progress by means of
messages at the bottom of the main Model window as well as by forms and prompts.
Control
The Control drop-down menu has four options; Re-initialise, Configure, Map Converter and Exit.
After changing any mapping files or any other variables:
Re-initialise reloads the files to save you having to rebuild the whole user interface from scratch.
Configure enables you to define run parameters, model parameters, display colours and environment
parameters. Refer to System Configuration for further information.
Map Converter starts the tool that helps you rebuild Profile mapping files. Refer to AVEVA ABSI/SDNF
Mapping File Converter for further information.
Exit command removes all forms and menus and global variables associated with the interface.
The General drop-down menu has one option, Highlight which displays the Highlighter window enabling
you to identify new, changed and deleted items in the model. The Highlighter window has more relevance to
the Import process and is described in detail. Refer to Highlight Changes in the Design for further information.
The Export Process

Exporting from AVEVA E3D™ all items are exported using millimetres as the distance units.
All reference data, such as any pre-existing reference model, is removed before exporting anything. Details
about saving the reference model are available. Refer to Import from SDNF for further information.
Prior to any Export process, all fields are checked for validity.
• Is the output file named?
• Is anything going to be exported?

• Are the mapping tables compatible with the Target Package?
• Is there a valid Steel Standard table?
In addition, there is an SDNF specific UDA, :SDNFEXCLUDE, attached to certain AVEVA E3D™ elements by
which you can define whether the item is to be exported or not. Setting this logical flag to true excludes the
item from the Export process. Refer to UDAs for further information.
Before continuing, the Export process polls all the Configuration objects for the high water mark on Transfer
and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest
Transfer value.
The list of all items listed in the Export list is then stored on Header element.
After verifying that all the data is correct and valid, the external program is called. The interface waits for a
certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised
by the external program you are notified and more detailed information is placed in the log file. If the waiting
period expires without the interface detecting that the external program has completed - it may have crashed,
or even not exist, you are asked if to carry on waiting for another time unit.
Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally
the system indicates its completion, whether successful or not. The completion message should be read in
conjunction with the log file, if any errors are indicated.
The message indicates a successful completion.
The error message indicates that a problem was encountered in the external program.
On completion of the external program, the status file is inspected and, if the result is favourable, you are then
asked whether or not to view the log file, if that option has been selected on the Run Information window.
To inspect the log file later, save it with the File > Save as option in the File Viewer window which opens a
File Browser, or click Save as to the suggested filename. Either way, if the file already exists, you are asked
whether to overwrite it. The log file window may then be closed, click Cancel.
If the Brief mode has been chosen on the Run Information window for displaying the log file, the window
displaying the log file filters out all warning messages, leaving only the error messages. Saving the log file,
however, all messages are retained in the file.
File does not exist Somehow there is no log file. Are there issues regarding
access rights to the%AVEVA_DESIGN_WORK%
folder?
Export Linear Members

A series of checks is made before a Linear Member is output.
• Is the SPRE set?
• Is it a zero length member?
• Does it have a valid material?
• Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
• Are the start and end points valid?
If any of the criteria is not satisfied, the linear member does not even get exported to the SDNF output file. As
has been indicated before, Linear Members can be transferred as either Straight in Packet 10 or Curved in
Packet 60. In SDNF, curved members are just circular arcs. However, GENSECs can be compound shapes
with both straight and arc sections. As a result, SCTNs and straight portions of GENSECs are transferred
through Packet 10, and the curved segments are transferred through Packet 60. Consult the section on
importing Linear Members for more information about the reconstruction of complex GENSECs.
Note: Subsequent import processes are affected if the member appears to have been deleted by the external
steel detailing package since its export. In fact, the linear member might never made the transfer to the
Target Package in the first place.
If the Linear Member is connected, the interface determines the offset of each end from its associated node.
Once the Linear Member has been output, the relevant UDAs specific for the interface associated with Export
are updated. These are the mark numbers, the export date and time and transfer and revision numbers.
The SDNF interface may not be able to update the export information on the elements, usually because the
database is read-only. If this is the case, a session related macro file is produced for execution immediately
afterwards, or when one has write access to the database. The file is called updateVersionNos<export
date/time>.mac and is stored in the AVEVA_DESIGN_WORK folder.
Illegal or unset SPRE - SPRE must be valid.

Not exported
Zero length Linear Length less than user definable tolerance.

Member - Not exported
No material Cannot determine material properties for member.

information - Not
exported
No material match for :SDNFMGRADE cannot be matched with a material in the

nnnn. - Unknown Properties database.
material
No material property :SDNFMGRADE cannot be matched with a material in the

match Properties database.
Inconsistent material The element's MATR and :SDNFMGRADE attributes are not
specification consistent.
Multiply defined Either a material to be mapped or a mapped profile appears

entries in more than once in the material file.
Material Table
No match for material The material is not in the material file
Syntax Error Other, less specific, errors.
Unrecognised Parse The error should not occur. If it does then it indicates a
State system error. Although the error is non-fatal it should be
reported. A number representing the parse state is also
output.
No match for Cardinal Pline or Cardinal Point not recognised. Neutral axis (Cardinal
Point nnnn Point 10) assumed.
No Cardinal Point JUSL unset.

nnnn
Bad Cardinal Point Cardinal Point/Pline identified is not valid. Does it exist?
nnnn Neutral axis (Cardinal Point 10) assumed.
Problem exporting Other errors found.

entity
Profile cannot be The profile is not in the profile mapping file.

mapped
Profile is not in the The profile is in the profile mapping file but is not in any one
standard of the set of standards.
Profile is not the The profile is in the profile mapping file and is in one of the
default set of standards, but not the default standard.
Multiply defined Either a profile to be mapped or a mapped profile appears

entries in more than once in the profile mapping file.
Profile Table
Export Plates
Panels in AVEVA E3D™ are to be transferred as Plates using Packet 20, inclusive of stiffeners, floor and
toe plates. Bent plates are also transferred if they are expressed as their component flat plates. If Bent Plates
are to be treated as Angle linear members then they should be modelled as such.
If the AVEVA E3D™ Penetration Application is used to generate Catalogue holes, the resultant holes,
kicker plates and stiffeners are not exported because they are contained in a Catalogue definition. Some
holes and negative primitives can be transferred from the model.
The Description attribute is used to store the flooring type, such as grating or chequer plate and is passed as
the type field (up to 24 characters).
The Material Grade transferred in Packet 20 represents the material type. It is a text attribute, rather than the
number field in AVEVA E3D™. Therefore a User Defined Attribute (UDA), :SDNFMGRADE, has been defined
within AVEVA E3D™ to store this information.
Note: Any edge preparation details and modelling, such as grinding, will be lost in the transfer operation.
A basic series of tests is performed before the Plate is exported.
• Is there any geometry?
• Is the height valid?
• Is it justified correctly?
• Does it have a valid material?
• Are there enough vertices?
If any of the criteria is not satisfied, the plate does not get exported in the SDNF output file.
Note: Subsequent import processes are affected if the plate appears to have been deleted by the external
steel detailing package since its export. In fact, the plate might never made the transfer to the Target
Package in the first place.
Once the Plate has been output, the relevant UDAs specific for the interface associated with Export are
updated. These are the mark numbers, the Export date and time and transfer and revision numbers.
Note: In Exporting a Plate, it has to be converted to the SDNF standard of being defined in a clockwise
direction relative to the plane normal. Thus Importing a Plate previously defined in Model, you may find
the order of vertices to have been reversed. Model is more tolerant about the ways in which you can
define a plate.
Although both plates and holes are supposed to have a clockwise definition (right hand screw rule) for their
boundaries in either AVEVA E3D™ or in the SDNF file, the interface must be able to cope with either
clockwise or anti clockwise directions. In exporting plates the vertex order is converted to satisfy the right-
hand screw rule.
Complex Plates (Type 1)

Plates with curved and straight segments to their boundaries can be transferred both to and from AVEVA
E3D™. Because of the difference between AVEVA E3D™ and SDNF boundary definitions, vertices stand a
high chance of being created in different places. Further, in order to recreate the shape, there may be a
different number of vertices in the boundary. It can become very difficult to compare the boundaries,
especially on import.
In order to assist the transfer of these complex shapes, the vertices are given a type code as a design
parameter. The code indicates whether the following boundary segment is straight, an arc, or whether the
vertex is a created one not contained in the SDNF file.
Complex Plates (Type 2 - Circular Ones)

Circular plates in AVEVA E3D™ are identified by the number of vertices, the geometry and possibly the vertex
type codes. There is no short-hand definition of a circular plate in AVEVA E3D™. As a result, a certain
amount of geometric testing is involved in identifying and exporting circular plates. The interface recognises
only 4 or 5 point circles, where the 5th point is a duplicate of the first point.
No geometry No PLOO element. Plate cannot be exported.

information - Not
exported
Plate too thin - Thickness less than user defined minimum. Plate not exported.
Not exported
Not enough vertices Fewer than 3 vertices. Cannot define valid geometry so Plate is
- not exported.
Not exported
No material Cannot determine material properties for member. A matching

information - Not set of :SDNFMGRADE and Matref cannot be determined.
exported
No material match Unknown material. :SDNFMGRADE cannot be matched with a

for nnnn material in the Properties database.
No material property Unknown material. :SDNFMGRADE cannot be matched with a

match material in the Properties database.
Inconsistent The element's MATR and :SDNFMGRADE attributes are not

material consistent.
specification
Multiply defined Either a material to be mapped or a mapped profile appears

entries in more than once in the material mapping file.
Material Table
No match for The material is not in the material mapping file.

material
Syntax Error Other, less specific, errors.
Unrecognised Parse The error should not occur. If it does then it indicates a system
State error. Although the error is non-fatal it should be reported. A
number representing the parse state is also output.

entity
Transfer of Holes
There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements
can be handled as well as NBOX and NCYL under certain conditions. PLOOs are full depth penetrations:
partial penetrations can be modelled using NXTR elements. Circular boundaries of holes and indentations can
be imported and exported if recognised as such, by having 4 unique fillet vertices.
On import, vertices in boundaries are given a DESP value.
PVTLastPoint 0
PVTStraight 1
PVTArc 2
PVTFillet 3
PVTCircle 4
Using these values, specific shapes can be detected, For example circles or ellipses.
A message is output when the export process ignores most non loop-based negative primitives. It is difficult to
determine the geometric intersection with the PANEL, especially if the primitive axis is not perpendicular to the
plate plane. In the future it may be possible to handle some of them, but still only within tight geometrical
constraints. Negative boxes and cylinders can be transferred only if a principal axis is parallel to the plate's
normal. The cylinder's Z-axis, and any of the box's X, Y or Z-axis must be parallel to the plate normal. We
even have to limit NXTR elements those with an extrusion vector parallel to the panel plane normal. Some
negatives are not exported at all:
(NBOX) NPOLYH (NCYL) NSLC NSNO
NDIS NCON NPYR NCTO NRTO
(NXTR) NREV
Imported holes are either NXTR or PLOO elements. A full penetration is a PLOO, and a partial penetration is
an NXTR.
Any other negatives are not compared or merged on import. Other pre-existing negatives are moved and
updated to maintain the original position and orientation.
Exporting Connections
End connections and base plates are modelled in Design Catalogue items and transferred to the SDNF file
using end coding information stored in the CTYA attribute of the Catalogue component. A mapping table is
required to enable the information to be transferred in order that a corresponding entity can be created in the
external 3D steel detailing package. Once the end has been detailed, the resultant geometry may be returned
to Model as Plate members in Packet 20 for graphical and clash checks. In AVEVA E3D™ Joint selection is
controlled by specification.
As it exports Connections (PJOI and SJOI elements), the interface uses only the old connectivity model. New
connectivity elements, such as FIXIngs are not handled. The system initially checks that the SPRE attribute is
set.
If so, the CTYA of the relevant Catalogue component is checked against the Connection mapping table. If it is
valid, the local CTYS or CTYE attribute of the attached member is set for the sake of consistency. As it is
doing so, the interface also checks that the connectivity references are consistent. The CTYA attribute is then
matched against the required text for output in the SDNF file.
The interface also determines the identifier and end of the Linear Member to which the joint is attached.
Illegal or unset SPRE SPRE must be valid.
No Connection Type - Cannot determine CTYA attribute. Joint cannot be exported.

Not exported
Inconsistent Connectivity not consistent, so the joint cannot be exported.

connectivity - Not There is probably something more fundamentally wrong with
exported the model.

entity
Testing AVEVA SDNF Export

A test can be performed after installing the AVEVA SDNF product to make sure that the installation is
complete and correct. All the required testing material can be found below the sub-folder
SDNF\test\results\export in the user data folder.
The test creates an SDNF model file output.
Initial Configuration
Enter Model. You must have write access to the database, even though you are testing the Export process.
The interface records the date and time of export as well as the revision numbers of the elements transferred.
Set the test project variables:
Project: APS
User Name/Password: SYSTEM/XXXXXX
MDB: /SDNF
Choose the SITE to export to SDNF by selecting SITE /TEST-SDNF-INTERFACE from the hierarchy list and
drag it into the 3D display window.
When that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further
information.
If required, modify the 3D view. Refer to Views for further information.
Prepare for Export

The Export window allows you to export a steel structure to a SDNF file.
You may be asked to install a Configuration details element. If so, accept the request.
On this window and associated windows, fill in the details prior to Export.
Note: The configuration details should be available to the SDNF interface user always in read/write mode.
This is because the export and import processes store information about how many transfers there
have been made by the interface, and in which direction.
Target Information
Click Target information on the Export window to display the Export Target Information window.
Select the Auto option button and select AVEVA from the list of Target Packages on the Target Package
drop-down list on the right hand side of the window. The system automatically detects the Target Package's
Profile mapping table and Material mapping table.
Select the profile mapping file for the old catalogue named Aveva_E3D1.1.map. located in the
Blockmaps\Aveva folder.
When the details are correct click OK.
Export Information
Click Export information on the Export window to display the Export Information window.
In the output file name field, input SDNF-Test.sdn
Check that the SDNF file header (Packet 00) is coming from /SDNF-CONFIG-DEMO-SYSTEM. Use the
navigator and browser if necessary.
Select which SDNF Packets to export: Packet 10 (Straight), Members + End Connections and Packet 20
(Plates).
Run Information
Click Run information on the Export window to display the Export Run Information window.
Select the Log File? check box and choose Verbose for the message mode.
Do not select the Test Run? check box as this is not a test run.
The Main Export

To add the SITE to be exported to SDNF, Select SITE /TEST-SDNF-INTERFACE in the Members list. Click
Add CE, all the members in the 3D view change colour to indicate they are being exported.
The Export window look similar to this.
Create Export File

On the AVEVA SDNF - Export window, click Export.
The status line displays the progress of the task.
When the process is complete, you are asked whether to inspect the log file. You can then save it with the
File > Save as option on the SDNF File Viewer window to display a File Browser, or click Save as to the
suggested filename. The log file window can then be closed, click Cancel.
Check the SDNF Output Files
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.

Export SDNF

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Export SDNF

Încărcat de

Drepturi de autor:

Formate disponibile

Export to SDNF Page 1 of 19

Structural Design User Guide

SDNF Export/Import : Export to SDNF

Error and Log File Messages

Internal error Internal lists are not in step.

Cannot find suitable Internal mapping files not found.

Export/Import different SDNF Format

Error and Log File Messages

Members and Export List

Error and Log File Messages

Can't export the WORLD You cannot export the WORLD

No owning Structure Cannot climb to Structure element from current

Cancel closes the AVEVA SDNF Export window.

The Export Process

• Is anything going to be exported?

The message indicates a successful completion.

Error and Log File Messages

Export Linear Members

Error and Log File Messages

Illegal or unset SPRE - SPRE must be valid.

Zero length Linear Length less than user definable tolerance.

No material Cannot determine material properties for member.

No material match for :SDNFMGRADE cannot be matched with a material in the

No material property :SDNFMGRADE cannot be matched with a material in the

Multiply defined Either a material to be mapped or a mapped profile appears

No match for material The material is not in the material file

Syntax Error Other, less specific, errors.

No Cardinal Point JUSL unset.

nnnn Neutral axis (Cardinal Point 10) assumed.

Problem exporting Other errors found.

Profile cannot be The profile is not in the profile mapping file.

Multiply defined Either a profile to be mapped or a mapped profile appears

Complex Plates (Type 1)

Complex Plates (Type 2 - Circular Ones)

Error and Log File Messages

No geometry No PLOO element. Plate cannot be exported.

No material Cannot determine material properties for member. A matching

No material match Unknown material. :SDNFMGRADE cannot be matched with a

No material property Unknown material. :SDNFMGRADE cannot be matched with a

Inconsistent The element's MATR and :SDNFMGRADE attributes are not

Multiply defined Either a material to be mapped or a mapped profile appears

No match for The material is not in the material mapping file.

Syntax Error Other, less specific, errors.

Problem exporting Other errors found.

(NBOX) NPOLYH (NCYL) NSLC NSNO

NDIS NCON NPYR NCTO NRTO

Error and Log File Messages

Illegal or unset SPRE SPRE must be valid.

No Connection Type - Cannot determine CTYA attribute. Joint cannot be exported.

Inconsistent Connectivity not consistent, so the joint cannot be exported.

Problem exporting Other errors found.

Testing AVEVA SDNF Export

Prepare for Export

The Main Export

Create Export File

Check the SDNF Output Files

S-ar putea să vă placă și