List of Opnet tutorials and documentation for wireless network creation

List of Opnet tutorials collection and documentations

-->

Files  1	14
2	15
3	16
4	17
5	18
6	19
7	20
8	21
9	22
10	23
11	24
12	25
13

>select the download file list
>select skip the ad in next link
>u will be navigated to the download page>
>download file


other useful for wireless

Wireless sensor network simulation.pdf

underwater simulation.pdf

survey sensor pdf

Radio  pdf

coverage pdf

adhoc survey pdf

Introduction to OPNET simulator, what can you learn?

What's OPNET?

OPNET Modeler is the industry's leading simulator specialized for network research and development. It allows you to design and study communication networks, devices, protocols, and applications with great flexibility. It provides a graphical editor interface to build models for various network entities from physical layer modulator to application processes. All the components are modeled in an object-oriented approach which gives intuitive easy mapping to your real systems. It gives you a flexible platform to test your new ideas and solutions with low cost.

Programming in OPNET

OPNET is a simulator built on top of a discrete event system. It simulates the system behavior by modeling each event happening in the system and processes it by user-defined processes. It uses a hierarchical strategy to organize all the models to build a whole network. The hierarchy models entities from physical link transceivers, antennas, to CPU running processes to manage queues or running protocols, to devices modeled by nodes with process modules and transceivers, to network model that connects all different kinds of nodes together. OPNET also provides programming tools for us to define any type of packet format we want to use in our own protocols. Programming in OPNET includes the following major tasks: define protocol packet format, define the state transition machine for processes running the protocol, define process modules and transceiver modules we need in each device node, finally define the network model by connecting the device nodes together using user-defined link models.

What can you learn?

As we stated above, OPNET is the leading simulator used in industry for network R&D. Also it provides a very detailed modeling tool for you to build a “real” system. By building up simulations in OPNET, you will gain experience of building a communication network in real world. It will also help you to understand all the layering techniques and protocol automatons you learned in the text. Imagine building up your own routers in OPNET and seeing how good they perform! You will become a very experienced network designer through programming with OPNET. A lot of big companies are using OPNET and your OPNET experience will be greatly appreciated by those companies.

IEEE 802.15.4/ZigBee OPNET Simulation Model

NEWS:

IEEE 802.15.4/ZigBee OPNET Simulation Model version 3.0 beta Overview of the simulation model of the IEEE 802.15.4 protocol The idea behind this simulation model was triggered by the need to build a very reliable model of the IEEE802.15.4/ZigBee protocols for Wireless Sensor Networks (WSNs). According to our personal experience, we strongly believe that the current version of the WPAN implementation in the Newtwork Simulator (ns-2) simulator is not accurate for the simulation of wireless sensor networks, even though existing modules can be reused in this context. Our OPNET simulation model implements more accurately the IEEE 802.15.4/ZigBee protocols without these unnecessary overheads, turning its results more reliable than those obtained with ns-2 or OPNET Modeler standard library. This is mainly due to the amount of additional overheads introduced by the ns-2 simulator, since it imposes the use of a UDP (User Datagram Protocol) agent in each node for generating data, and also the generation of ARP (Address Resolution Protocol) frames. In fact, ns-2 was originally developed for IP (Internet Protocol) networks and then extended for IEEE 802.11 wireless networks. Asa first step, we have developed a quite accurate simulation tool forthe IEEE 802.15.4 slotted CSMA/CA mechanism using OPNET Modeler simulator.In the next step, we have extended this simulation model about Guaranteed Time Slot (GTS) mechanism supporting deterministic real-time traffic. Then, we have implemented ZigBee network layer supporting cluster-tree topology and hierarchical tree routing (ZigBee's cluster-tree addressing scheme). Oursimulation model implements the physical layer of the IEEE 802.15.4 standard running at 2.4GHz Frequency band with 250 kbps data rate.The MAC layer supports the beacon-enabledmode and implements slotted CSMA/CA and GTS mechanism according to the standard specfication.There is also a battery module that computes the consumed and remainingenergy levels. The network layer implements hierachical tree routing according to the ZigBee standard. The application layer can generate best effort and/or real-time unacknowledged and/or acknowledged frames transmitted during Contention Access Period (CAP) or Contention Free Period (CFP) (contains GTSs) of the superframe, respectively. The sensor node model is composed of five functional blocks: The physical layer consists of a wireless transceiver (rx for reception and tx for transmission) compliant to the IEEE 802.15.4 specification operating at the 2.4 GHz frequency range with 250 kbps data rate. The modulation scheme is Quadrature Phase Shift Keying (QPSK). The MAC sub-layer implements the slotted CSMA/CA and GTS mechanism (e.g. GTS allocation, deallocation, and reallocation functions). The data traffic incomming from the network layer is stored in the buffers (one buffer for best effort (CAP) data and second one for real-time (GTS) data) and dispatched to the network when the corresponding Contention Access Period (CAP) or Guranteed Time Slot (GTS) is active. This module also controls the generation of the beacon, when the node acts as a PAN Coordinator. The network layer implements the hierarchical tree routing according to the ZigBee standard. The The application layer can generate best effort unacknowledged or acknowledged data frames transmitted during the CAP (using slotted CSMA/CA), and/or time critical unacknowledged or acknowledged data frames transmitted during the GTS. The battery module computes the consumed and remaining energy levels. The default values of current draws are set to those of the MICAz or TelosB mote specifications. Moreover, we use the default wireless models of OPNET library for emulating the background noise, propagation delay, radio interferences, received power, bit error rate, etc. In case of collisions, the reception result depends on the number of collided frames, received power and bit error threshold computed in the default receiver pipelines of the OPNET library. Supported (implemented) Features beacon-enabled mode (beacon frame generation) star-based, peer-to-peer and cluster-tree topologies slotted CSMA/CA MAC protocol different packet formats - directory packets (beacon, command, ack, MAC packet, PHY packet) physical layer characteristics computation of the power consumption (MICAz and TelosB (TmoteSky) motes supported) Guaranteed Time Slot (GTS) mechanism (GTS allocation, deallocation and reallocation functions) generation of the acknowledged or unacknowledged best effort application data (MAC Frame payload = MSDU) transmitted during the Contention Access period (CAP) generation of the acknowledged or unacknowledged real-time application data transmitted during the Contention Free Period (CFP) ZigBee network layer<\li> ZigBee hierarchichal tree routing verification of the nodes' addresses which must correspond to the ZigBee's cluster-tree addressing scheme Non-Supported Features Non beacon-enabled mode Unslotted CSMA/CA MAC protocol PAN management (orphan, join/leave, etc.) Installation Steps The IEEE 802.15.4 OPNET simulation model was developed and tested under the OPNET Modeler Wireless Suite provided under OPNET University Program licence. To install and run this simulation model in your computer, follow these steps (for simulation model version 2.1. and OPNET Modeler version 14.5): Intall the right version of the OPNET Modeler Wireless Suite and configure the environment, if you have not already done. Download the simulation model file and unzip it to any directory. Add this directory to the OPNET Model directories: File > Manage Model Files > Add Model Directory. The name of directory is automatically added to the environment database file: op_admin\env_db14.5. After this the directory name can be found in the Open file dialog: File > Open. Select appropriate Model Directory and File, and press Open. The default scenario contains one analyzer node (wpan_analyzer_node) and three sensor nodes (wpan_sensor_node) organized in a star-based topology. PAN_coordinator is star header and controls the network (e.g. enable/disable GTS mechanism, setting of BO, SO and PAN ID parameters for entire network). node_GTS generates only time critical traffic dipsatched during GTS. On the other side, node_CAP generates unacknowledged and acknowledged traffic dispatched during CAP. Additional nodes can be added from model repository: Topology > Open Object Palette > Node Models > Fixed Node Models > By Name > wpan. See video guide about how to set up the above mentioned network topology. Version History IEEE 802.15.4/ZigBee OPNET Simulation Model version 3.0 beta new structure of the node model ZigBee network layer hierachical tree routing verification of the nodes' addresses which must correspond to the ZigBee's cluster-tree addressing scheme IEEE 802.15.4 OPNET Simulation Model version 2.1 MAC frames (MPDU) are not dispatched direclty to the network but they are prefixed with PHY header (6 bytes) new packet formats for MSDU, MPDU and PPDU (see Data Units) only PPDU is dispatched to the network GTS Setting.Start Time parameter can be set to 0 sec - the dispatching of GTS request is postponed till beacon reception. acknowledgment mechanism for GTS transmission updated transaction-time checking mechanism (a device transmitting within the CAP/GTS shall ensure that its transaction is complete (i.e. including the reception of any acknowledgment) one IFS period before the end of the CAP/GTS). IEEE 802.15.4 OPNET Simulation Model version 2.0 added GTS mechanism GTS allocation, deallocation and reallocation functions in wpan_mac module GTS Traffic Source at the Application Layer generates unackowledged or acknowledged data frames transmitted during the CFP fixed a bug in wpan_backoff_delay_set() function backoff countdown was not paused at the end of the CAP fixed a predefined values of the Initial Energy attribute in Battery Module add TelosB (TmoteSky) current draw characteristics in Battery Module updated user-defined attributes updated a structure of the simulation model updated packet formats (beacon, command, ack, MAC_packet) update directories structure updated Traffic Source generator at the Application Layer independent parameters setting for generating acknowledged and unacknowledged data frames previous Sink module was improved and separeted into Traffic Sink and Synchro modules IEEE 802.15.4 OPNET Simulation Model version 1.0 beacon-enable mode beacon frame generation slotted CSMA/CA MAC protocol packet formats (beacon, command, data, ack, MAC_packet) computation of the power consumption (MICAz model supported) Downloads Package Version Date OPNET version Downloads OPNET Simulation Model 3.0 beta 20/11/2009 15.0 ZIP Video Guide * 2.1 31/03/2009 - AVI MPEG OPNET Simulation Model 2.1 31/03/2009 14.5 ZIP OPNET Simulation Model 2.0 22/05/2007 11.5 ZIP Reference Guide 2.0 22/05/2007 - PDF OPNET Simulation Model 1.0 06/04/2006 10.5 ZIP * MPEG mpeg2 codec, 720x576, size 44 MB AVI XviD codec, 720x576, size 14 MB Related References P. Jurcik, A. Koubâa, M. Alves, E. Tovar, Z. Hanzalek; A Simulation Model for the IEEE 802.15.4 Protocol: Delay/Throughput Evaluation of the GTS Mechanism; In Proc. of 15th IEEE International Symposium on Modeling, Analysis, and Simulation of Computer and Telecommunication Systems (MASCOTS07), Istanbul (Turkey), October 2007. A. Koubâa, M. Alves, B. Nefzi, Y. Q. Song; Improving the IEEE 802.15.4 Slotted CSMA/CA MAC for Time-Critical Events in Wireless Sensor Networks; In Proc. of the Workshop of Real-Time Networks (RTN 2006), Satellite Workshop to (ECRTS 2006), July 2006. A. Koubâa, M. Alves, E. Tovar; A Comprehensive Simulation Study of Slotted CSMA/CA for IEEE 802.15.4 Wireless Sensor Networks; In IEEE WFCS 2006, Torino (Italy), June 2006. A. Koubâa , M. Alves, E. Tovar; On the Performance Limits of Slotted CSMA/CA in IEEE 802.15.4 for Broadcast Transmissions in Wireless Sensor Networks; IPP-HURRAY Technical Report, HURRAY-TR-060401, Feb 2006.

Opnet INSTALLATION, OPNET 14.5 Configuration

Hello,
This is my first blog post. Hope it will be interesting to you. I am going to start with network simulator tool OPNET14.5.
So, What is OPNET14.5 ????
OPNET is a network modeler through which one can design any kind of network model and then can simulate it. 14.5 is the version of OPNET and it is freeware.
Here simulation means OPNET will generate the traffic as defined in attributes set by user and will generate results like utilization, collision, load, etc (these analysis parameters are again set defined by user. We will discuss later on how to define each attribute).

Now, first we will discuss about how to install and major part is how to configure the OPNET on MS VS2008.

INSTALLATION
OPNET 14.5 modeler have three packages. So install them in sequence as:
1. First install OPNET Modeler.
2. Second Install OPNET documentation.
3. Then last install OPNET library.
Also,  note that every package is installed in same directory.

CONFIGURATION

Now, after installing one have to set environment variables. So, I think first question will be why we need to set environment variables?? If we don't do what will happen???

Well, I will answer you at the end of this discussion. :) :)

I am considering that MS VS2008 is installed in default directory i.e.( C:\Program Files\Microsoft Visual Studio 9.0\ ). First right click on 'My Computer' choose 'Advanced" tab and the click on 'Environment Variables'. Then in system variables add following variables:

a) PATH

     C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE;

     C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN;

     C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools;

     C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\bin;

     C:\WINDOWS\Microsoft.NET\Framework\v3.5;

     C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;

     C:\Program Files\Microsoft Visual Studio 9.0\VC\VCPackages;

     C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin;

b) LIB

    C:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;

    C:\Program Files\Microsoft Visual Studio 9.0\VC\LIB;

    C:\Program Files\Microsoft SDKs\Windows\v6.0A\lib;

c) LIBPATH

    C:\WINDOWS\Microsoft.NET\Framework\v3.5;

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;

    C:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;

    C:\Program Files\Microsoft Visual Studio 9.0\VC\LIB;

d) INCLUDE

    C:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\INCLUDE;

    C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE;

    C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5\include; 

e) NetSamplePath

    C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5;

f) DevEnvDir

    C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE;

g) FrameworkDir

    C:\Windows\Microsoft.NET\Framework;

h) FrameworkSDKDir

    C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5;

i) FrameworkVersion

    v2.0.500727;

j) VCBUILD_DEFAULT_CFG

    Debug^|Win32;

k) VCBUILD_DEFAULT_OPTIONS

    /useenv;

l) VCINSTALLDIR

    C:\Program Files\Microsoft Visual Studio 9.0\VC;

m) VSINSTALLDIR

    C:\Program Files\Microsoft Visual Studio 9.0;

Oops!!!!! lot of variables...:) :)

Now I will answer the question raised at the starting of discussion Why it is required??

So we can design a network in two ways a) Using the Object Pallete and  b) Through coding... Obviously no one wants to do it though coding when everything is graphically done by just setting attributes and code will be generated for same. So whatever you are designing graphically , for same a code  will be generated in C that needed to be compiled before we do simulation so all these variable we defined above will set the path for all header files required for compilation and execution of the network. That's why OPNET requires VS2008 because it uses VS2008 for code compilation and execution. That's why we need to set these environment variables. I think now you got answer of first question that why we did that. Now if we don't do it then we can design the network but cant simulate it.

I think if you go to manual of OPNET you will find the same variable but if it is for VS2005 the directory names will be different for example .Net framework used in VS2005 is v2.0 while in VS2008 it is v3.5 so you need to make changes at all respective places.

Also if you get error during compilation that

gna_email_mgr.pr.tmp.c

c:\opnet\14.5.a\sys\include\vos.h(105) : fatal error C1083: Cannot open include file: 'WinDef.h': No such file or directory.

Then search the Windef.h in my computer. You will get lot of results but you have to select the path as:

C:\Program Files\Microsoft SDKs\Windows\v6.0A\Include;

Copy the address and append it to 'INCLUDE' environment variable value.

I think now we are done with configuration.

uuuhhhhh!!!!!! It seems that we have done a kind of project :) :) but exactly speaking we have just set the environment for our projects :) :).

Hope it gives you enough information to set OPNET 14.5 network modeler. 

Follow this steps instead to configuration files

OPNET 14 installation guide.doc

Configuring OPNET 12.0 with .NET 2005 on Windows 64 XP Professional.doc


see and do

Opnet does not have a compiler. You have to install compilers like VC++ or visual studio 2005 or anyother version. Then you have to change the environment variable of your computer. It will be in properties of your MyComputer

On Windows NT:
Start -> Settings -> Control Panel -> System -> Environment
On Windows 2000 and Win XP:
Start -> Settings -> Control Panel -> System -> Advanced -> Environment Variables

Each time a variable is updated, you need to click the Set button for the changes to take effect. Once all of the changes have been made, click OK to close the dialog box.

Note that for some systems, the 8.3 format must be used in order to see proper behavior (e.g. "C:\PROGRA~1\MICROS~1\Common\Tools"). Note also that spaces should not be used immediately after the semicolon (";") character in the environment settings. for further help in setting system environment variables, contact your system administrator.

----------------------------------------------
THE FOLLOWING INSTRUCTIONS ARE FOR Windows NT, Windows 2000 and Win XP:

************* IMPORTANT NOTE *****************
For all of the environment variables below, do not put spaces between the directories.
There should be NO SPACE between the semicolon ";" and the drive letter of the next directory!

For example, the following is CORRECT:
C:\Program Files\Microsoft Visual Studio\Common\msdev98\BIN;C:\Program Files\Microsoft Visual Studio\VC98\BIN;

However, the following is INCORRECT:
C:\Program Files\Microsoft Visual Studio\Common\msdev98\BIN; C:\Program Files\Microsoft Visual Studio\VC98\BIN;
******************************

Add the following items to the PATH environment variable.
C:\Program Files\Microsoft Visual Studio\Common\msdev98\BIN;
C:\Program Files\Microsoft Visual Studio\VC98\BIN;
C:\Program Files\Microsoft Visual Studio\Common\TOOLS\WINNT;
C:\Program Files\Microsoft Visual Studio\Common\TOOLS;

Add the following items to the INCLUDE environment variable.
C:\Program Files\Microsoft Visual Studio\VC98\ATL\INCLUDE;
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE;
C:\Program Files\Microsoft Visual Studio\VC98\MFC\INCLUDE;

Add the following items to the LIB environment variable.
C:\Program Files\Microsoft Visual Studio\VC98\LIB;
C:\Program Files\Microsoft Visual Studio\VC98\MFC\LIB;

Add the following item to the MSDevDir environment variable.
C:\Program Files\Microsoft Visual Studio\Common\MSDev98

Note: These instructions assume MSVC was installed in the default location.
If MSVC was installed in a different location on your system you may need to
modify the paths specified above to match your installation.

TO VERIFY THAT THESE SETTINGS ARE CORRECT:

One quick way is to open a new OPNET Console (from the "Start" button, select "Program Files"->"OPNET Modeler" -> "OPNET Console") then type the following and examine the output of "path", "lib" and "include" environment variables.

prompt> set

Another way to check, is to type the following command:

prompt> cl

If it returns the following output:

Microsoft (R) 32-bit C/C++ Standard Compiler Version 12.00.8168 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

Then it means that MSVC++ is in your path.

Note: If the instructions in this FAQ do not appear to succeed, in certain very rare cases, it has been reported that the issues may be fixed by using tildes ('~') in the above paths to achieve 8.3 format such as:
C:\PROGRA~1\MICROS~1\Common\MSDev98

If you continue to experience issues, you may also wish to see the paths used by MS Visual C++ by examining the file:
C:\Program Files\Microsoft Visual Studio\VC98\BIN\VCVARS32.bat

Have a nice day

Network Designing and simulation using OPNET 14.5.

Hello,

So we are back on our discussion on OPNET 14.5 , how to design network and then simulate it...:)
I already  talked about how to set the environment of OPNET to work on it in last post.
So, today we will be designing a small network and then we will move on to complex networks in later discussions.
Lets consider a simple office network of 10 workstations (clients) and 1 server connected through a hub.

First we have to design this network. Don't worry...... designing means we have to select respective objects and connect then...That's it and our network will be ready to work ... haha... :) Okay back to point and lets see how easy it is... :):)

Designing Network

Select  'New Project' and create a new project. In this project it will ask for a scenario create scenario_1 as example. So what is scenario???
Scenario is part of our complete network we want to simulate. Because we cant build and simulate whole network in one go, we divide network in areas, parts, domains, sub-nets, etc. called as scenarios.
So in scenario_1we will be designing the simple network.
1. Click on 'Open Object Palette'. We are creating a office network which is Ethernet based network so select 'ethernet'  in 'Shared Object Palettes'.
2. We need 10 workstations . So select 'ethernet_wkstn' from 'Node Models', drag it in scenario workspace. Left click ten times (replicate the same object) and then do right click to stop duplicating objects. So we added 10 workstations to network.
3. Select 'ethernet_server' from same 'Object palette', drag it to workspace and right click as we don't need more than 1 server. Similarly drag 'ethernet16_hub' to workspace.
4. Now we need to connect all nodes. So, select '10baseT' links from 'Object Palette'. First click on hub and then click on node. Do same for all nodes to connect every node with hub and then right click to stop connecting.
5. To set configuration of network traffic we need two more objects 'Profile Config' and 'Application Config' so drag them in workspace.
So I think the network you designed may look like this:

6. Now we need to set network traffic. So right click on Profile Config object and select 'Edit attributes'  and then

 

 a) Select Number of Rows as 2.
 b) Set the attributes as shown in pic (node_8 attributes).
7. Click 'OK'.
8. Select 'Application Config' Object and right click on it. Set Application Attributes to Default.

Till this point from configuration point of view we have set the network traffic but didn't set which node will generate what traffic.
9. So, Select all workstations, right click and select 'Edit Attributes'. 
 a) Select Application Supported Profiles.
 b) Select 'Number of rows' as 2.
 c) Set the parameters as shown in below:

d) After doing all this Check on 'Apply To Selected Objects'.  Here I have set all clients as same traffic generator you can experiment with different traffic also.

10. Now you have to configure server so select server, right click, select 'Application Supported Services'  and set it to 'ALL'.


11. Now everything is ready i.e. we have designed the network, defined all attributes of all objects.

Happy and ready to simulate it. Okay lets do simulation..

Ohhoohhooo!!!!....we have defined everything but we din't set, after simulation what we want to analyse...???? :) :)
Okay, lets quickly set the parameters we want to analyse and then ready set and go..............

Setting Analysis Parameters

1. Right click on workspace and select 'Choose Individual DES Statistics'.
2. In 'Global Statistics'  select 'Ethernet->Delay(sec)'.
3. Similarly in Node Statistics Ethernet select parameters like Load, Utilization, Collision Count, etc whatever you want to analyse.

Okay so all set ....

Save the Project and then  click on 'Configure/Run Discrete Event Simulation (DES)'. Set Simulation time to 20 minutes and click Run.
After simulation is over you can view results of all statistics you set. Statistics in form of graph I got look like this:

Hmmm......so finally designed and simulated a small office network using OPNET 14.5.
So for today, I think it is enough.
This was just an introduction of how to work on OPNET. In later discussions we will work on some big and complex networks and will try to figure out how different network fails, which equipment of which vendor are best for which network??? So lot of questions yet to answer....
Okay .Hope you enjoyed it..
Bbyyee..

how to Install Opnet version 14.0

Introduction

Source

• Files are in: \\storage1\cecn_admin\src\opnet\v14\wireless

Installation

• Run Visual Studio 2005 first before installing.

• Install Order

Install OPNET 14 (ignore the warning about the environment not being setup properly)

1. modeler_140A_PL3_6313_win.exe -f license_server.properties
2. models_140A_PL3_17Oct07_win.exe -i silent
3. modeler_docs_140A_PL2_24-Sep-2007_win.exe -i silent

License

olio.coe.ad.mtu.edu port_a

Configuration

• run opnetvariables.vbs ONCE to set all the opnet system environment variables needed to work with VS 2005
  • it must be run from cscrīpt
  • Cscrīpt //h:cscrīpt //nologo //s
• copy files:
  • copy c:\program files\opnet\14.0.A\sys\pc_intel_win32\bin\manifest\* c:\program files\opnet\14.0.A\sys\pc_intel_win32\bin

OPNET FAQ

• Question: What are the proper system environment settings for Microsoft's Visual Studio .NET 2005 compiler to work the 12.0 release of OPNET?
• Answer: As of 12.0 PL0,OPNET supports Microsoft Visual Studio .NET (2005 version).

• Note:Please refer to FAQ 1219 for .NET 2003 and FAQ 783 for .NET 2002 settings.

• Note that you must ensure your system environment is set up correctly. Here is the list of environment settings that should be added or set in the System Variables on your computer.
• (Note: If the variable name already exists, make sure that the value associated for that variable exists. If not, you must add the below value to the variable. Consult your System Administrator or Microsoft technical support for assistance. This FAQ is provided as a courtesy only.)

• NOTE: The following settings assume that Visual Studio .NET (2005 version) has been installed using the default installation directory settings and that your SystemRoot variable is set to C:\WINNT. If these are not the settings you have, then you must adjust the following settings accordingly.

My Computer-> advanced-> environment variable-> system environment variables

Variable 1: Path

Value:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;

C:\Program Files\Microsoft Visual Studio 8\VC\BIN;

C:\Program Files\Microsoft Visual Studio 8\Common7\Tools;

C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\bin;

C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\bin;

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;

C:\WINNT\Microsoft.NET\Framework\v2.0.50727;

C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin;

C:\WINNT\Microsoft.NET\Framework\v2.0.50727;

C:\Program Files\Microsoft Visual Studio 8\VC\bin;

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;

C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages;

Variable 2 : INCLUDE

Value:

C:\Program Files\Microsoft Visual Studio 8\VC\ATLMFC\INCLUDE;

C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE;

C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include;

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\include;

Variable 3: LIB

Value:

C:\Program Files\Microsoft Visual Studio 8\VC\ATLMFC\LIB;

C:\Program Files\Microsoft Visual Studio 8\VC\LIB;

C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\lib;

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\lib;

Variable 4: LIBPATH

Value:

C:\WINNT\Microsoft.NET\Framework\v2.0.50727;

C:\Program Files\Microsoft Visual Studio 8\VC\ATLMFC\LIB;

Variable 5: NetSamplePath

Value:  C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0;

Variable 6: DevEnvDir

Value:  C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;

Variable 7: FrameworkDir

Value:  C:\WINNT\Microsoft.NET\Framework;

Variable 8: FrameworkSDKDir

Value:  C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0;

Variable 9: FrameworkVersion

Value:  v2.0.50727;

variable 10: VCBUILD_DEFAULT_CFG

value:  Debug^|Win32;

Variable 11: VCBUILD_DEFAULT_OPTIONS

Value:  /useenv;

Variable 12: VCINSTALLDIR

Value:  C:\Program Files\Microsoft Visual Studio 8\VC;

Variable 13: VSINSTALLDIR

Value:  C:\Program Files\Microsoft Visual Studio 8;

• To ensure that the .NET product is installed correctly, open a Command Prompt and type "cl" to invoke the compiler. Then type "link" to invoke the linker/binder. Confirm that each of these commands returns the correct information for the .NET installation.

opening

    'cmd' at Run, and trying the command-line compiler and linker with the commands 'cl' and 'link' respectively.  If the environment is configured correctly, you should NOT get a "Bad command or filename" and the commands should execute.

• =============
• If you are using .NET 2005 on WinXP, then you will need to follow this additional step:
• =============
• After you have configrued your environment as listed above, open Windows Explorer and copy files from your \sys\pc_intel_win32\bin\manifest to \sys\pc_intel_win32\bin.

• If you are using .NET 2005 on a 64-bit machine, you will need to copy the corresponding manifest files from \sys\pc_amd_win64\bin\manifest to \sys\pc_amd_win64\bin.

• After this, you can start modeler and run simulations as usual.

• Note: There is a contributed paper with detailed steps and screenhots to help you set up this environment easily.
• https://enterprise16.opnet.com/4dcgi/Biblio_FullAbstract?BiblioID=1097
• Title: Configuring OPNET 12.0 with .NET 2005 on Windows 64 XP Professional

Retrieved from "https://secure.cecn.mtu.edu/cecndocs/index.php/InstallingOpnetv14"