Changes between Version 8 and Version 9 of WARPnet1/BuildClientScripts

Timestamp:

Jun 18, 2010, 2:38:39 PM (14 years ago)

Author:

sgupta

Comment:

--

WARPnet1/BuildClientScripts

@@ -23 +23 @@
         int pktGen_numPackets;
 } warpnetControl;
+
+typedef struct {
+        char structID;
+        char nodeID;
+        short cmdID;
+} warpnetAck;
 }}}
 
@@ -29 +35 @@
 {{{
 #!python
+STRUCTID_CONTROL = 0x13
+STRUCTID_CONTROL_ACK = 0x14
+
 class ControlStruct(ClientStruct):
         txPower = -1
@@ -53 +62 @@
         def prepToSend(self, nodeID):
                 self.updateDone = False
-                return struct.pack('!6BHII', self.structID, nodeID, self.txPower, self.channel, self.modOrderHeader, \
-                                self.modOrderPayload, self.reserved, self.packetGeneratorPeriod, self.packetGeneratorLength)
+                return struct.pack('!6BH3I', self.structID, nodeID, self.txPower, self.channel, self.modOrderHeader, \
+                                self.modOrderPayload, self.reserved, self.packetGeneratorPeriod, self.packetGeneratorLength, self.packetGeneratorNumPackets)
                 
         def updateFromNode(self, rawData, pcapts):
@@ -60 +69 @@
 
 }}}
+
+The `prepToSend` function creates the raw data that is seen by `warpnet.c`in the FPGA. It creates a byte packed data of 6 bytes (6B), 1 short (H) and 3 ints (3I). This is exactly what the node is expecting. A appropriate response from the node is a `warpnetACK` which `updateFromNode` parses in the python file.
 
 == Running the Client Script ==