A common field mistake is treating “has signal” as “is online.”
The module reports a signal value, the antenna is connected, and the SIM is inserted, but MQTT cannot connect, TCP fails, and the platform never sees the device. This may look like unstable network service, but the device can be stuck at very different layers.
Cellular data connectivity has several stages:
radio coverage
-> usable SIM
-> network registration
-> data bearer activation
-> IP or data channel
-> DNS, TCP, TLS, MQTT
-> application platform reachability
“Signal” usually covers only the first part.
Signal Does Not Mean Registration
A signal value means the module can see some cellular cells. Whether the network allows the device to attach depends on the SIM, operator, RAT, bands, roaming policy, and subscription.
Common causes include:
- SIM not provisioned for the required IoT service
- SIM operator does not match field coverage
- module locked to the wrong RAT or bands
- roaming access rejected
- LTE coverage exists, but the SIM only supports specific IoT access
The first question is not only whether signal is strong, but whether registration completed. If registration fails, check reject cause, operator selection, RAT configuration, and SIM state.
Registration Does Not Mean Data Works
Even when the module reports registered or attached, application data may still fail.
Data usually needs APN configuration, PDP/PDN context activation, IP address, routing, and the operator’s data path. A wrong APN can leave registration normal while sockets fail.
Common failures include:
- wrong or missing APN
- private-network SIM using a public APN
- subscription limited to a specific platform
- PDP activation failure
- IP assigned but DNS fails
- TCP connects but TLS or MQTT fails
These are bearer and application path problems, not just radio coverage problems.
Weak Coverage Makes Intermittent Success Hard
Under weak coverage, a module may register occasionally and send one packet, then drop again.
Record:
- RSRP, RSRQ, and SINR, not only RSSI
- antenna position, cable, enclosure, and grounding
- supply voltage during transmit bursts
- frequent search, re-registration, or PDP rebuilds
- whether application timeouts are too short
Many disconnects come from radio link, power supply, and retry strategy interacting.
Debug Order
Record the path in order:
- SIM detected, PIN, ICCID, and IMSI normal.
- Current RAT, bands, and operator selection.
- Cell camping and signal quality.
- Network registration state.
- APN and PDP/PDN activation.
- IP address and DNS.
- TCP, TLS, and MQTT failure point.
- Whether failure coincides with voltage drop, reboot, re-registration, or weak signal.
“Signal but no data” is rarely explained by one vague network problem. Separate coverage, registration, bearer, and application connection to find the real layer.