Version 0.8 Beta - CLIENT

Executable Alone - DOWNLOAD

Client Install - DOWNLOAD





Version 0.8 Beta - SERVER

OPNET 10.0 - DOWNLOAD

OPNET 10.5 - DOWNLOAD

OPNET 11.0 - DOWNLOAD





STK USERS CONFERENCE

2004 Presentation - DOWNLOAD

1. Download the client tool. The "Executable Alone" can be downloaded if you have Microsoft Word and the dll's that come with Microsoft Word. Otherwise you can download the install package.
   
   
2. Download the server for the version of OPNET you have.
   
   
3. Install the client or copy of the "Executable Alone" to anywhere on your machine. NOTE: The client does not need to be on the same machine as STK or OPNET.
   
   
4. Unzip the server to a directory located on the same machine as OPNET.
   
   
5. Open OPNET and go to Edit->Preferences and find the "mod_dirs" field. Add the server directory to the first item on the list of "mod_dirs".
   
   
6. Using either New... or Open... in OPNET, open a scenario. In the menu bar, there should be an option "STK"->"Listen For NetSimTool". When you select this, you will not be able to interact with OPNET until you press the cancel button.
   
   
7. Now that the server is listening, you can start up NetSimTool.exe and STK. NOTE: The NetSimTool can handle STK whether there is a scenario open or not. However, OPNET must have a scenario open to facilitate the transfer of data.
   
   
8. In the client tool (NetSimTool.exe), click Settings->Connections. The standard settings are "localhost" for the IPs, 5001 for STK, and 6001 for OPNET.
9. Then connect to both tools.

• Ability to set default node type in OPNET.
• Ability to change node type in OPNET.
• Mobile subnets pass their position information on to children nodes.
• If report cannot be connected to an object, it is connected to the GLOBAL object.
• Fix name translation to handle both OPNET's and STK's acceptable naming convention.
• Ability to import subnet along with nodes.
• Added cancel button for long wait times.
• Lookup by object name and path, not just object name.

• Moving objects from STK to OPNET.
• Moving objects from OPNET to STK.
• Use of physical layer in STK to do OPNET calculations.
• Import OPNET reports to STK.
• Import throughput for VO visualization.

1. What do I do if I want to set different OPNET node types?
Under the settings tab in NetSimTool, you have the ability to set the default node type. This will be applied only to objects brought over from STK. It will not change the current model type of any objects in OPNET.

2. Why are there so many objects populated in STK when I import objects?
OPNET has nodes, and usually any where from one to several hundred nodes make up a subnet. Subnets are conceptually closer to STK's objects, but in order to do the physical layer calculation, nodes must be brought into STK. You can hide these objects in the STK/VO window by turning off its track and 3D image.

3. How does the system decide what type of vehicles the nodes in OPNET are? Why is my satellite an aircraft? Why is my aircraft a ground vehicle?
The NetSimTool attempts to think for you and decide the vehicle of a node in OPNET. If the object does not move, it is assumed to be a facility. If the object moves, but the origin altitude is 0, it assumes a ground vehicle. If the object's origin altitude is above 0 and below 250,000 feet, it is assumed to be an aircraft. All others are assumed to be satellites. If you have an aircraft in OPNET that starts off on the ground, then it will be brought over as a ground vehicle. It give the ground vehicle all appropriate altitudes, so it does alter any calculations.

4. Why can't I connect to STK?
Check Settings->Connections. The standard setup is localhost (or 127.0.0.1) and 5001 for STK. If you still cannot connect, there is a connection in the way. Discontinue any other STK/Connect operations, or just restart STK.

5. Why can't I connect to OPNET?
Check Settings->Connections. The standard setup is localhost (or 127.0.0.1) and 6001 for OPNET. If you still cannot connect, make sure you selected "STK"->"Listen For NetSimTool" in OPNET.

6. How can I view my report data?
To view report data, select an object in STK and select Reports. Create a new style and edit that style. When you edit that style, you will see a data type called "User Defined Data". All reports are put in this area for a particular object. Most reports in OPNET are connected to a node, so the NetSimTool brings over the report connected to the tool. Any reports not connected to the tool will be connected to the GLOBAL facility.

7. I brought over a report that is not associated with an object in STK. How can I view my report data?
All reports not connected to an object will be connected to the GLOBAL facility.

8. Do I have to open the tools in a certain order?
No. STK, OPNET, and the NetSimTool can be started in any order. In order to use the NetSimTool, STK just has to be open, while OPNET needs to be open, have a scenario loaded, and listening for the NetSimTool.

9. What part of the OPNET pipeline is overwritten? What pieces of STK's physical layer is used in OPNET calculations?
There are three parts overwritten by the NetSimTool. They are the "link closure" or line of site, "received power", and the "bit error rate".

10. Why is there no transmitter/receiver connected to my STK object, but when I bring it over to OPNET it has both?
Because OPNET does not connect transmitters/receivers to nodes, but allows you to create a model and connect them to actual data processing. The NetSimTool, therefore does not try to edit the model but allows the user to select the OPNET model appropriate for that node. If you are not familiar with OPNET, you can stay with wlan_wkstn_adv.

11. What do I need to run this tool?

• STK
• STK/VO (optional)
• STK/Comm
• OPNET modeler or ODK
• OPNET wireless