Daytronic Corporation - System 10 - Satellite Network Cards

When equipped with a Model 10BD4, any System 10 "B-sized" mainframe can become a central "host" unit for a network consisting of one or more Daytronic "satellite" units.

Any of three basic types of instruments may function as a System 10 SATELLITE (see below for further details):

All in all, such satellites can provide complete remote-site data acquisition, data display, process control, and/or entry of "global" system commands.

While responding instantly and "transparently" to interrogation by the "B-sized" host mainframe, each satellite mainframe remains independently responsible for all data collection, control, and/or display functions relating to those data channels and logic bits for which it serves as a unique "local" origin. These functions may include cross-channel calculations, analog peak capture, logic and analog control I/O, automatic command "executes," maintenance of "live" data display, and digital "history" recording.

The following figure shows a generalized satellite network with the "host" mainframe in a "network-terminating" position ("non-terminating" placement of the host is also possible). Host-satellite and satellite-satellite interchanges are achieved via RS485 interface of fixed protocol (153.6K baud, 8 data bits, 2 stop bits, odd parity). The 10BD4 normally allows up to 31 satellites on a twisted-pair ring of up to 1 km (3279 ft.) in total length.

As stated above, every "A-sized" satellite must be an "S" version. An "S"-version unit has limited bidirectionality. It is provided with a capacity of 1000 data channels and with an external RS485 converter connector mounted on its Computer Interface Port. It permits direct keyboard entry of mnemonic commands, both "local" and "global." However, such a satellite cannot receive "local" commands through its Computer Interface Port, which is necessarily dedicated to the network (see the above diagram).

If an existing "non-S" A-sized mainframe is supplied with a Model 10D485 RS485 Satellite Interface Adaptor, that mainframe is capable of receiving "global" data from the System 10 satellite network. It will not be possible, however, for the mainframe to transmit its own "local" data to the network.

Every "B-sized" satellite requires a Model 10BD1 Satellite Slave Card in order to issue data to the network and to receive data from the network for "local" display, printout, etc. Such a satellite can receive commands "locally" through its plug-in keyboard, through its Computer Interface Port (which is this case is not dedicated to the network), or through an optional Auxiliary Computer Interface Card.

Every Operator Console satellite is furnished with an externally mounted RS485 converter connector, and can only receive "global" data from the network. Click here for a description of the Model 10CCONB Operator Console.

You will first assign a unique identifying "Satellite Number" to each satellite via the ASN command (see the table below). You may then dedicate to the host mainframe and to each satellite mainframe in the network a selected range of "global" data channels and a selected range of "global" logic bits. "Global" here means that such a data channel or logic bit may be simultaneously read and/or displayed, if desired, by any member of the satellite network.

Each network mainframe�including the "HOST"�will now serve as the unique "data origin" for its specified channels and bits. The dedication of "global" channels and bits to network mainframes is done via the SAT and SSB commands, respectively (see the table below). The following figure gives an example of how specific ranges of global channels might be set to originate from different network nodes. All channels below the lowest-numbered SAT-dedicated channel (in this case, No. 123) will automatically originate from the HOST. The figure also shows how each satellite node might be set to "hear" a specific range of global channels, some or all of which may not originate from that node.

After the network has been fully set up, the Model 10BD4 will automatically interrogate each satellite in turn, according to the predesignated "Satellite Number" sequence, having first interrogated the host unit. The 10BD4 operates on a scan cycle which is independent of that of the host's Central Processor.

Some Satellite-Related Mnemonic Commands
ASN = n	When issued to a network satellite node, ASSIGNS a SATELLITE NUMBER to that node
SAT n = x TO y	When issued to the network host, designates SATELLITE n to be the sole "data origin" of Global Data Channels x through y
SSB n = k	When issued to the network host, designates SATELLITE n to be the sole "data origin" of Global SYSTEM BIT GROUP k
DLC = x, y	Instructs the network host to DOWNLOAD Global Data CHANNELS x through y to each "A-sized" satellite node with each scan cycle (channels to be "heard" by a given "A-sized" node must be assigned the appropriate TYPE CODE)
DLB = k, l	Instructs the network host to DOWNLOAD Global BIT Groups k through l to each "A-sized" satellite node with each scan cycle (bits to be "heard" by a given "A-sized" node must be assigned the appropriate logic source designation)
GBL = ON	When issued to a network satellite node, enables the transmission from that node of any and all "GLOBAL" commands entered at that node
OPN = n	When issued to a network satellite node, OPENS an explicit command route between that node and Satellite n (see figure below)
NOD n, $	Routes a single command string $ directly between the network NODE at which the command is entered and any other Node n, once only
SEL or SEL n	Reads the SATELLITE ERROR LOG for all satellites or for Satellite n, respectively; returns the number of timeout and checksum errors since last reset and the total number of scan cycles since last reset
REL or REL n	RESETS ERROR LOG to zero for all satellites or for Satellite n, respectively

When interrogated, each network mainframe (host or satellite) will transmit a "data packet" to the 10BD4. That is, it will send to the 10BD4, in sequence, the numeric data values and logic states currently in its DATA RAM for all "global" data channels and logic bits that have been specifically dedicated to that mainframe. A simple "checksum" procedure allows detection of faulty data transfer to the 10BD4.

With each of its own scan cycles, the host mainframe's Central Processor interrogates the Model 10BD4 for all current data in the 10BD4's DATA RAM, as collected from all satellite mainframes in the network. The host then updates its own DATA RAM accordingly, publishing all network-collected data to any and all of its "COPROCESSOR" cards (i.e., to every History Card, Auxiliary Computer Interface Card, etc., contained in the host mainframe).

At the same time that it is transmitted to the Satellite Interface Card, a given "data packet" is transmitted to every "B-sized" mainframe satellite in the network. This same data is further available to every "A-sized" mainframe satellite that has been configured to receive it (see the DLC and DLB commands in the table, above).

After receiving a data packet, a satellite will accordingly update the corresponding data channels and logic bits in its own DATA RAM, and also any "local" display of these channels and bits for which it is responsible.

The network also allows any satellite to issue standard System 10 COMMANDS to any other satellite or to the host. Every interrogation by the 10BD4 for "local" satellite data will be accompanied by an interrogation for a "message packet"�i.e., for any mnemonic commands that may be currently awaiting delivery from the satellite in question to some other network node.

On receipt by the 10BD4, all such "global" commands are immediately sent to the host's Central Processor. From there each command is routed directly to the individual network unit to which it is "implicitly" addressed by virtue of the "global" data channel(s) or logic bit(s) referred to by the command itself, or to which it has been "explicitly" addressed by means of an OPN or NOD command (see table and the figure below). Because of this "global command" capability, the total system can accommodate more than one observation station throughout the network.

In contrast to a "global" command, which may be entered through the keyboard, Computer Interface Port, or optional Auxiliary Computer Interface Port of any network node in order to be sent to any other node, a "local" command can only be "heard" and acted upon by the node whose keyboard, Computer Interface Port, or Auxiliary Computer Interface Port has been used to enter that command.

When interrogated by the 10BD4, each Operator Console satellite will only transmit its current message packet (such a unit does not transmit data; it only receives it for purposes of "local" display, printout, recording, etc.). It can both issue and receive "global" commands via the OPEN (OPN) command, just like a mainframe satellite. Like an "A-sized" mainframe satellite, it can receive "local" commands through its keyboard (only).

LED status indicators on the 10BD4's front edge alert the operator to "timeout error" (when a satellite is not answering an interrogation by the 10BD4), or "checksum error" (indicating faulty data transmission to the 10BD4). Other indicators on both the 10BD4 and 10BD1 let you know when the respective data-transmission and data-reception lines are active. Special commands permit interrogation and resetting of the 10BD4's "Satellite Error Log" and "Cycle Counter" (see table, above).

The Model 10CCONB is only for use within Daytronic "SATELLITE" NETWORKS. Within a Model 10BD4-based network this unit can

The "console" monitor offers the same video functions as a Model 10KN8A mainframe, including

An Operator Console differs from a standard "B-sized" mainframe satellite, however, in several important ways:

Dimensions of the Model 10CCONB are identical to those of the Model 10KN8A mainframe. For optional 220 VAC power (50 Hz only), specify Model 10CCONB-F.