Changes between Version 2 and Version 3 of Software


Ignore:
Timestamp:
Sep 29, 2005, 10:04:42 PM (19 years ago)
Author:
max
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Software

    v2 v3  
    55The '''ORBIT Radio Grid Testbed''' is operated as a shared service to allow a number of projects to conduct wireless network experiments on-site or remotely.  Although only one experiment can run on the testbed at a time, automating the use of the testbed allows each one to run quickly, saving the results to a database for later analysis. 
    66
    7 In other words, Orbit may be viewed as a set of services into which one inputs an experimental definition and one receives the experimental results as output as illustrated in Figure 2 below.  The experimental definition is a script that interfaces to the ORBIT Services.  These services can reboot each of the nodes in the 20x20 grid, then load an operating system, any modified system software and application software on each node, then set the relevant parameters for the experiment in each grid node and in each non-grid node needed to add controlled interference or monitor traffic and interference.  The script also specifies the filtering and collection of the experimental data and generates a database schema to support subsequent analysis of that data.
     7In other words, Orbit may be viewed as a set of services into which one inputs an experimental definition and one receives the experimental results as output as illustrated in Figure 1 below.  The experimental definition is a script that interfaces to the ORBIT Services.  These services can reboot each of the nodes in the 20x20 grid, then load an operating system, any modified system software and application software on each node, then set the relevant parameters for the experiment in each grid node and in each non-grid node needed to add controlled interference or monitor traffic and interference.  The script also specifies the filtering and collection of the experimental data and generates a database schema to support subsequent analysis of that data.
    88
    9 [[Image(architecture.png, 50%)]]
     9[[Image(architecture-50.png)]]
     10Figure 1. Experiment Support Architecture
    1011
    11 Figure 2.  Experiment Support Architecture (see page 8 of [http://www.orbit-lab.org/download/presentations/Orbit_Architecture.pdf]).
    1212
    1313== Hardware Components ==
    14 The '''ORBIT Radio Grid Testbed''' as illustrated in Figure 3 consists of a multiply interconnected, 20-by-20 grid of '''ORBIT Radio Nodes''', some non-grid nodes to control R/F spectrum measurements and interference sources, and front-end, application and back-end servers.  These servers support various ORBIT services.
    1514
    16 Figure 3.  ORBIT Hardware (page 2 of [http://www.orbit-lab.org/download/presentations/Orbit_Hardware.pdf]).
     15The Orbit grid as illustrated in Figure 2 consists of a multiply interconnected, 20-by-20 grid of '''ORBIT Radio Nodes''', some non-grid nodes to control R/F spectrum measurements and interference sources, and front-end, application and back-end servers.  These servers support various ORBIT services.
     16
     17Figure 2.  ORBIT Hardware (page 2 of [http://www.orbit-lab.org/download/presentations/Orbit_Hardware.pdf]).
    1718
    1819Each '''ORBIT Radio Node''' is a PC with a 1 GHz VIA C3 processor, 512 MB of RAM, 20 GB of local disk, two 100BaseT Ethernet ports, two 802.11 a/b/g cards and a Chassis Manager to control the node, see Figure 4.  The Chassis Manager has a 10BaseT Ethernet port.  The two 100BaseT Ethernet ports are for Data and Control.  The Data ports are available to the experimenter.  The Control port is used to load and control the ORBIT node and collect measurements.