Technical reference · 12 September 2026
| Specification | Configuration |
|---|---|
| Radio / platform | Wi-Fi 7 | 2x2 per band | 5 + 6 GHz |
| Theoretical PHY reference | 8647 Mb/s aggregate PHY class |
| Host / processor | QCN9274; PCIe 3.0 / M.2 E-Key |
| Channel / network configuration | Up to 160 MHz at 5 GHz; up to 320 MHz at 6 GHz |
| RF / power | 4 RF paths; connector variant matched to order; 5 V |
| Mechanical / environment | 63 x 57 x 14 mm; 10 W maximum |
| Parameter | Pulse P7-04 |
|---|---|
| RF tuning ranges | 5150-5825 MHz and 5925-7125 MHz |
| Configuration storage | 2 Mbit serial I2C EEPROM |
| Supply and thermal design | 5 V; 8 W typical, 10 W maximum |
| RF allocation | Two spatial streams per band; four RF paths |
| Environmental design | -20 to +70 C operating; -40 to +85 C storage |
Model-specific datasheet reference points for RF design. TX is conducted power per RF chain; RX is input sensitivity. Configure channel, output power and antenna gain for the operating country.
| MCS | TX / chain (dBm) | RX sensitivity (dBm) |
|---|---|---|
| MCS0 | 21.0 | -87.0 |
| MCS1 | 21.0 | -83.0 |
| MCS2 | 21.0 | -80.0 |
| MCS3 | 21.0 | -78.0 |
| MCS4 | 20.0 | -74.0 |
| MCS5 | 20.0 | -70.0 |
| MCS6 | 19.5 | -68.0 |
| MCS7 | 19.5 | -66.0 |
| MCS8 | 18.5 | -63.0 |
| MCS9 | 18.5 | -61.0 |
| MCS10 | 17.0 | -57.0 |
| MCS11 | 17.0 | -55.0 |
| MCS12 | 16.0 | -52.0 |
| MCS13 | 16.0 | -50.0 |
Reference tolerance: ±2 dB.
| MCS | TX / chain (dBm) | RX sensitivity (dBm) |
|---|---|---|
| MCS0 | 21.0 | -83.0 |
| MCS1 | 21.0 | -80.0 |
| MCS2 | 21.0 | -76.0 |
| MCS3 | 21.0 | -73.0 |
| MCS4 | 20.0 | -71.0 |
| MCS5 | 20.0 | -66.0 |
| MCS6 | 19.5 | -64.0 |
| MCS7 | 19.5 | -62.0 |
| MCS8 | 18.5 | -59.0 |
| MCS9 | 18.5 | -57.0 |
| MCS10 | 16.5 | -53.0 |
| MCS11 | 16.5 | -51.0 |
| MCS12 | 14.5 | -48.0 |
| MCS13 | 14.5 | -46.0 |
Reference tolerance: ±2 dB.
Pulse P7-04 uses the ath12k driver family for Linux integration. Prepare the PCIe host, driver, device firmware and calibration as one matched software set. For an OpenWrt host, choose packages built for that host release and kernel ABI, then verify the detected device and radio profiles.
| Integration item | Configuration |
|---|---|
| Radio platform | QCN9274; PCIe 3.0 / M.2 E-Key |
| Driver family | ath12k |
| Firmware lookup family | /lib/firmware/ath12k/QCN9274/hw2.0/ — confirm the path requested in the device boot log |
| Board data | Retain the unit calibration and revision-specific board data; match the PCI/subsystem and board identity. |
| Radio profile | Wi-Fi 7 | 2x2 per band | 5 + 6 GHz; Up to 160 MHz at 5 GHz; up to 320 MHz at 6 GHz |
| Read-only first checks | lspci -nnk; dmesg; iw phy; iw dev; iw reg get |
Use the following commissioning procedure for Pulse P7-04. This is a test method, separate from the theoretical PHY specifications and datasheet RF references above.
| Step | Record and verify |
|---|---|
| Baseline | Model/revision, firmware build, host CPU, uplink speed, channel width, country profile, antennas and client spatial streams. |
| Link verification | Capture negotiated PHY, RSSI per chain and noise/retry statistics before sustained traffic. |
| Wired reference | Measure the wired path first; select a server link appropriate to 8647 Mb/s aggregate PHY class. |
| Traffic test | Run TCP in each direction, then concurrent clients; record duration, CPU load, temperatures and retransmissions. |
| Site acceptance | Repeat at the intended mounting positions; save results with the exact configuration for comparison. |
524WiFi™ engineering support · Tomorrow Systems®