Connect to nRF cloud using eSIM.

[Stas Jis]

We are using nRF9160 chip (in own custom board), SDK 1.9.1 board with "serial lte modem" firmware.
We are unable to get coordinates using AGPS.
I suppose this is due to the fact that the eSIM needs to be somehow registered on the nRF Cloud.
We used the sequence of commands from the "GNSS_AT_commands" example:

  AT%XSYSTEMMODE=1,0,1,0

  OK
  AT%XCOEX0=1,1,1565,1586

  OK
  AT+CPSMS=1

  OK
  AT+CFUN=1

  OK
  AT#XNRFCLOUD=1

  OK

  AT#XAGPS=1,1
  ERROR
  
  AT#XNRFCLOUD?
  #XNRFCLOUD: 0,0,16842753,"nrf-350916060695718" 

But there is no connection to the nRF cloud. eSIM is already used to upload / unload  data via MQTT using AT commands, so the SIM card is working.

[Øyvind]

Hello, 

I suppose this is due to the fact that the eSIM needs to be somehow registered on the nRF Cloud.

No, there is no need to have the eSIM registered other than to keep track of amount of data in SIM.

But there is no connection to the nRF cloud.

Does your device connect to nRF Cloud using e.g. Asset Tracker v2? Have you updated your certificates and registered the device in nRF Cloud?

Just our of curiosity, would it not be better to clarify the cause of issue in ticket #286860 first before registering a new?

Kind regards,
Øyvind

[Stas Jis]

 - Have you updated your certificates and registered the device in nRF Cloud?

What certificates are we talking about? No, we didn't separately register the device on the nRF cloud. 
Is it necessary for correct operation?

- Just our of curiosity, would it not be better to clarify the cause of issue in ticket #286860 first before registering a new?

The cases seemed different to me (a SIM card that used to work and stopped, and the use of eSIM).
Actually, we need to compare the GPS data with the evaluation board and ours custom board. 

[Øyvind]

Hello,

Stas Jis said:

What certificates are we talking about? No, we didn't separately register the device on the nRF cloud. 
Is it necessary for correct operation?

In order to use nRF Cloud A-GPS  you will need to ensure that your nRF Cloud certificates are correct, and that the device is registered to nRF Cloud. Please see nRF Cloud A-GPS documentation

As stated in the Serial LTE Modem application documentation: 

The #XAGPS command runs the GNSS together with the nRF Cloud A-GPS service. This requires access to nRF Cloud through the LTE network for receiving A-GPS data.

In regards to the certificates, this is described in our chapter on Connection in the nRF Cloud documentation.

Let me know how that works for you. 

Kind regards,
Øyvind

[Stas Jis]

Øyvind:
One more question, where / how can I get the PIN/HWID of my custom board? Can it be any user password?
I can't register it in the cloud in any way.

[Stas Jis]

Or should the Security tag value defined when generating certificates be used instead of PIN?

[Øyvind]

Stas Jis, the nrf-<IMEI> device ID should only be used with Nordic HW. For you custom board you can choose a Device ID that fits your application along with a PIN/HWID of your choice. 

Note that the default <sec_tag> for nRF Cloud credentials is 16842753, which you set when using LTE Link Monitor's Certificate Manager. More information on this under modem key management.