User guide

190 RealCT Direct API Developer Guide
Chapter 6: MVIP-95
Connecting Boards in an H.100 bus
This section provides information about the H.100 bus,
including information about how to set clocks and stream
speeds for boards connected in an H.100 bus.
This section only applies to boards that are physically connected
in an H.100 bus to other H.100-compliant boards. For
information about connecting your H.100-compliant board in an
MVIP bus, see Connecting Boards in an MVIP-90 Bus on
page 212.
Numbering Streams
The MVIP-95 standard defines CT bus and local streams.
CT bus streams are streams that connect the boards in a
CT bus. These are the streams running through the
physical H.100 connector.
Local streams carry the board’s internal line and VP
resources.
Both sets of streams are numbered sequentially, starting
with 0.
Streams in an H.100 bus are not directional; boards can
transmit or receive data on any stream. This lack of
directionality in H.100 streams is in contrast to MVIP-90
streams, where the streams are divided into DSix (input) and
DSox (output) directions, as described in Working with MVIP-90
Data Streams on page 145. However, when a board that uses
the H.100 standard is connected through an MVIP bus, the
application adheres to the MVIP stream directionality.