7 replies

Hi, @Enthernet Code I think creating

Hi, @Enthernet Code I think creating some projects about connecting any non-wifi mcu to the IoT server. We can connect ESP-01/ESP8266/ESP32 (AT command mode) to any 8/32-bit MCU (AVR/PIC/ARM/RISCV) to provide internet connectivity. And then cover different use cases to demonstrate the use of popular protocols in projects. Liked the idea by @techielew picking one platform and creating projects around it.

ZacckOsiemo•7/7/24, 10:45 AM

How come people favor this approach, why not just use the ESP as the MCU?

ZacckOsiemo•7/7/24, 10:45 AM

And not need 2 mcus?

Umesh LokhandeOP•7/7/24, 12:54 PM

I'm not against ESP but still plenty of MCUs without Wifi capability in the market. So there are many people, especially from the non-consumer electronics side. Still prefer to use the main MCU which is non-ESP and ESP will be just to provide Wifi. (I mean the approach Arduino UNO R4 followed) IMO there are other reasons too.

ZacckOsiemo•7/7/24, 1:14 PM

@Umesh Lokhande I'd be keen to hear about the other reasons, I understand legacy work and migration situations, but I've sometimes seen new designs with this. I guess it just works so well..?

ZZacckOsiemo @Umesh Lokhande I'd be keen to hear about the other reasons, I understand legac...

Umesh LokhandeOP•7/7/24, 1:24 PM

Hi @ZacckOsiemo right my friend migration and legacy works will cost time. And I don't think either companies or consultants prefer it unless it is a major feature update.

ZacckOsiemo•7/7/24, 1:32 PM

True, turns out hardware is stickier than software, so legacy is really legacy.

techielew•7/7/24, 1:46 PM

ESP is still not mainstream for professional development. I think it makes sense as a bolt on.

ZacckOsiemo•7/7/24, 3:21 PM

that's another way to look at it I guess.

Hi, @Enthernet Code I think creating

Similar Threads

Similar Threads

Similar Threads