Contact sales

Real-radio client emulation

MT-C24

Wi-Fi 7 client emulators

Real-radio clients with individual RF paths, for client scaling, MLO and interoperability testing. MT-C24 and MT-C4 use real radios at up to 2×2 MIMO; MT-BE emulates up to 4×4 MIMO.

Contact sales
Compare emulators
One radio. One independent path.24 radios
Each radio has its own RF path, so every link can be attenuated and observed on its own.
Real radios, MT-C24
Up to 24
Stations per band, MT-BE
Up to 128
MIMO, MT-BE
Up to 4×4
Channel width
Up to 320 MHz

Client emulator configurations

Platform selection follows spatial streams, station count and the MLO behavior under test.

MT-C24 / MT-C4

Real-radio clients

MT-BE

Up to 4×4 MIMO emulation

Feature availability depends on the selected radio, OS/driver, DUT and region.

Individual RF paths make tests controllable

  • A path for each radio

    Dedicated RF chains allow independent attenuation and observation of each test link.

  • Antenna selection

    Omnidirectional and directional antennas support different traffic and coverage scenarios.

  • Path-loss characterization

    Cable loss, splitters and attenuators form part of the test reference plane.

MT-Core test automation

Test setup, execution and reporting use a common sequence and configurable limits.

  1. Define

    • Select test cases.
    • Set traffic and RF profiles.
    • Choose acceptance limits.

  2. Execute

    • Apply DUT and client settings.
    • Run the test sequence.
    • Monitor per-test status.

  3. Evaluate

    • Compare KPIs with limits.
    • Capture diagnostic context.
    • Record the verdict.

  4. Report

    • Export an HTML report.
    • Review KPIs and charts.
    • Share the test evidence.

Automation support and DUT command integration follow the configured test package.

RF behavior in live telemetry

TX / RX MCS over time
MCS index
  • Tx
  • Rx
0
2
4
6
8
10
12
14
0
200
400
600
800
1000

Time (s)

TX / RX PHY data rate over time
PHY data rate, Mbps
  • Tx
  • Rx
0
1,000
2,000
3,000
4,000
5,000
6,000
0
200
400
600
800
1000

Time (s)

Per-link visibility

Data and beacon RSSI, MCS, channel width, rate, packets, retries and failures.

MLO session context

Bands, channels and per-band traffic identify how the connection uses its links.

Metric availability depends on the client and capture metadata. One-way latency requires an appropriate timing method.

Measured multi-gigabit throughput

MT-C24, 2×2 MIMO OTA
>5.4 Gbps
MT-BE, TCP MLO OTA
>8.5 Gbps
Reported UDP peak
>9.5 Gbps
MT-BE TCP MLO throughput trace
Throughput, Mbps
0
2,000
4,000
6,000
8,000
10,000
0
100
200
300
400
500

Time (s)

Wavemetrik lab examples. Throughput depends on the DUT, bands, bandwidth, RF path and traffic settings.

Rate adaptation as attenuation increases

The throughput curve identifies operating regions and the onset of link degradation.

MT-C24 throughput over time
Throughput, Mbps
0
1,000
2,000
3,000
4,000
5,000
6,000
0
100
200
300
400
500
600

Time (s)

Controlled variable

Increase attenuation in steps while maintaining the selected traffic profile.

Correlated evidence

Review throughput alongside RSSI, MCS, retries and receive drops.

Horizontal axis: elapsed time. The trace shows a sweep, rather than sustained peak throughput over its entire duration.

Rate vs range across device orientations

Throughput by orientation

Average throughput at 0°, Mbps

20 dB
915
30 dB
714
40 dB
552
50 dB
332
60 dB
169

Radius: average throughput. Angle: device orientation. Each trace represents one attenuation setting. Settings from 0 to 15 dB lie close to the 20 dB trace at this scale and are not drawn.

Peak at 0 dB attenuation
942 Mbps

Orientation sensitivity

The reported spread at 0 dB is approximately 2%.

Coverage roll-off

Mean throughput: 907 Mbps at 20 dB, 536 Mbps at 40 dB and 116 Mbps at 60 dB.

Client load and packet size affect capacity

Aggregate TCP throughput for 1, 2, 4, 8, 16 and 24 clients in an example MLO test.

With 1 client at 1500-byte MSS
2,425 Mbps
Aggregate with 24 clients at the same MSS
1,264 Mbps

Throughput against TCP MSS

Aggregate throughput, Mbps
  • 1 client
  • 2, 4, 8 and 16 clients
  • 24 clients
0
500
1,000
1,500
2,000
2,500
128
256
512
1024
1250
1500

TCP MSS (bytes)

Test configuration: 2.4 GHz at 40 MHz and 6 GHz at 160 MHz. Measurements show aggregate TCP throughput.

MLO operating modes and test objectives

Mode negotiation and packet timing determine which multi-link behavior a run demonstrates.

MLMR describes a radio arrangement. STR describes a simultaneous operating capability. Device support and link-pair constraints apply.

Puncturing and multi-user validation

Feature testing combines a controlled stimulus with evidence from actual transmissions.

  • Preamble puncturing

    Controlled stimulusSecondary-subchannel interference

    Packet / PHY evidenceEHT Operation signaling and EHT PPDU metadata

    Service KPIThroughput and active bandwidth

  • OFDMA

    Controlled stimulusMultiple active clients and selected traffic mix

    Packet / PHY evidenceTrigger/RU allocation and multi-user PPDUs

    Service KPILatency, capacity and per-client fairness

  • MU-MIMO

    Controlled stimulusConcurrent spatially separated clients

    Packet / PHY evidenceSounding and multi-user spatial transmissions

    Service KPIAggregate and per-client throughput

Advertised capability and observed feature use answer different questions.

MT-Sniffer and MT-SYS

MT-Sniffer: captured data and decoded features depend on the radio, driver and supplied PHY metadata.

Build your test environment

Put MT-C24 to work.

Tell us about your devices, test requirements and lab. We’ll help you find the right configuration.

Talk to our team