Home › Forums › Mayfly Data Logger › New Xbee Modem: XB3-C-GM1-UT-001 › Reply To: New Xbee Modem: XB3-C-GM1-UT-001
Oh interesting, Thanks for sharing, Sounds like it connected some of the time, showing that it was possible to connect. I’ve found there are four source of failure – setup to cell tower, TCP/IP setup, POST ack, MMW timeout,
I found this hardware data sheet – but it turns out there is a GM1 and GM2 – GM1 is the low power. I wonder which one you got?. https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/6378/XB3-C-GM2-UT-001.pdf
SUPPLY VOLTAGE 3.3 – 4.3 VDC
AVG TRANSMIT CURRENT (LTE-M) 1.25 A peak, 410 mA average (GM2 modules), 450 mA peak, 200 mA average (GM1 modules)
I was just wondering is the Mayfly 1.1 likely to handle the GM2 peak? though peaks are always a difficult number, as it should specify somewhere the capacitor (or pulse width) needed to handle that peak.
The XB3-C-A2-UT the data sheet .
SUPPLY VOLTAGE Standard Version: 3.3-4.3VDC;
PEAK TRANSMIT CURRENT Standard Version: 550mA;
AVG TRANSMIT CURRENT 235mA
For the low power (GM1) version of fw,
https://hub.digi.com/support/products/digi-xbee/digi-xbee-3-global-lte-mnb-iot/
and found this User Guide (I had to feed a few dragons tasty data on the way there) https://www.digi.com/resources/documentation/digidocs/PDFs/90002420.pdf
I have had this recent email for a survey on Digikey, (pasted below, hope it comes out ~ feel free to click on what you think)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thank you for taking the time to participate in this survey.
Ron Konezny
President & CEO
Digi
<table border=”0″ cellpadding=”0″ align=”center”>
<tbody>
<tr>
<td>
<div>What is your overall impression of Digi?</div></td>
</tr>
<tr>
<td>
<table border=”0″ width=”100%” cellspacing=”5″ cellpadding=”0″>
<tbody>
<tr>
<td>Very favorable</td>
</tr>
<tr>
<td>Somewhat favorable</td>
</tr>
<tr>
<td>Neither favorable nor unfavorable</td>
</tr>
<tr>
<td>Somewhat unfavorable</td>
</tr>
<tr>
<td>Very unfavorable</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>