我相信,在这个人工智能时代,只要坚持不懈,就一定能找到出路。
泰芯用户5901
-
Bandwidth 1MHz and 2MHz for WPA3 authentication -
Bandwidth 1MHz and 2MHz for WPA3 authentication====================================================================================
Wi-Fi HaLow(Morse Micro & TaiXin)认证支持和非认证互操作性指南
====================================================================================
- WPA2 相关认证支持的验证
A. 基本支持
-
基于 Morse Micro 和 TaiXin 芯片组的 SDK 支持 WPA2 WPA2-PSK/AES 是标准的 Wi-Fi 安全协议。
-
虽然 Wi-Fi HaLow (802.11ah) 标准本身推荐 WPA3 (SAE) 作为默认协议,但固件已配置为支持 WPA2-PSK (WPA2 Personal) 模式,以实现与现有 AP 和第三方芯片组的异构兼容性。
B. 芯片组间 WPA2 兼容性注意事项
-
在 Morse Micro 和 TaiXin 之间建立 WPA2-PSK 连接时,在四次握手过程中或切换到混合模式(WPA2/WPA3 混合模式)时可能会出现不一致的情况。
-
因此,在进行相互兼容性现场测试时,建议将安全加密方式显式设置为“WPA2-PSK-CCMP (AES)”(显式设置)。 2. 未认证互连方法(开放/共享模式)
要在不进行安全认证程序(WPA2/WPA3 握手)的情况下直接互连和测试两个异构芯片组(Morse Micro - TaiXin),必须将它们配置为开放系统(未加密/共享)模式。
A. 未认证(开放网络)配置的关键参数
-
SSID(网络名称):两台设备必须设置相同
-
安全/AKM 模式:无(或开放)
-
密钥管理:无
-
加密:无(或未加密)
-
工作频率/信道:设置为相同的信道 (CH) 和带宽 (BW,例如 1MHz / 2MHz / 4MHz)
B. 各芯片组的 CLI/AT 命令设置示例
[Morse Micro(AP/STA 设置)]
- 禁用安全模式:
mm-config set wifi.security none
- 设置 SSID:
mm-config set wifi.ssid "HALOW_OPEN_TEST"
- 设置带宽和信道:
mm-config set wifi.bandwidth 2
mm-config set wifi.channel 40
[TaiXin(AP/STA 设置)]
- 禁用安全模式连接到 SSID:
AT+WIFI_SEC=0 (0:开放模式)
AT+WIFI_SSID="HALOW_OPEN_TEST"
- 连接:
AT+WIFI_CONNECT
D. 原始数据包/混杂模式(绕过网络层)
- 当数据必须在 MAC 层直接传输和接收,而无需分配 IP 地址或建立 L3 连接时,双方设备可以切换到混杂模式(监听模式)或原始帧传输模式,直接交换 802.11ah 帧。
- 固件认证相关的开发和流程
A. 通过 SDK 工具链构建固件
- 使用开发环境(GCC/IDE 等)修改客户端配置代码,例如 Morse Micro(Morse SDK)和 TaiXin(TX SDK)。
B. 主要修改点
- 调整
wpa_supplicant.conf或 SDK 中的 Wi-Fi 协议栈配置头文件(例如wifi_config.h)中认证模式(WPA2-PSK 与 OPEN)的优先级。- 将异构芯片组互操作期间可能出现的四次握手超时时间从默认值(例如 1000 毫秒)增加到 2000 毫秒或更高。
C. 调试和验证方法
-
移植了一个调试 UART,用于在启动期间监控 802.11ah 状态机日志输出。
-
即使在现场测试期间信噪比急剧下降,在未认证模式下也不会发生因认证密钥交换失败而导致的连接断开,从而可以优先验证物理射频信号接收情况。
-
Bandwidth 1MHz and 2MHz for WPA3 authenticationOur company intends to build a system using components that have received WPA3 certification for 1 MHz bandwidth operation.
Specifically, we plan to use a Morse Micro product for the Access Point (AP) and a Taixin product for the Station (STA).
Since the number of STAs will be more than 50 times greater than the number of APs, wouldn't using a Morse Micro device as the AP actually be advantageous for Taixin?
We would appreciate your review of this approach.For the AP, we plan to purchase and utilize a commercially available Morse Micro product—specifically, the "Hellolink2." For the STAs, we intend to use Taixin products.
In this configuration, we anticipate having approximately 250 STAs connected to each AP. 1. Frequency: 920 MHz
2. Frequency Bandwidth: 1 MHz
3. Service Range: 1 km (line of sight)However, a potential issue arises: in today’s world, where artificial intelligence is becoming ubiquitous, the importance of authentication is increasingly coming to the fore.
Given this, we are considering implementing WPA3—a state-of-the-art security standard—to address these concerns.
We would appreciate it if you could review this.
-
2km range test / distance measurement MCS value is fixed at 2 / MCS is locked at MCS 2您好!感谢您的耐心等待与大力支持。
在过去两个月里,我们对泰信(TXW8301)产品进行了全面而深入的测试;今年10月,又用整整一个月的时间,对Morse Micro产品进行了系统性的验证与评估。
近期,我们顺利完成了两款产品的对比测试。经过严谨的实测数据分析,泰信产品在性能稳定性方面表现更为出色,令人印象深刻。基于此,我们拟采用如下方案:以Morse Micro产品作为AP端,泰信产品作为STA端,充分发挥双方优势,实现最佳协同效果。
在认证方面,Morse Micro已获得WPA3认证;泰信也于2024年顺利取得WPA3认证。两者的主要差异在于认证频段带宽:泰信认证覆盖1MHz和2MHz。而我们实际使用的频段带宽为1MHz,因此泰信的认证范围完全满足我们的应用需求,不存在任何合规性问题。
基于WPA3标准的统一性,我们有充分理由相信,Morse Micro与泰信产品之间的互操作性与兼容性将得到充分保障,本次联合测试必将取得圆满成功。
衷心感谢贵方一直以来的专业支持与密切配合。期待此次合作能够结出丰硕成果,实现互利共赢!
顺颂商祺!
-
IP allocation issues with Morse Micro and Taixin products.OpenWrt 23.05.6, Morse-2.11.13
root@halowlink2-908b:~# logread -f | grep hostapd_s1g
Sun May 24 00:57:10 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:57:21 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:57:33 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response
Sun May 24 00:57:43 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response
Sun May 24 00:57:55 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:58:05 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response
Sun May 24 00:58:15 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:58:27 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response
Sun May 24 00:58:39 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:58:49 2026 daemon.info hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: authenticated
Sun May 24 00:59:00 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response
Sun May 24 00:59:10 2026 daemon.notice hostapd_s1g: wlan0: STA ce:4f:26:8f:aa:88 IEEE 802.11: did not acknowledge authentication response -
IP allocation issues with Morse Micro and Taixin products.============================================================
Morse Micro <-> TaiXin IP Allocation Issue Summary[ Current Situation ]
- AP : Morse Micro MM8108-EKH05
- STA : TaiXin AH Module
- Symptom: Unable to obtain IP address (DHCP failure)
- Cause : "Invalid group cipher (0)" -> Connection fails at WPA authentication stage
[ Problem Flow ]
TaiXin STA -> Scans for Morse Micro AP (SSID found)
|
v
Attempts WPA Authentication
|
v
Invalid group cipher (0) <-- Security spec mismatch
|
v
Association Timeout
|
v
Disconnect -> Retry Loop
|
v
Result: No IP address assigned (fails before DHCP stage)[ Root Causes ]
-
TaiXin module is running in proprietary protocol mode (wnbsta)
- Morse Micro AP supports only standard WPA2-PSK
- Not compatible with TaiXin's proprietary PAIR mode
-
Failure to parse security specifications
- TaiXin cannot parse the WPA2 security header from the Morse Micro AP
- Result: group cipher = 0 (unrecognized)
-
Consequently, failure occurs at the Association stage
- IP allocation (DHCP) happens only after successful Association
- Therefore, this is NOT an IP issue, but a connection-stage issue
log data
"-------------------<CR><LF>
[1051276]LMAC STATUS:<CR><LF>
local: ce:4f:26:8f:aa:88 AID= 0 mode= 0(0/1:STA;2:AP)<CR><LF>
freq= 916.0 bw=1 bgr=-106 dc=0:0(5:44) <CR><LF>
chn: 908.0 916.0 924.0 <CR><LF>
bgr: -60 -60 -60 <CR><LF>
buf: free=65 tq=0 sq=0 <CR><LF>
irq: ac=42 bkn=0 bo(rts:frm)=0:0:0:0:42 to(rts:frm)=0:0 rx=52<CR><LF>
tx : cnt=42 dly=0:0ms est_rate=900kbps txp=0 fail=0 drop=0 <CR><LF>
rx : cnt=52 bus=0ms<CR><LF>
cca: st12= 0:0 mid1224= 0:0:0:0<CR><LF>
chip-temperature:36, vcc:3.37, vdd13b:1.35, vdd13c:1.34<CR><LF>
sta_list: no sta<CR><LF>
<CR><LF>
<ESC>[40;31m[1051550]ieee80211_sta_select_bss:24::by SSID find hgic_ah_test [50:2e:91:d2:c4:c9] at channel 2<CR><LF>
<ESC>[0m[1051559]vif1 state WPA_SCANNING -> WPA_AUTHENTICATING<CR><LF>
[1051569]Invalid group cipher (0).<CR><LF>
[1051570]vif1 state WPA_AUTHENTICATING -> WPA_ASSOCIATING<CR><LF>
<ESC>[40;31m[1052476]ieee80211_sta_assoc_timeout:53::connect to ap 50:2e:91:d2:c4:c9 timeout, disable it!<CR><LF>
<ESC>[0m[1052484]ieee80211_sta_disconnect LR= 0x20048df4. 50:2e:91:d2:c4:c9<CR><LF>
[1052490]lmac set GTK: cmd=1 addr=50:2e:91:d2:c4:c9 cipher= 0x0 flags= 0x0 keyidx= 0 keylen= 0<CR><LF>
[1052498]del_STA: addr=50:2e:91:d2:c4:c9<CR><LF>
[1052502]stamap=0x0<CR><LF>
[1052503]sleepmap=0x0<CR><LF>
[1052505]vif1 state WPA_ASSOCIATING -> WPA_DISCONNECTED<CR><LF>
[1052511]vif1 state WPA_DISCONNECTED -> WPA_AUTHENTICATING<CR><LF>
[1052516]vif1 state WPA_AUTHENTICATING -> WPA_SCANNING<CR><LF>
<CR><LF>
" -
2km range test / distance measurement MCS value is fixed at 2 / MCS is locked at MCS 2-------------------<CR><LF>
[561974]LMAC STATUS:<CR><LF>
local: ce:4f:26:8f:aa:88 AID= 0 mode= 0(0/1:STA;2:AP)<CR><LF>
freq= 916.0 bw=1 bgr=-106 dc=0:0(5:44) <CR><LF>
chn: 908.0 916.0 924.0 <CR><LF>
bgr: -107 -107 -107 <CR><LF>
buf: free=65 tq=0 sq=0 <CR><LF>
irq: ac=43 bkn=0 bo(rts:frm)=0:0:0:0:43 to(rts:frm)=0:0 rx=52<CR><LF>
tx : cnt=43 dly=0:0ms est_rate=900kbps txp=0 fail=0 drop=0 <CR><LF>
rx : cnt=52 bus=1ms<CR><LF>
cca: st12= 0:0 mid1224= 0:0:0:0<CR><LF>
chip-temperature:37, vcc:3.37, vdd13b:1.35, vdd13c:1.34<CR><LF>
sta_list: no sta<CR><LF>
<CR><LF>
<ESC>[40;31m[563415]ieee80211_sta_select_bss:24::by SSID find hgic_ah_test [50:2e:91:d2:c4:c9] at channel 2<CR><LF>
<ESC>[0m[563424]vif1 state WPA_SCANNING -> WPA_AUTHENTICATING<CR><LF>
[563434]Invalid group cipher (0).<CR><LF>
[563435]vif1 state WPA_AUTHENTICATING -> WPA_ASSOCIATING<CR><LF>
<ESC>[40;31m[564341]ieee80211_sta_assoc_timeout:53::connect to ap 50:2e:91:d2:c4:c9 timeout, disable it!<CR><LF>
<ESC>[0m[564349]ieee80211_sta_disconnect LR= 0x20048df4. 50:2e:91:d2:c4:c9<CR><LF>
[564354]lmac set GTK: cmd=1 addr=50:2e:91:d2:c4:c9 cipher= 0x0 flags= 0x0 keyidx= 0 keylen= 0<CR><LF>
[564363]del_STA: addr=50:2e:91:d2:c4:c9<CR><LF>
[564366]stamap=0x0<CR><LF>
[564368]sleepmap=0x0<CR><LF>
[564370]vif1 state WPA_ASSOCIATING -> WPA_DISCONNECTED<CR><LF>
[564375]vif1 state WPA_DISCONNECTED -> WPA_AUTHENTICATING<CR><LF>
[564380]vif1 state WPA_AUTHENTICATING -> WPA_SCANNING<CR><LF>"I am currently testing the connection between a Morse Micro AP and a Taixin product. The next step appears to be obtaining an IP address, but it is not being assigned. I would like to know how to proceed with this."
-
2km range test / distance measurement MCS value is fixed at 2 / MCS is locked at MCS 2 -
2km range test / distance measurement MCS value is fixed at 2 / MCS is locked at MCS 2Summary of Wi-Fi HaLow 2km Test MCS Fixed Settings
■ Overview
During the Wi-Fi HaLow (802.11ah) 2km long-range test using the TXW8301 chipset,
the MCS (Modulation and Coding Scheme) value is fixed at 2 for the test execution.■ Software Version
- TXW8301_FMAC: v2.4.1.5-43933
- TXW8301_WNB: v2.4.1.3-43933
■ Test Settings
[Basic Parameters for 2km Mode]
2km mode: ack_tmo=300, bss_bw=1, tx_mcs=0[Actual Test MCS Values]
- Fixed MCS: MCS 2
- Bandwidth: 1 MHz (BW=1)
- Frequency: 916.0 MHz
- ACK Timeout: 300ms
■ Test Log Example
[Confirmed in AP Log]
STA1: ce:4f:26:8f:aa:88 V2.4
tx1: mcs=2 snr=40 data=0KB(0kbps) per=0
rx1: mcs=2 evm(avg:std)=-29:1 rssi=-7 data=0KB(0kbps)[Reasons for Using MCS 2]
- Long-Range Communication Optimization: MCS 2 is a relatively low modulation
scheme, which helps maintain a stable connection during 2km long-range
communication. - Enhanced Robustness: Ensures communication even in noisy environments by
securing a high SNR margin. - Test Standardization: Enables consistent performance comparison across
different distances under uniform test conditions.
■ Related Configuration Commands
Settings confirmed in the log:
AT+TX_MCS=0 # MCS auto mode (actually uses MCS 2 internally)
AT+BSS_BW=1 # Set bandwidth to 1MHz
AT+ACK_TO=300 # Set ACK timeout to 300ms■ Notes
- Although tx_mcs=0 is set in the source code, MCS 2 is forcibly applied
internally when in 2km mode. - This is considered a firmware-level setting designed to ensure the reliability
of long-range tests. - MCS 2 utilizes the QPSK modulation scheme and is optimized for long-range
and low-power environments.
-
2km range test / distance measurement MCS value is fixed at 2 / MCS is locked at MCS 2Summary of TXW8301 Module 2km Long-Range Communication Test Results
- Test Overview
Module Used: TXW8301 (Wi-Fi HaLow)
Target Distance: 2km
Key Settings: MCS fixed at 2 (Long Range mode), Bandwidth 1MHz, Frequency 916MHz - Key Conclusion
With the MCS value fixed at 2, the maximum distance for stable communication based on RSSI and SNR was confirmed to be approximately 700m. This falls significantly short of the 2km target. - Key Observations from Logs
Severe Signal Degradation: As the distance increases, the RSSI drops below -80dBm and the SNR falls below 10dB, causing extreme signal instability.
Surge in Packet Error Rate (PER): In weak signal areas, the PER spikes to 50%~100%, resulting in frequent Ping failures (100% packet loss).
Connection Instability: Frequent disconnections and reconnections occur repeatedly due to Heartbeat failures.
Drastic Drop in Actual Throughput: The txp (transmit power index) drops to 0. Furthermore, unlike the displayed estimated rate (est_rate), the actual Packet Reception Rate (PRR) is very low, causing a significant drop in effective data transfer speed. - Recommendations & Requests for Improvement
Since guaranteeing 2km communication quality with the current fixed MCS 2 setting is difficult, please advise if the Auto Rate Fallback (MCS adaptation) feature can be enabled or optimized.
Physical antenna gain improvement or TX Power (transmit output) settings need to be re-evaluated.
MAC layer parameter adjustments, such as increasing the ACK Timeout value for long-range environments, appear necessary.
- Test Overview