Wireless test solutions
Test against everything in the air.
Wi-Fi shares its bands with Bluetooth, Zigbee, radar and noise, and with other Wi-Fi networks. These are the questions Wavemetrik systems are built to answer.
Applications
What you can test.
Performance & RF
Wi-Fi performance and range
Find the limits of a wireless link.
Explore the test approachWi-Fi 7
Wi-Fi 7 and Multi-Link Operation
Understand what each link contributes.
Explore the test approachInterference & coexistence
Coexistence and interference testing
Recreate the traffic around your device.
Explore the test approachDFS development
Radar detection and DFS validation
Exercise channel changes under radar.
Explore the test approachMobility & mesh
Mesh and roaming validation
Follow the connection as RF conditions change.
Explore the test approachAutomation & diagnosis
Repeatable testing and packet-level diagnosis
Turn an observation into a repeatable test.
Explore the test approach
From a baseline to a repeatable test.
Performance and rate versus range
Measure throughput as the signal is attenuated step by step. MT-C24 automates RVR and RVRO runs, with programmable attenuators setting the path loss.
MT-C24
Wi-Fi 7 and Multi-Link Operation
Check MLO in EMLSR and MLMR modes, preamble puncturing and Multi-RU against 24 or 48 real client radios.
MT-C24
Wi-Fi robustness and QoS
See how an access point or client behaves under co-channel and adjacent-channel congestion, at a level and channel load you choose.
MT-Wave + MT-C24
Wi-Fi and Bluetooth coexistence
Play Bluetooth Classic, Low Energy and Long Range signals in the 2.4 GHz band while Wi-Fi traffic runs.
MT-Wave
Zigbee, Thread and Matter coexistence
Place IEEE 802.15.4 frames next to busy Wi-Fi channels and watch what the device does.
MT-Wave
DFS development and pre-compliance
Exercise radar detection, channel availability check and channel-move behaviour with radar patterns for eight regulatory regions.
MT-Wave
6 GHz and Wi-Fi 6E stress testing
Generate interference across U-NII-5 to U-NII-8.
MT-Wave
Sensitivity and SNR curves
Raise the noise floor with AWGN without moving the device under test.
MT-Wave
Regression and field-issue reproduction
Script the interference scene once and replay it exactly on every build.
MT-Wave
Performance & RF
Wi-Fi performance and range
A peak throughput number is only the beginning. Measure how an access point behaves as signal level changes, more clients join, and traffic runs in both directions.
Instruments
Where does performance start to fall?
Rate-versus-range testing varies RF path loss while the device stays in a controlled environment. It makes changes in throughput, link rate and stability easier to compare across firmware versions. Add orientation to understand how the device’s physical position affects its radio performance.
What to evaluate
- Single-client baseline on each supported band
- Throughput as attenuation increases
- Multi-client loading and fairness
- Rate versus range with device orientation
Evidence to keep
- Throughput versus attenuation
- Per-station performance observations
- A recorded configuration for regression
Test workflow
STEP 01
Record the baseline
Document firmware, channel, bandwidth, security and traffic direction. Characterize the RF path before interpreting the result.
STEP 02
Sweep the RF path
Use programmable attenuation to vary received signal conditions. Keep the other test settings fixed so the comparison has a clear reference.
STEP 03
Add client load
Repeat with the required number of active clients. Compare aggregate throughput alongside the experience of individual stations.
STEP 04
Review the evidence
Compare throughput with RSSI, MCS and packet captures. Record the point where behaviour changes and rerun it on the next build.
Attenuation represents controlled path loss, not a direct distance in metres. Results depend on the DUT, RF path and test configuration.
What is the difference between RVR and RVRO?
RVR measures performance as RF path loss changes. RVRO adds device orientation to that evaluation, helping you compare how the device’s physical position affects the result.
Can this compare firmware builds?
Yes. Keep the RF path, traffic and client configuration consistent, record the firmware version, and repeat the same attenuation sweep on each build.
Wi-Fi 7
Wi-Fi 7 and Multi-Link Operation
Validate Multi-Link Operation, preamble puncturing and Multi-RU with real client radios. Look beyond the aggregate result to see how the device uses its available links.
Does the feature behave as intended?
MLO introduces more than one path for wireless traffic. A useful evaluation starts with individual links and then compares the supported multi-link modes under the same conditions. MT-C24 supports EMLSR and MLMR, with 24 or 48 client radios and 2×2 MIMO per radio.
What to evaluate
- Single-link and MLO throughput
- EMLSR and MLMR behaviour
- Preamble puncturing under selected conditions
- Multi-RU and client loading
Evidence to keep
- Single-link and multi-link comparisons
- Evidence of link utilization
- Feature-specific regression cases
Test workflow
STEP 01
Confirm the feature set
Agree which band combinations and link modes the DUT and client configuration support.
STEP 02
Measure each link
Create a single-link reference before enabling MLO. Record channel settings and RF path loss for each band.
STEP 03
Exercise MLO
Run the selected link modes and introduce controlled changes to one RF path at a time.
STEP 04
Correlate the result
Compare throughput with link-level evidence and captured frames. Use the same setup when reviewing a firmware change.
Supported feature combinations depend on radio hardware, driver, firmware and operating band. MT-C24’s stated peak is up to 5 Gbps at 6 GHz; it is not a guaranteed result for every DUT.
Does MT-Wave generate Wi-Fi 7 traffic?
MT-Wave supplies controlled interference; MT-C24 provides the real client radios for Wi-Fi 7 feature evaluation. MT-Wave’s stated Wi-Fi traffic support extends through 802.11ax, so use MT-C24 for the Wi-Fi 7 client role.
Should aggregate throughput be the only metric?
No. Compare individual links with the combined result, and retain link-utilization evidence and captured frames so you can see how each link contributes.
Interference & coexistence
Coexistence and interference testing
Combine real Wi-Fi congestion with Bluetooth, Zigbee or noise to understand how a device behaves in a shared spectrum environment.
What happens when the channel gets busy?
MT-Wave has two independent radios. One generates Wi-Fi traffic across 2.4, 5 and 6 GHz; the other plays a selected non-Wi-Fi signal. Both can run at once, allowing a controlled combined interference scene without repeatedly rearranging the test bench.
What to evaluate
- Co-channel and adjacent-channel interference
- WMM voice, video, best effort and background
- Wi-Fi with Bluetooth or IEEE 802.15.4 traffic
- Noise sensitivity using AWGN
Evidence to keep
- Performance under defined interference
- Comparison across WMM traffic classes
- A reusable interference configuration
Test workflow
STEP 01
Establish a quiet reference
Measure the DUT with the interferer stopped and record the reference traffic.
STEP 02
Define the scene
Select the interfering channel, bandwidth, traffic class, level and inter-frame spacing. Choose a non-Wi-Fi profile when needed.
STEP 03
Change one condition
Step interference power or channel load while keeping the remaining parameters fixed.
STEP 04
Repeat and compare
Review throughput, latency or recovery against the quiet reference. Preserve the settings for a repeat run through the HTTP API.
One non-Wi-Fi signal type runs at a time. Non-Wi-Fi output is a control setting rather than a calibrated absolute value; measure actual power when that value matters.
Can Wi-Fi and Bluetooth run at the same time?
Yes. MT-Wave’s independent radios can generate Wi-Fi traffic and the selected Bluetooth profile together. One non-Wi-Fi signal type runs at a time.
Does this generate Matter application traffic?
The IEEE 802.15.4 stimulus supports coexistence evaluation around Zigbee, Thread and Matter devices. It should not be treated as a complete Matter application-traffic generator; agree application-level requirements in the test plan.
DFS development
Radar detection and DFS validation
Use representative radar patterns to explore detection, channel availability checks and channel-move behaviour during development and pre-compliance testing.
How does the device respond to radar?
MT-Wave provides radar profiles for eight regulatory regions and lets the selected pattern be placed independently on a supported 5 GHz channel. A controlled setup helps reproduce the conditions around a channel transition and compare behaviour across firmware revisions.
What to evaluate
- Radar detection behaviour
- Channel availability checks
- Channel-move and recovery observations
- Regional profile selection
Evidence to keep
- Observed detection and channel behaviour
- Packet evidence around the transition
- Repeatable development checks
Test workflow
STEP 01
Select the region
Choose the required profile from FCC, ETSI, Japan, Korea, Taiwan, Canada, Singapore or Australia / New Zealand.
STEP 02
Set the channel
Configure the DUT and select the radar placement. Record the RF path and measured stimulus level.
STEP 03
Observe the transition
Start the selected radar profile and capture the device’s response and subsequent channel behaviour.
STEP 04
Build a regression case
Preserve the setup and observations so engineering can repeat the same development check.
Formal certification requires accredited test equipment. Five listed long-pulse chirp profiles cannot be transmitted with current firmware: Japan Type 3 and Korea, Taiwan, Canada and FCC Type 5.
Is this a certification system?
This approach supports development and pre-compliance checks. Formal certification requires accredited test equipment and the applicable certification process.
Are all listed radar profiles currently available?
No. Current firmware cannot transmit five listed long-pulse chirp profiles: Japan Type 3 and Korea, Taiwan, Canada and FCC Type 5. Confirm the required profile set when scoping the evaluation.
Mobility & mesh
Mesh and roaming validation
Evaluate a device across controlled RF transitions, roaming conditions and mesh backhaul loading using a system configuration matched to the topology.
Instruments
Does connectivity continue through the transition?
A multi-enclosure setup separates the gateway, mesh nodes and selected clients. Programmable RF paths vary the relative signal conditions between them, making it possible to repeat a transition while observing traffic continuity and recovery.
What to evaluate
- Roaming between defined RF conditions
- Band-steering behaviour
- Mesh backhaul and client traffic
- Application continuity during transitions
Evidence to keep
- Topology and RF-path definition
- Transition and recovery observations
- Packet context for roaming issues
Test workflow
STEP 01
Map the topology
Identify the gateway, mesh nodes, clients and RF links that the evaluation needs.
STEP 02
Define the RF transition
Record starting levels and the path-loss changes that will trigger the scenario.
STEP 03
Run the traffic
Observe the selected traffic while the RF conditions change. Include packet capture where it can explain the transition.
STEP 04
Review recovery
Compare continuity, loss and recovery against the agreed acceptance criteria and repeat the transition.
Mesh and roaming coverage depends on the configured system and agreed case matrix. Presentation block diagrams explain logical connections, not a complete port-to-port cable schedule.
Which system should we start with?
Start with the required topology: gateway, mesh nodes, clients and controlled RF links. Use that case matrix to select the enclosure and client configuration with our team.
Does TR-398 coverage mean certification?
A configured test package can cover agreed TR-398 cases. Coverage alone does not establish certification; confirm the applicable cases, method and acceptance requirements for your programme.
Automation & diagnosis
Repeatable testing and packet-level diagnosis
Connect test configuration, execution and evidence so a performance issue can be reproduced, investigated and checked again on the next firmware build.
Can another engineer reproduce the result?
A useful result includes the conditions that produced it. MT-Wave exposes browser controls and an HTTP API with JSON; the capabilities presentation also describes MT-Core test sequences and MT-Sniffer’s distributed capture workflow. Integration is scoped to the selected test package.
What to evaluate
- Recorded RF and traffic configurations
- Scripted interference control
- Per-station capture and analysis
- Configured acceptance limits and reports
Evidence to keep
- Repeatable test configuration
- KPI and diagnostic context
- Results linked to an engineering issue
Test workflow
STEP 01
Define
Select the test cases, traffic, RF profiles and acceptance limits.
STEP 02
Execute
Apply the DUT and client configuration, run the sequence and monitor status.
STEP 03
Evaluate
Compare measured KPIs with the selected limits and collect diagnostic context.
STEP 04
Report
Review the results, charts and capture evidence. Retain the configuration with the issue record.
Automation and DUT command integration depend on the configured test package. Capture analysis depends on the radio, driver and supplied PHY metadata.
Does MT-Wave need desktop software?
MT-Wave provides browser controls and an HTTP API with JSON. The automation and DUT integration required for a broader sequence depend on the selected test package.
What can MT-Sniffer help investigate?
Its distributed capture workflow adds per-station packet context to performance and connectivity observations. Available analysis depends on the radio, driver and supplied PHY metadata.
Test workflow
Build the evaluation around your DUT.
STEP 01
Scope the device
Identify the DUT, firmware, supported bands and features you want to validate.
STEP 02
Agree the case matrix
Select the baseline, feature and robustness cases. Define the measurements and acceptance limits before testing.
STEP 03
Configure the system
Match clients, enclosures and controlled RF paths to the agreed cases.
STEP 04
Review the findings
Keep the results and diagnostic context together so the next action is clear and the important cases can be repeated.
Example result
How much interference can an access point take?
MT-Wave’s interferer level was stepped from −20 dBm (heavy interference) down to −70 dBm (negligible), and throughput measured for each WMM traffic class on two access points.
About MT-Wave| Access point | Best effort and background recover at | Voice and video recover at |
|---|---|---|
| Model-1Wi-Fi 6E | About −40 dBm | About −52 dBm |
| Model-2Wi-Fi 7, set to 802.11ax on 6 GHz | About −55 dBm | About −55 dBm |
For a like-for-like comparison MT-C24 was set to 802.11ax on 6 GHz. Interferer levels include over-the-air and cable losses.
Services
Buy the system, or have us run it.
Wi-Fi testing
Test systems and instruments for your own lab, configured for the devices you build.
Wi-Fi automation
Scripted test runs, so the same cases can be repeated on every firmware build.
Test as a service
We run the tests on our systems for you. Ask sales what is in scope.
Talk to us about your test plan
Questions & answers
A few useful answers.
Can the test plan include application traffic?
Yes, application traffic can form part of an agreed evaluation. Define the application, traffic direction, continuity measurements and acceptance criteria before selecting the configuration.
Do I need to buy a complete system?
You can discuss individual instruments, a configured system for your lab, or test as a service on Wavemetrik systems. Sales can help scope the option around your devices and test cases.
How is standards coverage agreed?
Start with the applicable standard and required case matrix, then agree the method, equipment configuration and acceptance limits. Record coverage and any exclusions in the selected test package.