16.0 Glossary
bridge
modeD
The
QuickRing client port to another QuickRing client port. This
will provide a hop path from one ring structure to another.
(PIPE signal is negated.)
ability
to
directly
connect
one
hop fieldsD
The ring packet header has 5 fields allocated
to address to different rings. If the fields are not used to hop
rings, they can be used to identify separate data streams.
This allows up to 2
20
individually identified data streams.
hop pathD
The means of moving from one QuickRing to
another through a bridge connection. Hop fields in the head-
er symbol provide the addressing to achieve the routing.
initializationD
A user transparent process that begins upon
reset release by all nodes. During initialization, nodes are
assigned node ID numbers, then the total number of nodes
on the ring is distributed to each node. The node address
and total number of nodes is made available to the client.
Reservation and packet transmissions may begin immedi-
ately following.
Node0D
Node 0 is determined by the
Node0
pin being as-
serted. Node 0 governs the initialization process.
ring of ringsD
The result of connecting multiple rings to-
gether. Up to 5 QuickRings can be traversed by a packet
because there are 5 hop fields in the header.
symbolD
The ring transmission basic unit, on the ring. Each
symbol consists of 42 bits; 2 type bits, 1 frame bit, 32 data
bits, and 7 bits of error detection code. At the client ports, a
symbol is a 32-bit value on RxS
[
31:0
]
or TxS
[
31:0
]
.
voucherD
On the ring, vouchers are sent by source nodes
to obtain permission to launch packets of client generated
payload symbols.
ticketD
On the ring, tickets are returned by target nodes in
response to vouchers. They indicate that the target has re-
served FIFO space for one packet.
packetsD
On the ring, packets are limited to a size of 21.
Each packet at least consists of 1 head symbol and 1 tail
symbol/last symbol.
NullD
Null is the encoding on the Type fields which indi-
cates to ignore the associated symbol.
17.0 Revision Notes
Following is a list of some of the changes that have been
made between this version of the datasheet and the
December 1993 version. This is not a complete list of the
changes.
Change
Maximum Data Transfer Rate
Client receive port operation
EDC error and client ‘‘a(chǎn)bort’’ pin functionality
Resynchronizer issue
Multiple clock sources and ring with many nodes
Power and decoupling recommendations
Section
Front page
3.5.1
3.16
5.0
5.0
12.0
38