CME Error 23

7 thoughts on “CME Error 23

  1. We’re manufacturing a unit for a customer, using the GM862 module with firmware 7.02.604. The customer writes their own firmware.

     

    Our customer has reported that many of their units have failed with CME Error 23 after a period when the units could not access their server (server was down).

     

    Once the modules are in this state, they do not respond correctly to some AT command and need re-flashing to clear this fault. As the firmware version is 7.02.604 we can’t do this OTA and our customer is having to visit many sites!

     

    Its very hard to get any info on CME Error 23! Telit docs and internet searches just report "Memory Failure" with no further details.

     

    We sent one module back to Telit when this problem occurred previously (in a different situation), but Telit were unable to give us more information.

     

    We suspected that our customer wasn’t shutting down the module correctly, but have since confirmed their shutdown sequence (AT#SHTDN before removing power).

     

    Has anyone come across this error?

    What does it mean?

    How does it occur?

    Is it recoverable?

     

    Thanks

     

    John

  2. I am getting this error on my GL865 device all the time and I’m starting to worry how this will behave in the field. While I can do a format here on my test bench it will be a whole different story once the devices are let out into the open.
    When uploading I get these messages:
    > Uploading logger.py (570 bytes)
    < +CME ERROR
    < : operation not supported 
     
    And when trying to delete:
    > AT#DSCRIPT="BigEndian.pyo"
    < +CME ERROR
    < : memory failure 
    I just did a reformat and reuploaded every script again, and now the device is happily compiling them, but the "operation not supported" error still remains.
    1. Try to leave larger intervals between file handling commands; the file system management cannot be very fast; this is on only one module or do you have more like this?

       And do you use storage in Python file space?

       

       

      1. Try to leave larger intervals between file handling commands; the file system management cannot be very fast; this is on only one module or do you have more like this?

        This is the flow I’m using:

        for each file:
           if LCSCRIPT(file)   // Check if file exists
              if DSCRIPT(file) // Delete file
                 Delay 2000ms

           Send WSCRIPT
           if Got >>>:
              Send script content

         

         I might want to sleep after writing a script. I’ll try that.

         

         And do you use storage in Python file space?

         

        We do not, no. At least not for writing, AFAIK.

        1. I would say delays of seconds after each file command will help, in your code you have a delay only if a file exists and is deleted.

           

          1. Now I’m waiting after writing the .py file but some files still show this behavior when I try to delete them:

             

            > AT#DSCRIPT="main.pyo"

            < +CME ERROR

            < : memory failure

             

            The .pyo file is generated when I execute the main script and it’s functional since the script subsystem executes just fine. I just can’t delete some files without doing a format. 

  3. Maybe are you using also flie.close() method? pay attention if you are using close   and not close(). It’s necessary to put the brackets.

    If this is not the solution, please post the code or send the code by e-mail to Telit Technical  Support