hi Jeffrey,
If you aren't completely tied to your current design / implementation
solution ...
You might consider replacing the Arduino and ESP8266 micro-controllers
entirely with an ESP32.
- Removes the need to interconnect two different micro-controllers
- Removes the need to support two different micro-controller tool-chains
- Only need to power, configure and deal with a single micro-controller
and PCB
- ESP32 can be programmed using the Arduino IDE as just another
supported "board"
- Most common Arduino software libraries are supported on the ESP32
- Good chance that your existing Ardino software can run on the ESP32
(with little or no change)
- Mostly likely a cheaper hardware platform than what you now have
- Specially intended for modern wireless, embedded applications
- Considerably more GPIOs and other useful hardware peripherals
- More powerful dual 32-bit micro-controller with considerably more
Flash and RAM
- Has sufficient RAM and processing power to deliver secure (encrypted)
wireless communications
- Can switch to using FreeRTOS operating system (instead of Arduino
framework) in the future
- Can switch to using microPython, which is also a great fast-turnaround
prototyping environment
Integrating Wi-Fi functionality on the ESP32 will be a matter of using
the correct software library, instead of hooking together two
micro-controllers (at both the hardware and software level) ...
-
https://techtutorialsx.com/2017/06/29/esp32-arduino-getting-started-with-wifi
-
https://github.com/espressif/arduino-esp32/tree/master/libraries/WiFi
And the CCHS is very fortunate to have two monthly ESP32 meetings with
very capable and very friendly attendees ...
- Second Wednesday of the month: Mair hosts an ESP32 IDF (C / C++,
FreeRTOS) tutorial session
- Fourth Wednesday of the month: Matt, Damien and Nick host a
microPython session that supports the pyboard, ESP32 and more
Whilst it is a very tough decision to jump ship from something you have
in your hand and are comfortable with (apart from your interconnection
issues), but if you have the time to do-it-right and lay down a solution
that is more future-proof ... I'd say go-for-it.
cheers andyg