GL865 – Roaming net is changingin randomly

6 thoughts on “GL865 – Roaming net is changingin randomly

  1. Device: GL865 – DUAL

     

    What we are trying:

    We perform a network selection as following:
    1) Unregister from current network using AT+COPS=2

    2) Register to new network (using for example AT+COPS=1,2,23203 to select
    the 23203 network)
    3) We check the network by performing AT+COPS?
    3.1) This works and we are registered to the selected network at the beginning (AT+CREG? -> “Registered Roaming”)

    Our Problem:
    Roaming network changes after a random periode of time
    (but we want to prohibit this behavioral)

     

    Thanks in advance

    Nick Mayerhofer

    1.  AT+COPS:

      <mode>  

      1 – manual choice unlocked (network is kept as long as available, then it can be
      changed with some other suited networks to guarantee the service)

       

      Change the parameter to:

       

      5 – manual choice locked (network is kept fixed, if the chosen network is not
      available, then the mobile has no service) 

  2. Change the parameter to:

     

    5 – manual choice locked (network is kept fixed, if the chosen network is not
    available, then the mobile has no service) 

    For
    AT+COPS == 5
    we have to select AT#SELINT=0 or 1 – concerning to the datasheet (r13 p.99 / p.101).
    (Other way around: If we don’t select AT#SELINT=={0,1} we arn’t able to select AT+COPS == 5)

     

    at#selint

    But the modem returns an ERROR if we try to select AT#SELINT=0 or 1.
    (And the datasheet sayes that we should use AT#SELINT==2 – because it’s the newer one r13 p.18)

    at#cops

    If we’r trying to select AT+COPS=5,2,23203 without touching AT#SELINT – we’r receiving an ERROR too

    Thanks in advance

    Nick M.

    1. Indeed with #SELINT=2, or 0/1 with #COPSMODE=1 AT+COPS=1 is to be used. Set AT+CMEE=2 for verbose informative error messages.

       

      1. Indeed with #SELINT=2, or 0/1 with #COPSMODE=1 AT+COPS=1 is to be used. Set AT+CMEE=2 for verbose informative error messages.

         

        AT+CMEE=2

        AT+CMEE=2

        OK

        AT#SELINT=0

        AT#SELINT=0

        +CME ERROR: operation not supported

        AT#SELINT=1

        AT#SELINT=1

        +CME ERROR: operation not supported

        AT#SELINT=2

        AT#SELINT=2

        OK

         

        So we’r still hangin at the original problem.

        Any other ideas?

        1. Hi,

           

          there was a misunderstanding.

          AT+COPS=5….on SELINT=0/1 currently works like AT+COPS=1 on SELINT=2, so no need to change SELINT.

           

          ETSI
          specification 24.008 defines the procedure to select and get registered
          to the network operator, that is exactly the one I copied on my
          previous reply.
          i.e.

          ii) PLMNs contained in the
          "PLMN Selector"
          data field in the SIM (in priority order);


          iii) other PLMNs with
          received signal
          level above -85 dBm in random order;

          If there aren’t
          operator available from the one contained in the "PLMN Selector" the
          module will search for other PLMNs with the above requirements in
          automatic mode.

          When you set the manual selection with AT+COPS=1 (#SELINT=2)
          the module get registered to this one. If not available it camps to any
          other operator in emergency mode (only emergency calls) keep searching
          for the selected operator.
          Even
          if the signal is bad but enough for the module to keep the registration,
          it will not switch to any other network if AT+COPS=1 is used.