AggregatedServers

From ATCSMon Wiki
Jump to: navigation, search

Aggregating ATCS Monitor Data Streams

Combining multiple ATCS data streams as a user is fairly simple, you just add the servers to your Data Source / Network Settings in the Configuration/Options menu. However, if you wish to present this aggregated stream to the world as a server, a few more steps are required. Here is a simple example to show how to combine the streams from an MCP radio and a BCP radio into a single source and make it available through your server. This example requires that you already have a working server stream. If not, read through the section on setting up a server before attempting an aggregated feed.

There will be four instances of ATCS Monitor running on your machine:

A: The instance listening to your BCP radio

B: The instance listening to your MCP radio

C: The instance that combines the two radio instance streams

D: The instance that presents the combined stream to the main port

=ATCS Mon A & B configuration (Configure->Options menu)

"A"

Data Source Tab

Data Source: Sound Card (attached to the BCP radio)

Network Settings: Server Mode Listener: 4900


"B"

Data Source Tab

Data Source: Sound Card (attached to the MCP radio)

Network Settings: Server Mode Listener: 4901

ATCS Mon C (the aggregator) configuration


"C"

General Tab

Check the Enable DDE Relay output box

Check the Enable user-defined DDE names box

Data Source Tab

Data Source: Network Connection

Network Settings: Server Mode Listener: 4800 (Your "public" data server port)

Network Settings: localhost: 4900

Network Settings: localhost: 4901

Also: Off site streams can be aggregated directly into instance C by adding the appropriate Network Settings of the off site stream.

ATCS Mon D (the server) configuration


"D"

General Tab

Check the Enable user-defined DDE names box

Data Source Tab

Data Source: DDE

Network Settings: Server Mode Listener: 4800 (Your "public" data server port, same as "C") and in the Notes field put "SRV4800" ie SRV followed by the port # (ie SRVxxxx)

Also: If you wish to log data or connections, this should be done from the server instance, D. The other instances should probably be set up to be fairly silent with regard to data logging.

That should get you running. There are other configurations you can dream up, such as adding additional radios or even off-site streams. Each additional radio will require a new instance of ATCS Monitor configured similarly to A or B, but with a different listener port. (4902, 4903...).