Python AT commands

11 thoughts on “Python AT commands

  1. Dear Colleagues

     

    I am trying to understand some Python related commands and read the latest (to my knowledge) AT Commands Ref Guide, rev 10.

     

    In paragraph  3.5.7.11.4.  "Execute Active Script – #EXECSCR " it says:

    "Execution command causes the current script (see #ESCRIPT) execution
    not at startup. 
    This command is useful when the execution at startup has been blocked
    deliberately and the user wants to control execution start.  "

     

    Can you explain, in other words, what is meant here? Do you mean "prohibits" the execution at startup? Blocked? Who blocks?

     

    On the contrary, is there a way to FORCE a script being run, immediately? I am a bit lost with DTR swapping etc., to get a small script actually being run. How can I run it for sure?

     

    Thanks,

    Tom 

     

     

  2. Let me re-phrase:

     

    AT#EXECSCR causes the currently enabled script (see #ESCRIPT) to be started at command instead of being automatically started at module startup.
    This command is useful when the execution at startup is not enabled and the user wants to control the moment of the script start.

     

    Did I make it more clear?

     

    EXECSCR is a good way to control script start, however automatic start is simpler if you don’t use DTR line but mode 1 or 2 of  AT#STARTMODESCR,1 being better for development I think.

     

     

     

    1. Thanks Cosmin

       

      Sure, your wording is much more clear. I suggest you put it into the AT Commands Ref Guide as well, in the next release.

       

      But still, is there a definite way to start a script, by issuing an AT command, or a sequence of commands, without restarting the module and/or playing with the DTR line? 

       

      I now have downloaded a simple script, and I can list it as follows:

      at#lcscript           
      #LCSCRIPT: "LED.pyo",197,772D   
      #LCSCRIPT: free bytes: 2011984   

      OK

       

      Also, I have enabled it: 

       

      at#escript="LED.pyo"   
      OK

       

      But how to get it running?

       

      Thanks again,

      Tom 

  3. Hi All

    I have been playing around with a GE910-GNSS module. It was on 13.00.106 FW and I updated it to 13.00.107. Now I can’t get the python scripts to work. See the following screenshot. Can anyone assist me in with a possible exaplanation as to the following behaviour.

    AT#LSCRIPT
    #LSCRIPT: “decoded_seed”,8192
    #LSCRIPT: <MOD>
    #LSCRIPT: “GPSScript.py”,2280
    #LSCRIPT: free bytes: 3003392

    OK
    AT#EXECSCR
    ERROR
    AT#ESCRIPT=”GPSScript.py”
    ERROR
    AT#WSCRIPT=”GPSScript.py”,2280
    >>>
    OK
    AT#EXECSCR
    ERROR
    AT#ESCRIPT?
    ERROR
    AT#ESCRIPT=?
    ERROR
    AT#SELINT=2
    OK
    AT#ESCRIPT=?
    ERROR
    AT+CMEE=2
    OK
    AT#ESCRIPT=?
    ERROR
    AT#STARTMODESCR?
    ERROR

    An advice would greatly be appreciated!

    Regards

  4. Hi All

    I have been playing around with a GE910-GNSS module. It was on 13.00.106 FW and I updated it to 13.00.107. Now I can’t get the python scripts to work. See the following screenshot. Can anyone assist me in with a possible exaplanation as to the following behaviour.

    AT#LSCRIPT
    #LSCRIPT: “decoded_seed”,8192
    #LSCRIPT: <MOD>
    #LSCRIPT: “GPSScript.py”,2280
    #LSCRIPT: free bytes: 3003392

    OK
    AT#EXECSCR
    ERROR
    AT#ESCRIPT=”GPSScript.py”
    ERROR
    AT#WSCRIPT=”GPSScript.py”,2280
    >>>
    OK
    AT#EXECSCR
    ERROR
    AT#ESCRIPT?
    ERROR
    AT#ESCRIPT=?
    ERROR
    AT#SELINT=2
    OK
    AT#ESCRIPT=?
    ERROR
    AT+CMEE=2
    OK
    AT#ESCRIPT=?
    ERROR
    AT#STARTMODESCR?
    ERROR

    An advice would greatly be appreciated!

    I have updated the FW multiple times to make sure that is not corrupted in during the programming – but I still get the same results.

    Please note that the 13.00.107 FW is the appzone version. Is Python scripting enable in this version of the FW? FW Ver: streamGE910-GNSS-AZ-13.00.107

    Regards

    1. “Python and AppZone are mutually exclusive” applies to all modules so you must load the firmware version you intend to use.

      1. Thank you Cosmin

        Were can I find the 13.00.107 FW version for Python seeing that it is not listed on the download zone. I only see 13.00.106 and 13.00.107 for Appzone.

          1. I received the file, thank you. Just for the record – the non App Zone 13.00.107 version works 100% with Python scripts.