@mels-liefaard said in AT commands gezocht om SIM7020E te verbinden:

1752B06SIM7020E

Ik kan bevestigen dat het ook werkt met firmware versie 1752B07SIM7020E.
Ik heb er gisteren een berichtje mee verzonden met hulp van dit topic. (Bedankt !)

@Holger-Wech you can use LTE-M instead of the 2G/3G fallback that is described in our quick start guide. Please use the APN internet.m2mportal.de for LTE-M.

@pieterhoenderken

Sorry! We hadden wel je device verwijderd, maar dat vergat ik hier te melden!

@supersjimmie

Hoi Sjimmie. Mooi dat je het werkend hebt gekregen.

{“latitude”: 52.136421, “longitude”: 5.262903}

Ik zou dit anders aanpakken. Aan de kant van NB-IoT wil je enkel kale bytes sturen, het sturen van JSON data creëert onnodig veel overhead.

Je zou het ook zo kunnen doen namelijk:

AT+CIPSEND=16
031B89E500504E37

Is maar 8 bytes. In je python flask kun je dit vervolgens weer scheiden omdat je weet dat beide variabelen 4 bytes zijn:

latitude = 031B89E5
longitude = 00504E37

Dan converteren naar decimale notatie en de komma weer terugplaatsen.

@afzal_m said in Add subscriptions via api:

Thanks a lot @JeroenD. Maybe you are not aware of it but last month with did a major update on the document library after two years. But we only focused on the devices part.

In August we will update the API part as well 🙂
@Roalnd-Baldin is already working on it.

Nice @afzal_m 😃

Hello guys

@Yassine-Amraue : thank you for explaining that there is a GUI and an API user. I’ve been banging my head trying to send a downlink message via API and always getting an ‘unauthorized’ error. But after registering a callback URL for the API user as well I can now send downlink messages via API to my device. Thanks again.

@magnatron : I am using a SIM7020 based device and previously via API sent downlink messages are getting delivered to it as soon as the device sends an uplink message.

Thanks
Felix

@apuhl , with a classic M2M GSIM (IMSI starting with 90140), you may use the standard APN “internet.m2mportal.de”, with a Consumer SIM card (starting with 26201), it should be “internet.telekom.de”.

Best,
Ronan

Good morning @afzal_m, is it possible this Sim requires 3v? This would explain weird behavior when the module provides only 1.8v

@Eric-Barten said in Downlink API dataformat:

ary the device visualizes the received data for yo

Okay, that my bad.
Thanks for the answer

@Uta said in MFF2 + eSIM for IoT device (with end users owning subscriptions):

https://www.thalesgroup.com/en/markets/digital-identity-and-security/mobile/connectivity/esim/what-is-an-esim

Maybe this is even the complete solution which is needed here.
With that solution, there is not even the need to pass the QRcode data to the application as the module will download the prepared profile using a QRcode entered on a web portal. Even a change later on to another provider is possible by assigning a new profile to the eUICC which is downloaded by the module later on.

@trick2011 I use the following sequence:

AT+UDCONF=1,0

AT+USOCR=17,7000
<rx socket number>
AT+USOCO=<socket>,“172.127.131.100”,<udp port>
AT+USOWR=<socket>,<data length>

<wait for @>
<send user data>
AT+USORF=<socket>,127 #127 is max rx length, depends on yr buffers

+USORF: <socket>,“172.27.131.100”,15683,17,“downstream data”

AT+USOCL=<socket> # close socket

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

@florian-duecker test123 🙂

edit: works

@stefan-de-lange Heel mooi uitgelegd, Stefan!

Hoi @Eric-Barten, heb je al een idee of T-Mobile de andere manier van NITZ doorgeven gaat ondersteunen en wanneer?

Het zit ook niet in de sim profielen inderdaad. Maar bedankt voor het testen!

@techniek zou je aub de device configuratie met @TVDL kunnen doornemen aub?

@stefan-de-lange Thanks for the reply 🙂