a Telit FN990-A28 is waiting in the box to be tested once an adaptor arrives - it is based on the same Qualcomm chipset, just the AT commands differ.
It does work, however, it was not such a smooth ride like with the Quectel.
That would have been my expectation. As you note, Mikrotik uses Quectel so does seem a safer choice. But what I'd check is if fireware upgrade is supported on the Quectel you're using — as my main downside to Telit modem is Mikrotik does not support firmware upgrade with them. So if a firmware upgrade is needed, you need to pull the modem out and use a PC with Telit. Now.... whether your Quectel will support firmware upgrade IDK, that might be very model specific even if they generically support.
But if you ask me the biggest downside of any "3rd party" modem is the lack of firmware upgrade support. This remove the modem to upgrade is PITA. The LM960s have been stable in that department without any upgrades for 1-2 years I'd say. Anyway, I've been a happy 4G Telit on Mikrotik customer for a while. Now 5G... IDK, for that we've just not been using Mikrotik, since the lack of FOTA upgrades has been a real problem over the years, and adding the hassle to adapt M.2, and no board with slots are ARM64-based.
Anyway, here is what the LM960 reports for signal. FWIW, I did file a bug in 2021, and after some discussion, they did support for reading Telit's "AT#CAINFO" command which is what gets the data you see I suspect (i.e. Mikroik has support for reading AT to get signal data for SOME modem, "pure" MBIM would report less than what you're seeing for LN990). Now it appears to missing the ca-band, sinr, cqi in your screenshot - those do appear on LM960s. Now that could also be an artifact of monitor "once" may not have a chance to read all the variables. Anyway here is what is reported for LM960, if it helps
/interface/lte/monitor lte1,lte2
status: connected connected
model: LM960A18 LM960A18
revision: 32.00.148 32.00.128
current-operator: AT&T Verizon
phy-cellid: XXX XXX
data-class: LTE LTE
session-uptime: 6m11s 50s
imei: XXX XXX
imsi: XXX XXX
uicc: XXX XXX
primary-band: B66@10Mhz earfcn: 66986 phy-cellid: XXX B2@10Mhz earfcn: 1150 phy-cellid: 390
ca-band: B2@20Mhz earfcn: 800 phy-cellid: XXX B66@10Mhz earfcn: 67086 phy-cellid: XXX
B66@10Mhz earfcn: 66686 phy-cellid: 400 B13@10Mhz earfcn: 5230 phy-cellid: XXX
cqi: 7 10
rssi: -83dBm -56dBm
rsrp: -116dBm -86dBm
rsrq: -16dB -12dB
sinr: -3dB 11dB
Now what you don't get is the eNB# directly, which is useful for lookup in stuff like cellmapper.net or other LTE/5G databases. It's possible to get via some math and available data, but the critical RSRP and SINR you should be getting LN990.
Now Mikrotik is using just AT#CAINFO, which you'll see maps to what you see for LN990, with the output varying depending on primary band is LTE or 5G. So if you have a 5G with 2CAs connected, Mikrotik gets this today:
<On NR5G 2CA: PCC + SCC>
#CAINFO:
<band_class>,<nr_channel>,<nr_bandwidth>,<nr_pci>,<nr_rsrp>,<nr_rssi>,<nr_rsrq
>,<nr_sinr>,<tac>,[<tx_power>],<nr_ulmod>,<nr_dlmod>,5G_SCC_0:
<band_class>,<nr_channel>,<nr_bandwidth>,<nr_pci>,<nr_rsrp>,<nr_rssi>,<nr_rsrq
>,<nr_sinr>,<nr_state>,<nr_ulmod>,<nr_dlmod>
...and dozen other variants, just repeating same info for each CA ...
Now I suspect the display FN990 is that Mikroitk isn't handling the slightly newer response in AT#CAINFO like the one above from a 5G connection... Since for an LTE connection it look like:
<On LTE 3CA: PCC + SCC + ENDC>
#CAINFO:
<band_class>,<rx_channel>,<dl_bw>,<pci>,<rsrp>,<rssi>,<rsrq>,<sinr>,<tac>,[<tx_p
ower>],<uplink_modulation>,<downlink_modulation>,<band_class>,<rx_channel>,<
dl_bw>,<pci>,<rsrp>,<rssi>,<rsrq>,<sinr>,<state>,<uplink_modulation>,<downlink_
modulation>
I think Mikrotik expects it to be more CSV-ish, but if you lock 5G looks like there be 5G_SCC_0: marker introduced & that may be breaking support. Mikrotik support is pretty good on these modems. They add the RSRP/etc and CA info for Telit in 2021 based on a bug report. While there is newer AT#CAINFOEXT that has more 5G data, i.e.
And since I had the manual up, here is the FN990's specs for 5G version in AT#CAINFOEXT
#CAINFOEXT: 2, LTE
PCC- BandClass: <band_class>, RX_CH: <rx_channel>, DL_BW:
<dl_bw>, PCI: <pci>, RSRP: <rsrp>, RSSI: <rssi>, RSRQ: <rsrq>,
SINR: <sinr>, TAC: <tac>, [TX_PWR: <tx_power>], UL_MOD:
<uplink_modulation>, DL_MOD: <downlink_modulation>
SCC0- BandClass: <band_class>, RX_CH: <rx_channel>, DL_BW:
<dl_bw>, PCI: <pci>, RSRP: <rsrp>, RSSI: <rssi>, RSRQ: <rsrq>,
SINR: <sinr>, STATE: <state>, UL_MOD: <uplink_modulation>,
DL_MOD: <downlink_modulation>
(and other variants, just repeating same info for each CA)
Since you're forging new ground with FN990, thought I share what I know from now years of using LM960s. (And already had AT manual up so I just cut-and-paste'd in case you open a case).