Posts made by Daan2021
-
What are the roaming partners (PLMN ID & band) for IoT Easy Connect in Italy?
Hello,
I am currently using a NB IoT Easy Connect SIM card from T Mobile NL, see link.
In the Netherlands this has been working fine, however now I am in Italy (sicily to be precise) and I canât seem to connect to the internet.
Maybe I have the wrong roaming partner (PLMN ID & band) selected? I encountered the following resources on the internet to find out more about that:
-
This seems to be the official coverage map for T Mobile for roaming partners in the EU. However it is incomplete, because it only shows coverage for NL.
-
This is an overview from IoT creators showing roaming partners for Italy, but I am thinking that might not be applicable for my Easy Connect SIM card because the webpage says itâs for Global SIM 90140 (even though IoT creators is part of Deutsche Telekom).
So my question is: is the IoT creators overview applicable for my Easy Connect SIM card? Or is there another overview somewhere that I should be using and not aware of?
Any help is much appreciated!
-
-
RE: Olimex BC66 - Registration Denied
Hi @uta, thanks for the tip. Youâre right, I was using the wrong APN for the type of SIM I have. I have an easy connect SIM, and for that the APN should be just âiot.t-mobile.nlâ it turns out (without the CDP bit). Now the UE attaches & registers to the network perfectly fine
-
Olimex BC66 - Registration Denied
Hello,
I am using a brand new T Mobile SIM card with a Olimex BC66 development board. When performing the AT+CEREG? command, I get a response that registration is denied. Does anyone have any idea what could be wrong here?[2022-01-17_11:12:30:921]RRRRRĂł [2022-01-17_11:12:31:151]+CPIN: READY [2022-01-17_11:12:36:934]ATE1 [2022-01-17_11:12:36:934]OK [2022-01-17_11:12:42:067]ATi [2022-01-17_11:12:42:067]Quectel_Ltd [2022-01-17_11:12:42:067]Quectel_BC66 [2022-01-17_11:12:42:067]Revision: BC66NBR01A10 [2022-01-17_11:12:42:067]OK [2022-01-17_11:12:44:468]AT+CMEE=1 [2022-01-17_11:12:44:468]OK [2022-01-17_11:12:47:104]AT+QSCLK=0 [2022-01-17_11:12:47:104]OK [2022-01-17_11:12:48:146]AT+CIMI [2022-01-17_11:12:48:146]901405340011497 [2022-01-17_11:12:48:146]OK [2022-01-17_11:12:49:851]AT+CGMI [2022-01-17_11:12:49:851]Quectel_Ltd [2022-01-17_11:12:49:851]Quectel_BC66 [2022-01-17_11:12:49:851]Revision: MTK_2625 [2022-01-17_11:12:49:851]OK [2022-01-17_11:12:51:100]AT+CGSN=1 [2022-01-17_11:12:51:100]+CGSN: 867997032558396 [2022-01-17_11:12:51:100]OK [2022-01-17_11:12:54:120]AT+QBAND=1,8 [2022-01-17_11:12:54:120]OK [2022-01-17_11:12:59:705]AT+QCGDEFCONT="IP","cdp.iot.t-mobile.nl" [2022-01-17_11:12:59:705]OK [2022-01-17_11:13:01:609]AT+COPS=1,2,"20416" [2022-01-17_11:13:21:335]AT+QRST=1 [2022-01-17_11:13:21:335]+CME ERĂșRRRRRRĂłAT+QSCLK=0 [2022-01-17_11:13:27:374]OK [2022-01-17_11:13:33:054]AT+CPSMS=0 [2022-01-17_11:13:33:054]OK [2022-01-17_11:13:35:686]AT+CEREG=5 [2022-01-17_11:13:35:686]OK [2022-01-17_11:13:40:757]AT+CEREG? [2022-01-17_11:13:40:757]+CEREG: 5,3,,,,,0,19 [2022-01-17_11:13:40:757]OK [2022-01-17_11:13:49:079]AT+CSQ [2022-01-17_11:13:49:079]+CSQ: 11,0 [2022-01-17_11:13:49:079]OK [2022-01-17_11:13:52:730]AT+CGATT=1 [2022-01-17_11:13:52:730]ERROR [2022-01-17_11:13:56:912]AT+CGATT? [2022-01-17_11:13:56:912]+CGATT: 0 [2022-01-17_11:13:56:912]OK [2022-01-17_11:14:24:866]AT+CSCON? [2022-01-17_11:14:24:866]+CSCON: 0,0 [2022-01-17_11:14:24:866]OK
-
RE: RRC inactivity timer duration for NB-IoT and LTE-M
@david-micallef said in RRC inactivity timer duration for NB-IoT and LTE-M:
On the Sara N3 there is a special command NSOSTF (https://www.u-blox.com/sites/default/files/SARA-N2-Application-Development_AppNote_%28UBX-16017368%29.pdf) but could not find any other module that supports this type of command.
@Stefan-de-Lange ,@David-Micallef Quectel BC95-G also has the NSOSTF command, see AT commands manual. And Iâm assuming that their other modules (some of which are NB + LTE-M) will have that command too.