Anyone else seeing this error in the logs?
It only happens if you are using carrier aggregation. If you are in a single band, it will be stable. It happens in 7.1b3~b6, usually at night, but can happen whenever. It usually won't recover without a reboot, so the ping watchdog brings it back. Sometimes it will reboot constantly for a few hours, then nothing for a few days. Toggling the LTE interface (disable/enable), sometimes gets it to connect, but not most of the time.
It's not modem temp. It's not router temp. It's not the power supply. It's not a defective modem. It's not an obvious firmware problem with Quectel, but the logs are so vague, Quectel says they can't help. They also cannot recreate it in their lab. So until there's a repeatable pattern, there's no hope for a firmware fix from Quectel. The signals are great. These are all in fixed locations, not mobile. This happens on all US carriers. It happens on any CA band combo (41+41, 66+66, 2+14, 2+12, etc).
I've talked to people, and it seems to affect, at the least: RB33, RB11, SXT, LHG, LHGG, NetMetal, wAP.
Mikrotik support has gone dark and will not comment on the ticket. Quectel says it's Mikrotik's problem.
The only thing I'm sure of is that it's tied to carrier aggregation. It's very stable if you are in a single band...which defeats the purpose of this modem entirely.
The EM20G and 500/502 5G modems also do this. Using only 2x2 MIMO does NOT change this behavior.
I have an EM12G sitting right next to the EM160 on the same tower, same sector, same band, same carrier, that does not do this. It's not the network(s).
The EM12G pulls about the same power as these other modems do in 2x2 mode, but doesn't have this error.