This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 Unable to Connect to Anritsu Callbox

I sent some nRF9160 prototypes down to a CTIA certified test lab in North Carolina to do carrier TRP and TIS testing.  When they add their test sims they seem to be unable to connect to the nRF9160.  Was there anything special I needed to configure in the module for testing with a callbox?  I have the module setup to connect on bootup.  The lab inserts their sim card into the holder and applies power, booting up the module.  The module boots up and start looking for a base station, at that point the callbox the test center is using finds the device and starts to connect and initiate the test processes.  But it then fails establishing the connection. 

Prior to sending the units out I tested them both with an iBasis sim and they were able to register onto Verizon’s network.

 

Some other info:

Anritsu 8821 callbox

Using generic test sims

Testing bands 2, 4, 12, 13

For firmware on the nRF9160, I basically took the at_client sample and modified it to call the lte_lc_init_and_connect() function.  Was there something else I missed? I attached the config file and the main.c for quick review.

 

Is Nordic limiting the max power at all?

 

#include <zephyr.h>
#include <stdio.h>
#include <drivers/uart.h>
#include <string.h>
#include <modem/lte_lc.h>
#include <modem/bsdlib.h>

/**@brief Recoverable BSD library error. */
void bsd_recoverable_error_handler(uint32_t err)
{
	printk("bsdlib recoverable error: %u\n", err);
}

/**@brief Configures modem to provide LTE link. Blocks until link is
 * successfully established.
 */
static void modem_configure(void)
{

	if (IS_ENABLED(CONFIG_LTE_AUTO_INIT_AND_CONNECT)) {
		/* Do nothing, modem is already turned on and connected. */
                printk("Already Attempted Auto-Connect");
	} else {
		int err;

		printk("Establishing LTE link (this may take some time) ...\n");
		err = lte_lc_init_and_connect();
		__ASSERT(err == 0, "LTE link could not be established.");
		
	}
}

void main(void)
{
	printk("The AT host sample started\n");
        modem_configure();
        printk("We're done");
}

  

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#
# General config
CONFIG_ASSERT=y

# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y

# BSD library
CONFIG_BSD_LIBRARY=y

# AT host library
CONFIG_AT_HOST_LIBRARY=y
CONFIG_UART_INTERRUPT_DRIVEN=y

# Stacks and heaps
CONFIG_MAIN_STACK_SIZE=3072
CONFIG_HEAP_MEM_POOL_SIZE=16384

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n

  • I was able to get a log file of what the serial terminal for the program is outputting while it tries to connect to the callbox, I've pasted it below in case that helps.  I can have the test lab send some AT commands over the interface too to try and get more information.  But it looks like it's searching for a connection and simply fails.

    *** Booting Zephyr OS build v2.1.99-ncs1-2954-g479376885055  ***
    The AT host sample started
    Establishing LTE link (this may take some time) ...
    +CEREG: 2,"0028","00000000",7,0,0,"11100000","11100000"
    +CSCON: 1
    +CSCON: 0
    +CSCON: 1
    +CSCON: 0
    +CSCON: 1
    +CSCON: 0
    +CSCON: 1
    +CSCON: 0
    +CSCON: 1

    Some additional information I got from the test lab:

    They said that they can see the device attempting to register on their callbox.  Their callbox sees the nRF9160 and begins the registration and after a little bit that fails.  Then, it seems to just continuously attempt to register, and then fail over and over. The UART log file I provided is the output from one those sessions of repeated attempts and failures.

    One thing they brought up, is the nRF9160 'locked' or prevented from using test sims after it's registered to a network?  Before sending the units out to the test lab, I tested them at home using an iBasis sim and it connected to the Verizon network.  The test lab suggested that possibly the device is locked out and unable to use test sims after first registering on a network.

  • One command you might try is AT+CFUN=12 to reset all the stored settings in the 9160. It may default some settings that are preventing it from connecting or settings that may have been stored when you used the iBasis SIM.

  • Hello,

    can you please provide a link monitor log where you run 'AT+CFUN=1' and 'AT+CFUN?' ? It would be nice to have some information about the modem settings for debugging purposes.

  • I was not able to get the Link Monitor to connect to my board.  So I loaded my firmware onto the nRF9160 dev board and used the same iBasis sim.  Below is the output.  At the end it connects to Verizon's network, band 13.

    AT+CFUN=1
    OK
    AT+CFUN?
    +CFUN: 1
    OK
    AT+CGSN=1
    +CGSN: "352656100223174"
    OK
    AT+CGMI
    Nordic Semiconductor ASA
    OK
    AT+CGMM
    nRF9160-SICA
    OK
    AT+CGMR
    mfw_nrf9160_1.1.1
    OK
    AT+CEMODE?
    +CEMODE: 2
    OK
    AT%XCBAND=?
    %XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)
    OK
    AT+CMEE?
    +CMEE: 1
    OK
    AT+CNEC?
    +CNEC: 24
    OK
    AT+CGEREP?
    +CGEREP: 1,0
    OK
    AT+CIND=1,1,1
    OK
    AT+CEREG=2
    OK
    AT+CEREG?
    +CEREG: 2,4,"FFFE","FFFFFFFF",7
    OK
    AT%CESQ=1
    OK
    AT+CESQ
    +CESQ: 99,99,255,255,255,255
    OK
    AT%XSIM=1
    OK
    AT%XSIM?
    %XSIM: 1
    OK
    AT+CPIN?
    +CPIN: READY
    OK
    AT+CPINR="SIM PIN"
    +CPINR: "SIM PIN",3
    OK
    AT+CIMI
    204080813519279
    OK
    %CESQ: 33,1,13,1
    +CEREG: 2,"A902","0980FE01",7
    +CSCON: 1
    +CNEC_EMM: 11
    +CSCON: 0
    %CESQ: 28,1,13,1
    %CESQ: 33,1,13,1
    +CEREG: 2,"D113","03319203",7
    +CSCON: 1
    %CESQ: 38,1,13,1
    %CESQ: 38,1,18,2
    +CGEV: ME PDN ACT 0,0
    +CNEC_ESM: 50,0
    +CEREG: 5,"D113","03319203",7
    AT+CGDCONT?
    +CIND: "service",1
    +CIND: "roam",1
    +CGDCONT: 0,"IP","ibasis.iot","10.160.208.228",0,0
    OK
    AT+COPS=3,2
    OK
    AT+CGACT?
    +CGACT: 0,1
    OK
    AT+COPS?
    +COPS: 0,2,"311480",7
    OK
    AT%XCBAND
    %XCBAND: 13
    OK
    AT+CGDCONT?
    +CGDCONT: 0,"IP","ibasis.iot","10.160.208.228",0,0
    OK
    AT+CGACT?
    +CGACT: 0,1
    OK
    +CSCON: 0
    %CESQ: 38,1,13,1
    
    

  • Thanks for the log. I have reported this internally, and I will contact you once I get a response.

Related