HyperMesh and BatchMesher

Sensors entitySensors-24

Sensors entitySensors-24

Previous topic Next topic Expand/collapse all hidden text  

Sensors entitySensors-24

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Sensor entities are used to define and store sensors typically used in safety analysis.  Sensors are shown under the Sensor folder within the Model browser.

Sensors do not have a display state.

Sensors have an active and export state.  The active state of a sensor controls the listing of the sensor in the Model browser and any of its views.  If a sensor entity is active, then it is listed in the Model browser and any of its views.  If a sensor entity is inactive, then it is not listed in the Model browser or any of its views.

The export state of a sensor entity controls whether or not that sensor is exported when the custom export option is utilized.  The all export option is not affected by the export state of a sensor.  The active and export states of sensor entities can be controlled using the Entity State browser.

The data names associated with sensors can be found in the data names section of the HyperMesh Reference Guide.

 

The following panels can be used to create and edit sensors:

Sensors

Solver Card Support for Sensors


hmtoggle_arrow1RADIOSS

Supported Card

Solver Description

Supported Parameters

Notes

ACCEL

Defines accelerometers using a node and skew system.

 

 

/GAUGE

Defines gauges.

 

 

/SENSOR

Describes the sensors.

 

 

/SENSOR/ACCE/

Accelerometer.

 

 

/SENSOR/AND/

ON as long as sensors sensor_ID1 AND sensor_ID2 are ON.

 

 

/SENSOR/DIST/

Nodal distance.

 

 

/SENSOR/GAUGE

 

 

 

/SENSOR/INTER/

Interface activation and deactivation.

 

 

/SENSOR/NOT/

ON as long as sensor_ID1 is OFF.

 

 

/SENSOR/OR/

ON as long as sensors sensor_ID1 OR sensor_ID2 are ON.

 

 

/SENSOR/RBODY

 

 

 

/SENSOR/RWAL/

Rigid wall activation and deactivation.

 

 

/SENSOR/SECT

 

 

 

/SENSOR/SENS/

Activation with sensor_ID1, deactivation with sensor IS2.

 

 

/SENSOR/TIME/

Start time.

 

 

hmtoggle_arrow1OptiStruct

Supported Card

Solver Description

Supported Parameters

Notes

MARKER

Defines a marker used in multi-body dynamics.

 

Defined in the Markers panel.

hmtoggle_arrow1LS-DYNA

Supported Card

Solver Description

Supported Parameters

Notes

*DATABASE_CPM_SENSOR

Activates an ASCII file "cpm_sensor". Its input defines sensors' locations based on the positions of some Lagrangian segments. The output gives the history of the velocity, temperature, density, and pressure averaged on the number of particles contained in the sensors.

DT, BINARY

ArrayCount

 

*PART_SENSOR

Links part/component to a sensor to activate and deactivate during the analysis.

PID, SIDA, ACTIVE

This is supported as an attribute to an element to maintain its associativity with element inside HyperMesh

*SENSOR_CONTROL

Applies sensor result on an entity during run.

TYPE, TYPEID, INITSTT, SWIT

Number of Switch

 

*SENSOR_DEFINE_
ELEMENT

Strain gauge type sensor.

ETYPE, ELEMID, COMP, CTYPE

 

*SENSOR_DEFINE_
FORCE

Force transducer type sensor.

FTYPE, TYPEID, CRD

Vector Type (X, Y, Z, XMOMENT, YMOMENT, ZMOMENT, VECTOR)

 

*SENSOR_DEFINE_NODE

Accelerometer type sensor.

NODE1, NODE2, CRD, CTYPE

Vector Type (X, Y, Z, VECTOR)

 

*SENSOR_DEFINE_
CALC-MATH

Perform mathematical calculations on sensor values.

CALC, SENS

Number of Sensors

 

*SENSOR_SWITCH

Compares sensor value with input value and gives a logical signal.

TYPE, SENSID, LOGIC, VALUE, TIMWIN

 

*SENSOR_SWITCH_
CALC-LOGIC

Performs mathematical calculations on the logical signal from sensor logic.

SWIT1

Number of Switch

Switch 1 Option

 

hmtoggle_arrow1MADYMO

Supported Card

Solver Description

Supported Parameters

Notes

ACTUATOR

ACTUATOR.BODY applies a concentrated load (force or torque) on a single body with the magnitude of a selected input signal, in the direction specified by the user.

ACTUATOR.BODY_REL  applies a concentrated load, being a force or torque, on two bodies with the magnitude given by a selected input signal, at user specified points on those bodies.

ACTUATOR.JOINT_BRAKE applies a concentrated Coulomb friction load on the parent body of a joint with the magnitude of a selected input signal multiplied by the gain, the friction coefficient and the reaction load on the corresponding child body.

ACTUATOR.JOINT_POS applies a concentrated load on the parent body of a joint with the magnitude of a selected input signal and the reaction load on the corresponding child body.

TYPE (BODY, BODY_REL, JOINT_BRAKE, JOINT_POS)

INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL)

INPUT REF

LOAD_TYPE (FORCE, TORQUE)

CRDSYS (REF_SPACE, OBJECT)

LOAD_DIR (X, Y, Z)

POINT_OBJECT_1.MB (OBJECT, REF_SPACE)

POS (X, Y, Z)

define POINT_OBJECT_1.MB or select POINT_OBJECT_1.REF? (OBJECT, REF)

COMMENT

 

CONTROLLER

Proportional integrating and differentiating controller

TYPE (PID)

CONTROL_SYSTEM

INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL)

INPUT_REF, GAIN, TAUI, TAUD, COMMENT

 

OPERATOR

 

TYPE (DELAY, FUNC, MULTIPLY, SUM)

CONTROL_SYSTEM

INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL)

INPUT_REF

TIME_DELAY

COMMENT

 

PORT

Port selection for SWITCH.MULTI_PORT.

 

Defined on the card of the parent SWITCH.

SENSOR

 

TYPE (BODY, BODY_REL, CONTACT, JOINT, JOINT_CONSTRAINT, RESTRAINT, RETRACTOR, SURFACE_DIST)

SIGNAL_TYPE (ANG_DISP, ANG_VEL, ANG_ACC, LIN_POS, LIN_VEL, LIN_ACC, PLAN_ACC)

CRDSYS (OBJECT, REF SPACE)

VECTORX, VECTORY, VECTORZ

REF_SPACE, POS_X, POS_Y, POS_Z

define POINT_OBJECT_1.MB or select POINT_OBJECT_1.REF? (OBJECT, REF)

COMMENT

 

SIGNAL

 

TYPE (FUNC, EXTERNAL_INPUT, EXTERNAL_OUTPUT)

CONTROL_SYSTEM

ABS_VALUE (OFF/ON)

INTERPOLATION (LINEAR, SPLINE)

X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT

COMMENT

 

SIGNAL_VALUE

Signal value.

 

Defined on the card of the parent OPERATOR.

STATE

 

TYPE (CONTACT, FE_MODEL, INFLATOR, JOINT, JOINT_REMOVE, RESTRAINT_REMOVE)

SWITCH

NR_OF_CONTACTS

COMMENT

 

SURFACE.PLANE

Rectangular plane

multibody = BODY

N1 = POINT_1
N2 = POINT_2
N3 = POINT_3

To create a SURFACE under the SYSTEM.REF_SPACE, a reference to a null body must be selected because a reference to a multibody is required when creating a multibody plane. A null body can be created like any other BODY (card image is not relevant and should not be used),  Nullbody should be put under the SYSTEM.REF_SPACE assembly.

SWITCH

Switch on signal from a sensor.

TYPE (CONTROL_SYSTEM, LOGIC, MULTI-PORT, SENSOR, TIME, TIME_DELAY, TIME_FUNC)

INVERT (OFF,ON)

DYNAMIC_RELAX (NORMAL_ONLY, RELAX_ONLY, BOTH)

TIME_TYPE (ELAPSED, SIMULATION)

TIME

COMMENT

 

hmtoggle_arrow1PAM-CRASH 2G

Supported Card

Solver Description

Supported Parameters

Notes

SENSO /

Definition of a sensor

 

Types 2 and 4 are not supported.

SENSOR/

Definition of a sensor

 

Types 2 and 4 are not supported.

 

 

See Also:

Browsers

HyperMesh Entities & Solver Interfaces

Include Files

Model Setup