Oasys PRIMER Update

Transcription

Oasys PRIMER Update

PRIMER 11.0
Back to Contents
Slide 1
Contents
• LS-DYNA support
• Hardware support
• Viewing model data
–
–
–
–
–
–
–
–
–
–
–
–
• Ergonomics
• Model checking
Faster graphics
Loadcurve interactive edit
Loadcurve compare and edit
Material stress/strain visualisation
Loadcurve “import from CSV”
*BOUNDARY_PRESCRIBED
_MOTION animate
Graticule
Suspend TRANSFORM’s
Storage of blanking/properties
*SET Only
BOUNDARY_SPC/beam end
release display
*DATABASE_CROSS_SECTION
properties
–
–
–
–
Selective model checking
User defined checks
*RIGIDWALL nodes
Other new checks of note
• Contacts
– Penetration checking
– Crossed edge fixing
– Effect of SHLEDG
– Listing penetrations
– *CONTACT Only visible
– Updating existing models
– Part replace
– Assembly replace
– *DATABASE_CROSS_SECTION
transfer
Back to Contents
Slide 2
Contents
• Mechanisms
• Connections
– Automatic creation
– Stretching
–
–
–
–
–
–
–
–
• Mesh modification
–
–
–
–
“Cobweb” mesh
Split solids
Aligning element local axes
Orienting in local coordinate
systems
– Detach solids and beams
– Extrude thick shells
Tied contact creation
Connection filtering
Different PIDs per layer
Reverse orientation
Spotweld line connections
Generic bolts
“Discrete Beam” bolts
Rigid spider creation
• Reading, writing and translating
• Seatbelt fitting
– Automatic creation of
*DATABASE_CROSS_SECTION’s
– Belt path rotation at buckle
–
–
–
–
–
–
Back to Contents
Include file de-clash
Linux file selector
NASTRAN support
Encrypted dummy models
Model build log file
Label de-clash upon keyout
Slide 3
Contents
•
•
•
•
Output of D3PLOT file
PRIMER support for *CASE
Pedestrian protection
JavaScript & automation
– Debugger
– Pop-ups
– Speed improvements
• Included scripts
– FMVSS201 mark-up
– Crash test setup
• Miscellaneous
– *DEFORMABLE_TO_RIGID
creation
– *DEFORMABLE_TO_RIGID “Only”
– Material properties edit panel –
retain during type change
– NRB spider creation
– Geometry operations
– *AIRBAG_REFERENCE_
GEOMETRY edit panel
– Create a sub-model from parts
– New preferences of note
Back to Contents
Slide 4
LS-DYNA support
• Keywords: LS-DYNA 971 R6.0 and R6.1 are fully
supported
– *CASE is included – see slides later in this
presentation
– Exception: *EF is not supported
• LS-DYNA R7.0 is fully supported except for “Keyword
Manual Volume 3” (CFD, electro-magnetic solvers,
etc)
Back to Contents

R6.1 Vol 1 Keywords

R6.1 Vol 2 Materials

R7 Vol 1 Keywords

R7 Vol 2 Materials
X
R7 Vol 3 New solvers
Slide 5
Hardware support
• Hardware platforms supported for version 11.0:
– Win32, Win64 (XP, Vista, Win7)
– Linux 32 and 64bit
– Note: UNIX platforms no longer supported
Back to Contents
Slide 6
Viewing model data
Back to Contents
Slide 7
Faster graphics
• Graphics speed can be several times faster (e.g. for dynamic rotation,
zooming, etc) especially for large models, compared to PRIMER Version 10
Back to Contents
Slide 8
*DEFINE_CURVE Create/Modify
Switch to white background for
graph window
Dynamic viewing, same as
PRIMER’s graphics window
+
Shift
+
Shift
Back to Contents
Slide 9
Edit points by dragging
Data updates automatically
Back to Contents
Slide 10
Delete/insert points by
clicking in graph window
Back to Contents
Slide 11
*DEFINE_CURVE Compare
• The Compare function allows viewing/editing of
multiple curves simultaneously
Points are listed for the
“current” curve (bold line
in the graph)
Back to Contents
Slide 12
Material Stress/Strain
• Stress/strain curve can be displayed and edited for multiple
materials on one graph
Points are listed for the
“current” material (bold
line in the graph)
Back to Contents
Slide 13
Material Stress/Strain
• The Stress/strain function is available for:
• Materials that use a loadcurve: e.g. MAT_024,
MAT_057, MAT_083, etc
• Materials defined by stress-strain points within the
*MAT cards: MAT_024 etc
• Bilinear elasto-plastic: e.g. MAT_003
• Power law: MAT_098 (can be viewed but not edited)
• Where a *DEFINE_TABLE is used, only the curve for the
lowest strain-rate is shown
Back to Contents
Slide 14
*DEFINE_CURVE import from CSV file
• *DEFINE_CURVE Create => Import can accept CSV files, and the user can now
specify no. of lines to skip, and
different columns for X and Y data
Back to Contents
Slide 15
Animation of BOUNDARY_PRESCRIBED_MOTION
• *BOUNDARY_PRESCRIBED_MOTION and
*BOUNDARY_PRESCRIBED_FINAL_GEOMETRY can be animated in PRIMER
• Used to check that the correct motion is applied
Back to Contents
Slide 16
Animation of BOUNDARY_PRESCRIBED_MOTION
• *BOUNDARY_PRESCRIBED_MOTION and
*BOUNDARY_PRESCRIBED_FINAL_GEOMETRY can be animated in PRIMER
• Used to check that the correct motion is applied
Back to Contents
Slide 17
Graticule/Grid: 2D
Graticule may be drawn with grid-lines at user-defined
spacing (e.g. 100mm)
Back to Contents
Slide 18
Graticule/Grid: 3D
3D graticule is available
Back to Contents
Slide 19
*INCLUDE_TRANSFORM - Suspend and Reinstate
*INCLUDE_TRANSFORM active for ODB
*INCLUDE (ODB) in untransformed position
A similar capability is available for *NODE_TRANSFORM
Back to Contents
Slide 20
Saving blanking and other properties
After blanking certain parts or elements, the blanking property status may be
saved. The same blanking can be recovered later. “Property” includes
blanking, colour, transparency, entity visibility status; optionally, it can also
include view
Save some blanking states, then toggle
between them using the arrows.
“SP” means “Save Properties”
Back to Contents
Slide 21
Saving blanking and other properties
Hover the mouse over this button, then click Options
A menu appears, giving control of which properties should be
recovered when the arrow button is pressed
By default, the viewing angle and zoom are not recovered.
Switch on recovery of view here
The current blanking, colours, etc can be written to a file *.prp
for use in future sessions of PRIMER. The same file is also
compatible with D3PLOT
Back to Contents
Slide 22
Set ONLY
Model is blanked. Contents of
selected sets are then unblanked
for easy visualisation
Back to Contents
Slide 23
*BOUNDARY_SPC display
Translational or rotational
restraints applied by either
*BOUNDARY_SPC or
MAT_RIGID can be plotted in
PRIMER 11. The colour
indicates the degrees of
freedom of the SPC.
Back to Contents
Slide 24
*BOUNDARY_SPC display
For *MAT_RIGID, a larger circle is
drawn at the Centre of Mass. This may
be hidden inside the part; we
recommend to draw in Line mode.
Back to Contents
Slide 25
Beam element end-release display
• *ELEMENT_BEAM end release information
(RT1, RT2, RR1, RR2) can be displayed in
PRIMER 11
• This can be turned on through the entities
panel
Back to Contents
Slide 26
Section properties for *DATABASE_CROSS_SECTION
•
In v10 section properties could be
calculated/displayed for PRIMER Cut Sections
•
Geometric, 1st yield, and plastic section properties
are now available for
*DATABASE_CROSS_SECTION cards
Back to Contents
Slide 27
Ergonomics
Back to Contents
Slide 28
Increased height
• Right-hand menu
area can be dragged
wider – e.g. to reveal
long part names in
object menus or in
the Part Tree
• This also allows the
Tools and Keywords
menu buttons to be
re-arranged, so
more height is
available for the
docked menus
Drag
Draggable menu area
Back to Contents
Slide 29
Ergonomics
• Floating menus can be dragged outside the main PRIMER window
• Useful with wide-screen or dual-screen monitors
Back to Contents
Slide 30
Ergonomics
• To do this with the Part Tree, undock it first
Drag
Back to Contents
Slide 31
Ergonomics
• Now the Part Tree
is always available
without obscuring
other menus
Back to Contents
Slide 32
Ergonomics
• Undockable object menus
• Object menus will now also
automatically expand if required
when the mouse moves into them
Back to Contents
Slide 33
Ergonomics
• Object menu filter by text-string now searches the numeric label as well as
the title
• Example: 2155* will find Parts 21550, 21551, 215561, etc
• Wild-card “?” represents a single character, for example 2?151 will find
20151, 21151 but not 212151
Back to Contents
Slide 34
Copy/Paste by Ctrl-C, Ctrl-V
• In PRIMER version 10, text copy/paste could be done only linux-style (drag
over to copy, middle-mouse button to paste)
• In PRIMER version 11, CTRL-C and CTRL-V are also available
CTRL-C
My text file
CTRL-V
The part in question is: BIW - suspension frame brkt 6 -RR
Back to Contents
Slide 35
Quick-pick polygonal selection
Blanking operation using polygon quick pick:
Click once to activate
polygon pick
Quick picking using
polygon in process
Picked entities are blanked
(current quick pick mode)
Back to Contents
Slide 36
3D Connexion 3D Mouse support
• Support has been added for use of a 3DConnexion 3D mouse in PRIMER
– Pull, pull, twist or tilt the 3D mouse cap to simultaneously pan, zoom and rotate
your model
Back to Contents
Slide 37
Model checking
Back to Contents
Slide 38
Selective error checking
In PRIMER 11, the user can select which Include Files should be checked. For example:
- Avoid reporting errors in standard dummy or barrier models
- When working on one particular Include File, it may be useful to check just that Include file.
- Save time compared with checking the whole model
Switching off the checking for
an Include File means “do
not check the entities in this
Include File”. Entities in other
Include files might still have
errors caused by entities in
the switched-off Include
Files, and these errors would
still be reported.
Back to Contents
Slide 39
Selective error checking
The user can also select which entity types (“categories”) should be checked. For example:
- Switch off checking of Connections and/or Contacts
- Save time compared with checking the whole model
The categories are not
hierarchical, e.g. switching off
checking for “Dummies” does
not switch off checking of all
the entities contained in the
dummy. It only switches off
checking of the dummy
definition (tree file).
Back to Contents
Slide 40
User defined checks (customised model checking)
Back to Contents
Slide 41
User defined checks (customised model checking)
User-defined checks are written in Javascript and kept in $OA_INSTALL (or User’s Home directory)
\PRIMER_library\scripts\checks
Each script must have a filename that matches the Javascript Class name for the entity type being
checked (e.g. Part.js applies to every Part being checked); checks that apply to the whole model must be
in a script named custom.js
The user-defined checks are applied in addition to PRIMER’s normal Model Check..
// arguments[0] is name of script
var m
= arguments[1];
var ns = arguments[2];
// arguments[1] is model
// arguments[2] is node set
ns.Error("Constrained node sets are not allowed. Use nodal rigid bodies instead");
Back to Contents
Slide 42
Finding which nodes are behind a *RIGIDWALL
Nodes behind a *RIGIDWALL can now
be saved to a Node Set for further
checking or correction later
Back to Contents
Slide 43
Some of the new checks in PRIMER 11
• Duplicated shells – PRIMER 11 can check for duplicated shells when PID is
different
• New error checks for MAT_126
• Check for when Part and NRB share PID and used in
*BOUNDARY_PRESC_MOTION
• *ELEMENT_SEATBELT and *ELEMENT_BEAM (or ELEMENT_DISCRETE)
share same ID
• Check for cracks within a part
• Check for inconsistent normals within a shell part
• Check for Jacobian element quality
• Added an optional part size check to the rigid/deformable continuity checks
• Check for % triangles within a deformable shell part
Back to Contents
Slide 44
Contacts
Back to Contents
Slide 45
Contact Penetration checking
In some respects, LS-DYNA’s definition of Contact
Penetration differs between SMP and MPP contact
algorithms. In Version 11, PRIMER can check
according to SMP or MPP methods. MPP is the
default.
This applies also to tied contact (detection of which
nodes are tied).
Back to Contents
Slide 46
Contact Penetrations: Crossed Edge Fixing
Pick one node
Other nodes are
selected
automatically
New button “Pick & propagate” allows user to pick one node; PRIMER
then automatically selects all the other nodes that are on the same side
of the Crossed Edge. Selection can be adjusted using ADD, REM
Fixing the selected nodes is a separate operation. The usual methods
are available, e.g. “Auto fix”, “Normal to shell”, etc
Back to Contents
Slide 47
Contact Penetrations: Crossed Edge Fixing
Pick one node
auto
New button “Pick, propagate & fix” allows user to pick one node; the
selection of other nodes that are on the same side of the Crossed
Edge, and the fixing, are both performed automatically in a single
operation
Back to Contents
Slide 48
Contact Penetrations: SHLEDG
• Effect of SHLEDG now included in PRIMER’s Contact Penetration check
SHLEDG=0:
SHLEDG=1 (with SOFT=2):
“penetration” caused by
semi-circular segment
edges
square edges, no
penetration
Back to Contents
Slide 49
Penetration listing by interacting Parts
Contact penetrations can be summarised
according to each pair of interacting parts
Back to Contents
Slide 50
*CONTACT ONLY – Start from visible elements
“All in contact” – same as PRIMER Version 10 –
shows all elements in the *CONTACT
Back to Contents
Slide 51
*CONTACT ONLY – Start from visible elements
“Visible in contact” – displays initially visible
elements that are in the *CONTACT
Back to Contents
Slide 52
Updating existing models
Back to Contents
Slide 53
Part Replace
• Part Replace offers intelligent replacement
of parts with reconnection of spotwelds and
other attached entities
• Improvements in Version 11:
– Can replace a mixture of shell, solid and
beam parts in one operation
– Can select which nodes get re-connected
– Command-line available for automation
– “Assembly Replace”
Back to Contents
Slide 54
Part Replace
Intelligent Part Replace with re-connection of spotwelds, bolts,
adhesive, MIG, and other attached entities
New options allow user
to choose which nodes
should be re-connected
Back to Contents
Slide 55
Part Replace – PRIMER Version 10
PRIMER Version 10 multiple Part Replace
1. Old meshes removed, leaving the spotwelds
Back to Contents
Slide 56
PRIMER Version 10, multiple Part Replace
2. New meshes of the same Parts added,
reconnecting to same spotwelds
Back to Contents
Slide 57
Assembly Replace – PRIMER Version 11
PRIMER Version 11 Assembly Replace
1. Old meshes removed, including any spotwelds
and other connected items that are “internal” to the
selected parts
Back to Contents
Slide 58
PRIMER Version 11, Assembly Replace
2. New assembly, which can include its own
spotwelds and other connected items, new
parts, etc. The new assembly is connected
to the rest of the structure using existing
spotwelds
Back to Contents
Slide 59
Replace Assembly
Old model with spotwelds
New mesh of assembly,
spotwelded, may have
different number of parts
+
Old model with spotwelds
=
Spotwelds “around the
edges” of the assembly are
taken from the old model,
and re-connected.
Back to Contents
Spotwelds “inside” the
assembly are taken from
the new mesh
Slide 60
Replace Assembly
Action for *PART data
•
•
When replacing an assembly, if a part in the source model
has the same label as a part in the assembly you are
replacing in the target model, there are two options
available for data on the *PART card:
•
Retain target data – part will reference the section,
material etc. that it references in the target model
•
Set data from source – part will reference the
section, material etc. that it references in the source
model. With this option you can also choose to
import the referenced section, material, section,
hourglass and equation of state cards from the
source model to the target model
Note that if a part in the source model does not match the
label of a part in the assembly you are replacing in the
target model, all referenced data (section material etc.) will
be copied across
Back to Contents
Slide 61
Replace Assembly
New mesh assembly,
replaced into old model
Same capabilities as existing
Part Replace: re-creating bolt
connections, re-attaching
entities to the new mesh, etc
Spotwelds “around the edges” of
the assembly are taken from the
old model, and re-connected
Spotwelds “inside” the assembly
are taken from the new model
Back to Contents
Slide 62
Assembly Replace – Part Sets
• How to ensure that new parts are in the correct Part Sets for contact, initial
velocity, etc?
• Method 1 - *SET_PART_LIST_GENERATE.
– Incoming new parts are correctly numbered to fall within the ID range
New Part ID 24010 will
automatically fall into the Part Set
Body structure Part IDs are 20000 to
29999; SET_PART_LIST_GENERATE
references this ID range
Back to Contents
Slide 63
Assembly Replace – Part Sets
• How to ensure that new parts are in the correct Part Sets for contact, initial
velocity, etc?
• Method 2 - *SET_PART_LIST.
– If ALL the outgoing parts are in the set, then the incoming parts will all be placed
into the set automatically
PRIMER will put new Part ID
24010 into the Part Set
Part IDs are 24001 to 24005
are all in *SET_PART_LIST
Back to Contents
Slide 64
Assembly Replace - bolts
• Re-connection of bolt connections at the boundary of the new mesh depends on the
definition method. If the layer definition consists of Part IDs, the bolt will re-connect only
to those Part IDs, not to the new parts
No connection
to new red Part
Back to Contents
Slide 65
Assembly Replace - bolts
• If Part Set ID or Part Tree Assembly name is used in the bolt
definition, and if the new parts are included in that set or
assembly, then the bolt will re-connect to the new parts too
Bolt connects
to new red Part
Back to Contents
Slide 66
DATABASE_CROSS_SECTION – Transfer
Old model with
*DATABASE_CROSS_SECTIONs
New model
Includes options to
fix Part Set when
new model contains
different parts
+
New model with
*DATABASE_CROSS_SECTIONs
Back to Contents
Slide 67
Mechanisms
Back to Contents
Slide 68
Mechanisms: PRIMER Version 10
PRIMER has a Mechanism capability for positioning seats, suspension systems, etc.
In PRIMER Version 10, Mechanisms can be created by the user: define which parts are in each
assembly; define the connections; etc.
H-point
X2, Y2, Z2
H-point
X1, Y1, Z1
Back to Contents
Slide 69
Automatic creation of Mechanism – PRIMER 11
In PRIMER Version 11, Mechanisms can be created automatically by PRIMER,
if the LS-DYNA model already contains certain LS-DYNA connectors to joint
parts together
Pick “Start node”
Pick any node as
the “Start node”
Tell PRIMER what type of
elements are present at
the connections:
*CONSTRAINED_JOINT,
*ELEMENT_BEAM, etc.
Back to Contents
Slide 70
Press “Calculate”: PRIMER automatically groups the parts into Assemblies, and
creates the PRIMER mechanism connection data between the assemblies
based on the LS-DYNA connectors. Check that the parts seem to be grouped
correctly (using the colours). If not, change inputs in this menu and press
Calculate again. When it is correct, press Save.
Control what types of
elements count as
“connectors”
Back to Contents
Slide 71
Now the mechanism can be positioned by dragging
Drag
Drag
Back to Contents
Slide 72
Mechanism - stretch
Parts may be stretched during mechanism positioning. The stretching is calculated
from the distance between 2 nodes
Node 1
Stretched
part
Node 2
Back to Contents
Slide 73
Mechanism - stretch
The same capability could be used for stretching springs in a seat model
Node 1
Back to Contents
Stretched
part
Slide 74
Node 2
Mechanism - stretch
Node 1
Node 2
Stretched
part(s)
Back to Contents
Slide 75
Mesh modification
Back to Contents
Slide 76
“Cobweb” mesh
Can be used to locally remesh
an area where an impact will
occur
Back to Contents
Slide 77
Split solids (refine mesh)
In v10 shell elements could be
split. In v11, solid elements
can also be split
Back to Contents
Slide 78
Aligning element local axes – solids and shells
Before: local Xaxis direction is
random
After: local X-axis
direction is
consistent
Element local x axis (N1->N2)can
be aligned (through element
node order modifications) with a
specified vector or seed element
Back to Contents
Slide 79
Results in element coordinate system
Alignment needed when results are displayed in local element axes,
e.g. shell resultant force or moment
Back to Contents
Slide 80
ORIENT with coordinate systems
Translate, Rotate, Reflect, Scale: axis system can be
defined by a *DEFINE_COORDINATE_...
Back to Contents
Slide 81
Detach solids and beams
Back to Contents
Slide 82
Extrude Thick Shells
In PRIMER Version 10, solid elements could be
created by extruding shell elements. In Version 11, this
capability has been extended to Thick Shells.
Back to Contents
Slide 83
Seatbelt fitting
Back to Contents
Slide 84
2D Belts – DATABASE_CROSS_SECTION
Force output from 2D Belt elements can be achieved by
*DATABASE_CROSS_SECTION. This can now be specified in the belt-fitting menu, by
assigning a Path Point (usually the slipring) to have a DATABASE_CROSS_SECTION:
Back to Contents
Slide 85
2D Belts – DATABASE_CROSS_SECTION
The DATABASE_CROSS_SECTIONs are created at a pre-defined distance from the
slipring; the distance can be specified by the user and stored in a Preference :
Back to Contents
Slide 86
Belt path rotation at buckle
The belt path may be rotated parallel to 2 user-selected
nodes. This is useful at the buckle
PICTUREBefore fitting –
make belt path
NEEDEDparallel
with slot
by picking 2
nodes on slot
Back to Contents
Slide 87
Belt path rotation at buckle
The belt path may be rotated parallel to 2 user-selected
nodes. This is useful at the buckle
After fitting
Back to Contents
Slide 88
Connections
Back to Contents
Slide 89
Tied contact for spotwelds, adhesive, etc
• What type of tied contact should be used to fix spotweld and adhesive
elements to the panels?
• Constrained type, e.g. *CONTACT_TIED_NODES_TO_SURFACE
 – No relative movement or vibration
X – Cannot work when rigid parts or Nodal Rigid Bodies are attached to the panel
nodes – this may occur with, say 5% of spotweld nodes
• Penalty type, e.g. *CONTACT_TIED_NODES_TO_SURFACE_OFFSET
X – Relative movement, lack of stiffness, may cause noise
 – Works whatever is attached to the panel nodes
Constraint-type: best where possible (e.g. 95% of welds)
Penalty-type: required for, say, 5% of welds
The next slide describes what happens
when PRIMER automatically fixes this
Back to Contents
Slide 90
Tied contact for spotwelds, adhesive, etc
PRIMER v10
NRB
Constraint-type tied contact
panel
spotweld
spotweld
spotweld
Penalty-type tied contact
Version 10 auto-fix: Separate *SET_NODEs for spotweld/adhesive nodes that can be
attached by constraint-type, versus those that have to be attached by penalty-type.
X Requires maintenance each time the model is changed
PRIMER v11
NRB
Constraint-type tied contact
Penalty-type tied contact
Version 11 auto-fix: Constraint-type and Penalty-type are doubled up, allowing Partbased definitions of the tied contact. Can use Part ID ranges etc in *SET definitions
 No maintenance
Note: LS-DYNA R7.0 onwards has IPBACK on
*CONTACT_TIED…, same effect as PRIMER v11
Back to Contents
Slide 91
Connection menu
Connections can be filtered by type
(Spotweld, Bolt, Adhesive, Spotweld lines)
Back to Contents
Slide 92
Spotwelds – different PID per layer
PRIMER can now accept 3T or 4T spotwelds in which the spotweld elements (solid or beam)
have different PIDs per layer. These PIDs can be written to (and read from) connection xml
files. The PIDs can be input and modified on Connection Table
Solid element,
PID 9991
Solid element,
PID 9998
Back to Contents
Slide 93
Spotweld/SPR reverse orientation
Order of layers may be important for Self-Piercing Rivets, where insertion
direction affects the strength of the connection
Layer 1
Layer 3
Layer 2
Layer 2
Layer 3
Layer 1
Back to Contents
Slide 94
Spotweld Line connections
PRIMER can create a
line-type connection;
spotweld pitch is a
property of the
connection. Spotweld
line connections can
be created along a
free edge
Back to Contents
Slide 95
Spotweld Line connections
A spotweld line connection can be “locked”
to a free edge. This means that when
remade (for example during part replace)
the connection will follow any meshing
changes made to the model
Back to Contents
Slide 96
Generic bolt
• More complex bolt definitions are possible
• Can have different specification at each end
(thickness, diameter, orientation, etc)
Back to Contents
Slide 97
“Discrete Beam” Bolts + Coordinate System
• Bolts created with Discrete
Beams automatically create a
coordinate system with the
local X axis aligned with the
bolt axis
Back to Contents
Slide 98
Rigid Beam “Spider” tools
Click node on
edge of hole.
PRIMER
creates a
“spider” made
of rigid beam
elements
Back to Contents
Slide 99
Merge function: PRIMER automatically finds
rigid spiders that are close together, and
creates *CONSTRAINED_RIGID_BODIES
Back to Contents
Slide 100
When merging Rigid Spiders, the user can control the
merge distance, and whether spiders should be
merged across Include files or within Include files
When creating Rigid Spiders, the user can
control the ID of new entities
Spiders can be transferred between similar
models with the Import/Export buttons
Back to Contents
Slide 101
Reading, writing and translating
Back to Contents
Slide 102
Include File De-clash
Include_1.key
Include_2.key
*ELEMENT_SHELL
34
2
*ELEMENT_SHELL
34
5
1329
90
91
1330
9518
9519
9521
9520
• Clashing labels (same
ID) between two Include
files: PRIMER 10.x
explains which Include
files are clashing, but
cannot fix the error
Back to Contents
Slide 103
Include File De-clash
Include_1.key
Include_2.key
*ELEMENT_SHELL
34
2
*ELEMENT_SHELL
34
5
1329
90
91
1330
9518
9519
9521
9520
• PRIMER 11.0 has De-clash function to fix the problem while reading the model
Back to Contents
Slide 104
Linux file selector
• Similar capabilities to Windows file selector
• Sort by date, etc
• Multiple file extensions (e.g. *.key, *.k, *.dyn)
Back to Contents
Slide 105
NASTRAN support
• Model Build supports NASTRAN models
• Skip files now include Case Control, and keep the data in the correct
NASTRAN Include files
• PRIMER can read NASTRAN models in which nodes were defined in local
coordinate systems
• Titles from NASTRAN PSHELL, MAT, stored as Hypermesh comments are
now read by PRIMER
• Extended NASTRAN support in post-processing – e.g D3PLOT reads
NASTRAN’s OP2 file, T/HIS reads Punch files
Back to Contents
Slide 106
• There are two styles of encrypted models:
– “Fully encrypted” (most encrypted commercial dummy models are like this) – all
the *MAT and *DEFINE_CURVE definitions are in one single encrypted block.
The IDs cannot be seen.
– “Partially encrypted” – the data for each *MAT and *DEFINE_CURVE are in a
separate encrypted block. The ID and Title of each *MAT and *DEFINE_CURVE
can be seen, as shown here:
“Partially encrypted”
Title line includes the Material ID
*MAT_OGDEN_RUBBER_TITLE
1512051 MATL77B_12051
-----BEGIN PGP MESSAGE-----
Data for each material is in a
separate encrypted block
hQEOAynNq7gVWpx/EAP9FNA/iCkcZSS676q+/IwT6DxZr8jPbnTTR+2U7KL3BPgy
…
-----END PGP MESSAGE----$
*DEFINE_CURVE
1512005
0
1.0
1.2
0.0
0.0
-----BEGIN PGP MESSAGE----hQEOAynNq7gVWpx/EAP9F/11BveQIEkoIUH6PEf6iHBhNPqXQ12vxleV8mYXWSVA
…
0
Curve ID, offsets and scale
factors are not encrypted.
The XY points are in an
encrypted block.
-----END PGP MESSAGE-----
Back to Contents
Slide 107
• PRIMER Version 10 capability:
Fully encrypted
Partially encrypted
Reads the model


Writes the model, including
the encrypted data


Encrypted data protected
against renumbering
X
X
X

against “clean-up unused”
Model Check avoids
spurious errors due to
“missing” encrypted data
Model mass can be
calculated
X
X
Back to Contents

X
Slide 108
• For PRIMER Version 11, the Partially Encrypted style can include the
density. Model mass can then be calculated
• In Version 11, encrypted data is protected against renumbering
*MAT_OGDEN_RUBBER_TITLE
1512051 RO=1.2E-9 MATL77B_12051
Density can be included in the
Title line, as well as ID
Use this method for
partially-encrypted
models only
…
-----END PGP MESSAGE-----
Back to Contents
Slide 109
• For PRIMER Version 11, fully encrypted models can have additional *MAT,
*DEFINE_CURVE and *DEFINE_TABLE pre-processing data after *END:
Fully encrypted: all *MAT and
*DEFINE_CURVE in one
encrypted block
…
-----END PGP MESSAGE----*END
*ENCRYPTED_START
*MAT_VISCOELASTIC
100001
1.25E-9
*MAT_RIGID
100002
2.7E-9
0.0
0.0
0.0
0.0
It is allowed to input EITHER a full material definition,
or just one line containing ID and density
*DEFINE_CURVE
100001
0
0.0
0.0
0.0
0.0
1.0
1.0
0.0
0.0
0
*MAT and *DEFINE_CURVE data
for pre-processing can be given
after *END using special keywords
*ENCRYPTED_START and
*ENCRYPTED_END. These
keywords tell PRIMER that the
same Material and Curve IDs are
present in encrypted data blocks.
*ENCRYPTED_END
Back to Contents
Slide 110
• It may be more convenient to put this data in a separate Include file –
“Style (a)” for *MAT, *DEFINE_CURVE and *DEFINE_TABLE only:
*KEYWORD
Master Model
*INCLUDE
Encrypted_dummy.key
Fully encrypted dummy model, without any changes
*INCLUDE
Material_preprocess.key
Include file referenced before *END
*END
Material_preprocess.key
*KEYWORD
*END
Use *ENCRYPTED_START after *END; data is protected against
renumbering. These keywords tell PRIMER that the same IDs are
present within encrypted data blocks.
*ENCRYPTED_START
*MAT_VISCOELASTIC
100001
1.25E-9
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
*DEFINE_CURVE
100001
0
0.0
0.0
1.0
1.0
0
*ENCRYPTED_END
Back to Contents
Slide 111
• Another possibility (also new for Version 11) is to reference an Include file after
*END in the Master Model, and normal keywords (before *END) in the Include
file – “Style (b)”. This method allows any keyword to be used, but without any
implication about the same IDs being used in encrypted data blocks
*KEYWORD
Master Model
*INCLUDE
Encrypted_dummy.key
Fully encrypted dummy model, without any changes
*END
*INCLUDE
Preprocess_only.key
Include file referenced after *END will be read only by PRIMER,
not LS-DYNA
Preprocess_only.key
*KEYWORD
*SECTION_BEAM_TITLE
SectBeam_12055
1512055
2
1.0
2.0
a
iss
itt
irr
sa
1.0
1.0
1.0
1.0
1.0
0.0
0.0
0.0
$
Any keywords can be included, but they
behave like normal keywords –they are
not protected against renumbering or
locked against “clean-up unused”.
*MAT_VISCOELASTIC
100001
1.25E-9
0.0
*END
Back to Contents
Slide 112
• PRIMER Version 11 capability:
Fully encrypted
+ data after *END
Partially encrypted
Reads the model


Writes the model, including
the encrypted data


against renumbering


against “clean-up unused”


Model Check avoids
spurious errors due to
“missing” encrypted data
Model mass can be
calculated




Back to Contents
Slide 113
Model Build (Database/Template system)
• PRIMER Version 10 can accept connection files from the database/template,
and create connections during model assembly. In PRIMER Version 11, a log
file is produced listing the status of each
=====================================================================
Creating bolt at 105, 25, 0 ...
Connection projects to shells S296 S5283 - will be used to determine bolt axis.
Bolt created OK
=====================================================================
=====================================================================
Creating bolt at 104, 40, 30 ...
Connection projects to shell S5519 - will be used to determine bolt axis.
Creating NRB type connection at X=104 Y=40 Z=30
9/15 of the selected nodes are on rigid part(s)
PRIMER will create C_EXTRA_NO and C_RBOD instead of NRBC.
Creating dummy rigid master part (no elements)
Creating dummy rigid master part (no elements)
%%% WARNING %%%
P:10006 is already slaved to P:10004. Cannot slave to P:10021
Connectivity may be lost. Please check your model.
Bolt created OK
=====================================================================
Back to Contents
See next slide for more
details of where this file will
be written
This information is written to
the dialog box, and is saved
to a file named
pr_build_info_001 (in the
same folder as submit.lst)
after PRIMER exits.
The location of the file may
be changed by a preference
save_dialog_dir
Slide 114
Model Build (Database/Template system)
More about the log file for Model Build (shown on previous slide):
• The information is written to the dialog box while PRIMER is still running
– To see all the dialog box contents, right-click in top-left corner and “text edit”
• After PRIMER exits, the information is written to a file pr_build_info_001
– For multiple Model Build from Database/Template, it is written to the same folder
as submit.lst
– For other cases of Model Build from Database/Template, the file is written to the
Database directory
– For Build-from-csv (target file), the file is written to the same folder as the csv file.
– The folder where the file is written can be changed by the preference
save_dialog_dir
– For batch operation, the folder and filename can be controlled by
INFO_FILE=path\filename
Back to Contents
Slide 115
De-clash of element labels when writing the model
LS-DYNA and PRIMER allow clashes of element labels between different element types,
e.g. a solid element 100 and shell element 100. Some pre-processors cannot handle this.
When a keyword file is written, PRIMER 11 checks for clashes and, if a clash is found,
offers to fix the element labels
Back to Contents
Slide 116
Checking new component geometry
against deformed shape
Back to Contents
Slide 117
View mesh or geometry with deformed model – V11
In Version 11, a proposed new part (either mesh or IGES) can be written as a d3plot
(*.ptf) file. This can then be superimposed on existing analyses to check for
interference with existing structure
Mesh
Proposed new part
Or
D3PLOT file
PRIMER
IGES
(model only, no results)
LS-DYNA crash model
results (d3plot)
Back to Contents
Slide 118
PRIMER support for *CASE
Back to Contents
Slide 119
*CASE
• LS-DYNA’s *CASE keyword allows several LS-DYNA analyses (loadcases)
from one keyword file. PRIMER version 11 supports this. We will illustrate
how to do it with these examples:
– Loads and SPC restraints applied to different nodes in each loadcase
– Drop test with different impact angle in each loadcase
– Drop test with different material properties in each loadcase, by changing values
on *MAT card
– Drop test with different material properties in each loadcase, using
*PARAMETER
Back to Contents
Slide 120
*CASE – Example 1 – Load and SPC
• We will start with a
model containing all the
*LOAD and
*BOUNDARY_SPC
cards
• We want to create two
*CASEs, and move the
loads and SPC cards
into Case 1 and Case 2
• The other data (Node,
Element, Control, etc)
will remain in the Main
Model
Load for case 1
SPC for case 2
(red, pink)
Load for case 2
SPC for case 1
(blue)
Back to Contents
Slide 121
• Step 1 – create *CASE 1
• Repeat for Case 2
Must create a sub-case – this will contain the casespecific data. The simplest way is to make one SubCase per Case, with Sub-Case ID the same as the
Case ID (in this example, 1 and 1). However, it is
allowed to have many Sub-Cases in each Case
Back to Contents
Slide 122
• Step 2 – make *CASE 1 “current”;
this will allow us to move data into
the case
Green = Current Case
Back to Contents
Slide 123
• Step 3 – edit sub-case 1, add the
*LOAD and SPC data
Back to Contents
Slide 124
• Step 4: Repeat for Case 2
• Now when we switch from Case 1 to Case 2, we will see the Load and SPC
for each case:
Back to Contents
Slide 125
*CASE – Example 2 – Drop Test
• Main model contains *NODE, *ELEMENT, *MAT, *PART, *CONTROL, etc
• Each Case contains separate *INITIAL_VELOCITY and *RIGIDWALL:
Initial
velocity
Initial
velocity
Case 1
Case 2
Back to Contents
Slide 126
*CASE – Example 2 – Drop Test
• How to do it in PRIMER: similar to Example 1
–
–
–
–
–
Create *INITIAL_VELOCITY and *RIGIDWALL containing the data for Case 1
Make Case 1 current
Edit Case 1, Edit Sub-Case 1, Add the Initial Velocity and Rigidwall, Update
Make Case 2 current
The previously created *INITIAL_VELOCITY and *RIGIDWALL seem to have
disappeared, because they are now present only in Case 1
– Create *INITIAL_VELOCITY and *RIGIDWALL containing the data for Case 2
– Edit Case 2, Edit Sub-Case 2, Add the Initial Velocity, Update
Back to Contents
Slide 127
*CASE – Example 3 – Material (different data)
• How to do it in PRIMER:
This *MAT is present only in Case 1,
and absent from other cases
Different definitions of this *MAT are
present in Case 1 and Case 2. Each
can be modified separately, when
that Case is current
This same *MAT definition is present
in Case 1 and Case 2
Back to Contents
Slide 128
*CASE – Example 3 – Material (different data)
• Keyword file: different material data in each case
$
*CASE_BEGIN_1
*MAT_PLASTIC_KINEMATIC_TITLE
Steel
1
7.8E-9
2.0E7
0.3
0.0
0.0
0.0
0.0
250.0
1000.0
300.0
1000.0
*CASE_END_1
$
*CASE_BEGIN_2
Steel
1
7.8E-9
2.0E7
0.3
0.0
0.0
0.0
0.0
*CASE_END_2
Different definitions of this *MAT are
present in Case 1 and Case 2. Each
can be modified separately, when
that case is current.
Back to Contents
Slide 129
*CASE – Example 4 – Material (by Parameter value)
• Keyword file:
$
Steel
1
7.8E-9
2.0E7
0.0
0.0
0.0
0.3&YIELD
1000.0
The *MAT data is in the main model,
and contains reference to a
0.0
*PARAMETER
0.0
$
*CASE_BEGIN_1
*PARAMETER
R YIELD
250.0
The value of the parameter
is different in each Case
*CASE_END_1
$
*CASE_BEGIN_2
*PARAMETER
R YIELD
300.0
*CASE_END_2
Back to Contents
Slide 130
*CASE – Example 4 – Material (by Parameter value)
– Edit the *PARAMETER, go to
the Case Management menu,
select all cases, select
“Separate child cases”
– Make Case 1 current
– Keyword=>Parameter=>Modify,
change the parameter value,
Update
– Make Case 2 current
– Keyword=>Parameter=>Modify,
change the parameter value,
Update
Different definitions of this
*PARAMETER are present in Case 1
and Case 2. Each can be modified
separately, when that case is current.
Back to Contents
Slide 131
Pedestrian protection
Back to Contents
Slide 132
Pedestrian Mark-up – Version 10
In PRIMER Version 10, the impact points can be calculated, and
impactors can be positioned
Back to Contents
Slide 133
Default is for points spaced evenly on
a grid in the XY direction
Back to Contents
Slide 134
New option for NxM points
within each zone, e.g. 2x3.
Version 10 offered only NxN.
Back to Contents
Slide 135
Pedestrian Upper Leg – Version 11
In Version 11, the markup script can calculate impact angle, mass and kinetic energy for the Upper Legform.
The data is written to the csv file, and can be applied by PRIMER during Model Build
Vehicle geometry
Graphs from EuroNCAP
Impactor model contains a parameter that
controls the mass, e.g. density of certain
parts = &RHO. User supplies the name of
the parameter
Impact point (X,Y), Angle, Velocity and
Mass are calculated by script
Parameter value to achieve the mass is
calculated by script
Csv file for PRIMER Model Build
PRIMER uses the angle, velocity and
sets the Parameter value when setting
up the impactor model for each impact
point
Back to Contents
Slide 136
Reporter: Pedestrian Area Calculation Scripts
Back to Contents
Slide 137
JavaScript & Automation
Back to Contents
Slide 138
JavaScript update
Many new functions and capabilities, including:
•
•
•
•
•
•
Debugger
GUI enhancements: Pop-ups
User-defined error checks
Speedup of script execution in Version 11 (typically 2-10x faster)
*PARAMETER can be created and modified
Many new keywords supported, e.g.
– *LOAD_RIGID_BODY
– *SET_GENERAL
• Many new functions, e.g.
–
–
–
–
Node Merge
Contact Penetration check
Animation control for *BOUNDARY_PRESCRIBED_MOTION
Functions to find free edges easily
Back to Contents
Slide 139
Javascript debugger
Can step through the script, set
break-points, watch the values
of variables, etc.:
Back to Contents
Slide 140
Pop-ups
// Create popup window
var pw = new PopupWindow();
// Create some widgets in the popup window
var pl = new Widget(pw, Widget.LABEL,
1, 30, 1, 7, "Label");
var pb = new Widget(pw, Widget.BUTTON, 1, 30, 7, 13, "Button");
var pt = new Widget(pw, Widget.TEXTBOX, 1, 30, 20, 26, "Textbox");
// Create window
var w = new Window("Popup example", 0.9, 1.0, 0.5, 0.6);
// Create label widget
var l = new Widget(w, Widget.LABEL,
1, 50, 1,
7, "Right click for popup...");
// link popup window to widget
l.popupWindow = pw;
// Assign the onPopup callback method to the function 'do_popup'
// This is only required if you want to make any changes before the popup appears
l.onPopup = do_popup;
// Show the widget and start event loop
w.Show();
function do_popup()
{
Message("Showing popup");
}
Back to Contents
Slide 141
Speed of scripts in version 11
Scripts are significantly faster in version 11
Test
v10 time (ms)
v11 time (ms)
Speed up
Read text file (~500,000 lines)
550
230
x2.4
Read text file (~500,000 lines) and extract
keywords with regular expression
2200
330
x6.6
Create array of shells (~340,000) with
var shells = Shell.GetAll(m)
290
50
x5.8
Loop over all nodes (~200,000) using
Node.First() and Node.Next()
150
70
x2.1
Loop over nodes (~200,000) and find
average coordinate
385
110
x3.5
Lots of maths
15450
1030
x15
Back to Contents
Slide 142
Speed in version 11: New ForEach() method
A new way of doing something for every item in a model
E.g. Looping over every node to find average coordinate
v10
v11
var
var
var
var
x
y
z
t
var n
while
{
x
y
z
385ms
110ms
=
=
=
=
0.0;
0.0;
0.0;
0;
= Node.First(m);
(n)
+= n.x;
+= n.y;
+= n.z;
t++;
n = n.Next();
}
x /= t;
y /= t;
z /= t;
v11
var
var
var
var
x
y
z
t
=
=
=
=
0.0;
0.0;
0.0;
0;
Node.ForEach(m, doit);
x /= t;
y /= t;
z /= t;
function
{
x +=
y +=
z +=
doit(n)
n.x;
n.y;
n.z;
60ms
var
var
var
var
x
y
z
t
=
=
=
=
0.0;
0.0;
0.0;
0;
Node.ForEach(m, function(n)
{
x += n.x;
OR
y += n.y;
z += n.z;
t++;
}
);
x /= t;
y /= t;
z /= t;
t++;
}
Back to Contents
Slide 143
New scripts released with v11.0 (also
previously released with incremental
v10.2 release)
Back to Contents
Slide 144
Interior Head Impact Mark-up (FMVSS201)
FMVSS201 has complex geometrical rules
for determining the coordinates of the target
points for interior head impact
PRIMER 10.2/11.0 includes a script that
calculates the target point coordinates
according to those rules
Back to Contents
Slide 145
• Calculates impact points according to rules
of FMVSS201
• Angles and velocity can be modified by the
user
• Creates impact point file (csv format)
Back to Contents
Slide 146
• PRIMER can then
position the headform at
each point, using Model
Build
• Automatic postprocessing is available
to make a report
Back to Contents
Slide 147
Barrier positioning tool
• Crash Test Setup script for
positioning the barrier and
applying initial conditions
• Includes the detailed rules for
many crash test protocols
• Step 1 – select crash protocol
Back to Contents
Slide 148
• Step 2 – Vehicle data (e.g. coordinates of R-point for aiming the
barrier). This data can be stored and re-used next time
• This menu also allows the ground coordinates to be specified
Back to Contents
Slide 149
• Step 3 – Barrier data. This data is input once, then stored and reused next time
Back to Contents
Slide 150
Ground position
300mm
True ground
Wheel support plane
The vehicle’s tyres and suspension are usually not modelled with the compression that would occur under
normal gravity loading. Therefore the actual ground plane may not be located at the bottom of the tyres
The barrier must be the correct height above the true ground plane
We also need a “wheel support plane” at the bottom of the tyres, to prevent the model falling downwards
Back to Contents
Slide 151
The supported crash test protocols are listed here. Small changes to these crash types (e.g.
impact velocity) can be made by the user and saved easily:
EuroNCAP, UN-ECE:
Side Impact (R-Point)
EuroNCAP:
Side Impact (Pole)
FMVSS 214P: Side
Oblique Impact (Pole)
FMVSS 214D:
Angled Side Impact
FMVSS, UN-ECE:
Frontal Impact (Rigid)
IIHS:
Side Impact (IRD)
FMVSS 216A:
Roof Crush
EuroNCAP, FMVSS, IIHS,
UN-ECE: Frontal Impact (ODB)
FMVSS 301R:
Rear Impact
(MDB)
IIHS: Frontal
Small Overlap
Back to Contents
Slide 152
New in PRIMER 11.0
Crash Test Setup version 11.0 includes additional features:
•
•
IIHS Small offset rigid barrier (frontal)
FMVSS 301R Rear impact
•
•
R-point offset option added to side impact test
The ability to read barrier files from a web address
Import Settings Files
You may have settings files (preferences, vehicle settings entries, barrier settings entries and
crash test variants) that you wish to import from Crash Test Setup 10.2.
Run the script import_crash_test_setup_settings.js to merge your 10.2 settings with 11.0. The
script is found at:
•
$OASYS/PRIMER_library/scripts/crash_test_setup_utilities/import_crash_test_setup_settings.js
Click the button
for more help
Back to Contents
Slide 153
Miscellaneous
Back to Contents
Slide 154
*DEFORMABLE_TO_RIGID - multiple part selection
Multiple part selection is now available for for both D2R and R2D cards
Back to Contents
Slide 155
*DEFORMABLE_TO_RIGID - Only
New function to display parts referenced by *DEFORMABLE_TO_RIGID
Back to Contents
Slide 156
Material properties - retain during type change
Properties retained
when they have the
same label, e.g. “SIGY”.
Back to Contents
Slide 157
NRB spider in hole
Click on any node located
at the edge of a hole
PRIMER automatically creates a nodal body
tying nodes located at the edge of the hole
and the centre of the hole
Back to Contents
Slide 158
Geometry operations
• The Measure tool has three existing functions that work in
model space (nodal coordinates based). All three functions can
now work with both geometry points and nodes
• New function available to compute length of a geometry curve
Node edit panel now permits creation of any number of
nodes spaced equidistantly along the length of a
geometry curve
Nodes can now also be created at geometry point
locations by picking or selecting those points
Back to Contents
Slide 159
*AIRBAG_REFERENCE_GEOMETRY
*AIRBAG_REFERENCE_GEOMETRY can be
created and edited. In previous versions of
PRIMER, this could be done only by using the
Airbag Folder tool
Select nodes
Coordinates imported as
Reference Geometry
Back to Contents
Slide 160
Clipboard: sub-model from Parts
• User selects Parts, then “Save as model”
• New option “Create sub-model from parts”
– finds more data than “referenced items”
• *SET_PART and *SET_NODE are
included, plus data that references those
SETs, e.g. *CONTACT
Back to Contents
Slide 161
Clipboard: sub-model from Parts
“Find Referenced Items”:
*PART
*MAT
*DEFINE_CURVE, TABLE, etc
*SECTION, *HOURGLASS
*ELEMENT
*NODE
Connections (spotwelds, bolts)
Keywords e.g. *DAMPING_PART_... that
directly reference the PART
“Sub-model from Parts”:
*PART
*MAT
*DEFINE_CURVE, TABLE, etc
*SECTION, *HOURGLASS
*ELEMENT
*NODE
Connections (spotwelds, bolts)
Keywords e.g. *DAMPING_PART_... that
directly reference the PART
*SET_PART
*CONTACT (tied, sliding…)
*DATABASE_CROSS_SECTION
and other keywords that reference Part Set
*SET_NODE
*CONSTRAINED_NODAL_RIGID_BODY
and other keywords that reference Node Set
Back to Contents
Slide 162
New preferences of note
•
•
•
•
•
•
•
•
•
•
•
•
Seatbelt fitting settings
Control of macro echo during recording
Recursive blanking setting
Part shell normal consistency check setting
Panel layout settings
Multiple file extension preference for Linux
Feature line angle
Default settings for SPR & MPR when creating contacts
Setting for contact check mode (SMP or MPP)
Drawing true beam sections by default setting
Preference for specifying location of emergency keyout
Preference for locking loadcurves against deletion when using
*MAT_USER_DEFINED
• Directory for emergency keyout file
Back to Contents
Slide 163
Contact Information
www.arup.com/dyna
For more information please contact the following:
UK:
China:
India:
Arup
Arup
nHance Engineering Solutions Pvt. Ltd (Arup)
The Arup Campus
39/F-41/F Huai Hai Plaza
Plot No. 39, Ananth Info Park
Blythe Valley Park
Huai Hai Road (M)
Opposite Oracle Campus
Solihull, West Midlands
Shanghai
HiTec City-Phase II
B90 8AE
China 200031
Madhapur
Hyderabad - 500081
UK
T +44 (0)121 213 3399
T +86 21 6126 2875
India
F +44 (0)121 213 3302
F +86 21 6126 2882
T +91 (0) 40 44369797 / 8
[email protected]
[email protected]
[email protected]
or contact your local Oasys distributor
Back to Contents
Slide 164

Oasys PRIMER Update

Transcription

Similar documents

Influencer Testimonials In Ads Case Studies

amtech™ am-1250™ direct-to-metal primer

Technical Data

Rock Chucker Supreme Auto Prime

How to Spray Paint Metal Furniture | Krylon®

Transport Box - Cashels Engineering

ASK TIFFANY tiffany St. John answers your