You bought a '5G' CPE and speed tests are fast. But industrial control still shows jitter and the unit runs hot. The fault may not be signal — it's the network mode. Many 5G CPEs default to NSA, not full 5G.
How NSA and SA differ
- NSA (non-standalone): 5G rides on the 4G core, boosted by 'dual 4G+5G connection'. Fast, but latency is dragged by 4G and power use is high.
- SA (standalone): 5G runs on its own 5G core — real low latency, supports network slicing, the complete 5G form.
Three impacts that decide if you can use it well
- Latency: SA reaches milliseconds; NSA borrows 4G control plane so its latency floor is high and jittery.
- Power: NSA must hold both 4G and 5G, so the module draws more and runs hotter.
- Slicing: only SA supports network slicing (dedicated channels per service); NSA can't.
How to confirm which mode your device runs
- In settings/engineering mode, check access type: 'NR + LTE' or 'EN-DC' = NSA; 'NR only' = SA.
- See if a 'Network Slice/Slice' menu appears — that signals SA capability.
- Straight-up ask the supplier for an SA-mode screenshot — don't just trust '5G' on the box.
'Supports 5G' and 'runs 5G SA' are two different things. Before buying, ask 'can it switch to SA' — more useful than reading specs ten times.
FAQ
5G CPE power consumption and cooling?
5G modems draw more power—need metal casing/venting; industrially, check operating temp range.
Can 5G FWA replace fiber?
With good coverage it hits hundreds of Mbps—great where fiber is hard to run; but stability/latency still trail fiber.
What real-world speed does a 5G CPE deliver?
Depends on band (n1/n78/n41), signal, and carrier aggregation; real numbers fall short of specs.
Is lightweight 5G (RedCap) right for IoT?
RedCap cuts module cost and power—fits mid-speed IoT (surveillance/wearables), not high-bandwidth uses.