LX60 and RV55 LTE-M/NB-IoT Global not connecting to the network

I have LX60 and RV55, both units do not attach to the network.
They do not send RACH request or any comms with the network for both LTE-M and NB-IoT signals.

The Airlink GUI shows that the UE can see the network but RF signal seems low. (see attached captures)
I confirmed that the RF signal is not low because this is a lab environment.

LX60 AT Command:
ATI

LX60

OK
AT+COPS?

+COPS: 0
OK
AT+CEREG?

OK
AT+CGATT?

ERROR
AT+CGATT=0
ERROR

AT+CFUN=?
OK
AT+CFUN?
ERROR


Hi @abiodun,

Could you please take a look at the below question/concern and share your answers?

  1. Please make sure that antennas are attached to the routers. Two antennas are required when connecting to an LTE network.

  2. Which ALEOS version and Radio Module Firmware are LX60 and RV55 running? If they are not the latest versions, please refer to the following link to obtain the latest ALEOS version and Radio Module Firmware, and then recheck whether the problem is resolved.

    Link the latest FW LX60: https://source.sierrawireless.com/resources/airlink/software_downloads/lx/lx-firmware-list/#sthash.EynjXXtw.kYBAR4br.dpbs
    Link the latest FW RV55: https://source.sierrawireless.com/resources/airlink/software_downloads/rv55/rv55-firmware-list/#sthash.ITVBrOPN.dpbs

  3. Could you please let me know which carrier’s SIM card you are using?

  4. Also, could you please share full log file and Template file on LX60 and RV55 for analysis?

Thanks,

Hi @jerdung,

I tried all your suggestions with no success, see details below.

  1. I confirmed that functional antennas are been used for testing. LX60 and Rv55 use only one antenna.

  2. Current ALEOS & Radio Module Firmware
    LX60: ALEOS: LX_4.13.0.17
    Radio Firmware: WP7702_02.16.06.00_GENERIC_001.028_004

RV55: ALEOS: RV_4.13.0.17
Radio Firmware: WP7702_02.16.06.00_GENERIC_001.028_004

Upgrades to latest versions:
LX60: ALEOS: LX_4.16.0.21
Radio Firmware: WP7702_02.36.06.00_GENERIC_001

RV55: ALEOS: RV55_4.17.0.012 (Upgrade failed; Certificate verification failed: Unable to get a local issuer certificate)
Radio Firmware: WP7702_02.36.08.09_GENERIC_001

  1. SIM Carrier: Generic SIM on a private LTE network.

  2. Log files and templates file are attached.

SW LX60-RV55 templates-logs.zip (427.4 KB)

Thanks,
Abi

@jerdung,

I still await your reply based on the info and logs I provided.

Thanks,
Abi

Hi @abiodun,

Please try using the carrier’s SIM on a real network to see if the devices can connect to the network.
→ In order to narrow down the issue from simulator network, we need to recheck on the real network first, so please try to use the SIM from real network at your location to recheck the issue.

Thanks,

Hi @jerdung ,

I tested using Verizon & the LX-60 attached on Cat-M1.

filteredlogs(1).txt (1.3 MB)

hi ,
i also facing the same issue with RV55 LTE-M/NB-IoT, even update the software and firmware , still cannot connect to the network
2

Hi @isaacay,

Welcome to our community!

  • Based on the images you provided, I see that all signals (RSSI, RSRQ, RSRP) are at the Poor level. Please make sure the antenna is attached to the RV55.
  • Do you want to connect to LTE-M or NB-IoT? How did you configure the APN? Please check carefully with the network provider to ensure the APN is correct for connecting to LTE-M/NB-IoT.
  • Do you have any devices that have successfully connected to LTE-M/NB-IoT?
  • Additionally, please share the log file and template file with me.

***Here are the instructions for obtaining the log file and template file:

  1. The configuration template file can be found in ACEmanager → Template. Provide any desired name for the Template Name, and then press Download to retrieve the template file.
  2. Obtain the log file:
    a. Go to AceManager > Admin > Log > Configure Logging.

Set all log levels to DEFAULT (NOTICE).

Set Linux Syslog to DISPLAY.

Then select Apply.

b. Reboot the gateway.

c. Go to Admin → View log → Download Logs.

Thanks,

Dear Jerdung,

· Based on the images you provided, I see that all signals (RSSI, RSRQ, RSRP) are at the Poor level. Please make sure the antenna is attached to the RV55.

Yes. the antenna is well connected.

· Do you want to connect to LTE-M or NB-IoT? How did you configure the APN? Please check carefully with the network provider to ensure the APN is correct for connecting to LTE-M/NB-IoT.

Both tried . Using the same APN and the newtowrks all works well on Iphone.

· Do you have any devices that have successfully connected to LTE-M/NB-IoT?

This one is newly purchased . We only have one devices on hand. We cannot do the crosscheck.

· Additionally, please share the log file and template file with me.

Attached. By the way, after updated the software and firmware . The response time too slow and sometime no response

Thanks

20230909_000731_filteredlogs.txt (1.37 MB)

(Attachment template1.xml is missing)

Dear Jerdung ,

Attached the log.

Thank You!

template1.zip (222 KB)

Hi @isaacay,

“Both tried . Using the same APN and the newtowrks all works well on Iphone.”
→ On the phone, LTE CAT-M or NBiot cannot be used. Therefore, please confirm with the Mobile Network Operator to ensure that LTE-M or NB-IoT is supported.

Thanks

Hi,

Even we disable the LTE M1 and LTE NB-IOT, we still cannot get the IP,

We tested the same sim card and same APN in RV50X, APAC , it works.

Hi @isaacay,

There are a few cases where it’s mentioned to set “Extended Discontinuous Reception” to “Disable” and then reboot to fix the issue. You can try that.

Please refer to page 99 of the AirLink RV55 Series Software Configuration Guide at the following link for more information: source.sierrawireless.com/resources/airlink/software_reference_docs/airlink-rv55—configuration-guide/

On the other hand, in theory, CAT M (Category M) and NB-IoT (Narrowband IoT) are two wireless connectivity technologies designed specifically for the Internet of Things (IoT), and they are different from LTE (Long Term Evolution) networks.

Therefore, you cannot compare RV55 LTE-M/NB-IoT with RV50X APAC, which uses LTE.

It’s best to confirm with your carrier whether they support LTE-M or NB-IoT and which APN you should use.

Thanks,