Showing posts with label Tracegraph. Show all posts
Showing posts with label Tracegraph. Show all posts

Sunday, April 12, 2009

How to fix DYMOUM trace file can be use with tracegraph

Last week one final year student see me asking about problem how to analyze DYMO trace file using tracegraph, then I try to investigate what is the problem. When open DYMO trace file using tracegraph, it shown some error that about some sort "ip bla.. bla.. thing". That make me to do a comparison between other routing protocol trace file with DYMO trace file. Then I found that there is some new element that tracegraph cannot understand. So the easy way to solve it, just to delete that "not understand" data.
  1. By using Notepad++ software open that trace file.
  2. Then open find & replace menu.
  3. Select regular expression search mode. See figure attach
  4. Then at find what: type \[ pt . \]
  5. For replace with: leave it empty
  6. Replace all
  7. Dont forget to save your file

Your trace file now can open using tracegraph

Ok, peace

Friday, September 26, 2008

Protoname routing protocol with 10 nos of nodes

After I success installing new routing protocol call Protoname the I want to try these routing protocol performance, I try the same situation there are:


1.Scenery size350 meters X 350 meters
2.Transmission range175 meters
3.No. of node9 nodes (8 common nodes & 1 sink node)
4.Routing ProtocolProtoname (New protocol)

Then the result is:

Sent packet

Receive packet

Dropped packet




Lost packet

Saturday, July 19, 2008

DSDV routing protocol with 25 nos. of nodes

Another testing conduct with DSDV routing protocol and increased the number of nodes. From the result show some difference behaviour happen. The simulation environment is:

1.Scenery size400 meters X 400 meters
2.Transmission range200 meters
3.No. of node25 nodes (24 common nodes & 1 sink node)
4.Routing ProtocolDSDV


Result from the scenario show with DSDV always generate data to all nodes. But the total of amount packet generate not consistent and most nodes not much contribute to generate packet.


From figure above only 3 nodes manage generate more than 4000 packet. Now we try to see whether the three nodes most generate packet have relationship with forwarding packet.

There are several relation ship about the node there are:


This may be give some clue about forwarding packet...

From the result show not much packet manage to receive at access point, this what we want to figure about?


A lot of dropped packet, more than 8000 packet so, this what we want to avoid of.

Friday, July 18, 2008

DSDV routing protocol on 10 nos. of nodes

Now I try the same situation before but a bit of modification on type of routing protocol and size of area. DSDV routing protocol; it is not big reason for me to change the area size but just only to see the difference between of them. There are:

1.Scenery size400 meters X 400 meters
2.Transmission range200 meters
3.No. of node9 nodes (8 common nodes & 1 sink node)
4.Routing ProtocolDSDV


On this time from the simulation, we can see not all of the nodes generated the packet.

From figure above node no. 3 & 4 not activate to generate packet.

Also not many of intermediate nodes involve forwarding packet.

But quite much of packet generated can arrive to the access point.

Still we can see most of the packet dropped on network.

Next I will change try on environment with more no. of nodes (it is up to 25 no. of nodes) and but again with DSDV routing protocol.

Saturday, July 12, 2008

Run NS-2 TcL script and evaluate with trace analyzer

I try difference combination of simulation script with TcL generator on scenery size, transmission range and no. of node. Before this I was try some simulation show the power consumption not much used within 100 second simulation, where about 5 joules. So I try to set the initial energy at 5 joules where we can see power usage until the battery empty.

The simulation environment was set on:

1.Scenery size350 meters X 350 meters
2.Transmission range175 meters
3.No. of node9 nodes (8 common nodes & 1 sink node)
4.Routing ProtocolDSDV



The result was we can see all nodes generate and sent from common node


some forwarding packet in intermediate nodes and

only only a few of the packets can receive at access point

where others drop on the network.

In future work are I will simulate the scenario with the same no. of nodes but difference type of routing protocol.

Tuesday, March 4, 2008

Mannasim & Trace Graph

Mannasim is add-ons to NS-2 for wsn, we used it's GUI to generate tcl script but suddenly only AODV, DSDV, DYMO & Leach manage give the output & other than that still having problem, hopefully it can be solve later.

And another tool we use is trace graph, from tcl script we can generate trace file, from trace file we can analyze traffic to see behavior of the routing protocol. Only AODV & DSDV can give good graph. DYMO and Leach give some error like "cannot read the IP file" & "maximum variable size allowed by the program is exceeded...", I want to try by reducing the node like 2 or 3 nodes and see how the result is...?

Older Posts Home

 

blogger templates | Make Money Online