**IEEE P1451.3 Proposal**

+-----------------+----------------------------------------------------+
| Proposal Title: | Miscellaneous Modifications                        |
+-----------------+----------------------------------------------------+
| Proposal        | 03-006                                             |
| Number:         |                                                    |
+-----------------+----------------------------------------------------+
| Revision        | A                                                  |
| Number:         |                                                    |
+-----------------+----------------------------------------------------+
| Date:           | 37671.38                                           |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| Name:           | Mark Slack                                         |
+-----------------+----------------------------------------------------+
| Company:        | Boeing Commercial Airplanes                        |
+-----------------+----------------------------------------------------+
| Phone Number:   | 206-662-4771                                       |
+-----------------+----------------------------------------------------+
| Fax Number:     |                                                    |
+-----------------+----------------------------------------------------+
| Email Address:  | mark.b.slack@boeing.com                            |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| Proposal        | Initial Draft                                      |
| Status:         |                                                    |
|                 | [X]{.underline} Revised Draft                      |
|                 |                                                    |
|                 | Ready for Vote                                     |
+-----------------+----------------------------------------------------+
| Impacts:        | \_\_                                               |
|                 |                                                    |
|                 | \_\_                                               |
+-----------------+----------------------------------------------------+
| Action:         | \_\_ Approved                                      |
|                 |                                                    |
|                 | \_[X]{.underline}\_ Approved with changes          |
|                 |                                                    |
|                 | \_\_ Rejected                                      |
|                 |                                                    |
|                 | \_\_ Returned for revision                         |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+

# Background:

The changes proposed herein are a direct result of anticipating how a
Transducer Block will interpret information in various TEDS. These
changes were originally included in Part B of P03-004. That proposal was
rejected by the Working Group with the expectation that Part B would be
advanced as an independent proposal.

Among other minor fixes, we have recognized that the original definition
of Channel Groups was actually two semantically distinct categories of
Channel Groups. Herein, we propose to separate the specification into
Control Groups and Vector Group.

# Proposal:

Clause 3 \-- Definitions

::: definition
**3.2.11 Code-Division Multiple Access:** Code-Division Multiple Access
(CDMA) uses ...
:::

::: definition
**3.2.12 CommunicationsChannel:** For the purposes of this standard,
\...
:::

::: definition
**3.2.13** **ControlGroup:** ControlGroups are manufacturer
specifications that define the inherent relationships between the
TransducerChannels of a multi-channel TBIM. This ControlGrouping
information is not normally used by the TBIM itself. This information is
used to identify TransducerChannels that are used to control some
characteristic of another TransducerChannel. For example, a ControlGroup
could be used to identify an actuator that is used to set the threshold
of an analog event sensor.
:::

::: definition
**3.2.67 VectorGroup:** VectorGroups are manufacturer specifications
that define the inherent relationships between the TransducerChannels of
a multi-channel TBIM. This VectorGrouping information is not normally
used by the TBIM itself. This information is normally used by bus
controller applications to properly compose human readable displays or
in formulating other computations. For example, VectorGroupings may be
used to indicate which TransducerChannels represent the three vector
axes of a three-axis vector measurement.
:::

Clause 4 \-- Data types

Break Table 1 into 2 components to assign manifest constant. No change
to textual description

Table 1---Physical units data type structure

  ----------- --------------------------------------------------- -------- ----------
  **Field**   **Description**                                     **Data   **Number
                                                                  Type**   of
                                                                           octets**

  1           Physical units interpretation \-- see Table 2       U8E      1

  2           (2 \* \<exponent of radians\>) + 128                U8C      1

  3           (2 \* \<exponent of steradians\>) + 128             U8C      1

  4           (2 \* \<exponent of meters\>) + 128                 U8C      1

  5           (2 \* \<exponent of kilograms\>) + 128              U8C      1

  6           (2 \* \<exponent of seconds\>) + 128                U8C      1

  7           (2 \* \<exponent of amperes\>) + 128                U8C      1

  8           (2 \* \<exponent of kelvins\>) + 128                U8C      1

  9           (2 \* \<exponent of moles\>) + 128                  U8C      1

  10          (2 \* \<exponent of candelas\>) + 128               U8C      1
  ----------- --------------------------------------------------- -------- ----------

Table 2---Physical units interpretation

  ----------- -------------------------- ----------------------------------------
  **Value**   **Manifest constant**      **Definition**

  0           PUI_SI_UNITS               Unit is described by the product of SI
                                         base units, plus radians and steradians,
                                         raised to the powers recorded in fields
                                         2 through 10. Units for some quantities,
                                         such as the number of people through a
                                         turnstile, cannot be represented using
                                         these units. Enumeration zero, with
                                         fields 2-10 set to 128, is the
                                         appropriate enumeration for these cases
                                         when a quantity is being defined.

  1           PUI_RATIO_SI_UNITS         Unit is U/U, where U is described by the
                                         product of SI base units, plus radians
                                         and steradians, raised to the powers
                                         recorded in fields 2 through 10.

  2           PUI_LOG10_SI_UNITS         Unit is log~10~(U), where U is described
                                         by the product of SI base units, plus
                                         radians and steradians, raised to the
                                         powers recorded in fields 2 through 10.

  3           PUI_LOG10_RATIO_SI_UNITS   Unit is log~10~(U/U), where U is
                                         described by the product of SI base
                                         units, plus radians and steradians,
                                         raised to the powers recorded in fields
                                         2 through 10.

  4           PUI_DIGITAL_DATA           The associated quantity is digital data
                                         (e.g. a bit vector) and has no unit.
                                         Fields 2-10 shall be set to 128. The
                                         \"digital data\" type applies to data
                                         that does not represent a quantity, such
                                         as the current positions of a bank of
                                         switches.

  5           PUI_ARBITRARY              The associated physical quantity is
                                         represented by values on an arbitrary
                                         scale (e.g. hardness). Fields 2-10 are
                                         reserved, and shall be set to 128.

  6-255       ---                        Reserved
  ----------- -------------------------- ----------------------------------------

Clause 5 \-- Functional spec

New sub-clause, inserted before 5.6 (TransducerChannel Proxy)

**5.6 TransducerChannel groups**

There are two types of TransducerChannel groups defined in this
standard. They are ControlGroups and VectorGroups. They are similar in
implementation but are used for two different functions.

**5.6.1** **ControlGroups**

ControlGroups are used to define collections of TransducerChannels when
one TransducerChannel is the primary channel and the remaining
TransducerChannels in the group provide either additional information
about the primary TransducerChannel or are used to control some aspect
of the primary TransducerChannel. For example, a ControlGroup can be
used to define up to three additional TransducerChannels associated with
an analog event sensor. One is a sensor that is used to measure the
analog input to the event sensor. The second is an actuator that is used
to set the threshold for the event sensor. The third is an actuator that
can be used to set the hysteresis for the event sensor. **5.6.2
VectorGroups**

VectorGroups are used to define relationships between TransducerChannels
within a single multi-channel TBIM that imply a display or mathematical
relationship between the TransducerChannels. For example, they can be
used to identify the relationships between the components of a
three-axis accelerometer. VectorGroups are used by the software in the
TBC/NCAP or host processor to group the outputs of the individual
TransducerChannels into vectors for display or computational purposes.

Note: VectorGroups are in some ways similar to TransducerChannel
proxies. TransducerChannel proxies are used to identify
TransducerChannels that are grouped together for reasons such as
efficient transmission of the data and/or simultaneous triggering.
Proxies may or may not represent a vector for display or computational
purposes. However, it is recommended that all vectors be implemented as
proxies, especially in spatial vector applications (like velocity or
acceleration), where the measurements of the three components at
different points in time could lead to misinterpretation.

Change Meta-TEDS

**7.3.2 Data block**

Table [37]{.mark} summarizes the content of the data block. Subordinate
subclauses explain each data field in this data block.

Table 37---Structure of the Meta-TEDS data block

  ------- ---------------------------------------------- ---------- --------
  Field   Description                                    Type       \#
                                                                    octets

  ---     Length                                         U32L       4

  1       TEDS identifier                                U8E        1

  2       IEEE P1451 standards family number             U8E        1

  3       TEDS version number                            U8E        1

  ---     Timing related information                     ---        ---

  4       TEDS hold-off time (t~th~)                     F32        4

  5       Operational hold-off time (t~oh~)              F32        4

  6       Load current drawn from the transducer bus     F32        4

  7       Multi-range Capability                         U8E        1

                                                                    

                                                                    

                                                                    

                                                                    

                                                                    

                                                                    

  ---     ControlGroup information sub-block             ---        ---

  8       Number of ControlGroups (N~c~)                 U8C        1

  ---     Fields 9, 10, and 11 comprise a structure that ---        ---
          defines one ControlGroup. All ControlGroup                
          structures (N~c~ occurrences) shall be                    
          specified consecutively.                                  

  9       ControlGroup type                              U8E        1

  10      Number of TransducerChannels in the            U8C        1
          ControlGroup (NT~c~)                                      

  11      ControlGroup member list                       array of   NT~c~
                                                         U8E        

  ---     VectorGroup information sub-block              ---        ---

  12      Number of VectorGroups (N~v~)                  U8C        1

  ---     Fields 13, 14, and 15 comprise a structure     ---        ---
          that defines one VectorGroup. All VectorGroup             
          structures (N~v~ occurrences) shall be                    
          specified consecutively.                                  

  13      VectorGroup type                               U8E        1

  14      Number of TransducerChannels in the            U8C        1
          VectorGroup (NT~v~)                                       

  15      VectorGroup member list                        array of   NT~v~
                                                         U8E        

  ---     TransducerChannel proxy definition sub-block   ---        ---

  16      Number of TransducerChannel proxies (N~p~)     U8C        1

  ---     Fields 17, 18, 19, and 20 comprise a structure ---        ---
          that defines one TransducerChannel proxy. All             
          proxy definition structures (N~p~ occurrences)            
          shall be specified consecutively.                         

  17      TransducerChannel number of the                U8E        1
          TransducerChannel proxy                                   

  18      TransducerChannel proxy data set organization  U8E        1

  19      Number of TransducerChannels represented by    U8C        1
          this proxy (NT~p~)                                        

  20      TransducerChannel proxy member list            array of   NT~p~
                                                         U8E        

  ---     Checksum                                       U16C       2
  ------- ---------------------------------------------- ---------- --------

**7.3.2.8 Number of ControlGroups**

Data type: unsigned octet integer used for enumeration (U8C, 1 octet)

This field identifies the number of ControlGroups that follow.

**7.3.2.9** **ControlGroup type**

Data type: unsigned octet integer used for enumeration (U8E, 1 octet)

This field contains the relationship between the TransducerChannels
comprising the specific ControlGroup. It is defined by the enumeration
in [Table 40]{.mark}.

Table 40---Enumeration of ControlGroup types

+-----+-----+-----------------------------------------------------------+
| Va  | En  | Meaning                                                   |
| lue | try |                                                           |
+-----+-----+-----------------------------------------------------------+
| 0   |     | Reserved                                                  |
+-----+-----+-----------------------------------------------------------+
| 1   | 1   | Analog event sensor TransducerChannel,                    |
|     |     |                                                           |
|     | 2   | Analog input sensor TransducerChannel                     |
|     |     |                                                           |
|     | 3   | Upper threshold embedded actuator TransducerChannel       |
|     |     |                                                           |
|     | 4   | Hysteresis embedded actuator TransducerChannel            |
+-----+-----+-----------------------------------------------------------+
| 2   | 1   | Sensor TransducerChannel (any type)                       |
|     |     |                                                           |
|     | 2   | High pass filter embedded actuator TransducerChannel      |
|     |     |                                                           |
|     | 3   | Low pass filter embedded actuator TransducerChannel       |
|     |     |                                                           |
|     | 4   | Scale factor embedded actuator TransducerChannel          |
+-----+-----+-----------------------------------------------------------+
| 3   | 1   | TransducerChannel (any type)                              |
|     |     |                                                           |
|     | 2   | Sample interval embedded actuator TransducerChannel       |
+-----+-----+-----------------------------------------------------------+
| 4   | 1   | Digital event sensor TransducerChannel                    |
|     |     |                                                           |
|     | 2   | Digital input sensor TransducerChannel                    |
|     |     |                                                           |
|     | 3   | Event pattern embedded actuator TransducerChannel         |
+-----+-----+-----------------------------------------------------------+
| 5   | 1   | Time interval sensor TransducerChannel                    |
|     |     |                                                           |
|     | 2   | TransducerChannel number of the transducer that causes    |
|     |     | the output of the time interval sensor to be latched.     |
+-----+-----+-----------------------------------------------------------+
| 6   | 1   | Time-of-day sensor TransducerChannel                      |
|     |     |                                                           |
|     | 2   | TransducerChannel number of the transducer that causes    |
|     |     | the output of the time-of-day sensor to be latched.       |
+-----+-----+-----------------------------------------------------------+
| 7   | 1   | TransducerChannel number of an event sensor used to       |
|     |     | trigger other transducers.                                |
|     | 2   |                                                           |
|     |     | The number, N, of transducers triggered by the event      |
|     | --- | sensor.                                                   |
|     |     |                                                           |
|     |     | The remaining N entries give a list of TransducerChannels |
|     |     | triggered by the event                                    |
+-----+-----+-----------------------------------------------------------+
| 8   | 1   | TransducerChannel (any type),                             |
|     |     |                                                           |
|     | 2   | Embedded time delay actuator TransducerChannel            |
+-----+-----+-----------------------------------------------------------+
| 9-  |     | Reserved for future expansion                             |
| 127 |     |                                                           |
+-----+-----+-----------------------------------------------------------+
| 1   |     | open to manufacturers                                     |
| 28- |     |                                                           |
| 255 |     |                                                           |
+-----+-----+-----------------------------------------------------------+

Enumerations 1 and 4 may be used to identify the embedded actuator
TransducerChannels used to set up an event sensor. They also identify a
sensor TransducerChannel that may be used to read the level of the
signal in an analog event sensor or the current pattern input to a
digital event sensor.

Enumeration 2 may be used to identify the embedded actuator
TransducerChannels used to set the high pass filter, low pass filter,
and scale factor associated with a sensor of any type.

Enumeration 3 is used to identify an embedded actuator TransducerChannel
that may be used to set the *TransducerChannel sampling period*.

**7.3.2.10** **Number of TransducerChannels in the ControlGroup**

Data type: unsigned octet integer used for enumeration (U8C, 1 octet)

This field identifies the number of TransducerChannels in the group,
which is the number of entries required in the list described in
[7.3.2.11]{.mark}.

**7.3.2.11 ControlGroup member list**

Data type: an array of unsigned octet integers used for enumeration
(U8E, 0 to 255 octets)

This field contains a one-dimensional array (list) of 1-octet elements.
Each element is the TransducerChannel number for a member in the
specific ControlGroup. The values of the elements in this list shall be
in the sequence specified by the *ControlGroup type* field.

An element with value zero shall indicate that the TransducerChannel
does not implement this particular element of the enumerated
relationship. For example, a ControlGroup describing an analog event
sensor that implements the ability to change the threshold and
hysteresis but does not implement a sensor to read the analog input
could be specified by (1,0,2,3), where the TransducerChannel number for
the event sensor is 1, for the threshold actuator is 2 and the
hysteresis actuator is 3.

NOTE---a TransducerChannel may be represented in multiple ControlGroups.

**7.3.2.12 Number of VectorGroups**

Data type: unsigned octet integer used for enumeration (U8C, 1 octet)

This field identifies the number of VectorGroups that follow.

**7.3.2.13** **VectorGroup type**

Data type: unsigned octet integer used for enumeration (U8E, 1 octet)

This field contains the relationship between the TransducerChannels
comprising the specific VectorGroup. It is defined by the enumeration in
Table [41]{.mark}.

Table 41---Enumeration of VectorGroup types

+-----+-----+----------------------------------------------------------+
| Va  | En  | Meaning                                                  |
| lue | try |                                                          |
+-----+-----+----------------------------------------------------------+
| 0   | --- | an arbitrary relation                                    |
+-----+-----+----------------------------------------------------------+
| 1   | 1   | x component of a right hand rectangular spatial vector   |
|     |     |                                                          |
|     | 2   | y component of a right hand rectangular spatial vector   |
|     |     |                                                          |
|     | 3   | z component of a right hand rectangular spatial vector   |
+-----+-----+----------------------------------------------------------+
| 2   | 1   | ρ component of a right hand cylindrical spatial vector   |
|     |     |                                                          |
|     | 2   | φ component of a right hand cylindrical spatial vector   |
|     |     |                                                          |
|     | 3   | z component of a right hand cylindrical spatial vector   |
+-----+-----+----------------------------------------------------------+
| 3   | 1   | r component of a right hand spherical spatial vector     |
|     |     |                                                          |
|     | 2   | θ component of a right hand spherical spatial vector     |
|     |     |                                                          |
|     | 3   | φ component of a right hand spherical spatial vector     |
+-----+-----+----------------------------------------------------------+
| 4   | 1   | latitude component of a planetary coordinate system      |
|     |     |                                                          |
|     | 2   | longitude component of a planetary coordinate system     |
|     |     |                                                          |
|     | 3   | altitude component of a planetary coordinate system      |
+-----+-----+----------------------------------------------------------+
| 5   | 1   | in-phase component of a 2-dimensional vector             |
|     |     |                                                          |
|     | 2   | quadrature component of a 2-dimensional vector           |
+-----+-----+----------------------------------------------------------+
| 6   | 1   | red component in a color vector                          |
|     |     |                                                          |
|     | 2   | green component in a color vector                        |
|     |     |                                                          |
|     | 3   | blue component in a color vector                         |
+-----+-----+----------------------------------------------------------+
| 7-  |     | Reserved for future expansion                            |
| 127 |     |                                                          |
+-----+-----+----------------------------------------------------------+
| 1   |     | open to manufacturers                                    |
| 28- |     |                                                          |
| 255 |     |                                                          |
+-----+-----+----------------------------------------------------------+

The arbitrary relation, when the enumeration value is equal to zero,
shall be used to convey VectorGroup semantics not specifically
enumerated by this subclause, but deemed necessary by the
TransducerChannel manufacturer, for the correct operation or
interpretation of the data related to the TransducerChannels that are
members of the VectorGroup.

The arbitrary relation may be used to convey that correct behavior of
TransducerChannels with coupling terms in the calibration assumes that
all TransducerChannels involved are triggered at the same time.

**7.3.2.14 Number of TransducerChannels in the VectorGroup**

Data type: unsigned octet integer used for enumeration (U8C, 1 octet)

This field identifies the number of TransducerChannels in the group,
which is the number of entries required in the list described in
[7.3.2.15]{.mark}.

**7.3.2.15 VectorGroup member list**

Data type: an array of unsigned octet integers used for enumeration
(U8E, 0 to 255 octets)

This field contains a one-dimensional array (list) of 1-octet elements.
Each element is the TransducerChannel number for a member in the
specific VectorGroup. The values of the elements in this list shall be
in the sequence specified by the *VectorGroup type* field.

An element with value zero shall indicate that the TransducerChannel
does not implement this particular element of the enumerated
relationship. For example, a two axis vector measurement implemented by
TransducerChannels 1 (x) and 2 (y) may be specified by designating the
*VectorGroup type* ([7.3.2.13]{.mark}) as 1 (x, y, z) with the
*VectorGroup member list* of (1, 2, 0). The value zero shall not appear
in the *VectorGroup member list* for a VectorGroup of *VectorGroup type*
'arbitrary relation.'

A TransducerChannel may not be represented in multiple VectorGroups.

**7.3.2.16 Number of TransducerChannel proxies**

No change to text for the remainder of 7.3. Paragraph numbers and
Table/Figure numbers ripple.

Incidental change TransducerChannel TEDS

**7.4.2.2 Calibration key**

Data type: unsigned octet integer used for enumeration (U8E, 1 octet)

This field contains an enumeration that denotes the calibration
capabilities of this TransducerChannel. Table [43]{.mark} provides the
list of enumerated values and their meanings. The column labeled "Name"
defines manifest constants to symbolize the enumerated values, and these
names are used throughout the remainder of this standard.

Table 43---Enumeration of calibration keys

  ------------- --------------------------------------------- -------------------
  Value         Calibration capability                        Name

  0             No calibration information needed or provided CAL_NONE
                by the TBIM. This implies that there is no    
                Calibration TEDS associated with this         
                TransducerChannel. See Note.                  

  1             Calibration information provided as a         CAL_SUPPLIED
                Calibration TEDS, as specified in 7.5.        
                Correction is performed outside of the TBIM.  

  2             (reserved)                                    \-

  3             Calibration information is provided but in a  CAL_CUSTOM
                form that is not described in this standard.  
                Correction is performed outside of the TBIM.  
                See Note.                                     

  4             Calibration information is provided as a      TBIM_CAL\_ SUPPLIED
                Calibration TEDS, as specified in 7.5.        
                Correction is applied in the TBIM. See        
                7.5.1.2 for additional details.               

  5             Calibration information is provided as a      TBIM_CAL_SELF
                Calibration TEDS, as specified in 7.5, and is 
                applied in the TBIM. The calibration is       
                adjusted by a self-calibration capability.    
                See 7.5.1.2 for additional details.           

  6             Calibration information is provided but in a  TBIM_CAL_CUSTOM
                form that is not described in this standard.  
                It may be a manufacturer-defined TEDS.        
                Correction is performed in the TBIM. See      
                Note.                                         

  7-255         Reserved                                      ---

  Note---If the                                               
  Calibration                                                 
  TEDS is                                                     
  accessed, the                                               
  Calibration                                                 
  TEDS Length                                                 
  shall be zero                                               
  ------------- --------------------------------------------- -------------------

**7.4.2.2.1 System corrections**

*Calibration key* enumerations CAL_SUPPLIED or CAL_CUSTOM are to be used
when the correction is performed in the NCAP, a host processor or
elsewhere in the system.

**7.4.2.2.2 TBIM corrections**

*Calibration key* enumerations TBIM_CAL_SUPPLIED and TBIM_CAL_SELF are
to be used when the correction is performed in the TBIM using the
correction method specified in [7.5.1.1]{.mark} and information stored
in the Calibration TEDS ([7.5.3]{.mark}). TBIM_CAL_CUSTOM is used when
the correction method is **not** the one specified in [7.5.1.1.]{.mark}

**7.4.2.3 TransducerChannel type key \<\<*No change\>\>***

**7.4.2.4 Physical units**

Data type: physical units (UNITS, 10 octets).

The physical units that apply to the TransducerChannel data. If the
*Calibration key* is CAL_SUPPLIED or CAL_CUSTOM, the physical units
apply only to the TransducerChannel data *after* correction for the case
of sensors, or *before* correction for the case of actuators.

See [4.11]{.mark} for details on how to construct the value placed in
the *Physical units* fields.

**7.4.2.5 Design operational lower range limit \<\<*No change\>\>***

**7.4.2.6 Design operational upper range limit \<\<*No change\>\>***

**7.4.2.7 Worst case uncertainty \<\<*No change\>\>***

**7.4.2.8 Self-test key \<\<*No change\>\>***

**7.4.2.9 Data model**

Data type: unsigned octet integer used for enumeration (U8E, 1 octet)

This field describes the data model used when issuing [Read
TransducerChannel data](#_Read_TransducerChannel_data_1) or [Write
TransducerChannel data](#_Write_TransducerChannel_data) commands to this
TransducerChannel. Values are enumerated in [Table 46]{.mark}.

Table 46---Enumeration of data models

  ----------- -------------------------------- ---------------------------
  Value       Model                            Constraint on\
                                               data model length

  0           N-octet integer (unsigned)       0≤N≤8

  1           Single precision real            N=4

  2           Double precision real            N=8

  3           N-octet fraction (unsigned)      0≤N≤8

  4           Bit sequence                     0≤N≤255

  5           Long integer (unsigned)          9≤N≤255

  6           Long fraction (unsigned)         9≤N≤255

  7           Time of day                      N=8

  8 - 255     Reserved for future expansion    ---
  ----------- -------------------------------- ---------------------------

There are two differences between the integer forms (enumeration zero
and five) and fractional forms (enumeration three and six):

The radix point (which divides integer from fractional bits) is to the
right of the least significant bit for N-octet integer. It is
immediately to the right of the most significant bit for N-octet
fraction.

Justification of the significant bits differs, as explained in the
*Model significant bits* field ([xxx]{.mark}).

The use of enumerations 5 and 6 is expected to be rare. An NCAP is not
expected to process data with these enumerations but may pass them on
unprocessed to the entity requesting the data.

The N-octet fraction type may be used to keep the multinomial
coefficients (see [xxx]{.mark}) within representable bounds and to avoid
overflows when converting the data to physical units.

The bit sequence data model is for collections of bits that have no
numeric value. An example of this type is the position of each switch in
a bank of switches. Bit significance is user defined.

Boolean data (such as {0,1} or {false, true}) shall be represented as a
bit sequence with a length of one octet, in which the data resides in
the least significant bit.

The Time of day data model supports Time-of-day (ToD) data types defined
in [4.13]{.mark}.

**7.4.2.10 Data model length \<\<*No change\>\>***

**7.4.2.11 Model significant bits**

Data type: unsigned 16-bit integer used for counting (U16C, 2 octets)

When the *Data model* is N-octet integer (enumeration 0 or 5) or N-octet
fraction (enumeration 3 or 6), the value of this field is the number of
bits that are significant.

> *For example, if data from a TransducerChannel comes from a 12-bit
> ADC, then:*
>
> *Data model = 0 (N-octet integer)*
>
> *Data model length = 2 (the number of octets needed to hold 12 bits)*
>
> *Model significant bits = 12*

When the *Data model* is N-octet integer, N-octet fraction, long integer
or long fraction, the *Model significant bits* shall not exceed eight
times the *Data model length*.

When the *Data model* is N-octet integer or long integer, the data bits
shall be right justified within the octet stream. *Model significant
bits* specifies the number of bits that are significant. A value of zero
is illegal.

When the *Data model* is N-octet fraction or long fraction, the data
bits shall be left justified within the octet stream. *Model significant
bits* is ignored.

When the *Data model* is single or double precision real (enumerations
one or two), the value of this field is the number of bits in the
TransducerChannel's signal converter.

When the *Data model* is Time of day, *Model significant bits* is
ignored.

Incidental change Calibration TEDS

**7.5.1.2 Application**

If the value of the *Calibration key* field (7.4.2.2) in the
TransducerChannel TEDS is CAL_SUPPLIED, the correction algorithm shall
be performed in the NCAP, a host processor or elsewhere in the system.
It is recommended that it be performed in the NCAP.

If the value of the *Calibration key* field is TBIM_CAL_SUPPLIED or
TBIM_CAL_SELF, then the correction algorithm shall be performed in the
TBIM.

All remaining text in 7.5.1.2 remains unchanged.

Incidental change Commisioning TEDS

**7.10.2 Data block**

Table 63 shows the structure of the data block for this TEDS. The
content is user defined.

Table 63---Structure of the Commissioning TEDS data block

  ----------- --------------------------------- -------------- -------------
  **Field**   **Description**                   **Type**       **\# octets**

  ---         TEDS length                       U32L           4

                                                               

  1           Character set                     U8E            1

  2           Character code                    U8E            1

  3           Language                          U8E            1

  4           Length, in octets                 U8C            1

  5           Parameter name                    U8E            N

  ---         Checksum                          U16C           2
  ----------- --------------------------------- -------------- -------------

The manufacturer shall determine the size of this TEDS, but as a
minimum, the TEDS shall be at least 42 octets to accommodate a
32-character parameter name.

Incidental change to text that was located at 5.8.6 in D2.02, but moved
to Appendix J by Proposal P03-002

**J.4 Trigger logic based on event recognition**

The functional block diagram in Figure J.4 depicts a TransducerChannel
that is triggered by an event sensor. An event sensor may have
additional embedded actuators to implement features such as a
programmable analog threshold and hysteresis or a programmable digital
pattern.

Figure J.4

The event sensor has a special hardware relationship to one or more
TransducerChannels. This should be identified as a ControlGroup with
enumeration 7 in the Meta TEDS. A trigger message issued to the event
sensor causes the event sensor to begin monitoring. The occurrence of
the event, which may cause the Data Transport Logic to issue a trigger
acknowledgment (if appropriate), may also be used to trigger the
associated TransducerChannel(s).

The manufacturer may not honor a trigger message addressed to the
TransducerChannels so configured.