Hello Steven, you got the point, because the usage of blockage is not clear (at least for me). In particular I understood that I have to the define a blockage file if I would consider structure or support where the antenna is mounted. Is that right? In any case is not my scenario… for now.
I have point 2 point communication with omnidirectional antenna on one side and directional antenna on the other. I understood that I could create similar files to Listings 7.2 and 7.3 and from the Universal PHY GUI link to these specific profiles for each NEM. Is that right? I was asking because I was confused after your phrase : " If not, > you can just use fixed antenna gain (no profile necessary) which will engage the omni logic." Thanks. Regards, Simone On Jun 5, 2013, at 7:58 PM, Steven Galgano <[email protected]> wrote: > Simone, > > There is an example of defining a 6dBi omni antenna in user manual > Listing 7.2 and a more complicated 30 degree directional antenna > definition in Listing 7.3 [1]. > > You only need to create an antenna profile for an omni antenna if you > want to account for blockages associated with the platform the antenna > is mounted on in relationship to the NEMs it is communicating with. If > that is the case, you will also need to create a blockage file. If not, > you can just use fixed antenna gain (no profile necessary) which will > engage the omni logic. > > See user manual section 7.2 for Universal PHY configuration parameter > information. > > If all your NEMs are using the same antenna you only need to define it > once. Each NEM can be configured to use the same antenna profile. The > Antenna Profile Manifest XML *must* be the same for all NEMs since the > transmitter's profile id is sent with each packet. > > The training demonstrations contain the XML for user manual > demonstration 8 which illustrates the use of antenna profiles [2]. You > can experiment with the demonstrations using the training VM [3]. (Note: > Type 'make' in /home/emane/demonstration to generate all the required XML.) > > You only need to use events if you wish to switch antenna profiles or > re-point an antenna. If not, you can set those items via XML configuration. > > [1] EMANE User Manual > http://downloads.pf.itd.nrl.navy.mil/emane/training/user_training/emane-user_manual-0.8.1-rev2.pdf > > [2] EMANE User Manual demonstrations > http://downloads.pf.itd.nrl.navy.mil/emane/training/user_training/emane-user_manual_demonstration.20130228-1.tar.gz > > [3] EMANE User Training VM > http://downloads.pf.itd.nrl.navy.mil/emane/training/user_training/vm/emanedemo-0.8.x.20130225-1.tar.bz2 > > -- > Steven Galgano > Adjacent Link LLC > www.adjacentlink.com > > > On 06/05/2013 01:06 PM, smlabs wrote: >> Hi All, >> >> in previous version of CORE emulation EMANE offered a different way to set >> up Wi-Fi link with directional or omnidirectional antenna. >> In the new version of EMANE (I have 0.8.1) I have to write an XML file. >> >> Reading the EMANE-user-manual I still have some doubts. >> Do I have to write a separate XML (I mean antenna profile) for each >> antenna? (I suppose yes) >> Is there any other example that I could follow to write omnidirectional and >> directional antenna profile? >> >> Finally, do I have to launch any other emane-event program? >> >> Thanks in advance. >> >> Best Regards, >> Simone >> _______________________________________________ >> core-users mailing list >> [email protected] >> http://pf.itd.nrl.navy.mil/mailman/listinfo/core-users >> _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
