Tutorial 4 adding some details
- 1. By Mohammed Amer Al-Batati 2012
- 2. Let every node send a packet periodically. How? Time to go to C++ files. The model behavior is defined by the user as C++ code. The class has to be registered with OMNeT++ via the Define_Module() macro. The Define_ Module() line should always be put into .cc or .cpp files and not header file (.h).
- 3. 1) initialize(). This method is invoked after OMNeT++ has set up the network. 2) handleMessage(cMessage *msg). It is invoked with the message as parameter whenever the module receives a message. handleMessage() is expected to process the message, and then return. 3) finish(). It is called when the simulation has terminated successfully, and its recommended use is the recording of summary statistics.
- 4. The message can arrive: 1. From another module or 2. From the same module (self-messages are used to implement timers).
- 5. Add the following code in Node.cc Why??
- 6. Each node has a limited energy (e,g.; 100mW). Each transmission operation consumes energy (e.g.; 0.8mW per transmission). Make the initial energy variable. Make the transmission interval variable. When a node cannot transmit a packet (the remaining energy is less than 0.8mW), then it stops sending data (dies).
- 7. 1. Modifying NED file:
- 8. 2. Modifying .h file Is it important??
- 9. 3. Modifying .cc file
- 10. 3. Modifying .cc file Sir, Can I use CTRL+SHIFT+F and CTRL+SPACE here?
- 11. 3. Modifying .cc file Sir, Can I use CTRL+SHIFT+F Thanks!! and CTRL+SPACE here?
- 12. Be sure that the previous run was closed. Run the experiment, every thing should work fine. The events are shown in the Tkenv view. Inspect the network By double-clicking on either node1 or node 2, we can see the detailed implementation of our Nodes. But the variables (tx_interval and energy) are not there. To watch them, add WATCH(var) statement
- 13. OMNeT++ provides WATCH() and a set of other macros to allow variables to be inspectable in Tkenv. Always put watches in initialize() Syntax: WATCH(var) Save and Rebuild
- 14. In previous experiments, we were using the default values of both Tx_interval and Energy. Using different parameters can be achieved using the INI file. Open “omnetpp.ini” file. There are two modes, open the Source mode.
- 15. In previous experiments, we were using the default values of both Tx_interval and Energy. Using different parameters can be achieved using the INI file. Open “omnetpp.ini” file. There are two modes, open the Source mode.
- 16. Models can have a large number of parameters to be configured, and it would be tedious to set them one- by-one in omnetpp.ini. OMNeT++ supports wildcard patterns which allow for setting several model parameters at once.
- 17. Assume we want to test our system (Node) with two types of traffic: high and low. We can create a separate section for each type as follows: For every run, we need to select a specific ‘Config name’ .