|
There are four versions of Diagnostic D, which display message counts
broken down by Control Channel Processor (CCP), by message type, by message
subtype, and segmented message collection. The front panel and remote UP
and DOWN keys will cycle through these screens.
The CHANNEL_UP and CHANNEL_DOWN keys on the remote are used to change
the channel.
Pressing the BUY & INFO keys on any screen where they have no
defined action will clear the CCP packet message counts. It will also
cause the IRD to forget all the information used for duplicate detection,
both the one-minute CRC lists and the 24 hour mtv 1 table extension lists.
(The error counters will only be cleared if the INFO key is pressed while
the message counts by CCP screen is up, or the IRD is reset.) GUI-less
products have a front panel menu to perform this function.
All the message counters are decimal numbers which roll back to zero
at their limits.
Most of the message counters have two columns, the first for messages
received and the second for messages which pass low-level filtering. All
messages which pass hardware filtering are counted as messages received.
To be counted in the second column messages must pass duplicate detection,
language filtering, and several other firmware filters.
Messages which pass low level firmware filtering are not necessarily
processed by the IRD. Depending on the message type, higher level firmware
can reject messages for numerous reasons.
Figure -1. Message counts by CCP Diagnostic Screen D
Table -1. Message counts by CCP Diagnostic Screen D
| Line # |
Name |
Definition |
| Line D1 |
Channel number |
Current Virtual Channel Number or channel
entry accumulator. |
| Line D3 |
CCP 0 |
PID (0x0000..0xFFFF).
messages received (0..65535).
messages passing low-level filtering (0..65535).
integrity check failures (0..255).
+
CCP buffer overwrites (0..255).
pre-FIFO overflows (0..255).
DRAM buffer overflows (decimal 0..255).
lost message indications (0..7).
resets based on lost messages (0..8191). |
| Line D4 |
CCP 1 (EMM) |
<same format as CCP 0>. |
| Line D5 |
CCP 2 (SCC) |
<same format as CCP 0>. |
| Line D6 |
CCP 3 (APP1) |
<same format as CCP 0>. |
| Line D7 |
CCP 4 (APP2) |
<same format as CCP 0>. |
| Line D8 |
CCP 5 (Network) |
<same format as CCP 0>. |
The version of Diagnostic D which displays message counts broken down
by CCP is described by Table 1.5-1. In the case of segmented messages,
the counts increment for each message segment.
Figure -2. Message counts by message type Diagnostic Screen
D
Table -1. Message counts by CCP Diagnostic Screen D
| Line # |
Name |
Definition |
| Line D1 |
Channel number |
Current Virtual Channel Number or channel
entry accumulator. |
| Line D3 |
CCP 0 |
PID (0x0000..0xFFFF).
messages received (0..65535).
messages passing low-level filtering (0..65535).
integrity check failures (0..255).
+
CCP buffer overwrites (0..255).
pre-FIFO overflows (0..255).
DRAM buffer overflows (decimal 0..255).
lost message indications (0..7).
resets based on lost messages (0..8191). |
| Line D4 |
CCP 1 (EMM) |
<same format as CCP 0>. |
| Line D5 |
CCP 2 (SCC) |
<same format as CCP 0>. |
| Line D6 |
CCP 3 (APP1) |
<same format as CCP 0>. |
Figure -2. Message counts by message type Diagnostic Screen
D
Table -2. Message counts by message type Diagnostic Screen
D
| Field |
Definition |
| Message type: |
0x00 Service Association
0x01 Conditional Access
0x02 Service Map
0x7f PIDAC Compatibility
0x90 Antitaping Control
0x91 Barker
0x92 Channel Override
0x93 Download
0x94 Download Preamble
0x95 Entitlement Management
0x96 Fingerprint
0x97 Hardware Control
0x98 Reportback Control
0x99 Return |
0x9a Text
0x9c Unit Creation
0x9d Unit Information
0x9e Virtual Multiplex
0x9f Homing Parameters
0xa0 Manufacturer Specific
0xa1 Object Definition
0xc0 Program Information
0xc1 Program Name
0xc2 Network Information
0xc3 Network Text
0xc4 Virtual Channel
0xc5 System Time
0xc6 Subtitle |
| Messages received |
messages received (0..99). |
| Messages passed |
messages passing low-level filtering
(0..99). |
The version of Diagnostic D which displays message counts broken down
by message type is composed of four columns of three numbers each. The
contents of a column is described by Table 1.5-2. These counts include
messages from all CCPs. In the case of segmented messages, the counts increment
for each message segment.
Figure -3. Message counts by message subtype Diagnostic Screen
D
Table -4. Segmented message collection Diagnostic Screen D
| Line # |
Name |
Definition |
| Line D1 |
Message Buffer 1 |
message type
subtype
table extension
number of passes
elapsed time (seconds)
message size (kb)
last segment seen
collected segments / total segments
hole number : first missing segment : segments missing |
| Line D2 |
Segment Tracking 1 |
Bit field for received segments. One bit for
each segment, set when segment is collected. Segment 0 is at front of bit
field (most significant bit). Entire line is cleared after all segments
are collected. |
| Line D3 |
Message Buffer 2 |
<same format as Message Buffer 1> |
| Line D4 |
Segment Tracking 2 |
<same format at Segment Tracking 1> |
| Line D5 |
Message Buffer 3 |
<same format as Message Buffer 1> |
| Line D6 |
Segment Tracking 3 |
<same format at Segment Tracking 1> |
| Line D7 |
Message Buffer 4 |
<same format as Message Buffer 1> |
| Line D8 |
Segment Tracking 4 |
<same format at Segment Tracking 1> |
Segmented messages are collected in four message buffers. The contents
of these message buffers can be monitored from the segmented message version
of Diagnostic D, described by Table 1.5-4. The display for each message
buffer occupies two lines: the first line provides information about the
message and how the collection is proceeding; the second line provides
a bit-map showing which segments have been collected.
|
