I fail to connect an nRF9160DK (and thingy) to the Telenet network.
I know that telenet does not support LTE-M everywhere, NB-IOT is the general supported network.
This requires the network mode to be altered in the KConfig files.
The board/modem identifies the Telenet network as being available, but does not establishes a connection.
The Proximus network is directly recognised and connected to.
Hi,
Can you capture a Modem Trace and upload it here as a .binary file using Insert -> Image/video/file?
Also include modem firmware version.
Regards,
Sigurd Hellesvik
trace-2023-03-07T09-10-44.049Z.bin
Modem firmware 1.3.4
I asked around a bit, and found that Telenet has a bit older NBIoT system, and you therefore have to set the APN name manually.
Our Asset Tracker v2 shows how this can be done. Here are some configurations that I know have been used before with the Asset Tracker to connect to Telenet:
CONFIG_PDN=y
CONFIG_PDN_SYS_INIT=y
CONFIG_PDN_DEFAULTS_OVERRIDE=y
CONFIG_PDN_DEFAULT_APN="iot.telenet.be"
You should also send a AT command from your application before starting the connection: at_cmd_write("AT%XEPCO=0", NULL, 0, NULL);
Did this help?
Regards,
Sigurd Hellesvik
Sigurd,
I can confirm that the PND indeed requires to be configured.
These two settings did it for me:
And making sure the modem uses NB-IOT.
I got it working now.
The main reason for my issues is VS code, and how KConfig is handled.
Somehow VS Code resets settings you make in the KConfig menu at build.
So each time something in the code changed, the system reverted back to the standard where NB-IOT is not used, only LTE. Telenet deployed NB-IOT nationwide, not LTE.
I have it working using the new MQTT application, on a recent board.
As time allows I will go through the functionality of other applications and older boards
Any advice how we can create a new setting set, overriding the standards, that is kept over a pristine build?
Sigurd,
I can confirm that the PND indeed requires to be configured.
These two settings did it for me:
And making sure the modem uses NB-IOT.
I got it working now.
The main reason for my issues is VS code, and how KConfig is handled.
Somehow VS Code resets settings you make in the KConfig menu at build.
So each time something in the code changed, the system reverted back to the standard where NB-IOT is not used, only LTE. Telenet deployed NB-IOT nationwide, not LTE.
I have it working using the new MQTT application, on a recent board.
As time allows I will go through the functionality of other applications and older boards
Any advice how we can create a new setting set, overriding the standards, that is kept over a pristine build?
Good job fixing this!
Gwen Stouthuysen said:Any advice how we can create a new setting set, overriding the standards, that is kept over a pristine build?
I suggest putting your configurations into prj.conf, or using a configuration overlay. For the latter, see OVERLAY_CONFIG and this sample for some examples of how that can look.
Regards,
Sigurd Hellesvik
For clarification: any setting we make in KConfig can be specified in the prj.conf file and is thus overruling any setting that comes from the original project.
That is a good advice.
You will find a lot non formal computer science trained developers in the audience, persons who rolled in due they needed it in their main profession.
Gwen Stouthuysen said:For clarification: any setting we make in KConfig can be specified in the prj.conf file and is thus overruling any setting that comes from the original project.
Good that you ask. I would answer "kinda no".
Our nRF Connect SDK are not really for building on top of other projects.
Try to think of our examples as "code that you copy and then edit to make your own project".
If you look at it this way, putting the configurations into prj.conf will change the project that you use.
Did that make sense?
Gwen Stouthuysen said:You will find a lot non formal computer science trained developers in the audience, persons who rolled in due they needed it in their main profession.
We have a really good guide to get started at academy.nordicsemi.com/
Regards,
Sigurd Hellesvik
Sigurd,
I indeed try to copy an existing project and adapt it to do what I want it to do.
Frustrating part is that somehow these links remain and settings get reset to the original at build time.
potentially the start requires to be different
I will go through the suggested DevAcademy.
Regards,
Gwen
Gwen Stouthuysen said:Frustrating part is that somehow these links remain and settings get reset to the original at build time.
If you use the "Create application from existing" to create a new project, I believe that this should not be an issue.
Gwen Stouthuysen said:I will go through the suggested DevAcademy.
Nice!
Regards,
Sigurd Hellesvik
