Specifications

243
OPARAM Programming/TNPP Networking Using Version 8TNPP8C3
There is a special case of routing that should be noted. Any accepted packet that is
addressed to the terminal's physical node ID, i.e. the “us” setting, will always be routed to
Central even if that node ID or routing is not set up in the node table programming.
Bit mapping is used to specify ports to route inbound packets to, as well as for specifying
port to accept packets from.
Table 35: Ports versus Bit-mapping for Inbound Packets
Node Table Programming
The node table is a table in the network card that contains information on the nodes that
the card is to recognize, and route data from and to. This table is loaded using oparam.cds
entries, one record per node ID. If a node ID appears more than once in this programming,
the later settings will override the earlier settings. This is done so that the node table may
be adjusted using the “Set Oparam” ZlinkW command with small files containing just the
records for the nodes to change.
Oparam format for node table programming is:
Port
Port
Number
Bit Number Hex Value
Central 0 1 0001H
Serial 1 1 2 0002H
Serial 2 2 3 0004H
Serial 3 3 4 0008H
Serial 4 4 5 0010H
Serial 5 5 6 0020H
Serial 6 6 7 0040H
Serial 7 7 8 0080H
Serial 8 8 9 0100H