🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Connect COM.LTE to CoreS3?

    Scheduled Pinned Locked Moved Cores
    12 Posts 3 Posters 10.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      aezero @felmue
      last edited by

      @felmue
      Hi Felix! Good to hear from you again!

      Thanks for the clarification! The second serial connection is the blue connector, right?

      1 Reply Last reply Reply Quote 0
      • A Offline
        aezero
        last edited by aezero

        Looking at the pinout diagrams with some refreshed eyes and I see it now... "PA" is short for "Port A" and "PC" is short for "Port C". And PA has a red background, like the red Port A connector, and PC is in the same light blue as Port C's connector.
        alt text

        1 Reply Last reply Reply Quote 1
        • felmueF Online
          felmue
          last edited by

          Hello @aezero

          thank you for pointing that out as I haven't noticed that myself - even the background color matches the connectors.

          Thanks
          Felix

          GPIO translation table M5Stack / M5Core2
          Information about various M5Stack products.
          Code examples

          1 Reply Last reply Reply Quote 0
          • A Offline
            aezero
            last edited by

            And on further examination, there's the dark grey PB_IN and PB_OUT pins, at G8 and G9. The splash screen when you power it on shows G8 and G9 are on Port B (there's a typo, saying "Port.C" but it's in the position of the black Port B connector).

            alt text

            1 Reply Last reply Reply Quote 0
            • A Offline
              aezero
              last edited by

              I just made another discovery. If you power it up with the factory demo software, go the home screen, and then tap on "CORES3" six times, it puts you into a factory test mode

              1 Reply Last reply Reply Quote 0
              • C Offline
                Cohen
                last edited by

                I have the M5CoreS3 and the Com.x LTE, not having any success communicating with the COM.X LTE. the dips are on the default 5/13.
                what should they be set too? and is there any simple Example Test of LTE for me to test and follow??

                I see this comment
                "I suggest you set COM.LTE to use pins 16 / 17 and then use GPIO18 / 17 in your code. AFAIK PC_RX and PC_TX are the second serial."

                not sure if just Dip 5 should change to 16 or 17?? help appreciated.

                also in the Code is there a command to tell how to communicate with those different PINS??

                first time use of the LTE.
                thanks

                1 Reply Last reply Reply Quote 0
                • felmueF Online
                  felmue
                  last edited by felmue

                  Hello @Cohen

                  please find a simple test for the communication between M5CoreS3 and COM.LTE module.

                  In the COM.LTE module set the DIP switches as follows:

                  15 - off
                   5 - off
                  16 - on
                  13 - off
                   0 - off
                  17 - on
                  

                  Note: my COM.LTE module takes about 15 seconds (after power on) until it is ready and responds with AT OK.

                  Thanks
                  Felix

                  GPIO translation table M5Stack / M5Core2
                  Information about various M5Stack products.
                  Code examples

                  C 1 Reply Last reply Reply Quote 0
                  • C Offline
                    Cohen @felmue
                    last edited by

                    @felmue said in Connect COM.LTE to CoreS3?:

                    test

                    I give this a go. thanks

                    1 Reply Last reply Reply Quote 0
                    • C Offline
                      Cohen
                      last edited by Cohen

                      Thanks that did it.
                      I got a res: AT OK.

                      thanks.

                      I am trying to use TinyGSM
                      has any one got it working with he Core3 COM.X LTE?

                      but with no luck. get the following:-
                      22:44:52.276 -> [6988] Trying baud rate 115200 ...
                      22:45:02.304 -> [16999] Trying baud rate 57600 ...
                      22:45:12.314 -> [27009] Trying baud rate 38400 ...
                      22:45:22.312 -> [37019] Trying baud rate 19200 ...
                      22:45:32.324 -> [47029] Trying baud rate 9600 ...
                      22:45:42.325 -> [57039] Trying baud rate 74400 ...
                      22:45:52.334 -> [67049] Trying baud rate 74880 ...
                      22:46:02.336 -> [77059] Trying baud rate 14400 ...
                      22:46:12.356 -> [87069] Trying baud rate 28800 ...
                      22:46:22.358 -> [97079] Initializing modem...
                      22:46:32.393 -> [107111] Failed to restart modem, delaying 10s and retrying
                      22:46:32.393 -> [107111] Initializing modem...
                      22:46:42.440 -> [117143] Failed to restart modem, delaying 10s and retrying
                      22:46:42.440 -> [117143] Initializing modem...
                      22:46:52.451 -> [127175] Failed to restart modem, delaying 10s and retrying
                      22:46:52.454 -> [127175] Initializing modem...

                      Thanks

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        Cohen
                        last edited by

                        Got a bit further in the quest.

                        I added the following:-
                        void setup() {
                        // Set console baud rate
                        SerialMon.begin(115200);
                        delay(10);

                        SerialAT.begin(115200, SERIAL_8N1, 18, 17, false);
                        delay(3000);
                        modem.restart();

                        and got some responses

                        23:06:21.706 -> [14189] Wait...
                        23:06:27.695 -> [20189] Trying baud rate 115200 ...
                        23:06:30.064 -> [22535] Modem responded at rate 115200
                        23:06:30.064 -> [22535] Initializing modem...
                        23:06:35.068 -> [27555] ### TinyGSM Version: 0.11.7
                        23:06:35.068 -> [27555] ### TinyGSM Compiled Module: TinyGsmClientSIM7600
                        23:06:45.272 -> [37756] Failed to restart modem, delaying 10s and retrying
                        23:06:45.272 -> [37756] Initializing modem...
                        23:06:55.486 -> [47957] Failed to restart modem, delaying 10s and retrying
                        23:06:55.486 -> [47957] Initializing modem...
                        23:07:03.779 -> [56269] ### TinyGSM Version: 0.11.7
                        23:07:03.779 -> [56269] ### TinyGSM Compiled Module: TinyGsmClientSIM7600
                        23:07:03.843 -> [56316] ### Modem: SIMCOM SIM7600G-H
                        23:07:03.843 -> [56316] ### Modem: SIMCOM SIM7600G-H
                        23:07:03.877 -> [56369] ### Modem: SIMCOM SIM7600G-H
                        23:07:03.877 -> [56369] Modem Name: SIMCOM SIM7600G-H
                        23:07:03.910 -> [56397] Modem Info: Manufacturer: SIMCOM INCORPORATED Model: SIMCOM_SIM7600G-H Revision: SIM7600G_V2.0.2 IMEI: "redacted" +GCAP: +CGSM
                        23:07:03.910 -> [56397] Waiting for network...
                        23:07:03.975 -> [56440] Network connected
                        23:07:03.975 -> [56440] Connecting to vsh.pp.ua
                        23:07:04.008 -> [56482] ... failed
                        23:07:04.008 -> [56482] Requesting current network time
                        23:07:04.008 -> [56484] Couldn't get network time, retrying in 15s.
                        23:07:18.986 -> [71484] Requesting current network time
                        23:07:19.025 -> [71486] Year: 2024 Month: 1 Day: 26
                        23:07:19.025 -> [71486] Hour: 23 Minute: 7 Second: 3
                        23:07:19.025 -> [71486] Timezone: 11.00
                        23:07:19.025 -> [71487] Retrieving time again as a string
                        23:07:19.025 -> [71506] Current Network Time: 24/01/26,23:07:18+44
                        23:07:19.185 -> [71672] Battery charge state: 0
                        23:07:19.185 -> [71672] Battery charge 'percent': 0
                        23:07:19.185 -> [71672] Battery voltage: 3.80
                        23:07:19.219 -> [71691] Chip temperature: 37.00
                        23:07:19.219 -> [71691] End of tests.

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post