Have been attaching AntennaProfileControlMessage(s) in basemodelimpl.cc, sendDownstreamPacket(), for each transmit slot in the TDMA schedule. This profile is ultimately attached to the packet in frameworkphy.cc, processDownstreamPacket(), and the AntennaProfileStore_ local to that transmitting NEM's PHY via a call to gainManager_update().
However, I'm not convinced that either of the two attached AntennaProfileControlMessage(s) events have been handled at each receiving NEM's PHY since receive statistics available in RxSlotStatusInfoTable with antenna's properly oriented suggest that they are not. I was expecting to see a similar update of the gainManager_'s AntennaProfileStore_ for each of the receiving NEMs as the packet arrived prior to a subsequent calculation of the the gain via a call to gainManager_.determineGain, but there doesn't appear to be such an update. I cannot locate/identify the path that the packet would take to disperse the arriving AntennaProfileControlMessage although documentation suggests that the attached events should indeed be processed and should be processed prior to handling of the data in the packet. Can someone please help identify the path and where each receiving NEM's respective AntennaProfileStore_ is being updated with this information? Also, we are using a centralized deployment (for ease of debugging), having changed TDMA Demo 8 accordingly. The OTA Manager is effectively disabled within the .xml file in a platform.xml file used instead of the original 10 platformX.xml files. Does the disabling of the OTA Manager affect the ability to properly process the attached antenna events in arriving packets? Thanks for any help provided. Joe Stepien
_______________________________________________ emane-users mailing list emane-users@nrl.navy.mil https://publists.nrl.navy.mil/mailman/listinfo/emane-users
