Here we make the model look a bit prettier in the GUI. We assign the "block/routing" icon (the file
images/block/routing.png), and paint it cyan for tic and yellow for toc. This is achieved by adding display strings to the NED file. The
i= tag in the display string specifies the icon.
You can see the result here:
We also modify the C++ file to add some debug messages to Txc1 by writing to the OMNeT++
EV object like this:
When you run the simulation in the OMNeT++ runtime environment, the following output will appear in the log window:
You can also open separate output windows for tic and toc by right-clicking on their icons and choosing Component log from the menu. This feature will be useful when you have a large model ("fast scrolling logs syndrome") and you're interested only in the log messages of specific module.
In this step we add a counter to the module, and delete the message after ten exchanges.
We add the counter as a class member:
We set the variable to 10 in initialize() and decrement in handleMessage(), that is, on every message arrival. After it reaches zero, the simulation will run out of events and terminate.
line in the source: this makes it possible to see the counter value in the graphical runtime environment. Double-click on tic's icon, then choose the Contents page from the inspector window that pops up.
As you continue running the simulation, you can follow as the counter keeps decrementing until it reaches zero.
In this step you'll learn how to add input parameters to the simulation: we'll turn the "magic number" 10 into a parameter and add a boolean parameter to decide whether the module should send out the first message in its initialization code (whether this is a tic or a toc module).
Module parameters have to be declared in the NED file. The data type can be numeric, string, bool, or xml (the latter is for easy access to XML config files), among others.
We also have to modify the C++ code to read the parameter in initialize(), and assign it to the counter.
We can use the second parameter to decide whether to send initial message:
Now, we can assign the parameters in the NED file or from omnetpp.ini. Assignments in the NED file take precedence. You can define default values for parameters if you use the
default(...) syntax in the NED file. In this case you can either set the value of the parameter in omnetpp.ini or use the default value provided by the NED file.
Here, we assign one parameter in the NED file:
and the other in omnetpp.ini:
Note that because omnetpp.ini supports wildcards, and parameters assigned from NED files take precedence over the ones in omnetpp.ini, we could have used
with the same effect. (The difference between * and ** is that * will not match a dot and ** will.)
In the graphical runtime environment, you can inspect module parameters either in the object tree on the left-hand side of the main window, or in the Parameters page of the module inspector (opened via double-clicking on the module icon).
The module with the smaller limit will delete the message and thereby conclude the simulation.
If we take a closer look at the NED file we will realize that
toc differs only in their parameter values and their display string. We can create a new simple module type by inheriting from an other one and specifying or overriding some of its parameters. In our case we will derive two simple module types (
Toc). Later we can use these types when defining the submodules in the network.
Deriving from an existing simple module is easy. Here is the base module:
And here is the derived module. We just simply specify the parameter values and add some display properties.
Toc module looks similar, but with different parameter values.
Once we created the new simple modules, we can use them as submodule types in our network:
As you can see, the network definition is much shorter and simpler now. Inheritance allows you to use common types in your network and avoid redundant definitions and parameter settings.
In the previous models, tic and toc immediately sent back the received message. Here we'll add some timing: tic and toc will hold the message for 1 simulated second before sending it back. In OMNeT++ such timing is achieved by the module sending a message to itself. Such messages are called self-messages (but only because of the way they are used, otherwise they are ordinary message objects).
We added two cMessage * variables,
tictocMsg to the class, to remember the message we use for timing and message whose processing delay we are simulating.
We "send" the self-messages with the scheduleAt() function, specifying when it should be delivered back to the module.
In handleMessage() now we have to differentiate whether a new message has arrived via the input gate or the self-message came back (timer expired). Here we are using
but we could have written
We have left out the counter, to keep the source code small.
While running the simulation you will see the following log output:
In this step we'll introduce random numbers. We change the delay from 1s to a random value which can be set from the NED file or from omnetpp.ini. Module parameters are able to return random variables; however, to make use of this feature we have to read the parameter in
handleMessage() every time we use it.
In addition, we'll "lose" (delete) the packet with a small (hardcoded) probability.
We'll assign the parameters in omnetpp.ini:
You can try that no matter how many times you re-run the simulation (or restart it, Simulate|Rebuild network menu item), you'll get exactly the same results. This is because OMNeT++ uses a deterministic algorithm (by default the Mersenne Twister RNG) to generate random numbers, and initializes it to the same seed. This is important for reproducible simulations. You can experiment with different seeds if you add the following lines to omnetpp.ini:
From the syntax you have probably guessed that OMNeT++ supports more than one RNGs. That's right, however, all models in this tutorial use RNG 0.
Exercise: Try other distributions as well.
In order to get one step closer to modelling networking protocols, let us transform our model into a stop-and-wait simulation. This time we'll have separate classes for tic and toc. The basic scenario is similar to the previous ones: tic and toc will be tossing a message to one another. However, toc will "lose" the message with some nonzero probability, and in that case tic will have to resend it.
Here's toc's code:
Thanks to the bubble() call in the code, toc'll display a callout whenever it drops the message.
So, tic will start a timer whenever it sends the message. When the timer expires, we'll assume the message was lost and send another one. If toc's reply arrives, the timer has to be cancelled. The timer will be (what else?) a self-message.
Cancelling the timer will be done with the cancelEvent() call. Note that this does not prevent us from being able to reuse the same timeout message over and over.
You can read Tic's full source in txc8.cc.
In this step we refine the previous model. There we just created another packet if we needed to retransmit. This is OK because the packet didn't contain much, but in real life it's usually more practical to keep a copy of the original packet so that we can re-send it without the need to build it again. Keeping a pointer to the sent message - so we can send it again - might seem easier, but when the message is destroyed at the other node the pointer becomes invalid.
What we do here is keep the original packet and send only copies of it. We delete the original when toc's acknowledgement arrives. To make it easier to visually verify the model, we'll include a message sequence number the message names.
In order to avoid handleMessage() growing too large, we'll put the corresponding code into two new functions, generateNewMessage() and sendCopyOf() and call them from handleMessage().