# A-MPDU and MPDU stats **URL:** \ **Category:** Software\ **Created:** [December 12, 2024, 10:40pm UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187 "2024-12-12T22:40:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Luisschubert](https://avatars.discourse-cdn.com/v4/letter/l/ee7513/32.png) [@Luisschubert](https://community.morsemicro.com/u/Luisschubert)\ **Post date:** [December 12, 2024, 10:40pm UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187/1 "2024-12-12T22:40:10Z")
Is there anyway to see stats on the size of MPDUs and A-MPDUs? I’m trying to quantify the efficiency of sending data over the medium. Additionally is there anyway to control A-MPDU or MPDU sizes? Edit: Also found reference in the driver `skbq.c` and `rc.c` that suggests that the A-MPDUs are currently configured to only contain a single packet. Is this a correct interpretation of what’s happening in `morse_skbq_tx_status_fill()` and `morse_rc_sta_feedback_rates()`. ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [December 16, 2024, 6:06am UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187/2 "2024-12-16T06:06:42Z")
Hi @Luisschubert Strictly speaking, we don’t have stats on MPDU length. But we do have statistics on the aggregation counts. Note that the A-MPDU length is negotiated by devices on association. For the TX side, we have a count of how many times N packets were aggregated. This can be checked with `morse_cli -i wlan0 stats | grep 'AGG N aggregates'`. The output is a list of counts with the first entry showing the number of packets not aggregated, and then 1 through to 16. For the RX side, we have a count on the number of times a bit in the block ack bitmap was set. You can get this information with `morse_cli -i wlan0 stats | grep 'RX AMPDU bitmap'`. Note, we only support up to 16 aggregates at this stage. MPDU size is controlled by the MTU or fragmentation threshold, whichever is lower. On our evaluation kits, this (by default), will be the MTU at 1500. You can control the MTU with `ip` or `ifconfig`. For the fragmentation threshold, this can be managed with `iw`, or if you’re using OpenWrt, with the `frag` option in the relevant `wifi-device` [section of the wireless config](https://openwrt.org/docs/guide-user/network/wifi/basic#mac80211_options). You can limit the aggregation count with the `max_aggregation_count` module parameter of the Morse Micro driver. ---
**Author:** ![makadoodle](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@makadoodle](https://community.morsemicro.com/u/makadoodle)\ **Post date:** [September 20, 2025, 6:42am UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187/3 "2025-09-20T06:42:40Z")
Thank you for the info. What’s the max aggregates you support now? ---
**Author:** ![makadoodle](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@makadoodle](https://community.morsemicro.com/u/makadoodle)\ **Post date:** [September 20, 2025, 6:30pm UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187/4 "2025-09-20T18:30:12Z")
I’m seeing high AGG TX Param Mismatch, what causes this and how can I remediate? ---
**Author:** ![alexb](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexb](https://community.morsemicro.com/u/alexb)\ **Post date:** [October 23, 2025, 12:47am UTC](https://community.morsemicro.com/t/a-mpdu-and-mpdu-stats/187/5 "2025-10-23T00:47:19Z")
Bumping the question on what can cause a high AGG TX param mismatch. Seeing the same on custom hardware integrating with the Quectel FGH100M-H module. On devices with high AGG TX mismatch, total throughput is limited to 13mbps on a wired link. Attaching data package and reference materials. [Quectel Orange Pi Debug 102125 v1.zip](https://community.morsemicro.com/uploads/short-url/gYLg6H6ZEHwkY4F5g6bb7PmNxw9.zip) (2.5 MB)