[Top] | [Previous] | [Next]

F-5. Attitude

TT&C Applications

F-5.1 Mission Planning

F-5.1.1 Output - SV attitude ephemeris

type : data transfer

to/from : to Attitude Ephemeris data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {time, state_vector}+

time - discrete time interval

state_vector - orbitial positon and velocity

status reply : DB write error

F-5.1.2 Output - Attitude events

type : data transfer

to/from : to Attitude Ephemeris data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {event_type, time, event }+

event_type - type of event (Orbital, RFI, Viewing)

time - time of event

event - description of event

status reply : DB write error

F-5.1.3 Output - Attitude maintenance activity

type : data transfer

to/from : to Timeline data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : anomaly, predicted_time

anomaly - attitude anomaly predicted

predicted_time - predicted time for the anomaly

status reply : DB write error

F-5.2 Telemetry

F-5.2.1 Input - Telemetry data (raw attitude data and sensor data)

type : data transfer

to/from : from Quality Assessed EU Measurands data

store or from Process Telemetry function

method : DB read or discrete message

sync/async : async DB read or async message

timing : none, or TBD for real-time attitude

API standards : SQL, OQL (for implementation)

data arguments : stream_id {id, value}+

stream_id - identifier for telemetry stream

id - identifier for telemetry measurand

value - value for telemetry measurand

status reply : none

F-5.3 Orbit

F-5.3.1 Input - SV Orbit ephemeris

type : data transfer

to/from : from Orbit Ephemeris data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)same comment as F-1.3.1 data arguments : {time, state_vector}+

time - discrete time interval

state_vector - orbitial positon and velocity

status reply : DB read error

F-5.3.2 Input - Orbit events

type : data transfer

to/from : from Orbit Ephemeris data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {event_type, time, event }+

event_type - type of event (Orbital, RFI, Viewing)

time - time of event

event - description of event

status reply : DB read error

Mission Specific Applications

F-5.4 Vehicle Contractor

F-5.4.1 Input - sensor specs and geometries

type : data transfer

to/from : from vehicle contractor

method : DB read

sync/async : async

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, sensor_data, TBD

vehicle_id - identifier for space vehicle

sensor_data - data items describing sensor data

status reply : DB read error