HP Moonshot 1500 Chassis User Manual Page 118

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 117
Get SEL time command
This command returns the time from the SEL device. This time is used by the SEL device for event
timestampting.
Table 84 Get SEL time command request and respond data
Data field
Response data byte
number
Completion code1
Present timestamp clock reading. LS byte first.2:5
Data fieldRequest data byte
number
Time in four byte format. LS byte first.1:4
Set SEL time command
This command initializes the time in the SEL device. This time is used by the SEL device for event
timestamping.
Table 85 Set SEL time command response data
Data field
Response data
byte number
Completion code.1
SDR repository device commands
The following sections describe the commands that an SDR repository device provides for accessing
the SDR repository. The commands are designed to simplify the SDR repository device’s
implementation by pushing back intelligence to higher-level software where possible. The SDR
repository device is not intended to be a database engine. Thus, the SDR access commands do
not include automatic search functions. It is recommended that an application read the SDR
repository into a RAM buffer and work from that copy (keeping track of the SDR timestamp to check
for possible changes to the SDR repository). The general procedure for reading SDRs from the SDR
repository is described under the get sdr command.
As with event messages, the commands are designed so that the SDR repository device is isolated
and does not need to know the content and format of the SDR records themselves.
SDR record IDs
In order to generalize SDR access, sensor data records are accessed using a record ID number.
There are a fixed number of possible record IDs for a given implementation of the SDR repository.
The most common implementation of record IDs is as a value that translates directly to an index
or offset into the SDR repository. However, it is also possible for an implementation to provide a
level of indirection, and implement record IDs as handles to the SDRs.
Record ID values may be recycled so that the record ID of a previously deleted SDR can be used
as the record ID for a new SDR. The requirement is that, at any given time, the record IDs are
unique for all SDRs in the repository.
Record IDs can be reassigned by the SDR repository device as needed when records are added
or deleted. An application that uses a record ID to directly access a record should always verify
that the retrieved record information matches up with the ID information (slave address, LUN, sensor
ID, and so on) of the desired sensor. An application that finds that the SDR at a given record ID
has moved needs to re-enumerate the SDRs by listing them out using a series of get sdr commands.
It is not necessary to read out the full record data to see if the record ID for a particular record has
118 Command specification
Page view 117
1 2 ... 113 114 115 116 117 118 119 120 121 122 123 ... 188 189

Comments to this Manuals

No comments