- General Information
- Server Administration
- Mission Database
- Data Management
- Data Links
- Processors
- Commanding
- Services
- Global Services
- Instance Services
- Alarm Recorder
- Command History Recorder
- Event Recorder
- CCSDS TM Index
- Parameter Archive Service
- Parameter List Service
- Parameter Recorder
- Processor Creator Service
- Replay Server
- System Parameters Service
- XTCE TM Recorder
- Time Correlation Service
- Timeline Service
- Replication Master
- Replication Slave
- CCSDS File Delivery Protocol (CFDP)
- File listing service
- CFS Event Decoder
- Security
- Web Interface
- Programs
Yamcs Release Notes
Yamcs HTTP API
Source Code Documentation
XTCE TM Recorder¶
Records XTCE TM sequence containers. This service stores the data coming from one or more streams into a table tm
. The tm table has a column called pname
which stands for packet name. The main task of this service is to assign the value for that column; all the other columns will come directly from the tm stream as provided by the data links.
The pname is a fully qualified name of a matching XTCE container. In the XTCE hierarchy some containers have a flag useAsArchivingPartition
(this flag is an Yamcs extension to XTCE). That flag is used to determine the container that will give its name to the packet when saved into the tm table - the name of the lowest level matching container with this flag set is chosen as the pname. If no container matches, then the name of the root container will be used.
Class Name¶
Configuration¶
This service is defined in etc/yamcs.instance.yaml
. Example:
services:
- class: org.yamcs.archive.XtceTmRecorder
streamConfig:
tm:
- tm_realtime
- tm_dump
With this configuration containers coming from both the tm_realtime and tm_dump streams are stored into the table tm
.
Configuration Options¶
- streams (list of strings)
The streams to record. When unspecified, all
tm
streams defined instreamConfig
are recorded.