Posts made by afzal_m

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!

You can only send traffic to our server and we can help you with the HTTP integration to your environment.

2G and LTE-M are accessible. Pls use APN m2m.public.nl and you’ll get a public IP address. By doing this, you can send data to any destination.

You can only add users which are already known in our member-db. Apologies for that.

So after Jaap has created his account at https://porta.iotcreators.com, Pieter should be able to add Jaap as project-member

This is due to agentlifecycle queue being processed too slow, so the lifecycle event (registration) is sent with a delay.

We already prepared a fix for this. Next week we are going to test the fix on our staging environment!

Thanks, just saw it!
Just to be sure: so it’s not only about this gap of 30 or 40 minutes, right? Sometimes these payloads are from 2/3 weeks ago. Is my understanding correct?

@Cees-Meijer

could you please send me an example of such a message and the timestamp that you received this message?

You can send it via PM of via email

Changing the url is not possible afaik. You can only overwrite the URL.

You can set-up the first URL and overwrite the first URL by using the GUI and you can set-up the second URL and overwrite the second URL via the APO.

I’m not sure if you check the value what has been set via the API before.

I’ll ask @Roalnd-Baldin tomorrow

Activated yesterday and finetuning at the moment.

Will update you next week again!

To be continued. Already needed a link to make a QR code for the flyer with instructions

@Sergey-Vladimirov said in How to get your nuSIM dev-kit online?:

@afzal_m trust me Ive been pushing for it since I discovered that simcom had it last year but our choice of supplier for modules goes to Quectel so far.

Then I have some great news. Currently you’re testing with a BC-95… but the BG-95 also supports nuSIM as of now.

@rogierlodewijks

For non-ip we have to change some settings on your sim profile and CoAP is already possible. However, you’ll need to use the Neul Messaging flavour of CoAP which is supported by both our network and your Quectel BC-95.

And yes, our Service Capability Server (or CDP) also supports buffering capabilities for bulk transfers.

@Sergey-Vladimirov said in How to get your nuSIM dev-kit online?:

now just hope you spread it onto the whole line of modules

Yeah! Telit is coming soon with their nuSIM module. Others are working on it as well. But it will also help if you also push your module supplier a little bit.

Ah sorry! I had this problem as well the last Monday but I forgot to change the post. Will change it now.

Thanks a lot @Sergey-Vladimirov!!

So please tell me, how does it feel to connect a device to a mobile network without a physical sim-card?

Can you please test it again?

Ok,

before giving you a fuzzy and complex explanation, can you please try

• to remove the device
• register it again, but this time by using the API
• and then send your downlink message

Did you register the device via the GUI or did you use the API?

Can you please check again? We fixed a few things

No luck so far, today I will handover my devkit to our devkit-master @Eric-Barten. I am very sure that he well find the solution.

Sorry, I missed this post.

Showing the payload in our GUI is not a problem for new devices.

What you need to do is the following:

APN cdp.iot.t-mobile.nl
Send your payload to: 172.27.131.100

Not yet, sorry.

Super frustrating… I know that we just need to do some minor changes in both AT commands. But I can’t remember what exactly.

Hence, I want to try it out myself again. However, I have problems connecting the devkit to my computer. Will try a macbook now…

Will get back to you tomorrow again.

Hi Roman,

Yes, this has something to do with a problem that we had on Satuday October 23rd.

The good thing is: the problem only affects in the ‘last payload’ functionality in our GUI. If you connect your own application/paltform to our API, you should be able to receive all your device data.

I will post another update tomorrow.

Hmm ok but the error “invalid URL” is gone right?

@rogierlodewijks thanks for the heads up

I will come back with the correct commands tomorrow