[omnetpp] Event after Sim Time Limit reached omnet/ mobility Framework

[us...@stud.uni-karlsruhe.de]

Hello All,

in my simulation run I get an event during/after my sim-time-limt.
I writen my own ApplLayer Modul which send every second ONE Broadcast
Package. Beginning at 0s. My sim-time-limit is 0.8s. But OMNet++ did
not stop the simulation at 0.8s and send a new Broadcast Message at
1.00s. Then the Simulation stop.

** Event #170 T=0.0022210000 ( 2ms). (Mac80211) sim.host[0].nic.mac(id=49)
** Event #171 T= 1 ( 1.00s). (PeriodicBurstApplLayer)
sim.host[0].appl (id=45)
host[0]::PeriodicBurstApplLayer: Sending broadcast packet!

<!> Simulation time limit reached -- simulation stopped.

Calling finish() at end of Run #1...

So I am wondering why OMNet don´t stop the simulation at 0.8s

I use OMNet 3.3 and the mobility frameworkp3.
Thank you for help

Oliver Graute

_______________________________________________
OMNeT++ Mailing List
options: http://lists.omnetpp.org/mailman/listinfo/omnetpp-l
archive: http://www.omnetpp.org/listarchive/index.php

[Alfonso Ariza Quintana]

The timer is actualize each time that a event is produce, after arrive the 1 second packet the timer is not actualized.

In pseudo code :

Actualize timer to the next event time;
If timer >= time_limit
Finalize;

> Date: Fri, 16 Nov 2007 14:22:05 +0100> From: us...@stud.uni-karlsruhe.de> To: omne...@omnetpp.org> Subject: [omnetpp] Event after Sim Time Limit reached omnet/ mobility Framework> > Hello All,> > in my simulation run I get an event during/after my sim-time-limt.> I writen my own ApplLayer Modul which send every second ONE Broadcast > Package. Beginning at 0s. My sim-time-limit is 0.8s. But OMNet++ did > not stop the simulation at 0.8s and send a new Broadcast Message at > 1.00s. Then the Simulation stop.> > ** Event #170 T=0.0022210000 ( 2ms). (Mac80211) sim.host[0].nic.mac(id=49)> ** Event #171 T= 1 ( 1.00s). (PeriodicBurstApplLayer) > sim.host[0].appl (id=45)> host[0]::PeriodicBurstApplLayer: Sending broadcast packet!> > <!> Simulation time limit reached -- simulation stopped.> > > Calling finish() at end of Run #1...> > So I am wondering why OMNet don´t stop the simulation at 0.8s> > I use OMNet 3.3 and the mobility frameworkp3.> Thank you for help> > Oliver Graute> > _______________________________________________> OMNeT++ Mailing List> options: http://lists.omnetpp.org/mailman/listinfo/omnetpp-l> archive: http://www.omnetpp.org/listarchive/index.php
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

[Roberto Riggio]

Hi,

why the opp_makemake is an sh script? I'm using it in ubuntu
and in this distribution sh points to dash not to bash.

I believe that since opp_makemake uses bash stuff it should
be a bash script?

Basically if I use it unchanged i get the following error:

/bin/sh: Can't open opp_makedep
Error: command 'opp_makedep -Y --objdirtree -fMakefile -- *.cc' returned nonzero exit code

Bye
R.

[Christoph Sommer]

Hi,

Roberto Riggio wrote:
> why the opp_makemake is an sh script? I'm using it in ubuntu
> and in this distribution sh points to dash not to bash.
>
> I believe that since opp_makemake uses bash stuff it should
> be a bash script?
>
> Basically if I use it unchanged i get the following error:
>
> /bin/sh: Can't open opp_makedep
> Error: command 'opp_makedep -Y --objdirtree -fMakefile -- *.cc' returned nonzero exit code

I couldn't find any bash-specific commands in the script, so I guess the
error is because of dash not reading .bashrc or .bash_profile.

This way, the path to the omnetpp binaries is not added to the shell's
environment and execution of opp_makedep fails.

The easiest way I found around all the hickups with Makefiles' shells
not sourcing my .shrc was running "sudo dpkg-reconfigure dash" and
choosing bash as my /bin/sh :)

Regards,

Christoph