Device unable to get past CGATT:0 – power cycle fixes the problem instantly

3 thoughts on “Device unable to get past CGATT:0 – power cycle fixes the problem instantly

  1. We have many devices in the field that have been in operation for over a year based upon the HE910 chipset. All systems are stationary and never move (nor do their antennas.). All these systems continuously send telemetry data to our cloud platform. Occaisionally there is a loss of network access, and the units will re-establish a connection without any manual intervention.

    We now have some systems (around the globe) that appear to now be unable to get attached to the network. If we check the logs we see that we’re getting a CGATT: 0. The units have also tried turning the modem off for 10 seconds before trying to re-attach to the network. In all cases this has failed, and CGATT: 0 persists. If someone physically pulls the power from the system and turns it back on, we immediately get CGATT: 1 and the system continues to operate normally.

    Any suggestions as to what might be going on with these units?

    Thanks.

    1. Hi,

      Maybe the network operator is rejecting you for some reason. Can you check the attach state with “AT+CGREG?” instead of “AT+CGATT?” ?

      If you receive a 3 as a reply, can you check the cause code with this command: AT#CEERNET

      1. Hi,

        Maybe the network operator is rejecting you for some reason. Can you check the attach state with “AT+CGREG?” instead of “AT+CGATT?” ?

        If you receive a 3 as a reply, can you check the cause code with this command: AT#CEERNET

        Will see what we can do.  These units that that are experieincing these issues are unforunately on the other side of the planet, and operate without a screen or logging due to very limited amounts of memory on board.   

        Thanks for getting back to me with some suggestions.