SIMcom7070G PING working code



  • Hi,

    A few days ago, I purchased two development boards. One of them is featuring the SIMcom7070G.

    My location is Germany, I am using a SIM from the Netherlands with Roaming enabled.

    I have not yet managed to send a message through but I can PING 172.27.131.100 - I hope that this module is compatible as it is not one of the recommended or approved one’s.

    Here are the commands for a successful PING: (Some are probably redundant)

    AT+CPIN?
    +CPIN: READY

    OK
    AT+CSQ
    +CSQ: 9,99

    OK
    AT+CGATT?
    +CGATT: 1

    OK
    AT+COPS?
    +COPS: 1,0,“Telekom.de”,9

    OK
    AT+CGNAPN
    +CGNAPN: 1,“cdp.iot.t-mobile.nl”

    OK
    AT+CNCFG=0,1,“cdp.iot.t-mobile.nl”
    OK
    AT+CNACT=0,1
    OK

    +APP PDP: 0,ACTIVE
    AT+CNACT?
    +CNACT: 0,1,“10.0.2.13”
    +CNACT: 1,0,“0.0.0.0”
    +CNACT: 2,0,“0.0.0.0”
    +CNACT: 3,0,“0.0.0.0”

    OK
    AT+CAOPEN=0,0,“UDP”,“172.27.131.100”,15683
    +CAOPEN: 0,0

    OK
    AT+SNPDPID=?
    +SNPDPID: (0-4)

    OK
    AT+SNPDPID=0
    OK
    AT+SNPING4=“172.27.131.100”, 5, 1, 20000
    +SNPING4: 1,172.27.131.100,2577
    +SNPING4: 2,172.27.131.100,367
    +SNPING4: 3,172.27.131.100,279
    +SNPING4: 4,172.27.131.100,292
    +SNPING4: 5,172.27.131.100,311

    OK


  • Deutsche Telekom IoT

    Hi Daniel,

    many thangs for this sample code!

    Probably my hint comes to late and you did it anyway, but don‘t forget to register your device at IoT Creators portal before you send your first message 😏

    Regards, Roland



  • Hi @Daniel-Rueppel
    I don’t know if you managed already but I have been able to send the UDP message with the following additional code after the ping code:

    AT+CASEND=1,11
    
    48656c6c6f20576f726c64
    
    AT+CACLOSE=1
    


  • Hi Roland,

    I also managed to send UDP packages so far.

    I read a statement from SIMcom where it is mentioned that the module does not support LTE and GNSS functionality at the same time. Therefore, I am evaluating the SIM7000E soon. Not yet tested this myself.

    Thank you,
    Daniel



  • @Daniel-Rueppel I’m not so sure, I just queried GNSS successfully in the middle of an open data connection session. It’s also possible to set up frequent automatic GNSS reports in the AT console.

    I’ve done it without a fix now. I will let you know if it actually works when I’m outdoors.



  • 
    +APP PDP: 0,ACTIVE
    AT+CAOPEN=1,0,"UDP",172.27.131.100,15683
    
    +CAOPEN: 1,0
    
    OK
    AT+CASEND=1,11
    
    > 
    OK
    AT+CGNSINF
    
    +CGNSINF: 1,,,0.000000,0.000000,-18.000,,,1,,0.1,0.1,0.1,,,,9999000.0,6144.0
    
    OK
    AT+CASEND=1,11
    
    > 
    OK
    AT+CACLOSE=1
    
    OK
    AT+CNACT=0,0
    
    OK
    
    +APP PDP: 0,DEACTIVE
    


  • Hi Eben,

    Here is the resource that I have found, it relates more to TCP, maybe UDP works.

    https://stackoverflow.com/questions/61857667/sim7080g-module-cant-send-data-over-tcp-while-using-gnss

    Thank you for testing this!
    Daniel



  • @Daniel-Rueppel said in SIMcom7070G PING working code:

    https://stackoverflow.com/questions/61857667/sim7080g-module-cant-send-data-over-tcp-while-using-gnss

    Hi Daniel,
    Yes I can confirm this. UDP works with GNSS but TCP doesn’t when used at the same time on the 7070G.
    It would be interesting to know how quickly you can get a fix after powering down and back up again. Hopefully it keeps the satellite almanac in memory.



  • By the way, after some more research, I found that it’s not that unusual to report gps using UDP. I suppose there might be some good existing solutions to learn from.



  • Hi Eben,

    I should receive a SIM7000E tomorrow and I will test it. I hope the commands are identical or at least similar. Will revert back with my findings as soon as I get time to test.

    Best Regards,
    Daniel



  • Hi Eben,

    Quick feedback: I can use GNSS and TCP at the same time using the SIM7000E using the latest firmware, which I had to update beforehand.

    Best Regards,
    Daniel

    AT+CGMR
    Revision:1529B03SIM7000E
    
    OK
    AT+CGNSPWR=1
    OK
    
    AT+CGNSTST=1,1
    OK
    $GNGGA,,,,,,0,,,,,,,,*78
    $GNRMC,,V,,,,,,,,,,N*4D
    $GPGSV,1,1,03,18,,,32,20,,,33,30,,,38*78
    $GNVTG,,T,,M,,N,,K,N*32
    $GPGSA,A,1,,,,,,,,,,,,,,,,*32
    $GLGSA,A,1,,,,,,,,,,,,,,,*02
    $GAGSA,A,1,,,,,,,,,,,,,,,,*23
    
    AT+CGNSTST=1,1
    OK
    $GNGGA,,,,,,0,,,,,,,,*78
    $GNRMC,,V,,,,,,,,,,N*4D
    $GLGSV,1,1,04,69,04,320,31,85,11,011,23,,,,26,86,00,056,*5C
    $GPGSV,2,1,06,07,23,066,34,15,34,293,22,18,12,305,32,20,01,329,35*76
    $GPGSV,2,2,06,28,49,135,28,30,54,067,38*7D
    $GNVTG,,T,,M,,N,,K,N*32
    $GPGSA,A,1,,,,,,,,,,,,,,,,*32
    $GLGSA,A,1,,,,,,,,,,,,,,,*02
    $GAGSA,A,1,,,,,,,,,,,,,,,,*23
    AT+CGNSTST=1,1
    OK
    
    ... got a fix after that!
    
    Establish test TCP server (Simple Perl script)
    
    AT+CPIN?
    +CPIN: READY
    
    OK
    AT+CSQ
    +CSQ: 9,99
    
    OK
    AT+CGATT?
    +CGATT: 1
    
    OK
    AT+CSTT?
    +CSTT: "CMNET","",""
    
    OK
    AT+CSTT="iot.1nce.net"
    OK
    
    AT+CIICR
    OK
    
    AT+CIFSR
    100.84.13.2
    
    AT+CIPSTART="TCP","10.65.61.189","5000"
    OK
    
    CONNECT OK
    WILMA-SERVER #1
    
    AT+CGNSTST=1,1
    OK
    
    ... Got GPS FIX
    
    AT+CIPSEND
    > PING
    SEND OK
    100.84.13.2:PONG
    
    TCP connection successful.
    
    

Log in to reply