[EHSx] Priority switch to UMTS | Thales IoT Developer Community
June 3, 2014 - 8:34pm, 6593 views
At the moment I'm working on a project with the EHS6 module and I noticed that the module often switches back from UMTS to GPRS/EDGE. If this switching only occurs temporary, when needed, it would not be a problem. But I do not see the module switching back to UMTS when available. On my location is enough UMTS reception and I'm using an +5 db gain antenna.
My goal is to use UMTS as much as possible. How can this be done? (Without reboot / dettach / attach)
Edit:
OK
at^smoni
^SMONI: 3G,10661,119,-2.0,-82,204,08,178E,09AA0A6,10,33,NOCONN
OK
at^smoni
^SMONI: 3G,10661,119,-2.0,-79,204,08,178E,09AA0A6,10,36,NOCONN
OK
at^smoni
^SMONI: 3G,10661,119,-2.5,-79,204,08,178E,09AA0A6,9,36,NOCONN
at+creg?
+CREG: 2,1,"178E","009AA0A6",2
It looks like it is connected to 3G but still there is a ping of 500ms! If the last number of CREG is 6 I have a ping of 80ms.
Update:
AT^SMONI=255
^SMONI: 3G,10661,119,-2.5,-81,204,08,178E,09AA0A6,9,34,NOCONN
This I get even when I have a ServerSocket running, connected and read/writeing on the module. According to the documentation the NOCONN part should list more information when module is connected. (Not camping)