1
Download CGS User Manual
Transcript
astrium Space Infrastructure 6.4.3.6.3 Dok.Nr./Doc. No.: CGS–RIBRE–SUM–0001 Ausgabe/Issue: Überarbtg./Rev.: Seite/Page: 1 B 6–134 Datum/Date: Datum/Date: von /of: 19.10.2001 02.08.2002 6–185 EGSE_BINARY_PACKET This is a parameterizable MDB end–item defining a packet of data items sent within a data buffer. This end–item type defines a stimulus having a stream of binary data as contents. The enditem is sent to an SAS within a GDU. It is a parameterized end item type with up to 255 parameters. The data stream associated with the enditem may consist of up to 4096 bytes. Similar to the other stimulus definitions, the enditem definition contains some general information, physical address information and a parameter list. In addition, however, the necessary data to describe the layout of the binary packet has to be provided in the following aggregates: Bit stream layout description. This aggregate describes the predefined static bit patterns used for initializing the binary packet, i.e. the byte stream associated with it. a Command Verification Description, which is optional See EGSE_ANALOG_STIMULUS Formal parameter list (up to 255 parameters are allowed). For each parameter: – A common parameter declaration source, defining the names, the types and the default values for the parameters in UCL syntax. This source definition must be compiled with the CLS_Editor (to be called via the “tools” menu entry of I_MDB) – The following parameter types are supported: STRING,STATECODE,INTEGER,UNSIGNED_INTEGER,REAL,LONG_REAL,PATH NAME,TIME,BYTE,WORD,LONG_WORD,BYTE_STRING – The definition of the place in the data buffer where the parameter shall be replaced within the packet during online sending: offset, and length – a decalibration description which is optional. Depending on the parameter type, this may be analog (INTEGER, UNSIGNED_INTEGER,REAL,LONG_REAL) or discrete (STATE_CODE) decalibration – an optional raw value description. – an optional engineering value description. Note: Parameter are specified by the CLS Editor as usual, e.g. : (PARA1: INTEGER := 3.14); The meaning of the formal parameter list defined with this enditem is somehow different from the one defined for the other stimuli enditems. Here, the formal parameters defined for the binary packet will be substituted at run–time into the data buffer by CGS. The logic with respect to the handling of the bitstream layout and parameters is that first the static bit patterns defined by bitstream layout is put into the data buffer and then the actual values of the formal parameters will be substituted, possibly overwriting the static bits. Note: Binary Packets are issued via the UCL Issue command, as in: ISSUE (\A\B\C (123, 1.0, 100, $ON), stat); The enditem is only used for checkout (VICOS). Copyright per DIN 34
