IEEE 802.11n data rate and packet size

219 views
Skip to first unread message

Hassam Mughal

unread,
Jul 10, 2018, 11:47:10 PM7/10/18
to ns-3-users
Dear All,
I am trying to simulate the DSDV-Manet using the IEEE 802.11n default settings i.e. 1Mbps as data rate,  Phy mode as ErpOfdmRate54Mbps and on off application packet size of 1000 bits.
But I am getting the following error:
assert failed. cond="remainingAmpduDuration > 0", file=../src/wifi/model/mac-low.cc, line=1605
terminate called without an active exception
Please kindly guide or help me regarding this issue. 

Hassam Mughal

unread,
Jul 10, 2018, 11:54:02 PM7/10/18
to ns-3-users
I have attached my Dsdv Manet file.
dsdv-manet.cc

Hassam Mughal

unread,
Jul 11, 2018, 4:21:11 AM7/11/18
to ns-3-users
This bug is still there in ns-3.27. Link to the bug:
Has anyone tried to solve this? The remaining Ampdu Duration which I am getting at which this assert is triggered is -68393.0ns


On Wednesday, July 11, 2018 at 12:47:10 PM UTC+9, Hassam Mughal wrote:

Sebastien Deronne

unread,
Jul 11, 2018, 4:28:17 AM7/11/18
to ns-3-users
And what about ns-3.28?

Hassam Mughal

unread,
Jul 11, 2018, 4:33:11 AM7/11/18
to ns-3-users
Dear Sebastien,
Actually, I have done a lot of modifications in physical, mac and routing layers. So, making all the modifications in ns-3.28 will take a lot of time. Due to which I didn't move to it. Moreover, there were few methods which I am using in ns-3.27 and are not used in ns-3.28 while I was trying to move. Hence, I ended up sticking to ns-3.27.

Hassam Mughal

unread,
Jul 11, 2018, 10:55:56 AM7/11/18
to ns-3-users
Dear Sebastien,
I am getting the following errors while porting to ns-3-dev or ns-3.28
../scratch/dsdv-manet.cc:189:74: error: ‘State’ does not name an enumeration in ‘ns3::WifiPhy’
 void PhyStateTrace (std::string context, Time start, Time duration, enum WifiPhy::State state
../scratch/dsdv-manet.cc: In member function ‘void DsdvManetExample::CreateDevices(std::__cxx11::string)’:
../scratch/dsdv-manet.cc:844:27: error: ‘HtWifiMacHelper’ has not been declared
   WifiMacHelper wifiMac = HtWifiMacHelper::Default ();
 

On Wednesday, July 11, 2018 at 5:28:17 PM UTC+9, Sebastien Deronne wrote:

Gabriel Arrobo

unread,
Jul 11, 2018, 11:43:43 AM7/11/18
to ns-3-...@googlegroups.com
For the first error make sure the traceCallback (PhyStateTrace) is correct (arguments).

And for the MacHelper problem:
Change: WifiMacHelper wifiMac = HtWifiMacHelper::Default ();
To: WifiMacHelper wifiMac;


Best regards,
Gabriel



--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

Hassam Mughal

unread,
Jul 11, 2018, 12:05:30 PM7/11/18
to ns-3-...@googlegroups.com
Dear Gabriel,
Bundle of thanks, Yes I already changed the wifi mac one, actually I used this trace method in ns-3.27 and it is working fine. The error it shows is actually, state is defined as enum in the parameters, which was working till ns-3.27, but after that, there is no enum state, and I couldn't find any documentation that mentions what to use instead of that. You can check in the dsdv-manet.cc file that I have attached.

You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/mjNB9lEjNx8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.

To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.


--
Thanks
Best Regards,

Hassam Mughal
Research Associate & MS Student
Department of Information and Communication Engineering
Hankuk University of Foreign Studies, Global Campus, South Korea
Treasurer - IEEE Computer Society Karachi Section
Co-Founder - Electronics Junkies

Gabriel Arrobo

unread,
Jul 11, 2018, 1:22:47 PM7/11/18
to ns-3-...@googlegroups.com
Here is the documentation on how to modify your callback function for the WifiPhyState https://www.nsnam.org/doxygen/classns3_1_1_wifi_phy_state_helper.html#a7c976e20feb5c06594b14c4411609b2f

It works for me in ns-3-dev and it should also work with ns-3.28

Best regards,
Gabriel


Hassam Mughal

unread,
Jul 11, 2018, 1:32:59 PM7/11/18
to ns-3-...@googlegroups.com
Oh thanks a ton man! I will modify and get back if there will be any error. 
Message has been deleted

Hassam Mughal

unread,
Jul 11, 2018, 2:52:47 PM7/11/18
to ns-3-users
Dear Gabriel,
I am getting this error, I have attached the screenshot of running it under gdb debugger. Can you please view my Dsdv-manet.cc file and let me know if my implementation of traced call back is right? I am attaching the file again here. Will be grateful to you for this act of kindness.Thanks
Screenshot from 2018-07-12 03-45-10.png
dsdv-manet.cc

Hassam Mughal

unread,
Jul 11, 2018, 11:26:56 PM7/11/18
to ns-3-users
Dear Developers,
This issue (remainingAmpduDuration) can be regenerated in the dsdv-manet.cc class in NS-3.28 or ns-3-dev by using the following parameters:
std::string rate ("1Mbps");
  std::string phyMode ("ErpOfdmRate54Mbps");
wifi.SetStandard (WIFI_PHY_STANDARD_80211n_2_4GHZ);
and with 4+ nodes and 50+ simulation time.
I hope to get some guidance or help in this regard.


On Wednesday, July 11, 2018 at 12:47:10 PM UTC+9, Hassam Mughal wrote:

Hassam Mughal

unread,
Jul 13, 2018, 8:08:32 AM7/13/18
to ns-3-users
Dear All,
I was able to get rid of this issue by using ErpOfdmRate48Mbps and 20 MHz channel width.
But, I don't know the reason of why it is not giving the same error in this phy mode while it was giving in ErpOfdmRate54Mbps. Can anyone please explain me?
Thanks


On Wednesday, July 11, 2018 at 12:47:10 PM UTC+9, Hassam Mughal wrote:
Reply all
Reply to author
Forward
0 new messages