You are on page 1of 21

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !

PI

Co-Simulation Demo
Overview
Collectively, we will simulate a project containing several scenarios. Each computer station will run a different scenario in that project. The scenarios represent different sections of a large, international network. Using co-simulation, nodes in a particular scenario may communicate with nodes in other scenarios. The key to this is that the simulations communicate with a central software component running on the instructor’s machine. Using the co-simulation package and native sockets, each simulation sends packets to the central command. The central command then routes these packets to the appropriate destination simulator. ll of this is done in a synchroni!ed manner.

Objective
"ntroduce the co-simulation capa#ilities of $%&ET

CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. © Copyrigh !""# OPNET T$%h&o'ogi$(, I&%.

P)g$ * o+ !*

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

Instructions
Gather information '. Each computer will have #een given a num#er. %lease write that num#er here( )))))* +. The instructor will announce the name of the server. %lease write that name here( )))))))))))))))))))))**

Run the co-simulation '. $pen an $%&ET console a. ,indows -tart menu . %rograms . $%&ET /odeler ''.0 . $%&ET Console ''.0 +. Change to the c:\op_models directory.  cd op_models 1. 2un the following at the prompt(  1532-[*enter your number here].dev32.i0.sim –server [**server machine] –ef 1532-[*enter your number here] 3. $nce everyone has joined the co-simulation, the co-simulation will #egin. %lease #e patient as we wait for others to join. 4. a. a.

CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. © Copyrigh !""# OPNET T$%h&o'ogi$(, I&%.

P)g$ ! o+ !*

Note 6or the ne7t two la#s. P)g$ . you will write the running total of packets scheduled to #e sent.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Lab 1: Introduction to Co-Simulation Elements Overview 5ou are going to adapt the co-simulation model that was presented in a demo earlier. rather than sending the packets out. Preferences. o+ !* . change the primary model directory to c:/op_models/1532_ref. SHARE. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. you may use the reference models as an alternative to running the la#s. Objective -ynthesi!e the various elements of the co-simulation package. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. to which you may navigate in /odeler after choosing Edit . To do so. The primary model directory is the topmost directory in your mod_dirs environment preference. "n addition. "nstead of having the simulation communicate with other simulations. FORWARD. I&%. you will have it communicate with you. DISTRIBUTE. use instead c:\op_models\1532_ref. and also dynamically o#tain from it the num#er of packets sent out onto the esys interface. where the la#s mention the c:\op_models directory. © Copyrigh !""# OPNET T$%h&o'ogi$(. 5ou will control the rate at which the simulation advances. the user. 6or this first la#.

/odify the file so that we link in the e7ternal o#ject lab1_1532. I&%. File .sd) file '. -tart /odeler. Using . FORWARD.obj instead of the sim)manager and comm)support o#jects. 1. File . +.indows e7plorer 8right-click on -tart menu and choose E7plore9. c. This is the simulator descriptor used in the earlier demo. :ou#le-click on 1532_simdesc.sd. efres! Model "irectories +. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. . File . choose to open this file in &otepad. "n their place. -ave the file as lab1_1532. Save As #. Model Files .obj 3. c. a. navigate to c:\op_models.sd and click Save. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.sd. '. Click &'. P)g$ # o+ !* . $pen the simulator descriptor file 1532_simdesc. Create the ESD model The E-: model will define the esys interface you’ll use in the modified network. #. delete the two lines that follow use_esa_main: no #.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Instructions Create the simulator description (. E%ternal System "efinition #.hen prompted. #e$ . add the line( bind_obj: lab1_1532. or if already started. 2ecall that what we want to write on this interface is the num#er of packets sent out. a. d. Create a new E7ternal -ystem :efinition model. a. SHARE. Type lab1_1532. Change Save as type to All Files. refresh the model directories. a. DISTRIBUTE. © Copyrigh !""# OPNET T$%h&o'ogi$(.

. "n pull-down menu. I&%.o+ !* . 1. DISTRIBUTE. Change the name to o(t. of type integer. <erify that "irection is set to &P#E* to +osim 4.ave this E-: model use the simulator description file you just created. #. Click the first row in )nterfaces ta#le #. Create a single interface named o(t from $%&ET to the e7ternal code. a. =.1532.1532 and Click Save. Type lab1. Click 2eturn to make sure this change registers. a. 3. c. This integer represents the num#er of packets sent out. d. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. File .1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI 1. Click on #&#E ne7t to Sim(lator "escription. choose lab1_1532. © Copyrigh !""# OPNET T$%h&o'ogi$(. <erify that *ype is set to integer e. Completed E-: model should look like this( CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. Save #. a. FORWARD. SHARE. -ave the E-: model as lab1. P)g$ .

Close the editor. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. P)g$ . I&%.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI >. FORWARD. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. DISTRIBUTE. © Copyrigh !""# OPNET T$%h&o'ogi$(. o+ !* . SHARE.

Save As #. &ote that it is currently set to esd_1532. select lab1. :ou#le-click on the esys module. a. DISTRIBUTE. FORWARD.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Set up the project to use the ESD model '. This #rings up the router’s node model. initiali!ed to 0. #y clicking on the /0 #utton. dou#le-click on 1532. #. $pen the /eader 0loc. d._co(nt. :uplicate the scenario that the project opens to. a.1532 . © Copyrigh !""# OPNET T$%h&o'ogi$(. and name it lab1. a. Enter 1532_ro(ter_lab1 and press Enter. >. -et Files of *ype to Project. SHARE. 4. $pen project 1532. Scenarios . a. a. and in the pull-down menu. Click &' to close the Edit Attrib(tes dialog #o7. Save As #. Enter esys_1532_lab1 and press Enter. P)g$ / o+ !* . e. &pen #. "(plicate Scenario #. Click the Edit ES" Model #utton in the lower-left of the dialog #o7. =. :ou#le-click on the router node. Click on esd_1532. <erify that the E-: model you created earlier appears. 1. This #rings up the process model associated with the esys. Change the esd model attri#ute of the esys module to lab1. File . ?. Enter lab1 and press Enter. -ave the node model as 1532_ro(ter_lab1. a. -ave the model as esys_1532_lab1. Create a new glo#al varia#le p. type( int p _count ! 0" CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. Close the E-: model. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. 3. t the end of the file. c.1532. +. c. File . 2ight-click on the esys module 8named esys9 and select Edit Attrib(tes. f. I&%. File . "n the op_models directory. #. -_ro(ter. 6ind the attri#ute esd model.

:elete lines '0-'1. DISTRIBUTE. -et the process model associated with the esys module to esys_1532_ lab1. -ave the F(nction 0loc. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART._vvec to 55p. and thus no call#ack is issued. $pen the F(nction 0loc. Change the third argument from p. is the packet count 8rather than the packet9. P)g$ 0 o+ !* . '0. Compile the process model and close it. +lose '+. FORWARD. a. #. c. +ompile . a. Change the second argument from op_sim_time12 to &P+_ES3S_#&*)F3_#E4E .or File . ''. The final result should look like this( e. +ompile +ode. #. Save. a. © Copyrigh !""# OPNET T$%h&o'ogi$(. or click the Compile Code action #utton. I&%. -ave the /eader 0loc. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. the manager side is not notified that the value has changed. "f not already up. #ring up the node model 1532_ro(ter_lab1. i. SHARE. %ress Ctrl-. This means that. #. ii. File . /odify the function process_strm12 so that what’s written to the esys interface. d. 2ight-click on the esys module and select Edit Attrib(tes.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI @. although the value is updated immediately. a. c. #y clicking on the F0 #utton. Click the +lose #utton. "n the call to op_esys_interface_val(e_set12._co(nt. The manager will read the updated value when it is told to.

File . Click on esys_1532 and in the pull-down menu. 2ight-click on the router node 8-_ro(ter9 and select Edit Attrib(tes. "n the new pull-down menu.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI c. DISTRIBUTE. "t is now time to create the e7ternal code elements. "n the pull-down menu. Click &'. click Edit6 e. &ote that the process model attri#ute is set to esys_1532. File . d. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. a. +lose 5ou have completed all the elements on the $%&ET side. FORWARD. -ave and close the node model. f. File . P)g$ 1 o+ !* . File . © Copyrigh !""# OPNET T$%h&o'ogi$(. Click &'. '4. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. d. +lose '3. Save #. c. e. I&%. -ave and close the project. Click on 1532_ro(ter. &ote that the model attri#ute is set to 1532_ro(ter. select esys_1532_lab1. a. SHARE. a. -et the node model associated with the router to 1532_ro(ter_lab1. #. select 1532_ro(ter_lab1. Aring up the 1532 project. <erify that you are in the lab1 scenario. '1. Save #.

dou#le-click on lab1_1532. /(%sa_1nterface_8roup_8et #esa_6andle0 5interfaces0 5num_interfaces$"(/ 3. you may wish to e7amine the call to %sa_%&ecute_'ntil#$. &ote that there are two functions. main#$ and user_prompt#$.c. $pen and e7amine the file lab1_1532. DISTRIBUTE.ation code (/. This line of code will o#tain all esys interfaces across all esys modules in the simulator..1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Examine and modify external code that implements the user interface '. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. This should open up the file in /icrosoft <isual CBB.%). • Using . © Copyrigh !""# OPNET T$%h&o'ogi$(. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.read pac et count (/. 2emove the comments around the ne7t line.obtain interface (/. user_prompt#$ o#tains the instructions from the user and main#$ uses this information to advance the simulation. SHARE. • • Cook for the comment /( ')*+.. Uncomment code that will read the packet count off the interface. Uncomment E. +.ain #ar/c0 ar/v0 0$" %sa_1nit #ar/c0 ar/v0 %23*_+4-2_)+)%0 5esa_6andle$" %sa_7oad #esa_6andle0 %23*_+4-2_)+)%$"(/ 1..c. in c:\op_models. These lines of code perform the initiali!ation of the simulator.%). 2emove the comments around the ne7t lines.initiali. FORWARD.%).indows E7plorer. "n particular. Uncomment code that will o#tain a handle to the esys interface you defined earlier. I&%. P)g$ *" o+ !* . • Cook for the comment /( ')*+.initiali!ation code • • Cook for the comment /( ')*+. /(%sa_.

55pac. DISTRIBUTE. I&%.et_co(nt9 that was earlier written to the esys interfaces . P)g$ ** o+ !* . SHARE..e. /(%sa_1nterface_9alue_8et #esa_6andle0 5status0 iface0 5num_p s$"(/ CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. This line of code will o#tain the packet count 8i.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI • 2emove the comments around the ne7t line. © Copyrigh !""# OPNET T$%h&o'ogi$(. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. FORWARD.

9 4. 1.  op_m sim –net_name 1532-lab1 -c 4. Lab Questions '. -ave the file. SHARE.11133?G9. 4.  *7 /c lab1_1532.c /1*:\pro/ra:1\opnet\11. t the command prompt.hy do you think that many are sent out #y that timeD 8&ote( this will reEuire study of the network model. . Save Compile the simulation and run it '.owever. Change directory to c:\op_models. Compile the e7ternal code.i0. 95ou may have noticed that after the initial spike.0.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI 4..3\s. +. or as an e7ternal li#rary linked into an $%&ET simulationD +.dev32.2>: 4ac et sent to @. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. . FORWARD. "s the co-simulation structured as an $%&ET simulation in a larger program. F1. I&%.1 A 10@.'D 3. .indows -tart /enu. the packet count increments #y ' each time a message appears 8e. $pen up an $%&ET Console from the .  1532-lab1.s\include /<_=>?_ 3.ow many packets are sent out on the interface #y time 0. • File . DISTRIBUTE. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE.hat is the final packet countD 1. 2un the simulation. . type 6elp to see the list of commands availa#le. © Copyrigh !""# OPNET T$%h&o'ogi$(.sim =.g. P)g$ *! o+ !* . 6orce compile the static simulation.

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI #etween time '00 and +00. you will have to use the function %sa_1nterface_9alue_2et#$ with immediate notification.hy might this #e soD Extra Credit 5ou may have noticed that there is a feature in the help menu for resetting the packet count to !ero. I&%. there are two such messages #ut the packet count is only incremented once. © Copyrigh !""# OPNET T$%h&o'ogi$(. o+ !* .s#$ function to support this feature. SHARE. DISTRIBUTE. FORWARD. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. "mplement this option. . P)g$ *.ints( 5ou will have to alter the esys interface and modify the process_es. "n the e7ternal code. .

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Inter ace Callbac!s and "ac!et Conversion Overview 5ou are going to adapt the co-simulation model so that it sends out a reEuest packet on the esys interface and receives a FresponseG #ack. To the simulation. P)g$ *# o+ !* . The e7ternal code will read this packet 8in vvec form9 off the interface. FORWARD. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. DISTRIBUTE. SHARE. These are the types of operations upon which interfacing multiple simulators relies. The reEuest is intended for a node outside the network. I&%. swap the -rc and :est fields. convert it to native values. then send it #ack to the simulation. © Copyrigh !""# OPNET T$%h&o'ogi$(. Objective Hain familiarity with advanced co-simulation data e7change mechanics. even though this is not the case. it will appear that a response packet has arrived.

%acket 6ormat model. &ame the first field Src. Change name to Src. a. %lace three fields in the workspace. SHARE. d. © Copyrigh !""# OPNET T$%h&o'ogi$(. c. a. Change conversion met!od attri#ute to defa(lt_convert. File . OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. a. -et Files of *ype to Pac. #. open the lab2_1532_p. Click &'. "n /odeler.et Format. 4..1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Instructions   Create the packet format. 2ight click on the first field and select Edit Attrib(tes. a 1+-#it integer with conversion method defa(lt_convert. 1. P)g$ *. I&%. #. Change name to "est. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. f. 3. FORWARD. c. +. g. dou#le-click on lab2_1532_p. a. &pen #. Change conversion met!od attri#ute to defa(lt_convert. a. Click three times in the workspace to generate three packet fields. &ame the second field "est. DISTRIBUTE.o+ !* . Click on the +reate #e$ Field #utton 8top left9. a 1+-#it integer with conversion method defa(lt_convert. '. #. "n the op_models directory. h. 2ight-click on the second field and select Edit Attrib(tes. e.

Change name to +reation. a =3-#it floating point with conversion method defa(lt_convert. 2ight click on the third field and select Edit Attrib(tes. e. File . Change conversion met!od attri#ute to defa(lt_convert. I&%. Click &'. &ote that +onversion met!od is set to defa(lt_convert. g. +lose CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. ?. Save #. a. Change type to floatin7 point. >. FORWARD. =. Change si!e to 89. a. DISTRIBUTE. SHARE. c. #.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI c. d. g&ame the third field +reation. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. File . © Copyrigh !""# OPNET T$%h&o'ogi$(. c. 0inary +onversion #. Click &'. )nterfaces . P)g$ *. a. f. o+ !* . Click &' . <erify the packet’s #inary conversion method is defa(lt_convert. -ave and close the model.

converts it #ack to an $%&ET packet. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.ave this process model support the packet format you just modified. "eclare Pac. E7amine lines '+-'3. Compile then close the process model. S$itc! *o Scenario . &pen #. a. which convert the packet to a vvec packet. a. which o#tains a vvec from the esys interface 8placed there #y manager code9. a. >. File .1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI odify the esys process model '. dou#le-click on 1532. -et Files of *ype to Project. I&%. for use #y the manager code. c. Cocate and click lab2_1532_p. c. $pen the 6unction Alock #y hitting the F0 #utton. 2emove the comments that #racket these lines.S or File : Save. SHARE. lab2. E7amine the E-: model on which the esys interfaces are defined. +. "n the op_models directory. FORWARD. :ou#le-click on the -_ro(ter node to enter the &ode Editor. Click the +lose #utton. -ave the 6unction Alock. E7amine lines +@-1=. :ou#le-click on the esys module. a. 3. File . DISTRIBUTE. E7amine and uncomment the code that converts the packet to a vvec and writes the vvec to the esys interface a. 1. File : +lose @. #. a. then sets this vvec on the esys interface. Scenarios . c. $pen the scenario 1532.lab2. 4. +ompile : +ompile +ode or click the +ompile +ode #utton. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. 2emove the comments that #racket these lines. c.. . and then sets the creation time on the packet #ased upon the FCreationG field in the packet. o#tains the vvec from the vvec packet. E7amine and uncomment the code that retrieves a vvec from the esys interface and converts it to a packet of the format you created earlier. ?. d. P)g$ */ o+ !* .et Formats #. Ho to the 1532_ro(ter_lab2 node model. #. '0. =. #. %ress +trl. Click &'. © Copyrigh !""# OPNET T$%h&o'ogi$(.

Cook for the comment /( ')*+.. The cosimulation side will receive it as an array of '+? #its 8represented as chars9. you may e7it /odeler without saving.. Cook for the comment /( ')*+. Uncomment E.%). in c:\op_models. 6ill in main#$. #. 2ight-click on the esys module and select Edit Attrib(tes.and removing the relevant comments.%).callbac ii. &ote that there are two functions. +. Examine and modify external code '. ''. a.indows E7plorer.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI a.. SHARE. main#$ and p _received_6andler#$. DISTRIBUTE. 2emove the comment around the event stepping routine( /(%sa_%&ecute_'ntil #esa_6andle0 5status0 time0 %23*_')-17_+)%_%9%)-0 5finis6_time0 5num_events$"(/ CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. ii. I&%. main#$ then kicks off the simulation. This should open up the file in /icrosoft <isual CBB. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. #y looking for comments that #egin with /( ')*+. 2emove the comments around the call#ack registration( /(%sa_1nterface_*allbac _Be/ister #esa_6andle0 5status0 iface0 00 p _received_6andler0 0$"(/ re/istration (/ #. &otice that there is a 0idirectional esys interface of type bit and dimension 12. FORWARD. dou#le-click on lab2_1532. P)g$ *0 o+ !* .%)..c a. $pen the file lab2_1532. &ote that you just modified the process model so that it creates a '+?-#it vvec out of a '+?-#it packet.command to e&ecute a sin/le event (/. t this point. Using . i.interface call#ack registration code. i. Click the Edit ES" Model #utton. main#$ registers p _received_6andler#$ as the call#ack function that is called whenever something is written to the esys interface.c. © Copyrigh !""# OPNET T$%h&o'ogi$(. Uncomment code tells the sim to e7ecute a single event.

i. Enter the following #elow the comment( /(%sa_-erminate #esa_6andle0 %23*_-%B.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI c. I&%.rite the #it array to the E-: interface. SHARE. © Copyrigh !""# OPNET T$%h&o'ogi$(.* U&C$//E&T and removing the relevant comments. DISTRIBUTE. a. #y looking for comments that #egin with .%). Cook for the comment /( ')*+. into t6e simulation after a dela.37$"(/ 1. ii.code to terminate t6e simulation (/.%). Cook for the comment /( ')*+. Uncomment code that terminates the simulation. (/. i.0 bits0 0$"(/ CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. P)g$ *1 o+ !* .. Uncomment the code that writes data to the interface( /(%sa_1nterface_3rra. 6ill in pk)received)handler89. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.1)3-%_)+B. ._2et #esa_6andle0 5status0 iface0 time C dela.code to inject t6e arra.. ii. FORWARD.

could you write a single call to %sa_%&ecute_'ntil#$ that would have the same effectD fter the process model creates the packet and sends it out on the esys interface. $pen up an $%&ET Console from the . Save #.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI 3. File .s\include /<_=>?_ 3. "n the main#$ function. a. 6orce compile the simulation.  1532-lab2. P)g$ !" o+ !* . FORWARD. Compile the e7ternal code. 1.sim –ef 1532-lab2 Lab Questions '. SHARE. what happens to the packetD "f you had changed the encoding attri#ute of the packet fields.  op_m sim –net_name 1532-lab2 -c 4. Change directory to op_models . DISTRIBUTE. I&%.dev32.c /1*:\pro/ra:1\opnet\11. instead of the while loop. +. © Copyrigh !""# OPNET T$%h&o'ogi$(. +lose Compile the simulation and run it '. File . -ave and close the file. would the simulation still workD Either way. what would have changedD Extra Credit CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. +.0. 1. 3.i0.  *7 /c lab2_1532. 2un the simulation.3\s.indows -tart /enu. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.

P)g$ !* o+ !* . I&%. type and si!e. 5ou should pay attention to the slide on matching the the vvec conversion arguments with the packet’s encoding. CONFIDENTIAL INFORMATION: DO NOT DISCLOSE. FORWARD. © Copyrigh !""# OPNET T$%h&o'ogi$(. fter converting the packet to a vvec. DISTRIBUTE. SHARE.1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI Aecome more familiar with the vvec to value routines. try converting the vvec to native values using op)vvec)to)value89. OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.