Posts made by felixdonkers

@techniek Have a look at: http://simcomm2m.com/En/module/detail.aspx?id=168 It says (4G) Cat-M1, (4G) NB-IoT, (2.5G) Edge and (2G) GSM/GPRS.

Interessante info. Is er al iets meer bekend over de NB-IoT energy calculator die in dit artikel genoemd wordt?

Solved.

I implemented my own proxy that accepts the data from the T-Mobile CDP server, extracts the relevant data and forwards it to ATT using the appropriate credentials. Most relevant lessons learned are:

• The CDP server sends a JSON structure with lots of (valuable) data, not just the raw data that the NB-IOT device sends to the cell.

• ATT has a nice REST API that allows to send the raw data to a ATT device. The ABCL language can be used to convert the raw data back to individual sensor data. Essential is that credentials have to be included in the HTTP PUT message, in this case a bearer token.

I would like to forward the data from my SODAQ NB-IOT shield to the AllThingsTalk cloud. Is there a manual available that describes how to do that? (I know SODAQ could do that for me, but I would like to be in control myself).

Hi @waltert, I just implemented this and it indeed works as you describe. Thanks!

p.s. I prefer the “AT+NNMI=0” plus "AT+NMGS=11,“48454c4c4f2046454c4958"” plus “AT+NMGR” because it gives clear separation of AT commands and received data. With “AT+NNMI=1” I run the risk that things get cluttered…

Today I (finally) received my PyCom FiPy device. Anyone already experience with that device on the T-Mobile NB-IoT network?

Indeed, that makes sense. I’ll give it a try today.

Hi Waltert, I do understand the NNMI vs NMGR part, but not the AT+NMGS part. I would like to send messages from the gateway to my device, not from my device to the gateway. I use a Postman script to do so, but somehow this doesn’t work as I hoped for. I wonder what I’m doing wrong.

I tried to send a message to my SODAQ device by using Postman with NB-IoT TMNl collection:

1. Login -> successful
2. Get devices -> sucessful
3. Send command -> successful

Then when I use AT+NQMGR or AT+NMGR is see no messages…

Any suggestions?

Above work-around worked fine when I created it but not anymore ? In fact the situation is getting worse. Hoping for a fast solution.

Spijtig, mijn modems zitten al op firmware v6.57 en ook met de huidige RAN versie zijn beide AT commando’s nodig om het te laten werken. Maar na ca twee uur valt de verbinding weg… Een upgrade van de RAN om dit op te lossen zou dus fijn zijn.

Seems to work fine

Our goal is to develop an application in which the product moves (slowly, e.g. walking) from one place to another place and takes a measurement e.g. every minute. While moving, it gets out of range of the cell it initially connected to but gets in range of another cell. How can we ‘smoothly’ switch over from the initial cell to the other cell? A complete reconnect would be an option, but that takes quite some time and consumes quite some battery power. How can we switch over without having to completely reconnect ?

Note: we’re using the SODAQ module with N211 modem and v65.7 firmware.

Hope it will be solved soon, but until then I’ve added a work around to my sketch to overcome the incompatibility between the new uBlox G6.57 firmware and the current T-mobile network software: before sending new data to the network, test if the modem is still connected to the network. If not, re-establish the connection by:

• switch Radio off
• set IP of Chip and Set Vendor CDP again
• set PDP and ANP again
• switch Radio on again
• register With Network Operator again

It seems to work for me (at least for 10 hours now).

Regards,
Felix

P.s. the old board with N200 and the new board with N211 but with old firmware don’t seem to have this problem.

@afzal_m Thnx!

Ik heb afgelopen vrijdag de SODAQ training gevolgd. Daarbij wordt gebruik gemaakt van OceanConnect als CDP die de messages van mijn devices doorstuurt naar AllThingsTalk. In plaats daarvan zou ik mijn messages graag doorrouten naar mijn eigen cloud. Hoe regel ik dat?