-
Key: XTCE12-148
-
Legacy Issue Number: 9221
-
Status: closed
-
Source: Anonymous
-
Summary:
There are no specific descriptions of onboard memory possible, i.e. block size, addressing technique, etc as per tables 12, 13 of the ECSS. This I would expect at the space-system
description level?Onboard memory is a very specific type of space system element, for which a lot of specific data is always needed, and it would be worth making specific entry types appropriate to onboard memory system elements. This to include Memory ID, Accessibility (read,write), smallest addressable unit, addressing technique, block length, subblock symbolic name, subblock offset, subblock length, etc
-
Reported: XTCE 1.0 — Thu, 1 Dec 2005 05:00 GMT
-
Disposition: Closed; Out Of Scope — XTCE 1.2
-
Disposition Summary:
Should be considered as a future specification
Onboard memory handling between different spacecraft and ground systems has been even more varied than commands and telemetry. To the extent that onboard memory locations can be named and brought down as "software telemetry" they are supported by XTCE, however, an exchange format for memory definitions beyond telemetry parameter definition is out of the current scope. It is possible that this could be addressed by a future specification, but there are also numerous specifications for memory data for ordinary ground-based computer systems (Motorola S-records, Intel Hex format, Unix STABs, etc.) that may be applicable.
-
Updated: Tue, 10 Jul 2018 14:22 GMT
XTCE12 — OnBoard Memory
- Key: XTCE12-148
- OMG Task Force: XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF