No new platform Maarten. I was just not fast enough with sending out the email about the completion of the network change.

The short notice is something that shouldn’t happen again. The time window of these kind of changes is something that we’ve to look in.

Thx for bearing with us!

hi @Yentl1193, can you please write to support@iotcreators.com specifying your sim card iccid and imei? Thank you!

Best Regards
Marco

Problem solved: iotcreators fixed the sim card registration and all works now.

Hi,

the first version of documentation for SIMCom SIM7022 how to

attach the device to Telekom NB-IoT network of IoT Creators and get assigned an IP address. Send “Hello World” uplink message via UDP from device to IoT Creators UDP server. Send “Hello Device” downlink message via UDP from IoT Creators portal to device. Receive “Hello Device” downlink message on device via UDP from IoT Creators UDP server.

is available now in IoT Creators documentation library.

https://docs.iotcreators.com/docs/simcom-sim7022

Would be great if you check it and give me some feedback for improvements and corrections.

Regards, Roland

👍 Thanks

@HaraldNaumann maybe you’ve got some advice?

Btw: our goal is also to minimize signaling storms from inefficient IoT devices not supporting the TS.34 Radio Policy Manager (RPM) feature. What’s your experience with TS.34 RPM so far?

I see successful connections in our backend and will send you details by email.

Before activating radio module Set APN with AT+QCGDEFCONT rather than **AT+CGDCONT Set frequency band explicity with AT+QBAND Configure first APN, fequency band and mobile operator ID before switching on automatic attachment

Hi Frank,

WUS and other 3GPP Release 15 features aren’t yet supported in the DT networks and to our knoweldge in most other Operator networks.
Our focus is right now on completing the roll-out of key features like eDRX, while in parallel planning the introduction of new Rel. 14 features like New Category NB2.
WUS and other important Rel. 15 features are of course already on our Roadmap, unfortunately we cannot give you a concrete date when those will be deployed in the our networks yet.
Can’t eDRX to a certain extent address your power saving requirements for the time being?

Best regards,

Ronan

@Roalnd-Baldin

The 2 hours is probably related to the 3GPP TAU timer, if it expires the device is implicitly released from the network I believe. Which is bad if you have a device that wants to sleep for more than 2 hours. So usually you set this value to whatever is the greatest the network accepts. You can run AT+CEREG=5, AT+CEREG? and check the returned values. It will tell you the timers that are used.

@Lauwie007
I have not tested it myself, but I guess your live test has just proven it, hasn’t it? 😊
Keep in mind that this time is provided by the local network in which you are actually roaming, so if you’re roaming in say, the Vodafone UK network, this time and associated timezone will be provided by Vodafone UK (if supported as just discussed).
Kind regards, Ronan

Hi,

I did “normal” TCP/IP MQTT on top of NB-IoT connection with the Quectel BC66. So TCP/IP is possible. But I didn’t try to post a normal HTTP request.

LWM2M is implemented on top of CoAP and UDP. By this it works perfectly on NB-IoT. It is also supported by Quectel BC66. We tested it successfully with Eclipse Leshan server and the Nokia Impact LWM2M server.

Regards, Roland

Hi Thomas,

Yes, SMS is supported over our LTE-M network.

We will soon provide an detailed overview of the supported features and capabilities, please stay tuned!

Best,
Ronan

Hello @Ahmed-Elhaddad,

We do these tests in parallel to normal network maintenance and improvement measures and we can share some preliminary results in CE-0 conditions from measurements in our Labs.

• Up to 200 devices can attach successfully simultaneously within 10 minutes under the condition that they do not immediately send data after a successful attach.
• Average round trip time (RTT) increases with increasing number of parallel transmitting devices. A randomization of transmission attempts leads to reduction of RTT and potentially improvement of battery lifetime
• With regards to the initial attach, only a small number of devices should be activated simultaneously (max. 60 devices)
• With regards to the regular data transmission with good signal level the following was observed:
• Failure rates increase with more than 160 devices trying to send 100 byte of data within one second
• Introducing a randomization timer of at least 40 seconds solves this limitation
• Avoiding synchronized data transmission results in better share of coverage levels across all devices
• Implication - Customers should avoid synchronized attaches and data-transmission of their devices

Best,
Dominik

@afzal_m Proprietary sucks 😞 I hope more open protocols are added, UDP is pretty limiting

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

@trick2011 I use the following sequence:

AT+UDCONF=1,0

AT+USOCR=17,7000
<rx socket number>
AT+USOCO=<socket>,“172.127.131.100”,<udp port>
AT+USOWR=<socket>,<data length>

<wait for @>
<send user data>
AT+USORF=<socket>,127 #127 is max rx length, depends on yr buffers

+USORF: <socket>,“172.27.131.100”,15683,17,“downstream data”

AT+USOCL=<socket> # close socket

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.

Currently, data packet buffering works only in combination with PSM, in the nearest future it should also work with eDRX. So once you activated this feature on your module, packets will be buffered automatically.

@Dylan-Frings said in Connection to Azure IoT Hub:

Hi,

I’m trying to connect an Arduino MKRNB1500 to MS Azure IoT Hub but I constantly get the error -2 (Connection refused) on both port 443 and 8883. If I try to run the exact same script with a different SIM and carrier everything works perfectly.
My company uses T-Mobile SIMs and with those SIMs I can’t establish a connection to the IoT Hub.
Is T-Mobile blocking any ports on the mobile network in the NL or is there another fix for this problem?

Thanks a lot!

You can’t access any server on the internet directly, this is why it’s not working. The CDP is always in between and acts as a proxy. You can register a URL as an endpoint and the CDP will forward any trafic it receives from your device to your registered endpoint

Unfortunately there is no interactive map for the coverage of NB-IoT in Poland.
However, T-Mobile Poland has published a press release in which they announced the nationwide coverage (coverage of 94%).

They also published a map where you can get an overview of the coverage in different regions:

alt text

Problem solved. It denpends on the sim card