Http_test not working with NBIoT

Hey,

I tried the http_test example from the Sodaq_R4X library on a Sodaq Sara R412 AFF. When setting the connection RAT to 2G the example works like expected. When setting RAT to NBIoT there is an error when the +UHTTPC command is sent. Sending data via TCP/UDP socket is working fine when connected via NBIoT. Anyone else experiencing this behaviour?

I also posted a question here:
https://portal.u-blox.com/s/question/0D52p00008ntkadCAA/sarar412m02b-uhttpc-command-fail-when-connected-via-nbiot

Hi @thomas,

Can you check if your R412M module has the latest firmware?
https://support.sodaq.com/Boards/Sara_AFF/#r4

Best regards,
Jan

Hi,

yes, I updated two days ago to M0.10.00,A.02.14.

Hi @thomas,

I have tested the today the http_get on the AFF R412M with the latest firmware.
For me it works fine.

Maybe you need to whitelist the IP before you can reach it on NB-IoT?
Do you have a battery attached? (I think yes, since 2G works)

Best regards,
Jan

Hi @Jan,

the module has the same IP address no matter if connected via 2G or NBIoT. So I think its not a problem with the modules IP-address. The battery is connected. I think the next thing I will try is to send the HTTP POST to the servers IP-Address and not to its URL. Maybe it is a DNS resolving problem.

Best regards
Thomas

1 Like

Hi @Jan,

it really seems to be a DNS issue as the DNS servers are not set when connected via NB-IoT

2G:

AT+CGCONTRDP=1
+CGCONTRDP: 1,5,iot.1nce.net,foo.foo.foo.foo, ,8.8.8.8,8.8.4.4
OK

NB-IoT:

AT+CGCONTRDP=1
+CGCONTRDP: 1,5,iot.1nce.net,foo.foo.foo.foo, , ,
OK

Any idea how to set the DNS IP manually?

Best regards
Thomas

Hi @thomas,

Have you managed to find a solution for this?

I was going to suggest that you try doing a manual DNS resolve with AT+UDSRN?
This was in case there was just an issue with the AT+CGCONTRDP output with NB1.

However, I have see that you made a post with uBlox that this was related to MNO profile 100.
Could you share what you learned about this issue here?

Thanks,

Hi @GabrielNotman,

it seems AT+CGCONTRDP output is set correctly.

  • When the DNS servers are shown in AT+CGCONTRDP (connected to 1NCE via 2G with at+umnoprof=100), the manual resolve with AT+UDSRN and http-commands are working as expected.
  • When the DNS servers are not shown in AT+CGCONTRDP (connected to 1NCE via NB-IoT with at+umnoprof=100), none of the above is working.

However, when I set the ublox module to at+umnoprof=0, it can connect to 1NCE via NB-IoT and the DNS-servers are set correctly and everything is working as expected. So it seems my operator 1NCE is sending DNS-Server adresses when the module attaches to the network. Unfortunately the R412M manual says I am not supposed to use at+umnoprof=0 and some commands like manual RAT selection (AT+URAT) are not available with this profile.

The case is still open and I got no response from ublox so far.

Regards
Thomas

Hi @thomas

Have you tried +UMNOPROF=1? That profile should be based on the SIM card in use.
We have however, seen issues with some MVNO SIM cards, so it might not work with 1NCE.

Kind regards,

Hi @GabrielNotman,

the command at+umnoprof=1 has no effect and after reboot at+umnoprof? still returns the previous value. Maybe there is no profile info available on my 1NCE sim card.

Regards
Thomas

Hi @Jan, hi @GabrielNotman,

it took some time, but now I have a solution for my problem. As my module support told me, in my special case there is an issue with the profile I am using while attaching to the 1NCE NB-IoT network. Ublox provided a special MNO profile based on profile 100 and now everything is working fine.
I will not share the profile since it is all confidential, but maybe for others first-level support will be faster when pointing out something like this exists.

Regards
Thomas

@thomas,

Thanks for sharing your solution. This will help if other people have issues with 1NCE.

Best regards,
Jan