@Lauwie007 said in Downlink API dataformat:
Downlink data received: 00 (but this is ASCII, which translates to 3030 in HEX)
Your assumption here is wrong @Lauwie007 this is binary the device visualizes the received data for you in HEX so it received 0x00 binary 2 bytes which is what you want to achieve.
+CSONMI: 0,2,00 means I received 2 bytes both all zeros.
Regards,
Eric
Hi Erwin,
Unfortunately MQTT(-SN) over NB-IOT as of yet is still unavailable for the iotcreators SIM cards this will be available shortly.
The manual kindly referred to by @Stefan-de-Lange is not related to IOT creators but to cloud of things which is a different offering entirely.
MQTT over LTE-M is available with these sim cards as can be read here. But this won’t help you with your NB-IOT modem.
Alternatively if you don’t like to wait I would suggest a different type of SIM offering (prepaid) we have also with a free plan here this has the MQTT-SN capability.
Hi @Artur-S ,
@Stefan-de-Lange is correct public DNS is not reachable from the IoT creators sim cards. I didn’t see and DNS option available in NB-IOT only capable modems I must say. Indeed LTE-M gives access to public DNS and internet. You could try one of the prepaid cards some of the T-Mobile operators are offering for IoT.
@rogierlodewijks and @afzal_m
Thanks for the honors and the devkit.
First of all; indeed you cannot turn on the echo using the standardised commands also I have found no alternative.
So sharing logs is more difficult.
I think the example above has a small error in the order of things.
Due to AT+CFUN=0 (which is switch off phone functionality)
You cannot issue at+cops and at+cgdcont commands
So the correct order is;
AT+CMEE=1;+CSCON=1;+CEREG=5 (turn on some informative feedback)
AT+CFUN=1
AT+COPS=1,2,“20416”
AT+CGDCONT=1,“IP”,“cdp.iot.t-mobile.nl”
See if we are searching for a network
AT+COPS? (If answer is 2 we are still searching)
AT+CSQ (if first number is unequal to 99 we have a radiosignal)
And then wait for:
+CSCON:1 (RRC Connected)
+CEREG:5,5,###### (Registered roaming)
(I have updated the example above)
@Dirkie123 I would like to investigate this topic a bit more. Could you send me some logs I can’t see which device / SIM card you are using in your tests. You can DM me or send details to hi@iot.t-mobile.nl?
There is no option to query the status of a downlink message. Buffering of downlink messages may occur on different places in our solution it is hard to give an clear response to such a request due to the asynchronous nature of the protocols.
Note: after sending an uplink message we will try to downlink all buffered messages.
The correct syntax for deleting a subscription is
curl --location --request DELETE 'https://iot.netwerk.t-mobile.nl/m2m/subscriptions/98f7bf0b-0000-0000-000-e077030e42ae' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic xxx' \
--data-raw ''
The subscription Id to be used is the one of the packets that you receive!
And Basic Auth is your authorization header.
Hi @Jurriaan-Vollebregt could you check the protocol you used when you registered your device? The protocol selected determines the encoding for downlink. We didn’t have changes that I m aware of.
Hi @Martijn-Kooijman , I think that the extra messages that you receive might be related to the lifecycle events that our platform sends. Sometimes when your device sends a message an re-registration event occurs this generates an lifecycle message. Have a look at this text: https://docs.iot.t-mobile.nl/docs/device-data-reporting we create both a lifecycle and a resource subscription when you register a device.
@Crowdsourcer I see that the socket id of the created socket is 2. In the consecutive commands you should use that Id. All other steps seem fine.
@IoT-Arista and @Sopwafel,
If you still encounter problems, I can try to investigate for you in the platform whether the subscriptions to your data contain any errors.
You can send me a direct message or a mail to our mailbox with the device and account details.
Hoi @David-van-Manen ik zie dat we hier nooit op gereageerd heb. Het toevoegen van een poortnummer op de juiste plaats moet gewoon kunnen. Wel moet er een webserver draaien die in eerste instantie 200 OK respons geeft op een leeg bericht.
Hi @tibor-casteleijn, I have a question regarding the SIM card you are using. Is this a SIM card provided by particle? Or did you also obtained it from our webshop? A particle SIM card might not be able to roam on our NB-IOT network yet.
A second thing if you are using our sim card the first connection might take up to 15 minutes, can you stretch the time-out for this initial connection? Next connections are faster but the initial one can take a while.
@cees-meijer if you would like us to review the behavior you can contact me in a DM. There might be optimisations possible.
Hi @Robin-Finkers ,
I have been reviewing our documentation and noticed that this might not be clear; in the att asset did you register the device connectivity with the IMEI: prefix? This should be the case otherwise the device is not found.
@cees-meijer this messagetype is an registration message. This event occurs when the device is seen for the first time after a certain period this depends on several factors for instance after the device is switched-on and transmits its first message from a new IP address. It allows you to capture the payload of the first message ever sent to the udp adapter, otherwise this event would be lost.
We plan to added some more information in the future to this message as can be seen from the empty data elements.
@cees-meijer sorry for the inconvenience and thanks for the suggestion we will take this in consideration!
@bart-abel thanks for the update
All is resolved now
Very sorry for all the issues this must have created
All we are facing an issue with an message broker database we are currently trying to fix it.
It is not a network issue we see all your messages coming in and we will try to resolve this with ASAP
Hoi @derko-drukker ,
Via de mail reeds op de hoogte gesteld.
We hebben tijdelijk geen voorraad van dit specifieke type sim kaart (Industrial 3FF) er wordt gewerkt aan het aanvullen van de voorraad en dan gaan we alsnog de leveringen afronden.
@rhalflex so called multi-mode simcards will become available soon an exact date is still uncertain but we expect commercial availability by the second quarter of this year.
@stefan-de-lange and @rhalflex indeed standard based NB-IOT roaming is becoming possible but it will take a while before a significant global footprint becomes available. With LTE-M it will be available earlier because operators can re-use the roaming technology in place for LTE networks.
However for NB-IOT internatco (meaning DT footprint) roaming is possible today! In every country where the Telekom Group has NB-IOT available NB-IOT roaming is possible without additional charges.
If you would like to have this enabled let us know on hi@iot.t-mobile.nl , we will switch the profile of your SIM card!