Unable to connect to nRF9160 with R&S CMW500

[David Palchak]

We are having difficult getting a R&S CWM500 to connect to our nRF9160-based device (operating in CAT-M1 mode). We are using a R&S test UICC. We have already attempted all of the settings changes documented in the following issues:

 when i connect NRF9160-DK to the CMW 500 for CAT-M test, the NFR9160 can register with CMW500, but the connect drop very quickly, 

 Using nRF9160 against R&S CMW500 (or CMW290) in signalling callbox mode 

 NRF9160 RRC Connection Re-established CMW500 

 Unable to connect to R&S CMW500 

Here are some screenshots of the CMW500 configuration that we have tried:

Finally, here is a copy of the full CMW-500 configuration that we tried:

CMW500 settings, Signaling failure, Boosty Device, 2022-10-27.zip

The devices we are testing are pre-production devices, which means that we do not have immediate access to any logging output at the moment. Additional connectors would have to be reworked on to the board to permit this, and the test facility (where the boards are) is located in a completely different region of the country.

Any guidance that you can provide on what setting(s) might need to be adjusted on either the nRF9160 or the CMW-500 would be tremendously helpful.

Cheers,
David

[Didrik Rokhaug]

Hi,

What application is running on the device?

How does the application behave if it doesn't have internet connectivity?

Have the test house tried the .dfl's attached to one of these guides?

 Using nRF9160 against R&S CMW500 (or CMW290) in signalling callbox mode 

https://devzone.nordicsemi.com/power/w/opp/4/user-guide-lte#h54skc3ia2mr1m1t0sg1piiyrk1cmx8n8

What is the RLC mode of the default bearer? (should be "Acknowledged")

Best regards,

Didrik

[David Palchak]

Hi Didrik,

The device is running a custom application. The correct operation of the application has been been confirmed with multiple independent eUICC and UICC devices from different carriers.

For you question on how the application behaves if it doesn't have internet connectivity, do you mean how does it behave if it cannot establish a radio link, or how does it behave it the default bearer does not provide Internet connectivity?

Upon boot the application attempts to initialize the modem and then attempt to connect to a network using the default profile on the eUICC. If a network connection is never established, the device simply suspends further initialization and ignores future attempts to perform network-dependent operations (such as retrieving the current time, sending data, etc).

The settings file (DFL) attached to the first link has been tried. We will try the settings file mentioned in the second link and report back.

Cheers,
David

[David Palchak]

The file that did not work was the one named "CMW500 settings for nRF9160, Nordic Semidconductor, DAU-NB1-M1" provided in this article:

devzone.nordicsemi.com/.../user-guide-lte

[David Palchak]

I'm having trouble including the link to the actual file. The DevZone website keeps popping up an error. Let's see if this works:

https://devzone.nordicsemi.com/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-01/DAU_2D00_NB1_2D00_M1.dfl

[Didrik Rokhaug]

That file should support both LTE-M and NB-IoT, giving the operator a choice between the two when the file is loaded into the callbox. So it could be that when the file was loaded, they selected NB-IoT rather than LTE-M. Another possibility is that the callbox is using a newer firmware version than the file was created for, causing some setting to not be set correctly.

[Iisko84]

We also had problems establishing a connection between the nRF9160 and the CMW500 Radio Communication Tester. However, we used the configuration zip archive "M1_configuration file for signalling.zip" recommended by this thread, after which the connection was established successfully.

We use a custom board with nRF9160 SIP. The nRF9160 is flashed with MFW version 1.3.3 and a modified AT-client sample. The AT-client sample has been modified so that the program feed the same AT command sequence that the LTE link monitor feed when the AT-client sample starts. This is because we don't want to connect a computer to the device during the RF-test.

The problem is, that during the RF test, the device is forcibly switched to transmission (TX) mode which messes up the test. My question is that, can the AT-client sample go to transmission mode (TX) during RF-test, even though it is commanded to RX mode? 

Best regards Iisko84

[Didrik Rokhaug]

Hi Iisko84 ,

Could you open a new ticket?

Also, if you could attach any logs, from either the nRF9160 or the CMW500, that would be very helpful.

Best regards,

Didrik

[Iisko84]

Hi,

Ok, I'll open a new ticket.

-Iisko84-