Changes between Version 10 and Version 11 of OFDMReferenceDesign/Applications/Characterization

Timestamp:

Jun 29, 2009, 12:16:00 PM (15 years ago)

Author:

rpl1

Comment:

--

OFDMReferenceDesign/Applications/Characterization

@@ -337 +337 @@
 
 === Dumb Server Code ===
-Summary: The attached file dumb_server.zip contains the code for receiving data from the Tcl Client, processing this data, and sending the appropriate structs to the warp nodes. The current setup has the code connect to the Tcl Client over port 9090 and has the PC with the server_code on 10.0.0.6
+__Summary:__ The attached file dumb_server.zip contains the code for receiving data from the Tcl Client, processing this data, and sending the appropriate structs to the warp nodes. The current setup has the code connect to the Tcl Client over port 9090 and has the PC with the server_code on 10.0.0.6
 
 Because this page is made to show how one can use tcl to control warp nodes, we will assume the dumb server can change tcl strings to warpnode management structs without going into the details.
 
 === Tcl Client Code ===
-Summary: The Tcl Client automates control of warpnode parameters. The Tcl Client sends values to the server. Attached are two versions of the tcl client. The ''automated_client.tcl'', which loops through changing txpowers and modOrders with a set time interval, and the ''interactive_client.tcl'', which pauses before transmitting a request to start transmission on nodes, asks for a time interval or defaults to a user input for stopping the data transmission. The Tcl Client can either be on the same machine running the Dumb Server code or be on a machine connected to the router. To run a tcl program, open up a command line such as a terminal and type:
+__Summary:__ The Tcl Client automates control of warpnode parameters. The Tcl Client sends values to the server. Attached are two versions of the tcl client. The ''automated_client.tcl'', which loops through changing txpowers and modOrders with a set time interval, and the ''interactive_client.tcl'', which pauses before transmitting a request to start transmission on nodes, asks for a time interval or defaults to a user input for stopping the data transmission. The Tcl Client can either be on the same machine running the Dumb Server code or be on a machine connected to the router. To run a tcl program, open up a command line such as a terminal and type:
 {{{
  tclsh filename.tcl
 }}}
 
-
+The following will explain how to create an automated test similar to automate_client.tcl
 Initially, a few user specified global parameters needs to be set. This includes the filename for where statistics are written, the number of nodes, and information for connecting to the socket. In this set up, the dumb_server contains the IP address of 10.0.0.6 and connects through port 9090.