Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

CR1000 two GSM re-connection problems


smeck Jan 28, 2021 10:50 AM

Hi all,

we have installed a meteostation with CR1000 datalogger, connected to internet via Sierra modem and PPP connection set in Device config utility. Data are sent to FTP each 15min and parallelly downloaded from datalogger via Loggernet RTMC. Station is working since 2016 and all data operations/GSM connection were fine until last months of 2020.

Few months ago station started loosing connection to GSM network. This means that suddenly dataflow to Loggernet stops, no FTP data come, there is no remote connection to datalogger. We have implemented restart of modem in CR basic if no connection is available:


PPPClose
Delay(0,1,sec)
SW12(0)
Delay(0,5,sec)
SW12(1)
Delay(0,5,sec)
PPPOpen


but this does not help. Only possible solution is manual restart of datalogger and modem (hard power switch off - switch on). After restart, station will reconnect and connection works for two-three days and then again lost connection. I am suspecting overloaded GSM network, because last year there were finished huge business buildings nearby so maybe connection requests increased. But this is something what we can't change.

So problem no.1 is - what else we can try to change in our connection properties to make it more stable? Or how properly restart both logger and modem remotely/automatically via settings/CR basic program to force reconnection to network?

Problem no.2 is, that after manual restart, datalogger wants to send all data since last FTP push, so it is slowly sending and sending and sending ... But probably connection is not so stable, so logger re-starts sending data, breaks somewhere, starts again since last FTP push and breaks and again and again and cycling itself since last succesfull transmission and never reaching end (i.e. actually last measured value). So it is wasting data, creating big files on FTP and does not deliver last data. So my question is what can be set in logger to avoid re-sending data after reset? In case of connection failure we are ok with manual download of missing data via Loggernet, so FTP files are not neccessary to deliver. But we need to restore normal operation after restart, what means sending actual data to FTP each 15 min.

Please, do you have any ideas on problems above?

Thank you

Branislav

Log in or register to post/reply in the forum.