Applicable VersionsNetsim AcademicNetsim StandardNetsim Pro

Applicable Releasesv11

(Note: From Netsim v12.1 onwards, Physical layer parameters are local, hence the user can configure different Transmitter Power in different nodes via Netsim GUI)

To set individual values for transmitter power, you would need to edit the config file. It cannot be done via the GUI. The steps are given below -


Create the desired network scenario in MANET and simulate it (this would obviously have a global value set for transmitter power)


After the simulation, a configuration.xml file gets created in the NetSim temp path( path…..\AppData\Local\Temp\NetSim). To open the Temp path, enter %temp%\NetSim in the Run window and click on OK.



Open configuration.xml file present in the temp path of NetSim using visual studio. It may look like




To format it suitably, click on reformat selection icon shown below


After formatting, the file would look like



Now go to the physical layer properties of each device and change the transmitter power value as per your requirement


After changing the values, save the file (Ctrl + S). Now right click on configuration.xml present in the temp path and click on Properties. Make it read-only by unchecking the Read-Only box present below. Click on Apply and then OK. 

Note: If you make the configuration.xml file as read-only, you will not be able to make any other changes via the GUI



Open NetSim GUI, go to MANET and create some network scenarios and run the simulation. Since the config file is in read-only mode, no new config file will be written. The config file you had edited will be taken as simulation input.


We generally do not recommend our users to edit config files / set as read-only because it can cause unpredictable behavior if not done correctly.  Please take care to do the modifications exactly as we have written. Any other changes to the config file can case NetSim to crash. Further, take care to uncheck the Read-only option after running your simulation. If not every simulation will simulate the same config file and hence always output the same results.