Topics created by felixdonkers

Veel toepassingen zullen het niet nodig hebben (alhoewel…), maar soms is het nodig om niet alleen korte berichtjes maar ook (middle-)grote bestanden te kunnen versturen of te ontvangen. Bijvoorbeeld als je een firmware upgrade wilt doen van je product of voor het versturen van uitgebreide meetdata in het geval je device een storing heeft. Met een download bandbreedte van 250kbps en een upload bandbreedte van 20kbps (of 250kbps igv dual tone) zou er binnen NBIOT wel wat mogelijk moeten zijn. Vraag: hoe is het versturen en ontvangen van bestanden binnen NBIOT het beste te realiseren?

@eric-barten, zie snapshot

0_1526287618403_Capture.PNG

@felixdonkers

volgens mij was @ericbarten of @Eric-Barten al voor je aan het zoeken naar de slides 🙂

@andre-rodenburg Ja als ik via postman stuur krijg ik een bericht binnen, maar als ik verstuur via mijn device krijg ik het niet binnen. Heb alles gecheckt aan de hand van de handleiding en alles staat in gesteld zoals aangegeven.

@techniek
Ik ben ook heel benieuwd naar de antwoorden.

@felixdonkers said in NB-IOT in nomadic mode:

Will this also work abroad and with other MNO’s (NB-IOT interoperability question) ?

Definitely 3gpp standard will be inter operable across all operators global…
The latest non-backwards compatible change happened during rel 13… but this is a rare event… Not all operators have this change implemented but this will be resolved in the next couple of months… And this has only some effects on PSM I believe.

Today read: "GSMA counts 31 NB-IoT launches to date… " As far as I can see is the NB-Iot rollout pace a lot faster than Cat-M1…

What if connection is lost after all, e.g. due to a bad signal, how to detect that in a reliable manner? Using parameters CSQ=99 or RSRP=0 does not seem to be reliable. Is there a white paper that describes a solid solution?

I would assume that connection only gets lost when after device misses its periodic registration requirements…
AT+CGATT? if returns 1 the device is attached.

NB-IOT provides various parameters to minimize power consumption; T3314, T3324, etc. I’m wondering how to apply those parameters in the most efficient way. And also what the impact is, e.g. on responsiveness, when changing these parameters. Is there a white paper that demonstrates adequate use of these parameters. And when will they be supported (roadmap question), as experiments have shown that these parameters currently seem to have no noticeable effect.

AT+CPSMS command influences this.

White paper covering these topics:
NB-IoT Deployment Guide to Basic Feature set Requirements.pdf

regards,

Is there a datasheet of the SIM cards provided by TMNL? I would like to know the current consumption of the SIM.

Ik vermoed dat de 3 piekjes momenten zijn waarop het device nog luistert naar een paging request.

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.

Hi @juan-carbonell,

Pycom as released the first NB-IoT firmware:
https://forum.pycom.io/topic/2902/cellular-radio-firmware-release-sqn3330-for-both-cat-m1-and-nb-iot/14

unfortunately support for Huawei based networks such as T-Mobile isn’t working yet. Also we need UDP passthrough support from the network (coming before Summer as Afzal said) because we only support IP operation.

We’re only limited by what Sequans - the modem chipset manufacturer - can offer us so once they supply a working firmware for Huawei and either Sequans supports CDP or T-Mobile supports UDP Passthrough mode we’ll be able to support this amazing network.

I have to say I feel bad because of all the NB-IoT networks I have tested T-Mobile NL has been the best so far - great service uptime, coverage even during trial phase and of course great support team. I really wish Pycom could support it sooner.

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…

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.

Seems to work fine 🙂