AT#SSEND +CME ERROR: activation failed

18 thoughts on “AT#SSEND +CME ERROR: activation failed

  1. Hi,

     From time to time I got this error from GE864-QUAD V2 after sending payload data instead of OK.

    Can you tell me please what this mean?

    Socket is already successfully activated, connected etc – which activation failed then?

    How to avoid this error?

    I am monitoring ‘not acknowledged’ field in socket info and didn’t send if it is above 10000 …

    1. Please send the firmware version (at+cgmr) and the complete sequence you are using.

      From time to time : what does it mean exactly? 

  2. GE864 QUAD V2 sw 10.00.022


    I am attaching log captured with saleae logic analyzer to show you both rx/dx and exact timings. Saleae client software can be free downloaded from their site:

    Problems are on 40s, 84.3s, 111.3s

    In this version of my software I am sending data on portions around 3500 bytes and wait that they are completely ACK-ed before next sendings. This reduces the error occurences but decreases significantly overal bandwidt, and this is problem because device is Ultra Low Power and each second from lifetime matters


      1. I am trying couple of times to add it without success. Can I send it to a email or something like that?


        I don’t know why this site delete my message and attachments …

    1. thanks for the analyser log, but we would need the AT command sequence
      or is there the possibility with this Saleae tool to read each character
      sent and received in ASCII format?

      1. Hi Andrea,

        Yes, it is possible to read ascii/hex with Saleae logic analyzer software.

        It is better than simple text log because you can see both chanels at same time, with timings, etc.

        Of course if you preffer I can prepare pure text logs, but then you’ll miss the whole picture.

        What I found till now is that when I send packets slowly everything works pretty fine (i.e. around 500 bytes  per 3-4 sec). Problem occurs when I am sending quickly.




        1. I set the options => Display in Ascii & Hex

          but I assume it is something else I have to do to have ASCII characters represented. 

          I can only measure the width of the signal

          1. You need to zoom to certain level to see ASCII characters in the signal.

            Serial line analyzing is already configuret in this data file and should work without additionall efforts.

            I will try to attach screenshot to see what I mean. (Don’t know why never succeed with attachments here)

          2. Hi Atanas,


            I’ve analysed the logs. It is difficult to say why AT#SSEND return an ERROR after a while.

            I can only see that you reset the connection and everything works correctly for another period.

            I can only say  that some improvements were introduced on 10.00.023 for AT#SSEND command. Have you had time to test a newer version?


          3. Hi Andrea,


            Thanks for your analyzys.


            For the moment I switch to another project and didn’t test with newer versions but will forward your notes about that to our managers.