Ensor, Eading, Ommand – ADLINK aTCA-6200A User Manual

Page 36: 5 get sensor reading command

Advertising
background image

36

09h system firmware (EFI / BIOS) change
0Ah SMBIOS change
0Bh operating system change
0Ch operating system loader change
0Dh service or diagnostic partition change
0Eh management software agent change
0Fh management software application change
10h management software middleware change
11h programmable hardware change (e.g. FPGA)
12h board/FRU module change (change of a module

plugged into associated entity)

13h board/FRU component change (addition or

removal of a replaceable component on the
board/FRU that is not tracked as a FRU)

14h board/FRU replaced with equivalent version
15h board/FRU replaced with newer version
16h board/FRU replaced with older version
17h board/FRU hardware configuration change (e.g.

strap, jumper, cable change, etc.)

4.2.5

Get Sensor Reading Command

Byte Data field

Request data

1

Sensor Number (FFh = reserved)

1 Completion

Code

2 Sensor

reading

Byte 1: byte of reading. Ignore on read if sensor does not return an
numeric (analog) reading.

3

[7] - 0b = All Event Messages disabled from this sensor
[6] - 0b = sensor scanning disabled
[5] - 1b = reading/state unavailable (formerly “initial update in progress”).
This bit is set to indicate that a ‘re-arm’ or ‘Set Event Receiver’ command
has been used to request an update of the sensor status, and that update
has not occurred yet. Software should
use this bit to avoid getting an incorrect status while the first sensor
update is in progress. This bit is only required if it is possible for the
controller to receive and process a ‘Get Sensor Reading’ or ‘Get Sensor
Event Status’ command for the sensor before the update has completed.
This is most likely to be the case for sensors, such as fan RPM sensors,
that may require seconds to accumulate the first reading after a re-arm.
The bit is also used to indicate when a reading/state is unavailable
because the management controller cannot obtain a valid reading or
state for the monitored entity, typically because the entity is not present.
For more in formation, please see Section 16.4, Event Status, Even
Conditions, and Present State
and Section 16.6, Re-arming on the PICMG
specification 3.0.
[4:0] - reserved. Ignore on read.

Response data

4

For threshold-based sensors
Present threshold comparison status

Advertising