Changes between Version 40 and Version 41 of expansion/gw16167

Timestamp:

03/20/2026 06:29:21 PM (3 days ago)

Author:

Ryan Erb

Comment:

add notes for fixed MCS rate

expansion/gw16167

@@ -967 +967 @@
 
 Actual throughput will be less taking into account overhead, congestion, and RF factors. To examine your link you can use the following:
- * examine the rate control stats:
+ * Examine the rate control stats:
 {{{#!bash
 cat /sys/kernel/debug/ieee80211/phy0/morse/mmrc_table
 }}}
- * examine your link status (RSSI and MCS info):
+ * Examine your link status (RSSI and MCS info):
   - AP:
 {{{#!bash
@@ -1060 +1060 @@
 [[Image(tx.jpg​,400px)]]
 
+== Fixed MCS Rate
+
+For certain scenarios or applications, a fixed MCS rate may be desired. 
+
+This can be done at boot by modifying the module conf file, as shown in the example below:
+{{{
+###UBUNTU
+root@noble-venice:/etc# cat /etc/modprobe.d/morse.conf 
+options morse country=US enable_ext_xtal_init=1 fixed_mcs=2 enable_fixed_rate=1
+
+####OPENWRT
+root@OpenWrt:~# cat /etc/modules.d/morse 
+morse country=US enable_ext_xtal_init=1 fixed_mcs=2 enable_fixed_rate=1
+}}}
+
+An alternative way to set a MCS index while running from userspace, use the command:
+{{{
+echo "18" > /sys/kernel/debug/ieee80211/phy0/morse/fixed_rate
+}}}
+
+18 in this case corresponds to 2MHz LGI. If you want a list of available indexes run:
+{{{
+cat /sys/kernel/debug/ieee80211/phy0/morse/mmrc_table
+}}}
+
+Note, the driver may push it back to auto MCS and thus a custom script / process will need to be continually run to force it to fixed MCS. 
+
+
 
 == Troubleshooting