SENSOR

Bulk Data Entry Sensors may be used to activate loads.

Format


(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
SENSOR	`SID`	`TYPE`	`STYPE`	`COMP`	`ID`

Continuation line if TYPE=TEMP


(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
	`LSID`	`GID`	`LBOUND/LTID`	`UBOUND/UTID`

Continuation line if TYPE=DISP, SPCF, or FORCE


(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
	`COND`	`CTYPE`	`LBOUND`	`UBOUND`
	`ACTION`	`ATYPE`

Example


(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
SENSOR	2	TEMP	4
	4	933	100.0	200.0

Definitions


Field	Contents	SI Unit Example
`SID`	Unique sensor identification number. No default (Integer > 0)
`TYPE`	Sensor type. TEMP Temperature. 1 2 DISP Displacement. SPCF SPC Force. FORCE Force. No default
`STYPE`	Sensor sub-type. SECTION Section Force (currently only supported for `TYPE`=FORCE). blank No default
`COMP`	Component of the specified `SENSOR` type. For `TYPE`=DISP or SPCF: TX, TY, TZ, RX, RY, RZ, T, or R For `TYPE`=FORCE: FX, FY, FZ, MX, MY, MZ, F, or M
`ID`	Entity ID for the specified `SENSOR` type. For `TYPE`=DISP or SPCF: Grid ID. For `TYPE`=FORCE: Section ID.
Descriptions for `TYPE`=TEMP:
`LSID`	Load set identification number of a QBDY1 or QVOL Bulk Data Entry. No default (Integer > 0)
`GID`	Grid or scalar point identification number. No default (Integer > 0)
`LBOUND/LTID`	Lower bound of the temperature range, or the table identification number of a TABLEDi entry which specifies the lower bound as a function of time. No default (Real or Integer)
`UBOUND/UTID`	Upper bound of the temperature range, or the table identification number of a TABLEDi entry which specifies the upper bound as a function of time. No default (Real or Integer)
Descriptions for `TYPE`=DISP, SPCF, and FORCE 3
`COND`	Continuation line flag indicating that condition information is to follow.
`CTYPE`	Condition type. BOUND Upper and lower bounds indicate the actual bounds of the defined sensor component. SLOPE Upper and lower bounds indicate the bounds of the gradient (with respect to time) between the current and previous timesteps. DROP Only lower bound is allowed for the DROP condition type. With DROPT, if the difference between the maximum value of this sensor (in the previous timesteps) and the current value of the sensor drops below the specified lower bound, this condition is triggered. No default
`LB`, `UB`	Lower and upper bounds, which are interpreted based on the defined Condition Type (`CTYPE`). No default (Real)
`ACTION`	Continuation line flag indicating that action type information is to follow.
`ATYPE`	Action type. This specifies the action performed when the above conditions are satisfied. WARN A warning message is issued and the solution continues. ERROR The current subcase is stopped and an ERROR message is issued. The job then proceeds to the next subcase (unless the next subcase is a continuation subcase).

Comments

A SENSOR with TYPE=TEMP can only be activated once. Sensor with TYPE=TEMP is supported only for Transient (linear and nonlinear) Heat Transfer analysis.
The presence of the SENSOR Bulk Data Entry with TYPE=TEMP turns off the referenced LSID loading outside the defined temperature range and turns on the LSID loading inside the temperature range (LBOUND/LTID to UBOUND/UTID).
SENSORs of TYPE=DISP, SPCF, and FORCE are only supported for Implicit Nonlinear Static and Implicit Nonlinear Transient analyses. Any number of conditions and actions can be specified, and the corresponding conditions and actions are appropriately combined.