Patran 2014 1D Spring ---> 1D Spring Property Inputs Explaination?

[rkilgore28]

I'm still rather new at using Patran as I am still a student. I've searched online for help, MSC's Nastran 2013 release doc, MSC's online help, and YouTube, but wasn't successful.
I'm trying to model a control arm with bushings using springs in order to perform an initial rough stress analysis. The analysis is on a 3D solid. I applied meshseeds around the bushing holes then created the 3D solid Tet10 mesh. Afterwards, I created a center node for each bushing and then created bar2 elements connecting the nodes created by the meshseeds to each center node. Each bar2 element had the center node designated as node1 and the corresponding meshseed node as node2. The bar2 elements were oriented in the X,Y, and Z directions. Each bar2 element was assigned a spring properties with a spring constant and node DOF's were both in the direction of the element's orientation. Even though the center nodes were assigned a degree of freedom within the spring properties menu, the center nodes were constrained in the X,Y, and Z directions. A point force with X and Y components was applied to the ball joint location. In addition, I also constrained the whole control arm from translating in the Z direction. The control arm lays on the X-Y plane.

Any help will be greatly appreciated.

Thanks

F06 file:
1 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 1

0 N A S T R A N F I L E A N D S Y S T E M P A R A M E T E R E C H O
0


NASTRAN BUFFSIZE=8193 $(C:/MSC.SOFTWARE/MSC_NASTRAN/20131/CONF/NAST20131.RCF[2])
$ NASTRAN INPUT FILE CREATED BY THE PATRAN 2013 64-BIT INPUT FILE
$ TRANSLATOR ON DECEMBER 05, 2014 AT 15:16:38.
$ DIRECT TEXT INPUT FOR NASTRAN SYSTEM CELL SECTION
$ DIRECT TEXT INPUT FOR FILE MANAGEMENT SECTION
$ DIRECT TEXT INPUT FOR EXECUTIVE CONTROL
$ LINEAR STATIC ANALYSIS, DATABASE
1 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 2

0 N A S T R A N E X E C U T I V E C O N T R O L E C H O
0


SOL 101
CEND
1 MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 3

0
0 C A S E C O N T R O L E C H O
COMMAND
COUNT
1 $ DIRECT TEXT INPUT FOR GLOBAL CASE CONTROL DATA
2 TITLE = MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04
3 ECHO = NONE
4 SUBCASE 1
5 SUBTITLE=DEFAULT
6 SPC = 2
7 LOAD = 2
8 DISPLACEMENT(SORT1,REAL)=ALL
9 STRESS(SORT1,REAL,VONMISES,BILIN)=ALL
10 $ DIRECT TEXT INPUT FOR THIS SUBCASE
11 BEGIN BULK
1 MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 4

0
I N P U T B U L K D A T A E C H O
ENTRY
COUNT . 1 .. 2 .. 3 .. 4 .. 5 .. 6 .. 7 .. 8 .. 9 .. 10 .
*** USER INFORMATION MESSAGE 9991 (SDLWIF)
Messages are being generated at include level 0.
File: C:\SCRATCH\baseline_control_arm2_bushingmp.bdf
*** USER FATAL MESSAGE 9994 (BULKPM)
MAT1 with MID=2 near line 120381
User information: E:3.40282+38 is an illegal real value.
1 MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 5

0
*** USER FATAL MESSAGE 208 (SCA.MDSolver.Io.AccessAccess.AccessAccess::StreamToBinary)
Fatal messages were encountered while converting the stream input file C:\SCRATCH\baseline_control_arm2_bushingmp.bdf.
*** USER FATAL MESSAGE 102 (SCA.MDSolver.Obj.InputFile.InputFile::read)
Severe fatal Errors occured while reading the input file C:\SCRATCH\baseline_control_arm2_bushingmp.bdf.
Check the MDSolver.System.PrintListener output.
M O D E L S U M M A R Y BULK = 0
ENTRY NAME NUMBER OF ENTRIES
---------- -----------------
CELAS1 8
CTETRA 60163
FORCE 2
GRID 98834
LOAD 1
MAT1 1
PARAM 2
PELAS 4
PSOLID 2
SPC1 3
SPCADD 1

*** USER WARNING MESSAGE 285 (DML)
FATAL ERRORS WERE FOUND WHILE READING THIS BEGIN SECTION
MODEL SUMMARY DOES NOT INCLUDE COUNT OF FATAL ENTITIES
^^^
^^^ >>> IFP OPERATIONS COMPLETE <<<
^^^
^^^
*** USER FATAL MESSAGE 9002 (SUBDMAP IFPS)
ERROR(S) ENCOUNTERED IN THE MAIN BULK DATA SECTION
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE IFP,
^^^
1 MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 6

0
0


*** USER INFORMATION MESSAGE 4425 (PRTPRN)
ONE OR MORE FATAL ERRORS HAVE OCCURRED. THERE MAY BE MORE ERROR MESSAGES IN THE PRECEDING OUTPUT
1 MSC.NASTRAN JOB CREATED ON 03-DEC-14 AT 17:28:04 DECEMBER 5, 2014 MSC Nastran 3/14/14 PAGE 7

0
* * * * D B D I C T P R I N T * * * * SUBDMAP = PRTSUM , DMAP STATEMENT NO. 41



0 * * * * A N A L Y S I S S U M M A R Y T A B L E * * * *
0 SEID PEID PROJ VERS APRCH SEMG SEMR SEKR SELG SELR MODES DYNRED SOLLIN PVALID SOLNL LOOPID DESIGN CYCLE SENSITIVITY
--------------------------------------------------------------------------------------------------------------------------
0SEID = SUPERELEMENT ID.
PEID = PRIMARY SUPERELEMENT ID OF IMAGE SUPERELEMENT.
PROJ = PROJECT ID NUMBER.
VERS = VERSION ID.
APRCH = BLANK FOR STRUCTURAL ANALYSIS. HEAT FOR HEAT TRANSFER ANALYSIS.
SEMG = STIFFNESS AND MASS MATRIX GENERATION STEP.
SEMR = MASS MATRIX REDUCTION STEP (INCLUDES EIGENVALUE SOLUTION FOR MODES).
SEKR = STIFFNESS MATRIX REDUCTION STEP.
SELG = LOAD MATRIX GENERATION STEP.
SELR = LOAD MATRIX REDUCTION STEP.
MODES = T (TRUE) IF NORMAL MODES OR BUCKLING MODES CALCULATED.
DYNRED = T (TRUE) MEANS GENERALIZED DYNAMIC AND/OR COMPONENT MODE REDUCTION PERFORMED.
SOLLIN = T (TRUE) IF LINEAR SOLUTION EXISTS IN DATABASE.
PVALID = P-DISTRIBUTION ID OF P-VALUE FOR P-ELEMENTS
LOOPID = THE LAST LOOPID VALUE USED IN THE NONLINEAR ANALYSIS. USEFUL FOR RESTARTS.
SOLNL = T (TRUE) IF NONLINEAR SOLUTION EXISTS IN DATABASE.
DESIGN CYCLE = THE LAST DESIGN CYCLE (ONLY VALID IN OPTIMIZATION).
SENSITIVITY = SENSITIVITY MATRIX GENERATION FLAG.

No PARAM values were set in the Control File.

1 * * * END OF JOB * * *

 

[hezhj2000]

Usually you search 'FATAL' in the f06 file, and the first finding will give you the hint about your problem.
In your case, it is
'*** USER FATAL MESSAGE 9994 (BULKPM)
MAT1 with MID=2 near line 120381
User information: E:3.40282+38 is an illegal real value.'

Go check the E (Young's modulus) for material definition with ID 2.