Changes between Version 8 and Version 9 of OFDMReferenceDesign/Applications/Characterization

Timestamp:

Jun 29, 2009, 11:29:54 AM (15 years ago)

Author:

rpl1

Comment:

--

OFDMReferenceDesign/Applications/Characterization

@@ -23 +23 @@
 === OFDM Reference Design Code ===
 
-__Summary:__ The following extensions to the OFDM Reference Design expand node control by allowing a server to relay requests to warpnodes. The requests are sent as different struct types. These structs will set board parameters to certain values using Command and Traffic structs, and command (command structs) the board to stop and start transmissions, as well as request data (stat structs) about the transmission. This model places the boards in a state where data for wireless transmission is locally created instead of taken from the Ethernet.
+__Summary:__ The following extensions to the OFDM Reference Design expand node control by allowing a server to relay requests to warpnodes. The requests are sent as different struct types. These structs will set board parameters to certain values using Command and Traffic structs, and command (command structs) the board to stop and start transmissions, as well as request data (stat structs) about the transmission. This model places the boards in a state where data for wireless transmission is locally created instead of taken from the Ethernet. The two complete codes for the modifications are the attached files csmaMac.c and warpnet_node2.c
 
 The development of creating an interactive warpnet control requires the introduction of new structure types for the warp platform
@@ -340 +340 @@
 
 === 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. To run a tcl program, open up a command line such as a terminal and type:
+{{{
+ tclsh filename.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.
+
+{{{
+set filename "PacketData.m"
+set NumNodes 2;
+set dumbServerIP 10.0.0.6
+set dumbServerPort 9090
+}}}
+
+
+To main code for developing an automated experiment that writes statistic data to a file begins by connecting the socket with the dumb server and configuring the socket to automate flushing of the memory
+
+{{{
+#Open a socket connection
+set sock [socket $dumbServerIP $dumbServerPort] 
+
+#Automate flushing of the socket
+fconfigure $sock -buffering none -blocking 0
+}}}
+
+Next a default time interval is set and an blank file $filename is created (clears the file if it contains data)
+
+{{{
+set TimeInterval 100
+;#Create Blank File
+set fileID [open $filename "w"] 
+}}}
+
+A create a test for sweeping through txpowers would use a for loop that modifies the txpower value in the control structure.
+
+The following lists supported structures definitions and examples of how to use them:
+
+{{{
+;# Control Struct: structType, nodeID, modOrder, txPower, coding, channel
+set ControlStruct0 [list 50 0 4 63 3 9 ]
+set ControlStruct1 [list 50 1 4 63 3 9 ]
+
+;# Traffic Struct: structType, nodeID, trafficMode 0 = RECEIVE 1 = TRANSMIT , reserved0, txInterval, txPacketLen, reserved1 
+set TrafficStruct0 [list 52 0 1 0 0 1470 0 ]
+set TrafficStruct1 [list 52 1 1 0 0 1470 0 ]
+
+;# structType, nodeID is only relevant for ack on stop, cmdID, cmdParam
+set CommandStructStart [list 51 0 102 0 ]
+set CommandStructStop [list 51 0 103 0 ]
+
+;# structType, nodeID, cmdID, cmdParam
+set CommandStructStats0 [list 51 0 104 0 ]
+set CommandStructStats1 [list 51 1 104 0 ]
+set CommandStructResetStats0 [list 51 0 97 0 ]
+set CommandStructResetStats1 [list 51 1 97 0 ]
+}}}
+
+The function ''senddata'' sends a struct to the dumb server. The first parameter is the struct to send. The second parameter specifies modes, such as requesting an ackPacket with ''$SendAck'' or statPacket from the server with ''$WriteStat.'' The default parameter requests nothing from the server.
+
+The following highlights a test for sweeping through txPowers from 0 to 63 while changing from QPSK to 16QAM:
+
+{{{
+for {set power 0} {$power < 64} {incr power} {
+        for {set mod 1} {$mod<3} {incr mod} { ;#set mod
+        
+#Send a Control Struct to node 0
+senddata $sock [list 50 0 [expra  {$mod*2}] $power 3 9 ] $SendAck
+#Send a Control Struct to node 1
+senddata $sock [list 50 1 [expr {$mod*2}] $power 3 9 ] $SendAck
+
+#Send a Traffic Struct to node 0
+senddata $sock [list 52 0 1 0 0 1470 0 ] $SendAck
+#Send a Traffic Struct to node 1
+senddata $sock [list 52 1 1 0 0 1470 0 ] $SendAck
+
+#Reset Statistics on nodes, sets everything to 0
+senddata $sock $CommandStructResetStats0 $SendAck
+senddata $sock $CommandStructResetStats1 $SendAck
+
+#Begin data transmission over the air
+senddata $sock $CommandStructStart
+after $TimeInterval
+#Stop data tranmission over the air
+senddata $sock $CommandStructStop $SendAck
+
+senddata $sock $CommandStructStats0 $WriteStat
+senddata $sock $CommandStructStats1 $WriteStat
+        
+        }
+}
+}}}
+
+
+The last step is to close the socket and exit the tcl script:
+
+{{{
+close $sock
+exit
+}}}
+
+
+
+