RPS is composed of modular system components that are responsible for API interaction, VST instrument control, data movement, and storage of RF data.

Each system component is composed of a service application and a specific subset of the RPS system hardware that the system component manages. The service application for each system component must run on the computer that is interfaced with the hardware the component interacts with. Little to no direct interaction with these applications is required to use RPS. These service applications are controlled by the main RPS application and are intended to be left to run in the background.

The RPS InstrumentStudio panels, custom applications written using the RPS APIs, and system component service applications all communicate with each other over network ports, so many applications can be run on the same computer, or they can be distributed across network-connected computers. The following figure illustrates the network topology.

Figure 1. RPS System Component Topology

Network topology of the RPS software offerings.

Each modular system component is described in more detail in the following dedicated subsections of this manual.

Note You may find it helpful to refer to the following topics before proceeding further in this manual:
  • Record and Playback Software Application (RPS.exe)
  • Instrument Controller System Component (ICsc)
  • Stream Translator System Component (STsc)
  • Record and Playback Data Storage Server System Component (RPDSsc)
  • Terminology and Concepts