<div dir="ltr">The link I shared was for ESP32 boards. What I was trying to convey (and maybe was miscommunicated, yay email!) is that these linked ESP32 boards seem to follow a form factor and convention of prior/historical ESP8266 boards, and therefore bring some additional consistency. I attached a screenshot of the page that loads for me, from that Amazon link.<div><br></div><div>Thanks,</div><div>Josh</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 15, 2021 at 1:16 PM Peter Soper <<a href="mailto:pete@soper.us">pete@soper.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> <span style="font-family:monospace">Thanks very much, Josh. Agree with point about pin conflicts. But did i go to the wrong page? I want to use an esp32 not 8266. This is for the "0.01" versuon of the community project board.</span>
<br>
<div>
<br>
<p>Nov 15, 2021 1:11:29 PM Josh Wyatt <<a href="mailto:dragojdw@gmail.com" target="_blank">dragojdw@gmail.com</a>>:</p>
<blockquote>
<div dir="ltr">
This is sort of an indirect response to your question, but my experience is that the more complex and "featured" the dev board, the less consistent. For example, for boards with onboard 18650 battery holders and Liion charger, OLED display, and even onboard LEDs will be on different I/O ports. So my guidance would be to choose the simplest boards available, which is sort of antithetical to the "dev board" concept.
<div>
<br>
</div>
<div>
I've had pretty good luck with consistency on the "wemos esp8266 clone" boards, presumably because the Wemos D1 mini became very established with the 8266; search on amazon for "esp32 d1 mini." Here's a link: <a href="https://www.amazon.com/Bluetooth-Internet-Development-Functional-Ardu-ino/dp/B08MFCC4SR/?th=1" target="_blank">https://www.amazon.com/Bluetooth-Internet-Development-Functional-Ardu-ino/dp/B08MFCC4SR/?th=1</a>
</div>
<div>
<br>
</div>
<div>
You mentioned soldering footprint, and that one's not super friendly; but it should be pretty consistent since the design tries to adhere to the original ESP8266 Wemos D1 Mini form factor.
</div>
<div>
<br>
</div>
<div>
You mentioned Amazon specifically, so I assume you're prototyping?
</div>
<div>
<br>
</div>
<div>
Thanks,
</div>
<div>
Josh
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Mon, Nov 15, 2021 at 11:38 AM Peter Soper via TriEmbed <<a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> <span style="font-family:monospace">What esp32 dev board soldering footprint should be used on a board combining this with other stuff where it has to be 1) obtainable reliably 2) offer wifi and BT and 3) be cheap? I see many cheap on amazon. Are their pinouts de facto standard? And finally, anybody got an Eagle lib for this board? Or could you make and send me an .lbr for it?</span>
<br> <span style="font-family:monospace">Thanks in advance.</span>
<br> <span style="font-family:monospace">Pete</span>
<br>
</div> _______________________________________________
<br> Triangle, NC Embedded Computing mailing list
<br>
<br> To post message: <a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a>
<br> List info: <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a>
<br> TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a>
<br> To unsubscribe, click link and send a blank message: mailto:<a href="mailto:unsubscribe-TriEmbed@bitser.net" target="_blank">unsubscribe-TriEmbed@bitser.net</a>?subject=unsubscribe
<br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote></div>