haw to visualiza the node's rage transmission range ??

[amal abdelkarim]

hi all,
my problem is that i 'm not able to visualize the transmission range
of nodes while running the simulation. i need to see circules's range
to be able to place node with the appropriate scenario. any help
please!!

thanks a lot.

[Rudolf Hornig]

you should set the 'r' tag in the node's displaystring. Adding r=100 will draw a 100unit radius circle around the host...

If you need several circles (i.e. separate for interference and transmission range), you can use also r1 r2 r3 etc tags...

Rudolf

--
You received this message because you are subscribed to the Google Groups "omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.

[amal abdelkarim]

hi ,
thanks for your response, iknow that the r tag can draw the range but, my problem is how to get the real range calculated from the connection manager

interfDistance = pow(waveLength * waveLength * pMax
                           / (16.0*M_PI*M_PI*minReceivePower),
                         1.0 / alpha);


i want to visualize this value od interference distance. have you any idea ??

 

[Rudolf Hornig]

I'm not sure I get you completely, but my suggestion was that you set the range using the r tag to this value - programmatically in your code.

Rudolf

[Rudolf Hornig]

On additional tip: AbstractRadioExtended::updateDisplayString() does this in the INETMANET project. Check how it is done.

Rudolf

[amal abdelkarim]

hi,
i'm not using inetmanet , that's my problem, instead i'm using mixim.

2011/6/1 Rudolf Hornig <rudolf...@gmail.com>

--

Amal Abdelkarim éléve ingénieur

à l'école nationale  des sciences de l'informatique ENSI

 

[Sebastian Helmle]

hi fans,

this is an interesting topic and i made a first look into the omnetpp manual.

here i found the information, that it is able to set the display string via

setDisplayString() at runtime. you will find this information on page 170.

cheers!

sebastian

[Rudolf Hornig]

I'm not suggesting to use INETMANET, rather to look into the INETMANET code and check how it is done there.

[Sebastian Helmle]

hi fans,

i've tested to change the display strin like this : 

//TEST display change

this->setDisplayString("i=block/socket,red");

it works fine, so once you have the information from the connectionManager you are able to set

the r tag with this value via string concatenation, etc..

cheers!

sebastian

[Oudam]

Hi,

for visualizing the interferance distance in OMNeT++/MiXim, you can
just put **.drawMaxIntfDist = true
in omnetpp.pp (the configuration file).

interfDistance = pow(waveLength * waveLength * pMax
/ (16.0*M_PI*M_PI*minReceivePower),
1.0 / alpha);

But, this is the interference distance (a maximum value which is fixed
once it is computed) and is not
the tramission range.

The radio model is not an “on/off” mechanism, right ?

I'm also interested to know how we can compute the maximum tranmissin
range value. I have been still
searching for the answer... and am still confused on computing this
value as many others do :
here: http://groups.google.com/group/omnetpp/browse_thread/thread/9bdac5a90f76f8e0#
or
http://groups.google.com/group/omnetpp/browse_thread/thread/89744f97e371cf13
...

Could anyone explain clearly how to compute the maximum value of the
tranmission range by using
the free space path loss formula http://en.wikipedia.org/wiki/Free-space_path_loss,
please ?

Thanks in advance :)

Regards,
Oudam

On 1 juin, 15:25, amal abdelkarim <abdelkrim.a...@gmail.com> wrote:
> hi,
> i'm not using inetmanet , that's my problem, instead i'm using mixim.
>

> 2011/6/1 Rudolf Hornig <rudolf.hor...@gmail.com>

>
> > On additional tip: AbstractRadioExtended::updateDisplayString() does this
> > in the INETMANET project. Check how it is done.
>
> > Rudolf
>

> *Amal Abdelkarim éléve ingénieur*
> *à l'école nationale  des sciences de l'informatique ENSI*

[Leonardo Maccari]

On 17/10/2011 12:03, Oudam wrote:

>
> interfDistance = pow(waveLength * waveLength * pMax
> / (16.0*M_PI*M_PI*minReceivePower),
> 1.0 / alpha);

> Could anyone explain clearly how to compute the maximum value of the
> tranmission range by using
> the free space path loss formula http://en.wikipedia.org/wiki/Free-space_path_loss,
> please ?

Theoretically it is just the formula you reported. In practice, it
depends on the settings you're using (power, sensitivity, PER
tables...). Usually I use a scenario similar to the one I paste below
and a corresponding ANF to check the max distance.

ciao,
leonardo.

[Config TestDistance]

# See anf file for evaluating the max transmission distance
# at various transmitting power level.
# Sensitivity values from:
# http://www.smarteq.se/4.1b27248111ee6cfde1e800011072.html
# @54Mbps sensitivity is -67db for some nics
# @11Mbps it is around -82

#**.wlan.radio.berTableFile="per_table_80211g_Trivellato.dat"

description = "Nodes diverging"
*.numHosts = ${nn = 2}
sim-time-limit = 1000s
repeat = 1
**.mobility.rng-0 = 1
**.wlan[*].mac.rng-0 = 2
#debug-on-errors = true

**.constraintAreaWidth = 1000m
**.constraintAreaHeight = 1000m
**.debug = false
**.coreDebug = false
**.host*.**.channelNumber = 0

**.wlan[*].radio.bitrate = 54Mbps
**.wlan[*].radio.transmitterPower = ${transmissionPower =
2,3,5,10,50,100,200,500}mW
**.wlan[*].radio.thermalNoise = -110dBm
**.wlan[*].radio.sensitivity = -95dBm
**.wlan[*].radio.pathLossAlpha = 2
**.wlan[*].radio.snirThreshold = 4dB

**.host*.routingProtocol = "OLSR"

# mobility

**.host[0].mobilityType = "NullMobility"
**.host[1].mobilityType = "LinearMobility"
**.mobility.initFromDisplayString = false
**.host*.mobilityType = "NullMobility"
**.host[0].mobility.initialX = 10m
**.host[0].mobility.initialY = 10m
**.host[1].mobility.initialX = 10m
**.host[1].mobility.initialY = 10m
**.host[1].mobility.speed = 1mps

**.host[*].udpApp[0].typename = "UDPBasicBurst"
**.host[*].numUdpApps = 1

#**.host[0].udpApp[0].destAddresses = "255.255.255.255"
**.host[0].udpApp[0].destAddresses = "host[1]"
**.host[*].udpApp[0].destAddresses = ""

**.host[*].udpApp[0].localPort = 1234
**.host[*].udpApp[0].destPort = 1234

**.host[*].udpApp[0].messageLength = 1400B
**.host[*].udpApp[0].messageFreq = 1s
**.host[*].udpApp[0].burstDuration = 1000s
**.host[*].udpApp[0].sleepDuration = 0s

**.host[*].udpApp[0].stopTime = -1s
**.host[*].udpApp[0].startTime = 5s
**.host[*].udpApp[0].delayLimit = 5s

--
Leonardo Maccari, Post-doc researcher@University of Trento
Tel: +39 0461 285323, project website: www.pervacy.eu

[Oudam]

Hi,

yes of course, the value of interfDistance depends on the values of
other parameters (waveLenght, pMax, etc).
It's true theoretically or pratically :)

_______________________________________________________________________________
Plase see also part of my configuration file (in MiXim) below :
##############################################################################
# Parameters for the
ConnectionManager #
##############################################################################
**.connectionManager.carrierFrequency = 2.4e+9Hz # [Hz]

# max transmission power [mW]
**.connectionManager.pMax = 110.11mW # [mW]
# signal attenuation threshold [dBm]
**.connectionManager.sat = -120dBm # [dBm]
# path loss coefficient alpha
**.connectionManager.alpha = 4
**.connectionManager.sendDirect = false

##############################################################################
# Parameters for the Mac
Layer #
##############################################################################
# debug switch
**.mac.headerLength = 272 bit
**.mac.queueLength = 14
**.mac.bitrate = 2E+6bps# in bits/second
**.mac.autoBitrate = false
### values if no fading is modelled, gives at most 1% packet error
rate
**.mac.snr2Mbit = 1.46dB # [dB]
**.mac.snr5Mbit = 2.6dB # [dB]
**.mac.snr11Mbit = 5.68dB # [dB]
**.mac.rtsCtsThreshold = 400
**.mac.neighborhoodCacheSize = 30
**.mac.neighborhoodCacheMaxAge = 100s # [s]
**.mac.txPower = 110.11mW # [mW]

##############################################################################
# Parameters for the
Phy #
##############################################################################
**.phy.usePropagationDelay = false
**.phy.thermalNoise = -110dBm # [dBm]
**.phy.analogueModels = xmldoc("config.xml")
**.phy.decider = xmldoc("config.xml")
**.phy.sensitivity = -119.5dBm # [dBm]
**.phy.maxTXPower = 110.11mW
**.phy.initialRadioState = 0
**.phy.useThermalNoise = true
_______________________________________________________________________________
With these parameteres, we obtain (from connectionMananger module):
carrierFrequency: 2.4e+09
pMax: 110.11
sat: -120
alpha: 4
waveLength: 0.124914
minReceivePower: 1e-12
interfDistance: 322.966

And I insist that interfDistance is not the transmission range, but
the interferance distance.
Two nodes in the interference range of each other can not necessary
send/receive to each other.

My question is how to compute the (maximum) transmission range.

Regards,
Oudam.

On 17 oct, 12:18, Leonardo Maccari <leonardo.macc...@disi.unitn.it>
wrote:

> On 17/10/2011 12:03, Oudam wrote:
>
>
>
> > interfDistance = pow(waveLength * waveLength * pMax
> >                             / (16.0*M_PI*M_PI*minReceivePower),
> >                            1.0 / alpha);
> > Could anyone explain clearly how to compute the maximum value of the
> > tranmission range by using

> > the free space path loss formulahttp://en.wikipedia.org/wiki/Free-space_path_loss,

> > please ?
>
> Theoretically it is just the formula you reported. In practice, it
> depends on the settings you're using (power, sensitivity, PER
> tables...). Usually I use a scenario similar to the one I paste below
> and a corresponding ANF to check the max distance.
>
> ciao,
> leonardo.
>
> [Config TestDistance]
>
> # See anf file for evaluating the max transmission distance
> # at various transmitting power level.
> # Sensitivity values from:

> #http://www.smarteq.se/4.1b27248111ee6cfde1e800011072.html

[Oudam]

Sorr for my double reply,

I would like to precise that I have also computed the value the
transmission range by simulation.
With the parameters below, the estimated value of the tranmission
range is between 180m and 200m.

Less than 175m most of all messages are received, and over than 200 m
no message is received.

Threfore, the maximum value of the transmission range (computed by the
formula) should be around
200m.

[Leonardo Maccari]

On 17/10/2011 12:32, Oudam wrote:
> Hi,
>
> yes of course, the value of interfDistance depends on the values of
> other parameters (waveLenght, pMax, etc).
> It's true theoretically or pratically :)

Ok I'll express it better...
What I meant is that theoretically you can use the same formula you use
to calculate interference for calculating pathloss but then,
communication range changes with the kind of radio you're using. As far
as I've seen with Inet there are a few different ways of doing it (fixed
minimum snir, table..) so it is easier to test it than to calculate it.
Now this is true with Inet, I see now you're using Mixim which I don't
know but i guess it works the same.

ciao,
leonardo.

[Oudam]

Hi Leonardo and everyone, thanks for your reply. Yes, I guess it works
the same too.

I would like just to give some information that may help others to
compute the transmission range in OMNeT++/MiXiM.

As also noted here : http://groups.google.com/group/omnetpp/browse_thread/thread/4322abb33a587582
"The connection manager parameters are used to define the maximum
distance over which a node's transmissions can cause interference.
[...]
The analog model and decider parameters (usually in config.xml) and
the nic.phy parameters (usually in omnetpp.ini) are the ones that
actually model radio behavior and determine the (combined) signal
strength of various transmissions and whether the frame is received
correctly."

In my confix.xml :
------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<root>
<AnalogueModels>
<AnalogueModel type="SimplePathlossModel">
<parameter name="alpha" type="double" value="4.0"/>
<parameter name="carrierFrequency" type="double" value="2.412e
+9"/>
</AnalogueModel>
</AnalogueModels>
<Decider type="Decider80211">
<!-- SNR threshold [NOT dB]-->
<parameter name="threshold" type="double" value="0.12589254117942"/>
</Decider>
</root>
------------------------------------------------------------------------------------

The packet is received if (Tranmission power [dBm]) - (Attenuation
[dB]) > (Sensitivity [dBm]).
(Path loss =) Attenuation [dB] = 10*alpha*log10(f) + 10*alpha*log10(d)
+ 32.45 [dB]
Under ideal conditions, the path loss is calculated with the path loss
coffecient alpha = 2. In my case, alpha = 4.

That is in my omnetpp.ini
**.phy.maxTXPower = 110.11mW (= 10*LOG_10(110.11) = 20.4182676264)
**.phy.sensitivity = -119.5dBm

With d = 201m:
- Attenuation = 139.8729344355dB
- Tranmission power - Attenuation = 20.4182676264 - 139.8729344355dB =
-119.4546668091
- Tranmission power - Attenuation > Sensitivity (-119.4546668091 >
-119.5)

With d = 202m:
- Attenuation = 139.9591469166dB
- Tranmission power - Attenuation = 20.4182676264 - 139.9591469166 =
-119.5408792902
- Tranmission power - Attenuation - Sensitivity (-119.540879290 <
-119.5)

Therefore, the maximal tranmission range (in my case) is between 201m
and 202m.
I have obtained the same results in my simulation (with two nodes A
and B): if distance(A,B) > 200m, no message is received (and less than
175m, most of broadcast messages are received).

Could anyone confirme my calculations (is the formula is correct ? or
may I have forgetten some parameter... ?) ?

Thanks in advance, and I hope this can help.

Regards,
Oudam

On 17 oct, 15:00, Leonardo Maccari <leonardo.macc...@disi.unitn.it>
wrote:

[Faranak Moayeri]

Thank you Oudam :)

[Gary G.]

Hi there. Is it possible to do so in INET MANET?

On Oct 18, 11:54 pm, Oudam <oudam.ream....@gmail.com> wrote:
> Hi Leonardo and everyone, thanks for your reply. Yes, I guess it works
> the same too.
>
> I would like just to give some information that may help others to
> compute the transmission range in OMNeT++/MiXiM.
>

> As also noted here :http://groups.google.com/group/omnetpp/browse_thread/thread/4322abb33...

[Awais Ahmad]

I have used "r" tag in my display setting but it even remove the icon from my nodes. my setting statement is .

 @display("p=139,96;i=device/cellphone,r=100");

[nb1...@shibaura-it.ac.jp]

Awais,

You should put a semicolon ";" before the "r=100", not a comma ",". That's just a syntax error. It should be written as follows:

@display("p=139,96;i=device/cellphone;r=100");

[Ahtesham Rahim]

dear. thought I can't help you because I am in initial stages.. can u please let me know how to define rage of the node and how to introduce mobility? 
if u could send me some attachments of pictures or some some file.. this will help me a lot.. and this really means to me...
thanking you in advance... 
my email
ahtesha...@gmail.com

[Alfonso Ariza Quintana]

**.maxDistance = 100m

 

Set the transmission distance to 100 meters

See the examples. The mobility model is selected in the ini file, for example

**.host*.mobilityType = "LinearMobility"

--

You received this message because you are subscribed to the Google Groups "omnetpp" group.

To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ahtesham Rahim]

can you send me the a small example ? or I should give you my project and can you help me in making it..?? your help really means to me... 
Thanks a lot for your attention..
if you feel free my skype name is:  ahteshamrahim
if you can give me sometime there.. I shall be very thankful to you..

[Alfonso Ariza Quintana]

There are several examples in in the inet framework, you can use them

[Ahtesham Rahim]

thank you sir. but can you just give me some time so it may help me..
can you contact me through skype..??

[vikram kumar]

can anyone here help in how to show and form cluster of nodes in ns2....code would be helpful

.