GL866 difference between syshalt and shdn

15 thoughts on “GL866 difference between syshalt and shdn

  1. Hallo,

    I’m testing power-off procedure of module GL866 (but I have other in mind). I’ve read Telit’s documentation.

    What’s the difference between command syshalt and shdn? In hardware user guide Telit recommend using syshalt. But in description of these two commands shdn provides network detach. Does syshalt also provide network detach?

    I’ve noticed that for my network both commands provide network detach. But syshalt consumes less power than shdn. Can you explain that?

     

    Regards,

    Maciej Smyczek

    1. Hi,

      we have GL865 and GE866 but not GL866 🙂 anyway the behavior is the same.

      Basically these 2 products don’t have the ON_OFF pin to turn on the module. The module is automatically turned on when VBATT is applied.

      Therefore AT#SHDN turns off the module with network detach but after few seconds the module is automatically turned on again, therefore the consumtion you are measuring is higher because the module is in Idle state again.

      The #SYSHALT detach from the network and put the module in a very low sleep mode.

      You can refer to the HW User Guide of your product, Turning OFF section.

      1. Thank you for answer. We use both GL865 and GE866.

        I confirm that higher power consumption was due to almost instant startup of the module after shdn (we wait 10 seconds for detach). I’ll use shdn command then.

  2. Hello,

    I try to upload a python script with a size of 668bytes to the GE866-QUAD FW 16.01.202. I used RX/TX/GND.

    Unfortunately it fails. #LSCRIPT shows free bytes: 971280.

    What could be wrong?

    Is there smething missing?

    You hint is highly appreciated.

    Thank you.

    1. All scripts are failing to upload or only this? Is the upload reported as OK or with an error?

      1. I’ve got this:

         Send: AT#WSCRIPT=”main.pyo”,1445,0<cr>
         ready …

         Send: AT#LSCRIPT<cr>
        #LSCRIPT: free bytes: 972736
        OK

          1. I don’t know. For that reason I ask.

            By the way, the communication with At commands works fine, a firmware upload as well.

            So we can assume the serial line is ok.

            Maybe there is a setting in the parameter needed?

          2. For firmware please see my previous post. Hardware control is needed for big files > 4096byte and fast upload. Right?

          3. This is not what official documentation says, even it works in many occasions. I wouln’t let my precious programs to run if they are uploaded in a non-supported way, at least not in production.

            Anyway I the “ready” thing cannot be really because of the flow control. It must come from elsewhere.

            Have you tried other (older) firmware versions?

          4. I have make the test with Telit AT-Controller with HW flow control.

            I’ve got this:

            05/21/16 14:44:17>>>: AT+CGMR
            05/21/16 14:44:18<<<:  AT+CGMR

            16.01.202

            OK

            05/21/16 14:44:24>>>: AT#LSCRIPT
            05/21/16 14:44:24<<<:  AT#LSCRIPT

            #LSCRIPT: free bytes: 970148

            OK

            05/21/16 14:44:27>>>: AT#WSCRIPT=”test.py”,244
            05/21/16 14:44:27<<<:  AT#WSCRIPT=”test.py”,244

            >>>
            05/21/16 14:44:56<<<:  
            ERROR

            any idea?

            Thanks.