<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Different PCBs and modem modules in COM.LTE unit!!]]></title><description><![CDATA[<p dir="auto">We have a number of <em>M5Stack CoreS3 ESP32S3 loT Development Kit</em> units, including a DIN base, for a product prototype.<br />
We’ve  also purchased <strong>13 COM.LTE</strong> units from 2 different, Swedish, distributors.</p>
<p dir="auto">And we have problems…<br />
See text and image below.</p>
<p dir="auto"><em>Minor issue but still irritating</em>. The mechanical tolerances of the DIN rail mount are such that it is unusable on all DIN rails we have tested (several). Perhaps DIN-rail specs are different in Sweden…. (probably not though).</p>
<p dir="auto"><strong>Major issue with modem module</strong>.</p>
<p dir="auto">The first 3 COM.LTE units we purchased work fine. I used the TinyGSM library with the ”SIM7600” header/spec. These units have a PCB that ”is aware”  of the CoreS3 existence, see image, and also include a SIMCOM SIM7600G-H modem module.</p>
<p dir="auto">The second set (10) of COM.LTE units ….</p>
<ul>
<li>The <strong>antenna cable on all units was connected to the contact marked GNSS</strong>. This is not correct!</li>
<li>The PCB is most likely older. No CoreS3 ”marking”.</li>
<li>The exact same code does not work!</li>
</ul>
<p dir="auto">Please note that the pin mapping from modem module UART RX/TX to the bus contact is the same on both PCBs ( I measured/tested) and the DIP-switch setting is the same.<br />
Due to other sensor connections I want to keep the DIP-switch setting =&gt; I use GPIO 1 and 7 to communicate with the modem module. SERIAL_AT.begin(115200, SERIAL_8N1, 1, 7, false);</p>
<p dir="auto">So now I have 10 COM.LTE units that do not work and I really don’t know what to do. Return/throw away/?</p>
<p dir="auto">Perhaps someone has some tips</p>
<p dir="auto"><em>BTW1</em>: Yes, I’ve tried miscellaneous modem test code from the TinyGSM library as well as even simpler code to test the UART connection.</p>
<p dir="auto"><em>BTW2,</em> I’ve ordered 5 new COM.LTE units from distributor that supplied working units. We’ll see how it goes.</p>
<p dir="auto"><img src="https://www.majodang.se/senspix/jobb/modemstrul.jpg" alt="alt text" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/topic/6483/different-pcbs-and-modem-modules-in-com-lte-unit</link><generator>RSS for Node</generator><lastBuildDate>Sun, 17 May 2026 06:42:12 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/6483.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 17 May 2024 07:47:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Different PCBs and modem modules in COM.LTE unit!! on Fri, 17 May 2024 12:54:46 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/senspix" aria-label="Profile: Senspix">@<bdi>Senspix</bdi></a></p>
<p dir="auto">I just tried with my SIM7600G (non -H; 3 years old) and M5CoreS3 using aforementioned test program and the modem does react to <code>AT</code> commands just fine after about 14 seconds.</p>
<p dir="auto">Recently I purchased a separate green board with a SIM7600G-H on it which I use in the same COM.X module. Initially it did not work. Turns out the green board had a layout error - RX and TX needed to be swapped electrically in order to work in the COM.X module.</p>
<p dir="auto">In conclusion: I can use either SIM7600G or SIM7600G-H with M5CoreS3 just fine.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/25311</link><guid isPermaLink="true">https://community.m5stack.com/post/25311</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 17 May 2024 12:54:46 GMT</pubDate></item><item><title><![CDATA[Reply to Different PCBs and modem modules in COM.LTE unit!! on Fri, 17 May 2024 09:17:29 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/senspix" aria-label="Profile: Senspix">@<bdi>Senspix</bdi></a></p>
<p dir="auto">I don't think the PCBs are different - to me it looks more like a sticker has been added to the same PCB. But I could be wrong.</p>
<p dir="auto">Maybe try swapping a SIM7600G (non -H) into a PCB with sticker to see if that works? Also make sure you firmly stack the COM.X to your M5CoreS3. It could be a simple connection issue.</p>
<p dir="auto">Maybe this simple <a href="https://github.com/felmue/MyM5StackExamples/blob/main/M5CoreS3/COMLTETest/COMLTETest.ino" target="_blank" rel="noopener noreferrer nofollow ugc">test program</a> might help evaluating the hardware? It sends an <code>AT</code> command repeatedly. Edit: I just re-read your post. You already tried simpler programs.</p>
<p dir="auto">Edit: Well, it could also be a power issue. How are you powering your LTE modems? Through the DC jack or from the M5CoreS3?</p>
<p dir="auto">BTW: I noticed the incorrect antenna connection about 3 years ago. See <a href="https://community.m5stack.com/topic/3378/com-lte-module-sim7600g-antenna-was-attached-to-incorrect-connector">here</a>.</p>
<p dir="auto">Same with the SIM7600G vs SIM7600G-<strong>H</strong> version. At the time (3 years ago) the M5Stack shop talked about CAT4, but was selling the non -H version (which is only CAT1). See <a href="https://community.m5stack.com/topic/3582/com-lte-module-sim7600g-only-cat1">here</a>.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/25309</link><guid isPermaLink="true">https://community.m5stack.com/post/25309</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 17 May 2024 09:17:29 GMT</pubDate></item></channel></rss>