Apply automatic numbering of ports to T'.
@@ -3450,6 +3485,32 @@FPP checks telemetry packet group specifiers as follows:
+Check that no two telemetry packet group specifiers have +the same name.
+Check that each telemetry packet group specifier is +valid.
+Note that a telemetry packet group specifier is not required. +If there is no specifier, then the topology has no packet definitions. +Note also that two or more telemetry packet group specifiers +are allowed. +Each one specifies a way of assigning the telemetry channels +of the topology to packets.
+FPP automatically assigns port numbers as follows.
@@ -5204,14 +5265,14 @@[
unmatched
]
-port-instance-id
+port-instance-id
[
[
expression
]
]
->
-port-instance-id
+port-instance-id
[
[
expression
@@ -7072,18 +7133,237 @@
A telemetry packet group specifier groups the telemetry channels of a +topology into telemetry packets. +A telemetry packet group specifier is part of a +topology definition.
+telemetry packets
+identifier
+{ telemetry-packet-group-member-sequence }
+[
+omit
+{ telemetry-channel-identifier-sequence }
+]
telemetry-packet-group-member-sequence is an +element sequence in +which each element is a telemetry packet group member, +and the terminating punctuation is a comma. +A telemetry packet group member is one of the following:
+telemetry-channel-identifier-sequence is an +element sequence in +which each element is a +telemetry channel identifier, +and the terminating punctuation is a comma.
+FPP recursively resolves any include specifiers in +telemetry-packet-group-member-sequence. +This action converts telemetry-packet-group-member-sequence to a +list L of telemetry packet specifiers, +each of which is a list of telemetry channel identifiers. +FPP then checks the following:
+Each telemetry packet specifier in L is +valid,
+Each telemetry packet specifier in L has +a distinct name and a distinct identifier.
+For every component instance I available in the enclosing topology, either through +direct specification +or through +import, +for every telemetry channel T that is a member of I, +exactly one of the following is true:
+T appears in at least one of the telemetry packet specifiers of L.
+telemetry-channel-identifier-sequence is present, and T appears in +telemetry-channel-identifier-sequence.
+packets Packets {
+
+ packet CDH id 0 level 0 {
+ commandDispatcher.commandsDispatched
+ rateGroup1Hz.rgMaxTime
+ fileUplink.filesReceived
+ }
+
+ packet ADCS id 1 level 2 {
+ adcs.mode
+ adcs.attitude
+ }
+
+ include "PowerTelemetryPackets.fppi"
+
+} omit {
+ adcs.extraTelemetry
+}A telemetry packet specifier specifies the format of a data +packet containing telemetry points. +A telemetry packet specifier is part of a +telemetry packet group +specifier, which is in turn part of a +topology definition.
+packet
+identifier
+[
+id expression
+]
+level expression
+{ telemetry-packet-member-sequence }
telemetry-packet-member-sequence is an +element sequence in +which each element is a telemetry packet member, +and the terminating punctuation is a comma. +A telemetry packet member is one of the following:
+non-annotatable-include-specifier.
+A non-annotatable-include-specifier is identical to an +include specifier, +but it is not an +annotatable element.
+The optional expression e following id specifies the numeric
+identifier for the packet.
+If e is present, then the type of e must be
+convertible to
+Integer, and e must evaluate
+to a nonnegative integer.
+If e is not present, then the default identifier is either zero (for the
+first
+packet appearing in a packet group) or the previous packet identifier plus one.
The expression e following level specifies the
+level of the packet.
+The level is a number that governs the sending of the packet.
+In the F Prime flight software, sending of packets can be filtered
+by level, so that only packets at or below a specified level are sent.
+The type of e must be
+convertible to
+Integer, and e must evaluate
+to a nonnegative integer.
FPP recursively resolves any include specifiers in +telemetry-packet-member-sequence. +This action converts telemetry-packet-member-sequence to a list L of +telemetry channel identifiers. +For each telemetry channel identifier I in L, +the component instance referred to in I must be +available in the enclosing topology, either through +direct specification +or through +import.
+@ CDH packet has id 0 and level 0
+packet CDH id 0 level 0 {
+ commandDispatcher.commandsDispatched
+ rateGroup1Hz.rgMaxTime
+ include "DownlinkTelemetryChannels.fppi"
+ include "UplinkTelemetryChannels.fppi"
+}
+
+@ Implicit id of ADCS packet is 1. Its level is 2.
+packet ADCS level 2 {
+ adcs.mode
+ adcs.attitude
+}A topology import specifier imports one topology into another one.
The qualified identifier must refer to @@ -7174,7 +7454,7 @@
topology A {
@@ -7264,24 +7544,30 @@ 7.16.3. Example
A component instance member identifier refers to a member of a +component instance.
+A port instance identifier identifies a port instance that is part of a component instance. Port instance identifiers appear in connection graph specifiers.
For each port instance identifier Q . P:
a.b
@@ -7325,6 +7611,69 @@ 8.3. Examples
A telemetry channel identifier identifies a telemetry channel that is part of +a component instance. Telemetry channel identifiers appear in +telemetry packet group +specifiers and telemetry packet +specifiers.
+qual-ident
+.
+identifier
For each telemetry channel identifier Q . T:
The qualified identifier Q must +refer to +a component instance I.
+I must refer to a component +instance definition I'.
+I' must refer to a component +definition C.
+The identifier T +must refer to a +telemetry channel specifier +of C.
+a.b
+A.b.cIn the first example, a names a component instance, and b names a
+telemetry channel.
+In the second example, A.b names a component instance, and c names a
+telemetry channel.