Re: [Omnetpp-l] Digest for omnetpp@googlegroups.com - 25 updates in 10 topics

48 views
Skip to first unread message

Bhaskar Bhuyan

unread,
Nov 26, 2014, 8:56:10 AM11/26/14
to omn...@googlegroups.com

Hi
I am facing installation problem of omnetpp-4.5 in open suse 12.3

Following is the snapshot of error:
make[2]: *** [/home/work/omnetpp-4.5/out/gcc-release/src/envir/opp_run_release] Error 1
make[2]: Leaving directory `/home/work/omnetpp-4.5/src/envir'
make[1]: *** [base] Error 2
make[1]: Leaving directory `/home/work/omnetpp-4.5'
make: *** [allmodes] Error 2


Looking forward to some suggestion.

Regards,

Bhaskar

On Wed, Nov 26, 2014 at 4:31 AM, <omn...@googlegroups.com> wrote:
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 05:39AM -0800

That is no error message, that's just the environmental variables.
 
Please provide your exact error message not just some output from the
console...
 
Am Dienstag, 25. November 2014 06:03:54 UTC+1 schrieb Taher Antara:
Taher Antara <anta...@gmail.com>: Nov 25 09:03AM -0800

The problem occurred box shows this
 
ORun #0: Finished with Error
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 03:00PM -0800

Great... and that tells me (again) nothing.
 
What did you start? An INET example?
 
Am Dienstag, 25. November 2014 18:03:50 UTC+1 schrieb Taher Antara:
"Đạt Lê khánh" <datl...@gmail.com>: Nov 24 11:53PM -0800

In inetmanet / src / wpan / applications / Ieee802154TestApp
/ Ieee802154TestApp.cc.
 
 
void Ieee802154TestApp::handleLowerMsg(cMessage* apMsg)
{
...
simtime_t e2eDelay;
Ieee802154AppPkt* tmpPkt = check_and_cast<Ieee802154AppPkt *>(apMsg);
e2eDelay = simTime() - tmpPkt->getCreationTime();
e2eDelayVec.record(SIMTIME_DBL(e2eDelay));
....
}
 
and
 
sumE2EDelay += e2eDelay;
meanE2EDelayVec.record(sumE2EDelay/numReceived);
 
 
I know this code to calculate delay by dont understand meaning of these,
Can you explain to me?
 
thank you!
Alfonso Ariza Quintana <aari...@hotmail.com>: Nov 25 08:57AM +0100

1.- End to end delay vector
 
2.- mean end-to-end delay
 

 

 
De: omn...@googlegroups.com [mailto:omn...@googlegroups.com] En nombre de Ð?t Lê khánh
Enviado el: martes, 25 de noviembre de 2014 8:54
Para: omn...@googlegroups.com
Asunto: [Omnetpp-l] Can you explain to me the meaning of this code
 

 
In inetmanet / src / wpan / applications / Ieee802154TestApp / Ieee802154TestApp.cc.
 

 

 
void Ieee802154TestApp::handleLowerMsg(cMessage* apMsg)
{
...
simtime_t e2eDelay;
 
Ieee802154AppPkt* tmpPkt = check_and_cast<Ieee802154AppPkt *>(apMsg);
 
e2eDelay = simTime() - tmpPkt->getCreationTime();
e2eDelayVec.record(SIMTIME_DBL(e2eDelay));
....
}
 

 
and
 

 
sumE2EDelay += e2eDelay;
meanE2EDelayVec.record(sumE2EDelay/numReceived);
 

 
I know this code to calculate delay by dont understand meaning of these, Can you explain to me?
 
 
thank you!
 
--
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 <mailto:omnetpp+u...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.
"Đạt Lê khánh" <datl...@gmail.com>: Nov 25 12:07AM -0800

Can you explain this in more detail? For example,
 
e2eDelay = simTime() - tmpPkt->getCreationTime();
 
What is meaning of this line code?
 
Vào 14:58:22 UTC+7 Thứ ba, ngày 25 tháng mười một năm 2014, Alfonso Ariza
Quintana đã viết:
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 05:51AM -0800

Simple...
end-to-end-delay is calculated by substracting the creation time (
getCreationTime) of the received packet from the current time (simTime).
 
Am Dienstag, 25. November 2014 09:07:15 UTC+1 schrieb Đạt Lê khánh:
"Lê Khánh Đạt" <datl...@gmail.com>: Nov 25 10:38PM +0700

what is "creation time", can you give me an example?
 
On Tue, Nov 25, 2014 at 8:51 PM, Michael Kirsche <
 
--
---------------Le Khanh Dat
--------Student of K56D-FET-UET-VNU
-----Tel: 0164.874.1193
--www.facbook.com/khanhdatle
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 02:57PM -0800

You're kidding right?
 
getCreationTime -> time that the message was created.
This is more than obvious...
 
Am Dienstag, 25. November 2014 16:38:41 UTC+1 schrieb Đạt Lê khánh:
mohammad nekooei <nekoo...@gmail.com>: Nov 25 02:40PM -0800

I am running a test in IEEE 802.15.4 in inetmanet 2.0. However, the average
end to end delay dose not show reasonable results. When there are two
sensors, the average end to end delay is about 0.5s. But when I increase
the number of nodes in the network, the average end-to-end delay decreases
instead of increasing and reaches about 0.2s! Also I set **.mac.BO= 8
and **.mac.SO= 7. Could anybody help me out?
 
 
 
seed-0-mt = 861
sim-time-limit = 1800s
############################################7#################################
# Network settings
#
##############################################################################
 
**.constraintAreaMinX = 0m
**.constraintAreaMinY = 0m
**.constraintAreaMinZ = 0m
**.constraintAreaMaxX = 300m
**.constraintAreaMaxY = 300m
**.constraintAreaMaxZ = 0m
 
##############################################################################
# Mobility settings
#
##############################################################################
**.sensor[*].mobilityType = "StationaryMobility"
**.mobility.initFromDisplayString = false
**.sensor[0].mobility.initialX = 150m
**.sensor[0].mobility.initialY = 150m
 
**.sensor[1].mobility.initialX = 65.14m
**.sensor[1].mobility.initialY = 65.14m
#**.sensor[2].mobility.initialX = 170m
#**.sensor[2].mobility.initialY = 33.8m
#**.sensor[3].mobility.initialX = 65.14m
#**.sensor[3].mobility.initialY = 234.86m
#**.sensor[4].mobility.initialX = 33.8m
#**.sensor[4].mobility.initialY = 150m
#**.sensor[5].mobility.initialX = 270m
#**.sensor[5].mobility.initialY = 150m
#**.sensor[6].mobility.initialX = 215.14m
#**.sensor[6].mobility.initialY = 234.86m
#**.sensor[6].mobility.initialX = 215.14m
#**.sensor[6].mobility.initialY = 65.14m
#**.sensor[7].mobility.initialX = 234.86m
#**.sensor[7].mobility.initialY = 234.8m
#**.sensor[8].mobility.initialX = 107m
#**.sensor[8].mobility.initialY = 50m
**.sensor[*].mobility.initialZ = 0m
 
##############################################################################
# Parameters for the application-layer (TrafGen)
#
##############################################################################
**.sensor[0].app.isSink = true
**.sensor[0].app.packetSize = 10B
**.sensor[0].app.firstPacketTime = exponential(1s)
**.sensor[0].app.WBANSensorType ="Coordinator"
 
**.sensor[*].app.trafDest = "sensor[0]" # the default is "BROARDCAST"
 
**.sensor[1].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
**.sensor[1].app.packetSize = 2.5B
**.sensor[1].app.interDepartureTime = exponential(1s)
**.sensor[1].app.firstPacketTime = exponential(1s)
 
 
#**.sensor[2].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[2].app.packetSize = 12.5B
#**.sensor[2].app.interDepartureTime = exponential(1s)
#**.sensor[2].app.firstPacketTime = exponential(1s)
 
 
#**.sensor[3].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[3].app.packetSize = 102B
#**.sensor[3].app.interDepartureTime = 0.6528s
#**.sensor[3].app.firstPacketTime = exponential(1s)
 
 
#**.sensor[4].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[4].app.packetSize = 12.5B
#**.sensor[4].app.interDepartureTime = 1s
#**.sensor[4].app.firstPacketTime = exponential(1s)
 
 
#**.sensor[5].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[5].app.packetSize = 20B
#**.sensor[5].app.interDepartureTime = 1s
#**.sensor[5].app.firstPacketTime = exponential(1s)
 
#**.sensor[6].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[6].app.packetSize = 12.5B
#**.sensor[6].app.interDepartureTime = exponential(1s)
#**.sensor[6].app.firstPacketTime = exponential(1s)
 
#**.sensor[7].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[7].app.packetSize = 45B
#**.sensor[7].app.interDepartureTime = 1s
#**.sensor[7].app.firstPacketTime = exponential(1s)
 
#**.sensor[8].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[8].app.packetSize = 100B
#**.sensor[8].app.interDepartureTime = 1s
#**.sensor[8].app.firstPacketTime = exponential(1s)
 
#**.sensor[9].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[9].app.packetSize = 110B
#**.sensor[9].app.interDepartureTime = 1s
#**.sensor[9].app.firstPacketTime = 1s
 
#**.sensor[10].app.isSink = false # the default is ture, if it is ture then
the node doesn't send traffic
#**.sensor[10].app.packetSize = 62.5B
#**.sensor[10].app.interDepartureTime = 1s
#**.sensor[10].app.firstPacketTime = 1s
 
##############################################################################
# Parameters for the network-layer #
##############################################################################
 
**.sensor[0].net.isPANCoor = true # should be consistent with those in MAC
**.sensor[*].net.isPANCoor = false
 
##############################################################################
# Parameters for the network interface and IFqueue #
##############################################################################
 
#**.nic.ifqType = "PriorityQueue"
**.nic.ifqType = "DropTailQueue"
**.ifq.frameCapacity = 200000 #default is 100
##############################################################################
# Parameters for MAC layer #
##############################################################################
 
**.sensor[0].**.mac.isPANCoor = true
**.sensor[0].**.mac.WBANSensorType="Coordinator"
 
**.sensor[*].**.mac.isPANCoor = false
**.mac.panCoorName = "sensor[0]"
**.mac.BO = 8 # range [1,14]
**.mac.SO = 7 #range [0, BO)
**.sensor[*].**.mac.dataTransMode = 1 # 1: direct; 2: indirect; 3: GTS
# GTS settings
**.sensor[*].**.mac.ack4Gts = false
**.sensor[*].**.mac.gtsPayload = 0 # should be consistent with that in
trafconfig.xml
**.sensor[*].**.mac.isRecvGTS = false # transmit GTS
 
##############################################################################
# Parameters for PHY layer #
##############################################################################
 
**.phy.channelNumber = 11 # default 2.4G, (range [0, 26])
**.phy.transmitterPower = 1.0mW #[mW]
**.phy.sensitivity = -85dBm #[dBm]
**.phy.thermalNoise = -110dBm #[dBm]
**.phy.pathLossAlpha = 2
**.phy.snirThreshold = 4dB
 
##############################################################################
# Parameters for the channel control
#
##############################################################################
 
# channel physical parameters
*.channelControl.carrierFrequency = 2.4GHz
*.channelControl.pMax = 2.0mW
*.channelControl.sat = -85dBm
*.channelControl.alpha = 2
*.channelControl.numChannels = 27
*.channelControl.propagationModel = "LogNormalShadowingModel"
 
##############################################################################
# Parameters for the display module in the hosts
#
##############################################################################

# display parameters (same as channelControl parameters and mac parameters)
**.disp.carrierFrequency = 2.4GHz
**.disp.pMax = 2.0mW
**.disp.sat = -85dBm #[dBm]
**.disp.alpha = 2
**.disp.numChannels = 27
**.disp.transmitterPower = 1.0mW #[mW]
**.disp.sensitivity = -85dBm #[dBm]
 
##############################################################################
# Parameters for the Energy Model (units: mAh and mA)
#
##############################################################################
**.phy.usageCpuActive = 7.6
**.phy.usageCpuSleep = 0.237 ## 3.3 mA for IDLE mode, 0.237 mA for Standby
 
 
**.phy.usage_radio_idle = 1.38mA #[mA]
**.phy.usage_radio_recv = 9.6mA #[mA]
**.phy.usage_radio_sleep = 0.06mA #[mA]
 
 
**.battery.nominal = 25
**.battery.capacity = 25
**.battery.voltage = 10
**.battery.resolution = 1s
**.battery.publishDelta = 0.5
**.battery.publishTime = 20s
 
##############################################################################
# Output vectors
#
##############################################################################
**.End-to-end delay.vector-recording = true
**.Mean end-to-end delay.vector-recording = true
#**.vector-recording = true
**.queueLength.vector-recording = true
 
##############################################################################
# Simulation runs
#
##############################################################################
"Rayane Sibaï" <rayyan...@gmail.com>: Nov 25 07:02AM -0800

Hello,
In the results of the simulation in OMNeT + sumo using Veins3a3, a vehicle
has such position: startPos (616.75,48.45,0) direction (6.12303e-017,1,0).
however, in my network, the maximum value of x 500m and for y is 300m. My
question is how to know the true position (x and y coordinates of the
vehicle) at a precise moment.
Thank in advance
Christoph Sommer <som...@ccs-labs.org>: Nov 25 07:40PM +0100

Rayane Sibaï wrote:
> a vehicle has such position: startPos (616.75,48.45,0) direction
> (6.12303e-017,1,0). however, in my network, the maximum value of x 500m
> and for y is 300m. My question is how to know the true position
 
This is a frequently asked question.
 
Please have a look at the FAQ on
http://veins.car2x.org/documentation/faq/
 
Best,
 
Christoph
 
--
Dr. Christoph Sommer
Distributed Embedded Systems Group
University of Paderborn, Germany
http://www.ccs-labs.org/~sommer/
"Anna Förster" <anna.f...@gmail.com>: Nov 25 12:31AM -0800

Dear all,
 
I am looking for an existing virtual image of OMNeT++/MiXiM. We are
preparing a summer school course on simulation of WSNs with OMNeT++, but we
would like to prepare all our examples before the course and provide a
complete virtual image to the students. I know that installation is quite
straightforward, but in fact we had some troubles installing MiXiM on top
of the newest OMNeT++ and it still takes some time, which we would prefer
to use for teaching.
 
Has someone already done it?
 
Thank you,
Anna
Florian Meier <floria...@koalo.de>: Nov 25 09:59AM +0100

Hi Anna,
I can not provide you a working image, but maybe you should consider
using the newest INET
(https://github.com/inet-framework/inet/tree/integration), since MiXiM
is now fully integrated there.
 
MiXiM itself does not seem to be maintained any longer and contains at
least one unfixed bug (that is fixed in INET).
 
If you are interested, I would try to set up something with the newest
INET, since it would be interesting for me anyway.
 
Greetings,
Florian
 
On 11/25/2014 09:31 AM, Anna Förster wrote:
"Anna Förster" <anna.f...@gmail.com>: Nov 25 01:03AM -0800

Hi Florian,
 
this sounds great! In fact, I just reported a bug, which we discovered
during our latest work with MiXiM. I have to admit that it would be a great
help, if you can find the time to make the virtual image. If you do not,
please let me know, so we can start doing it.
 
Thanks!
Anna
 
On Tuesday, November 25, 2014 10:00:12 AM UTC+1, Florian Meier wrote:
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 06:29AM -0800

I have a couple of "naked" VMs with OMNeT 4.6 and INET 2.5 installed. 32 or
64bit and the basic toolset is of course installed.
Usually Xubuntu or Lubuntu with basic tools.
Set-up for VMware...
 
Are you planing to use Virtual Box or VMware Player Anna?
 
Cheers,
Michael
 
Am Dienstag, 25. November 2014 10:03:05 UTC+1 schrieb Anna Förster:
"Anna Förster" <anna.f...@gmail.com>: Nov 25 03:46PM +0100

I think we are going for VirtualBox, but this is not a hard requirement. Could you put the VM somewhere to download, so we can try it out? Thank you!!!
 
Anna
---
Dr. Anna Förster
Gradinata ai Ronchi 5
6962 Viganello, Schweiz
anna.f...@gmail.com
 
 
 
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 07:43AM -0800

I'll have to change the VM from VMware to Virtualbox first and pack it.
Any other specific software requirements? Or just INET, OMNeT and MiXiM???
 
Am Dienstag, 25. November 2014 15:47:09 UTC+1 schrieb Anna Förster:
jay doley <jay129...@gmail.com>: Nov 24 11:48PM -0800

Moreover Sir tclConfig.sh file is present in usr/lib/tcl8.4, is it
necessary to have init.tcl file too in that tcl8.4 directory !!! please
help ..
 
 
On Tuesday, November 25, 2014 12:58:38 PM UTC+5:30, jay doley wrote:
Michael Kirsche <michael...@tu-cottbus.de>: Nov 25 05:50AM -0800

On one of my VMs where I've installed TCL/TK 8.5, the TCL_LIBRARY variable
points to /usr/lib/tcl8.5.
 
So you settings is probably wrong (or the installation not correct).
 
You should adjust the setting via your .bashrc file (under Ubuntu and its
derivates for example) with
export TCL_LIBRARY=/usr/lib/tcl8.5
 
 
Am Dienstag, 25. November 2014 08:48:13 UTC+1 schrieb jay doley:
Christoph Sommer <som...@ccs-labs.org>: Nov 25 10:16AM +0100

krisies1150 wrote:
> The nodes will teleport out from the simulation after the accident
> happens. i would like to know how to change or disable [this]
 
This behavior is hard-wired in SUMO and can only be changed by modifying
the source code of the traffic simulation.
 
SUMO employs a movement model that (in theory) is collision free. When a
collision happens, it concludes that there must be a problem with the
simulation and tries to resolve this by removing affected vehicles, so
that the simulation can continue as normal.
 
 
Best,
 
Christoph
 
--
Dr. Christoph Sommer
Distributed Embedded Systems Group
University of Paderborn, Germany
http://www.ccs-labs.org/~sommer/
smn smn <smn...@gmail.com>: Nov 25 06:14PM +0900

Dear All,
 
How to get packet delivery ratio, avg end to end delay and no. of link
failure in AODV? How to get it in the result file?
 
Also, there is no unit in scalar or vector files. How to change it?
 
"Anna Förster" <anna.f...@gmail.com>: Nov 25 01:00AM -0800

Dear all,
 
this is to draw your attention to a small error in the parameter settings
of BMAC for MiXiM. In the omnetpp.ini file of the default installation, you
can find:
 
**.node[*].nic.phy.timeRXToTX = 0s
**.node[*].nic.phy.timeRXToSleep = 0s
 
**.node[*].nic.phy.timeTXToRX = 0s
**.node[*].nic.phy.timeTXToSleep = 0s
 
**.node[*].nic.phy.timeSleepToRX = 0s
**.node[*].nic.phy.timeSleepToTX = 0s
 
This means that the switching times of the radio have been set to zero.
This is OK, even if quite unrealistic. However, a change in MiXiM from
2.2.1 to 2.3 in BasePhylayer.cc says:
 
// if switching is done in exactly zero-time no extra self-message is
scheduled
 
if (switchTime == SIMTIME_ZERO) {
 
// In case of zero-time-switch, send no control-message to MAC!
 
finishRadioSwitching(false);
 
}
 
 
This leads to the NON sending the RADIO_SWITCHING_OVER message, which
breaks BMAC. What happens is that BMAC is waiting for this message in order
to start sending something. If it never arrives, it will never send
anything.
 
 
SOLUTION: simply put some tiny numbers for the switching times in
omnetpp.ini.
 
 
LONG-TERM SOLUTION: I don't know why this change was introduced. However, I
am not convinced that this is a good idea. This means that the behaviour of
a simulation is different dependant on a parameter in a way, that it breaks
it. The parameter of the switching time for the radio should be used only
in the corresponding module and not in other, completely independent ones.
Or what was the idea behind this?
 
 
Cheers, Anna
"Đạt Lê khánh" <datl...@gmail.com>: Nov 24 11:59PM -0800

In inetmanet / src / wpan / applications / Ieee802154TestApp
/ Ieee802154TestApp.cc.
 
 
void Ieee802154TestApp::handleLowerMsg(cMessage* apMsg)
{
...
simtime_t e2eDelay;
Ieee802154AppPkt* tmpPkt = check_and_cast<Ieee802154AppPkt *>(apMsg);
e2eDelay = simTime() - tmpPkt->getCreationTime();
e2eDelayVec.record(SIMTIME_DBL(e2eDelay));
....
}
 
and
 
sumE2EDelay += e2eDelay;
meanE2EDelayVec.record(sumE2EDelay/numReceived);
 
 
I know this code to calculate delay by dont understand meaning of these,
Can you explain to me?
 
thank you!
Alfonso Ariza Quintana <aari...@hotmail.com>: Nov 25 09:08AM +0100

when the a packet is created the field creationTime is set,
 
e2eDelay = simTime() - tmpPkt->getCreationTime();
 
is the time since the creation, due to that the packet is sent immediately after the creation this is the end to end delay
 

 
the second you can find in any basic statistic book
 

 
 
 

 

 
De: omn...@googlegroups.com [mailto:omn...@googlegroups.com] En nombre de Ð?t Lê khánh
Enviado el: martes, 25 de noviembre de 2014 9:00
Para: omn...@googlegroups.com
Asunto: [Omnetpp-l] Can you explain to me the meaning of this code
 

 
 
In inetmanet / src / wpan / applications / Ieee802154TestApp / Ieee802154TestApp.cc.
 

 

 
void Ieee802154TestApp::handleLowerMsg(cMessage* apMsg)
{
...
simtime_t e2eDelay;
 
Ieee802154AppPkt* tmpPkt = check_and_cast<Ieee802154AppPkt *>(apMsg);
 
e2eDelay = simTime() - tmpPkt->getCreationTime();
e2eDelayVec.record(SIMTIME_DBL(e2eDelay));
....
}
 

 
and
 

 
sumE2EDelay += e2eDelay;
meanE2EDelayVec.record(sumE2EDelay/numReceived);
 

 
I know this code to calculate delay by dont understand meaning of these, Can you explain to me?
 
 
thank you!
 
--
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 <mailto:omnetpp+u...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to omnetpp+u...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages