Dear IoT Creators,

we are using the following sensor which is also listed in the off-the-shelve listed hardware devices in the docs: https://docs.iotcreators.com/docs/ellenex-pls2-n-liquid-level-transmitter

Until now we used the device with a 1NCE LTE-M Germany modem configuration and want to switch now to Deutsche Telekom M2M SIMs. We have the needed configuration from Ellenex for Deutsche Telekom for their on-board modem:

cgdcont="IP","iot.telekom.net" nwscanmode=3,1 iotopmode=0,1 band=0,80080,0 cops=1,2,"26201" scramble=0 qicsgp=1,1,"iot.telekom.net","","",0 cfgstr1:at+qcfg="roamservice",1,1

We updated the config of the device accordingly. But we run into connection issues:

Connection logs snippet:

rx: OK IDLE tx: at+cfun=1,0 rx: rx: OK IDLE tx: AT+CREG? rx: rx: +CREG: 0,1 got CREG: 1 rx: rx: OK IDLE tx: at+qeng="servingcell" rx: rx: +QENG: "servingcell","CONNECT","GSM",262,01,4340,C205,7,74,-,-70,255,255,0,37,37,1,-,-,-,-,-,-,-,-,-,"-" got qeng got CONNECT Got: "CONNECT" rx: rx: OK IDLE tx: at+qcsq rx: rx: +QCSQ: "GSM",-70 BG96_QcsqCallback: {+QCSQ: "GSM",-70 } GSM rssi: -70 rx: rx: OK BG96_QcsqCallback: {OK } IDLE tx: at+qnwinfo rx: rx: +QNWINFO: "EDGE","26201","GSM 900",74 rx: rx: OK IDLE tx: AT+CCLK? rx: rx: +CCLK: "24/10/01,07:19:47+08" Set rtc: ok rx: rx: OK IDLE tx: AT+QIACT? rx: rx: OK IDLE tx: AT+QIACT=1 rx: rx: ERROR IDLE

Do we first need to register the device / EUID & SIM here at iotcreators to get a connection established?
We would prefer to use direct IP connection by just placing in a DT M2m SIM in the device as we are used with 1NCE.
We have a couple of devices and matching a SIM with a device is creating extra friction in our process.

Thanks for you help and best wishes,
Lars

Hi everybody,

I have been following this forum for quite a while now and it’s great to see how many designers are working with cellular IoT. We had in the past created some designs based on the PyCOM GPy as it was one of the only solutions that was small and fully certified. When the GPy became EOL we were left in the dark and took on the challenge to create a pin and software compatible upgrade. We have called our module Walter and it has the following functionality:

Ultra low 9.8uA deep sleep current in PSM mode Open source and software support for ESP-IDF, Arduino, Micropython and Toit LTE-M, NB-IoT (3GPP rel. 14) GNSS (GPS + GLONASS) WiFi and BLE CE, UKCA, FCC, IC and RCM certifications

I hope this might be of interest to you, please do not hesitate to ask questions. You can read everything on our Crowd Supply page: https://www.crowdsupply.com/dptechnics/walter

Kind regards,
Daan

I don’t require esims on every iot device all the time
So is there a mechanism to redistribute my esim profiles on the devices i am using ?
Want to save money on purchasing so many subscriptions by sharing esims on my devices

@magnatron yes this is a known bug unfortunately and we already requested a fix from our vendor. In case that the device is not functional at the moment or the device data aren’t forwarded to the correct application URL please send the IMEI to our support mailbox, we’ve got a workaround to fix it for you.

@uta I might be biased, but I love it. Thanks a lot - great work 👍

Btw: our goal is also to minimize signaling storms from inefficient IoT devices not supporting the TS.34 Radio Policy Manager (RPM) feature. What’s your experience with TS.34 RPM so far?

@Tuyen-Phan I have mailed support@iotcreators with the imei number.

@Cees-Meijer I just got an error message that the email couldn’t be delivered to you email address. Could you please send an email to support@iotcreators.com to make sure I am using the right address?

Thanks!

Cheers.

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

@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 😃

@afzal_m Bedankt !!

@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

Hi Mario,

Tuino 096 is an Arduino Zero (M0) compatible board. Grove Base Shield V2.0 doesn’t support this explicitity.

I recommand to try"ARDUINO MKR CONNECTOR CARRIER (GROVE COMPATIBLE)" instead. With this shield you can bridge from Zero/M0 to sensors with Grove connectors.

Regards, Roland

Hi Tibor,

Did you succeed to connect?
I want to use the Boron to.

Ah that’s a shame 😞

Good luck with finding solution.

Yes it’s working now. Thank you!

Problem solved. It denpends on the sim card

Hi Thomas,
sorry for late response. Please check our latest version of the Solution Guidelines, we have extended it with the information you inquired about.

BR, Aleksandra

Does it also work for @trick2011 now?