@Cher Hi, looking at your screenshot, I think there is a bug in the modem firmware. If you look at the logs on the right you can see: +CPIN: RE DY This means the sim card is detected and ready. However, one letter is missing. This is supposed to be +CPIN READY. So I think the serial tool is therefore failing to interpet the correct string. Can you query the CCID/IMSI? If it returns a number then the sim card is for sure working. You can also try updating the firmware

Hi, currently it is not possible to query the IMSI of a device via the API. BUT the IMSI is delivered along with the lifecycle event when the device registeres it self. In this case you get forwarded to your configured application url a payload like this. { "reports": [ { "serialNumber": "IMEI:123456789012345", "timestamp": 1623278710492, "subscriptionId": "63b07b01-4c14-4bba-8bc4-f3a89b3c94ff", "resourcePath": "uplinkMsg/0/data", "value": "500a060800101a181", "customAttributes": {} } ], "registrations": [ { "deviceType": "device", "serialNumber": "IMEI:123456789012345", "timestamp": 1623278710457, "make": "Generic", "model": "Sensor", "groupName": "TMNL.PROFESSIONAL.CON_0000001204", "imsi": "N/A", "protocol": "HTTP", "tags": "N/A", "subscriptionId": "cc48f3fa-7147-4b6d-9fe7-fe5b108e50dc", "deviceProps": { "device/0/imsi": "IMSI:123456789012346", "device/0/model": "Sensor", "uplinkMsg/0/data": "500a060800101a181", "device/0/manufacturer": "Generic", "connectivity/0/port": "62509", "connectivity/0/mncmcc": "", "location/0/longitude": "", "connectivity/0/cellid": "", "connectivity/0/ip": "10.0.5.183", "location/0/radius": "", "connectivity/0/rat": "", "location/0/latitude": "", "connectivity/0/apn": "" }, "customAttributes": {} } ], "deregistrations": [], "updates": [], "expirations": [], "responses": [] } You can see the IMEI in the IoT Creators portal because we did some implementation regarding this Hope this helps a bit. Regards, Roland

Yes, the SIM cards that we as IoT Creators send out are always activated when you get them delivered. And our SIM can connect to the 4G network using our publick APN: m2m.public.nl You can check our “roaming” page to read about operators and bands that you need for LTE-M at your location, please note that LTE-M is not necessarily available everywhere where you’ve got 4G coverage. If all this seems to be fine on your end and you still can’t connect please tell us the details where you got stuck. (AT commands and module logs)

Hi @MeneerJacco please send me your ICCID or IMSI in a private message via the forum chat tool and I’m going to look at your tariff. Thanks, Uta

Hi, I’ve checked and everything seems to be fine on our side. However, of course I cannot see if the SIM card itself got some physical damage. Did you try the other SIM cards that you have? Florian

For NB-IoT we have an UDP adapter. So with NB-IoT you’ll need to use APN cdp.iot.t-mobile.nl which will allow you to send device data to 172.27.131.100. To retrieve the device data in your back-end/cloud server/iot platform, you’ll need to create an HTTP integration. If you use the sim-card for LTE-M or 2G, you’ll need another APN: m2m.public.nl. By doing this, the device will get a public IP address just like any other device on the open internet. This means that you can send device data directly to your own server while using LTE-M or 2G. Hope this helps!

Good morning @afzal_m, is it possible this Sim requires 3v? This would explain weird behavior when the module provides only 1.8v

@Malte-Neumann Hi Malte, please send the 10 ICCIDs to support@iotcreators.com . I will check them . Please use as PLMN IDs from page https://docs.iotcreators.com/docs/telekom-iot-networks-in-europe Regards, Roland

Hi Petr, if I understood you right I see the following challenges: find a location with NB IoT coverage. attach your device to the NB-IoT network of T-Mobile Czech. send messages via UDP to Cloud of Things decode the payload of your UDP message and integrate it with Cloud of Things Please let us get directly in contact, that we can speak about it (roland.baldin@t-systems.com). Regards, Roland

@afzal_m Hallo Afzal. Ik weet niet zo snel hoe ik een DM naar jou toe moet sturen. Maar heb het nummer van de SIM in een Chat met jou doorgegeven. En natuurlijk zal ik doorgeven wat het resultaat is van de test

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

Strange! I’ve just sent you an e-mail.

I received this question a lot these days. I still need to understand why. Is our document library (getting) too complex maybe? Please let me know However, if you ordered your NB-IoT simcard at iot.t-mobile.nl, I can assure you that your simcard is already active. We want to save you from the simcard hassle as much as possible. All our NB-IoT simcards have the same configuration. To make sure that you can simply keep one single stock for all your different use cases/projects, Just register the IMEI number of your module in one of your projects. Configure your module with the right settings, put your simcard in it and it should work right away.

Hi Tibor, Did you succeed to connect? I want to use the Boron to.

Ah that’s a shame Good luck with finding solution.

Okay, my problem is fixed. I flashed the sequans modem again and I tested my code again. But it was still not working. I wiggled the cable of the antenna a bit and it connected to the network! I think the antenna of my gpy wasn’t connected properly or the antenna cable is broken or something.

Hi @white apologies I did not see your post earlier. But according to my colleague you already received your card right? I will also send you an e-mail.

Hoi @derko-drukker , Via de mail reeds op de hoogte gesteld. We hebben tijdelijk geen voorraad van dit specifieke type sim kaart (Industrial 3FF) er wordt gewerkt aan het aanvullen van de voorraad en dan gaan we alsnog de leveringen afronden.

Problem solved. It denpends on the sim card

May I suggest you also take a look at our central FAQ page for NB-IoT Roaming?

The NB-IoT service offering has started in all countries with pure NB-IoT SIM cards. In Germany, Austria and the Netherlands Multimode SIM option (NB-IoT, LTE-M, 2G and 3G) is supported.

Deutsche Telekom supports all current SIM formats, including the embedded SIM Form Factor (MFF). eSIM as of eUICC currently does not fit with the NB-IoT business model due to high costs. Instead, a more suitable option for NB-IoT use-cases is nuSIM, which is currently in launch preparation. Find out more about nuSIM.

Yes, NB-IoT always comes with a SIM card, as it features LTE-like security, which is based on standardization and specifications of 3GPP. A standardized SIM profile also allows international usage of NB-IoT on the networks of foreign mobile network operators as soon as roaming is agreed and deployed. NB-IoT is always SIM-based, but different form factors will be offered.