Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Documentation for structure of UNV files

Siemens Phenom Siemens Phenom
Siemens Phenom

Dataset 164 contains unit information

 

Universal File Dataset Number 164

Re: Documentation for structure of UNV files

Phenom
Phenom

Hello Jim,

thank you for answering. I seek for the method to define a specific measurement unit of an explicit user-defined output result, e.g. for density. That is : MASS / LENGTH ^3

The values which are placed in Data block 2414 for density are given in g/cm³ with 7.85 but in t/mm³ with 7.85e-9.

The question is: Does NX converts the values when importing UNV file?

I believe it would be good if the UNV file would contain the information that the artificial result values of "Density" are given in g/cm³ or in t/mm³ but at least (mass unit)/(length unit)^3. - Is that possible?

Best wishes, Michael

| Production: NX10; Development: VB, TCL/TK, FORTRAN; Testing: NX11 | engelke engineering art GmbH, Germany
| Kudos for good posts! And if my post answers your question, please mark it as an "Accepted Solution".

Kick Off (2015-09-14)On the Map (2016-10-21)1st Gear 2018 (2018-02-19)To the Rescue (25, ‎2018-02-24)5th Birthday! (2018-02-25)Popular (100, ‎2018-10-30)Prolific (100, 2019-02-27)Philosopher (500, ‎2019-02-28)

Re: Documentation for structure of UNV files

Gears Legend Gears Legend
Gears Legend

@MiDi1791 - The short answer to your question is "No", Simcenter does not convert the values when importing the UNV values in a 2414 dataset.

Rather, it assigns units to those values based upon the Result type specified in 2414 (Record 9, Field 4) and the Units Code in the 164 dataset (Record 1, Field 1 & Record 2) or the units you specify in the Import Results dialog box.

For example, if the Result in 2414 is set to 116 (Mass Density) and one of the values is 2,000 then:

  • If the Units Code in 164 is 1 (SI: Meter newton) then it will show up as 2,000 kg/m^3
  • If the Units Code in 164 is 10 (MN: mm newton) then it will show up as 2,000 t/mm^3

Another method you could use is to set the Result in 2414 to 94 (Unknown Scaler) and then Simcenter will view the results as unitless. In this case, specify the units in the RESULT_NAME_KEY in 2414 (Record 4, Field 1) and they will show up in both the Navigator and the graphics window.

A benefit of specifying a Result in 2414 that actually matches the units of the values is that you can use the Units dropdown in the Set Results dialog box to convert the units that are displayed.

Re: Documentation for structure of UNV files

Phenom
Phenom

@JamesD, thank you for answering.

I think  now I can solve all my problems in post processing for density and Young's modulus.

 

Density :

    -1
  2414
         1
LOADCASE_NAME_KEY MODEL Description
         2
RESULT_NAME_KEY Density
NONE
NONE
NONE
NONE
         1         1         1       116         2         1
         1         0         1         0         1         0         0         0
         0         0
  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00
  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00

 

Young's modulus:

I couldn't find Young's modulus so I decide to use a stress component instead. It has  the same measurement unit. Therefore, my declaration are conform to correct units and transformable. That is good.

LOADCASE_NAME_KEY Model Description
         2
RESULT_NAME_KEY Young's modulus
NONE
NONE
NONE
NONE
         1         1         1         2         2         1
         1         0         1         0         1         0         0         0
         0         0
  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00
  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00  0.00000E+00

 

I did play with the record values of DATA Block 164, Record 1, Field 1.

I couldn't find any changings by modifying from

                                = 1 - SI: Meter (newton) or

                                = 5 - MM: mm (milli newton)

to

                               = 7 - IN: Inch (pound f)

    -1
   164
         7                             2
    1.000000000000000E+03    1.000000000000000E+03    1.000000000000000E+00
    2.731500000000000E+02
    -1

NX ignores that value and only uses the scaling factors acc. to SI units of Record 2.

That's also understandable because the scaling factors can be used independently to declare combinations which are not provided by declaration with integer values in Record 1 Field 1.

 

So, work is done. Thank you all! Best wishes, Michael

| Production: NX10; Development: VB, TCL/TK, FORTRAN; Testing: NX11 | engelke engineering art GmbH, Germany
| Kudos for good posts! And if my post answers your question, please mark it as an "Accepted Solution".

Kick Off (2015-09-14)On the Map (2016-10-21)1st Gear 2018 (2018-02-19)To the Rescue (25, ‎2018-02-24)5th Birthday! (2018-02-25)Popular (100, ‎2018-10-30)Prolific (100, 2019-02-27)Philosopher (500, ‎2019-02-28)

Re: Documentation for structure of UNV files

Gears Legend Gears Legend
Gears Legend

Michael,

 

I'm glad you were able to get to a solution. As you observed, for Dataset 164 you can't just change Record 1 (the units class info), you have to also change Record 2 (the scaling factors). In the Universal File Dataset Number 164 Help file that @JimB previously shared, the example they show is for units class 2 - BG: Foot (pound f):

 

    -1
   164
         2Foot (pound f)               2
  3.28083989501312334D+00  2.24808943099710480D-01  1.79999999999999999D+00
  4.59670000000000002D+02
    -1

 

If you want to use units class 7, you just need to modify the length scale factor (Record 2, Field 1)

 

 

Regards,

 

James

Re: Documentation for structure of UNV files

Phenom
Phenom

James,

oh no, I want to use "mm" and "mN" like NX expects from its common NASTRAN solutions. Therefore, my scaling factors are both 1'000. Indicating "7" only should show that nothing happens by changing that Field.

With regards, Michael

| Production: NX10; Development: VB, TCL/TK, FORTRAN; Testing: NX11 | engelke engineering art GmbH, Germany
| Kudos for good posts! And if my post answers your question, please mark it as an "Accepted Solution".

Kick Off (2015-09-14)On the Map (2016-10-21)1st Gear 2018 (2018-02-19)To the Rescue (25, ‎2018-02-24)5th Birthday! (2018-02-25)Popular (100, ‎2018-10-30)Prolific (100, 2019-02-27)Philosopher (500, ‎2019-02-28)