GE865 +CALA #SHDN power off/wake up?

21 thoughts on “GE865 +CALA #SHDN power off/wake up?”

  1. I’m writing an application much in common with the “Telit Modules Software Guide” 3.8.5.7. A simple Alarm Application example.

    I have set the +CALA with a time of +CCLK + 2 minutes and then tried software shut down command #SHDN.

    Unfortunately I don’t seem to get the module to wake up with the alarm, no matter what I try.

    I’m using GE865 with sw version 10.00.008.

    Is it even possible to get it to wake up again with alarm? (without any outside stimuli ?)

    I have tried both using the AT interface with serial and also tried within python. Also tried all kinds of different +CALA options etc.

    The #SYSHALT seem to be nice but that seems to not be supportet for the GE865.

    Any help/hint is appreciated.

    Best regards and thanks in advance,

    Jan

      1. Thanks for the reply, sorry for a bit late feedback.

        Here is from the AT command line (with responses):

        ——-

        at+cclk?
        +CCLK: “15/11/27,12:38:19+04”

        OK
        at+cala=”15/11/27,12:40:19+04″,0,6,”wake up!”
        OK
        at+cclk?
        +CCLK: “15/11/27,12:39:00+04”

        OK
        at+cala?
        +CALA: “15/11/27,12:40:19″,0,6,”wake up!”,””,0

        OK
        at#shdn
        OK

        —–

        Never wakes up.. I’m also monitoring GPIO6 with oscilloscope to try to catch the alarm triggering but nothing there.

        (If I don’t do a #shdn I can see that GPIO6 gets high for a short moment with same CALA options.)

        If I use python I get the same results.. 

        I have tried different CALA options too, and also gpio=6,0,2 before without any success.

        I’m using a GT864-PY Terminal device. Maybe there is a hw issue?

        I notice that if I have the DTR line constantly active/high and try the same command sequence,  the device gets in some kind of semi-sleep and is able to wake up. Unfortunately it consumes too much current (8mA). (Running the module at 12V)

        Questions:

        1. Is the device able to wake up from sleep without using GPIO6? IE should it be able to wake up with cala <timestring>, 0, 1 for instance?

        2. If not, is the correct way to wake it up by connecting GPIO6 to DTR?

        3. Any hints/directions to get it work or other things to check?

        Best regards and thanks in advance,

        Jan

        1. Hi 

          it is strange since I flashed the same SW version on my module and sending the same your setting I get module working correctly.

          Are you testing module directly with a PC connected to module via serial?

          Do you have only one sample to test?

          Thanks

          1. I’m suspecting it might be a hw issue with the RTC not getting any voltage. Unfortunately it is not possible to verify this on the  GT864-PY Terminal, at least not by opening it up and inspecting it..

            If so, this is thread might be at the wrong place. Is there any for the  GT864-PY Terminal?

            Are there any SW-ways to detect if the RTC has voltage after #SHDN?

            The module you were using, is it a GT864-PY Terminal?

            If the sequence I’m trying to run is supposed to work on that hw I have no problem getting another one to ensure it’s not an individual problem with my hw. But I’m not that interested to have two units that’s not able to do what I want 😉

            Also, are there different versions of the GT864-PY Terminal?

            I know the first ones having the 864 and newer seem to have the 865 but could there be other differences?

            Also there are GT864-PY Terminal from CEPAG?  Or are the Telit ones also CEPAG ?

            I’m testing with PC and serial, with a cable with just Rx/Tx/GND. If I connect DTR and has it high the “semi-sleep” 8mA mentioned before occurs.

            I have also tested the sequence from within Python with no serial and then it just sleeps without waking up.

            Thanks for helping!

            Best regards,

            Jan

          2. Hi

            I tested a terminal with the same your SW version and at command, after #shdn module wake up at the time indicated via AT+CALA.

            Are terminal always connected to pw supply after #SHDN?

            Did you send other at command or only cclk and cala and #shdn?

            Could you send AT+CMAR=00000000 to restore parameters

            and retry?

          3. Yes, the terminal is always connected to pw supply after #SHDN.

            Tried after restoring with AT+CMAR=00000000 but without any success. (Still never wakes up/any change on GPIO6..)

            Do I need to use GPIO6 to make it wake up? Or will any CALA options work? (will ease my test-setup if I don’t have to use it.)

            Also, is there any way to figure out if the VRTC gets power during #SHDN?

            Since it should work with my GT864-PY Terminal, I’ll fix another terminal to test if my one is broken. Could take some days though.

            Thanks so far, really appreciated!

            Best regards,

            Jan

          4. Hi

            I done further test on my sample in both way, by RTC or by nitz and in both case it work as you can see.

            I set the module with a different cala mode (refer to at command below), but also in  GPIO 6 mode works well. Please exclude PY script, and power supply only the module directly with power input: 5 – 36 V

            Thanks

             

            at

            OK

            at+cgmr

            10.00.008

             

            OK

            at+cclk?

            +CCLK: “00/01/01,00:00:43+04”

             

            OK

            at+cclk?

            +CCLK: “00/01/01,00:00:49+04”

             

            OK

            at+cclk=”15/12/03,09:47:40:00+04″

            ERROR

            at+cclk=”15/12/03,09:48:30+04″

             

            OK

            at+cclk?

            +CCLK: “15/12/03,09:48:36+04”

             

            OK

            at+cclk?

            +CCLK: “15/12/03,09:48:51+04”

             

            OK

            at+cala=”15/12/03,09:50:00+04″,0,2,”W”

            OK

            at#shdn

            OK

             

            +CALA: W

             

            +CALA: W

             

            +CALA: W

             

            +CALA: W

             

            +CALA: W

          5. Hi 

            Any news?

            Further doubt:

            after setting module (at+cala) and sent AT#SHDN, module does’not wake up, ok, but when you power on again the module, what about at+cclk response do you see the time correctly?

          6. We are still investigating with another module but unfortunately it looks like the same behaviour. I’m not conducting the testing myself unfortunately. We have to test some more to be sure.

            After CALA+SHDN without waking up and forcing it to wake up with setting DTR high and a “quick” CCLK command shortly after results in “00:00:00”..

            after a few seconds more the module seems to have correct time. Could this be an indication that the RTC is not active during software shut down?

          7. Hi

            I confirm you that if you use at#shdn at command to shut-down the module you do not reset cclk setting.

            You loose +cclk setting only after HW power off (disconnecting power supply), so if module after at#shdn is woke up via DTR and +cclk=”00/00/….” it means that module has been turn off completely not only via SW.

             

            Test on my lab with a module including the same SW version

            module turn on:

            Now turn on again the module via DTR (plug in serial cable) with out disconnect power supply and check cclk:

          8. Unfortunately the other terminal tested behaves the same. No wake up after #shdn. Also the other module indicates power loss for the RTC by having the answer “00/01/01,00:00..” shortly after turning on the terminal after a #shdn.

            This means that 2/2 terminals we have here does have the problem.

            The first terminal (mine) has the SN: 062356363054989514 with a HW-Rev. G1b-43´4, made by CEP AG. Also the number 0889 is below CE.

            The second terminal has S/N: 0602356363054716271, HW-Rev: G1b-43´4 (same as the first)

             

            The pictures included in your last post can not be showed by the way.

            We made a test-procedure for the test: (the ampere-meter could be ignored), included below:

            —
            Test procedure for testing the “#CALA+#SHDN” problem on GT864-PY

            Equipment:
            GT864-PY Capag (test object)
            Power supply at 12V
            Ampere-meter
            Computer with serial port and terminal program
            Serial cable DB9 straight with only Rx/Tx+GND pins connected (2,3,5) and with pin 4 connected via a toggle switch.

            Test setup (hw)
            Pin 1 (VCC) of RJ11 connected via ampere-meter to power supply at 12V.
            Pin 6 (GND) of RJ11 connected to power supply GND

            Pin 2,3,5 on DB9 RS232 serial port connected to computer serial port
            Pin 4 on DB9 RS232 serial port connected to a toggle switch straight to pin 4 of the computer serial port.

            Test setup (sw)
            Start terminal program on the computer. Setup serial port to 115200 8N1 no flow control. Ensure that the DTR pin is set high. (more than +4V)

            Test execution
            1. Turn on the power supply for the module.
            Press the button enabling DTR to be set on the module.
            On the terminal, type in “AT”, ensure it is awake and says “OK”
            2. Type “AT+CCLK?”, notice the answer and time. The module should answer like:
            +CCLK: “15/12/04,12:15:50+04” (If the module answers “00/01/01..” wait some and send the command again.)
            3. Set alarm time to current time from CCLK command above with 5 minutes
            added with options 0,2,”W”
            Example: “AT+CALA=15/12/04,12:15:55+04″,0,2,”W”
            4. Verify that the larm was set ok with “AT+CALA?”
            5. Check the time and verify that at least 90 seconds are left before alarm
            is set with same CCLK command: “AT+CCLK?”
            6. Set module to software reset “AT#SHDN”.
            7. Wait for at least 10 minutes to ensure that the alarm time is due.
            8. If the module is ok, it would wake up and print out “+CALA: W” – Test
            finished ok!
            (9.) If the module never woke up, restart it by pressing the button,
            connecting DTR high to the module for a short while.
            (10.) Quickly type in first “AT” to get a response and then “AT+CCLK?” after restart and notice the time. If the
            answer from the module is “00/00/00,00:00:00…” it would indicate that the
            RTC lost power during the test. – Test failed. (Could be tricky to have time to do this..)
            The RTC test could also be done after a “AT#SHDN” without CALA as long as the power has been turned on all time.

            Power reading with ampere-meter:
            1-5: around 20-30mA or more
            After shutdown: 0.13mA
            —

            Also here is the testlogg: (output from the module first, then the commands sent to the module:

            —

            <00><00>at

            OK
            at+cclk?

            +CCLK: “00/01/01,00:00:08+04”

            OK
            at+cclk?

            +CCLK: “15/12/14,20:48:53+04”

            OK
            at+cala=”15/12/14,20:52:53+04″,0,2,”W”

            OK
            at+cala?

            +CALA: “15/12/14,20:52:53″,0,2,”W”,””,0

            OK
            at+cclk?

            +CCLK: “15/12/14,20:49:42+04”

            OK
            at#shdn

            OK

            <00><00>t
            at

            OK
            at+cclk?

            +CCLK: “00/01/01,00:00:04+04”

            OK

            ——————
            at
            at+cclk?
            at+cclk?
            at+cala=”15/12/14,20:52:53+04″,0,2,”W”
            at+cala?
            at+cclk?
            at#shdn
            at
            at
            at+cclk?

            —

            Sorry for the long post. I guess this means that there might be a problem with VRTC on the terminals we have here?

            Has the terminal you are using same HW rev? Could it be that newer versions of the GT864-PY Terminal has VRTC problems and not the older ones?

            Best regards and thanks for keeping trying to help us,

            Jan

          13. Hi

            I replied the same your test:

            module power supply 12 V (pin 1 and 6)

            RS232 PIN connected TX, RX, GND and GND.

            Run +cclk and cala and shdn

            module wake up with alarm.

            Note:

            please check DTR status, it has to be always to high level (9V), after #SHDN.

            I suppose DTR go low in your application. For this motive, module does not wake up

            Other thing, but I suppose it is a mistake only, I see on your sample you set an alarm at  “AT+CALA=15/12/04,12:15:55+04″,0,2,”W”

            where +cclk is: +CCLK: “15/12/04,12:15:50+04″

            So you set only 5 sec, not minutes and alarm is not valid, the time in your test is already elapsed.

          14. Thanks for the reply!

            Yes, sorry was a typo 5 seconds alarm 🙂

            But ok, the DTR must be on whole time? I have tried that, mentioned it in the thread, I thought that was some kind of “semi-sleep” since the terminal uses 8mA @12V. (Which is unfortunately way too much for our battery operated application..)

            Best regards,

            Jan

          16. I guess the GT terminal is not designed for battery-application with RTC sleep/wake up. This means we have to find some other hw for our app.

            Thanks for all the help and answers!

            Best regards,

            Jan

          17. Hi

            GT terminal, can work correctly if you use a network operator that support NITZ command or to maintain serial cable connected to module..