Hey Ali,
Although Helium was available in the dropdown of protocols, it doesn’t work in this type of project. Sorry for that.
However, if you go to your project page you’ll see that I have added a new project to your account. In this new project you should be able to add Helium devices succesfully. 
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!
@magnatron thanks for the feedback. As already discussed today, we do realize that this was too short notice. We, therefore, postponed the maintenance to Mon Dec 19th 10:00 - 12:00.
@Reinier-Hasper are you very sure you are using the APN m2m.public.nl?
If I look at your IP address it really looks like you are using one of the other APNs.
Hey all,
I am trying to connect a Quectel BG96. Every time after configuring
AT+COPS=1,2,"20416",9
It says
CME Error: 13
Also a simple command to retrieve the IMSI AT+CIMI gives an error then.
When I reset the modem and use AT+CIMI again, it works and returns the IMSI. However, after trying to configure the COPS again, the error comes back…
Any ideas?
Should be fixed now!
Sorry for the inconvenience. I think you’re trying to use a license which was expired months ago.
I’m double checking it with my colleague and will get back to you tomorrow again.
when using APN cdp.iot.t-mobile.nl you can indeed only access our servers via 172.27.131.100. We have different servers available: MQTT, UDP, CoAP, LWM2M and NON-IP.
By using on of our services you will be able to get your device data in your preferred platform via webhook (http/callback).
when using APN m2m.public.nl you can send data to any IP destination on the public internet.
Hey Tibor,
Shoudn’t you also execute AT commands to configure the band and the PLMN id?
By using eDRX the device is able to receive downlink messages without sending uplinks.
Let me know if this helps:
https://docs.iotcreators.com/reference/send-base64-edrx-downlink-message
Copy / paste what one of my colleagues wrote:
I must admit I am not sure regarding the polarization used on our cell sites, an article stating that most operators use +/- 45° is probably correct. I’ll try to find out and let you know.
That said, knowing the base station antenna’s polarization is not as important as it might appear at first glance. In fact, it only matters in cases where a direct, uninterrupted, line-of-sight exists between the base station antenna and the UE antenna. In most practical cases, the signal the UE sees (and what the base station sees in the uplink case) is a mixture of signals that have been reflected off of and scattered by all kinds of objects (mountains, buildings, trees, vehicles etc.) in and around the line-of-sight. This is called “multipath”.
In a multipath environment, there is no way to predict the polarization of the signal at the receiving antenna, even if the polarization of the transmitting antenna is well known.
This is why the more complex variants of LTE (CAT.1 and above) require at least two antennas, which are typically set up to be sensitive to signals with different polarization.
I have no clue what this means.
But I got this question from a customer and I thought it makes sense to try to get the answer here.
I just reached out to @Roalnd-Baldin, he will post something on Monday
I am running out of ideas then 
Do you have access to the support teams of Simcom maybe?
Could it be that this is just a message from the Qualcomm chipset which is displayed every time when the module enters PSM?
It doesn’t really mean that the device has closed the context.
One of my colleagues has observed the same behavior on the BG96 which relies on the same chipset and always displays a similar message when it enters PSM.
One of my colleagues did a test with the same device. He confirmed that this issue was not observed during our testing. Tests in our lab were performed with an evaluation board, which had a little momentary switch connected to the pwrkey pin on the module. When the device was sent to PSM and then the button was pressed, the device woke up and was able to connect to the cell just by raising an RRC connection, the attach and PDN connection were always maintained.
My colleague wonders if the issue has something to do with the fact that you have sent the device to slow clock mode (at+csclk=1) before sending it to PSM…
I’ve reached out to some colleagues who might have an answer on this one. Will keep you posted.
Sorry for the inconvenience
Hope it works now
The sim that you already registered had an old profile. Therefore it was not able to connect to APN m2m.public.nl. I have changed the profile, as of tomorrow it should work.
The batch of 10 simcards that you have sent me do have the new profile already. And as promised, I have added them to your account, so now you will be able to register them.
Hope this works!
@cees-meijer that is probably because our backend doesnt know that these simcards belong to you… (our fault, sorry for that).
I can fix that for you if you send me the simcardnumbers (just the last 6 digits of each or the first and last one of the batch).
You can send me a pm here or email me directly
@MeneerJacco any news? Did you reach out to Simcom?
“Might be a different default setting for the UART slow clock control.”
