@Crowdsourcer If you see 15 mA it means there is a problem. I measured an average of 6.7 uA in PSM

@Martijn-Kooijman I solved it by checking the return message after sending “AT+USOCR=17,7000”. Once it is contains “+USOCR: 0” in the returning string I know it is ok: (it takes about 5 s after a reset) added code: String check_sara=cmd("AT+USOCR=17,7000"); while ((check_sara.indexOf("+USOCR: 0",1)<0)) { delay(500); check_sara=cmd("AT+USOCR=17,7000"); Serial.println(check_sara);//just for checking }

@thijsbuuron Deel je bevindingen!

@afzal_m Proprietary sucks I hope more open protocols are added, UDP is pretty limiting

We do not have a message broker @Robin-Puthli. But we do use a SCS. The SCS is an essential component for NB-IoT (as also described by 3GPP). Without the SCS you will get in trouble with your battery.

Spain confirmed!

Does it also work for @trick2011 now?

@afzal_m Sounds good, how about BG600? - it has a similar FW to BG95/96

@lorenz Dear Lorenz, Thanks a lot for the feedback and I’m glad to see eDRX is delivering its promise on energy saving! Another tip maybe: please consider setting your preferred Periodic TAU Timer to save further energy. This can be done without setting any PSM activity timer with the CPSMS command, with a TAU-timer of up to 310 hours. To enable Long-Periodic TAU without PSM, use value “11100000” for parameter <Requested_Active-Time>. Best regards, Ronan

@Timo-Siekmann said in Limited Data Rate after to many messages on aday?: Quectel BG96 Hi, please try: AT+QCSCON=1 AT+CEREG=4 I highly suggest to plot the current too.

@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 !)

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

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