> Do I have to set the refgeo point also with X,Y locations?

Yes.

> session.location.refscale=100.0   #100 pixel = 100m
> 
> first distance, e.g. 200 m:     Node1 = (100, 50) and Node2 = (300, 50)
> first distance, e.g. 500 m:     Node1 = (100, 50) and Node2 = (600, 50)

Seems correct.

> This point is not clear, at least for me, few months ago I used in CORE the
> emanelosscontroller.
> Is that still alive?
> Which is the difference  with emaneeventpathloss?

You're right! My mistake, I forgot about emaneeventpathloss. We need to 
integrate that with the GUI, so you can double-click the WLAN if 
pathlossmode=pathloss, to invoke that GUI. (You can invoke 
emanecommeffectcontroller in this way.)

> I said that in my emulations the GUI attached to a session wasn't able to
> produce any effect because I had the following scenario:
> I launched a session with a python script.
> I opened CORE with this command:  "sudo core"  (not cored!)
> In the window a select the session already launched with the script.
> I reduced the txpower till based on my calculation I shouldn't have any
> wireless link, BUT I continued to ping the two nodes.
> 
> Which was my mistake?

Python scripts launched on their own will not show up in cored or the GUI. They 
must be launched from the GUI using "Execute Python script..." or using "cored 
-e ..." if you want to later attach the GUI. Changing the txpower via the GUI 
at run-time is also not supported since the value ends up in XML. Also, you 
shouldn't run the GUI with sudo but as a normal user.

-Jeff
_______________________________________________
emane-users mailing list
[email protected]
http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users

Reply via email to