Unable to connect to nRF9160 with R&S CMW500

RE: Unable to connect to nRF9160 with R&S CMW500

Iisko84 — Tue, 29 Nov 2022 15:44:37 GMT

Hi,

Ok, I'll open a new ticket.

-Iisko84-

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Tue, 29 Nov 2022 13:27:37 GMT

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

RE: Unable to connect to nRF9160 with R&S CMW500

Iisko84 — Sat, 26 Nov 2022 10:47:22 GMT

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

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Thu, 10 Nov 2022 10:00:32 GMT

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.

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Wed, 09 Nov 2022 17:38:17 GMT

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

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Wed, 09 Nov 2022 17:36:56 GMT

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

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Wed, 09 Nov 2022 17:35:35 GMT

[deleted]

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Tue, 08 Nov 2022 12:24:36 GMT

Assuming "RSRP RSRQ meas.zip" is the other config file, that failed, this is what I am told is the difference:

"RSRP RSRQ meas.zip" shows own cell Cat-M measurements in the CMW500 GUI by reporting RSRP and RSRQ using measurement reports for half-duplex device like nRF9160.

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Mon, 07 Nov 2022 23:41:47 GMT

The settings file that worked is the one from the zip archive "M1_configuration file for signalling.zip" that was attached to this article:

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

Both of the files that we tried are purported to be for LTE-M signaling, so it seems unlikely that it was a LTE-M vs -NBIoT thing.

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Fri, 04 Nov 2022 14:50:21 GMT

That's great to hear.

[quote user="dpalchak-google"]However, it's interesting that there is a difference between the two. I don't know what that difference is, but it's worth figuring out so that others don't keep getting tripped up by this same problem.[/quote]

Just so we are clear, which file did they use that worked (and which files did they try that did not work)?

Between the two blog posts I linked, there are 4 configuration files.

Anyway, my guess would be that one of the files are configured for LTE-M, and the other for NB-IoT, while your application only supports LTE-M.

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Mon, 31 Oct 2022 23:54:41 GMT

We tried both settings files, and one of them worked and one of them did not. We will proceed with the settings file that worked. However, it's interesting that there is a difference between the two. I don't know what that difference is, but it's worth figuring out so that others don't keep getting tripped up by this same problem. There seem to be a lot of dev zone posts about this exact same issue....

Cheers,
David

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Mon, 31 Oct 2022 15:55:51 GMT

[quote user="dpalchak-google"]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?[/quote]

I was thinking about lack of internet connectivity. We have seen cases where the test houses have been using e.g. the asset_tracker_v2 as the application, while they want to test the LTE stack.

However, because the asset_tracker_v2 will turn off LTE if it is not able to connect to the server, they were not able to do their tests.

[quote user="dpalchak-google"]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.[/quote]

Please let me know if it works or not.

RE: Unable to connect to nRF9160 with R&S CMW500

David Palchak — Fri, 28 Oct 2022 19:40:07 GMT

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

RE: Unable to connect to nRF9160 with R&S CMW500

Didrik Rokhaug — Fri, 28 Oct 2022 15:01:45 GMT

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