You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As am amateur ESP8266/ESP32 developer who has done a few projects, I wonder:
Why doesnt the main openEVSE module just use an ESP32 as it's µC and provide Wifi out-of-the-box? (Even an ESP8266 should be powerful enough I think?)
Why seperate the 2? Are there safety concerns or are there actual technical reasons?
Or has just nobody yet found it worthwhile to redesign the openEVSE main board so drastically?
The text was updated successfully, but these errors were encountered:
I have already asked this question - it's mostly about certification - you would need to rewrite whole code for ESP32 - then get certification that takes time and I assume costs money. So it was easier/cheaper to just add WiFi module.
Oh, I didn't know openEVSE had any kind of certification... If that's the case then I understand fully why it makes sense to not change the hardware. On the other hand... the hardware (and software) do get updated now and then, even if only minor hardware changes, shouldn't that require re-cert anyway?
Maintainability, Internetwork operations, Reliability for the cluster and other topics that do not come to case specifically. . This is not an Issue and should be probably placed in the Forum @arnolde I recomend you open a discussion there. https://openev.freshdesk.com/support/discussions/topics/new
As am amateur ESP8266/ESP32 developer who has done a few projects, I wonder:
Why doesnt the main openEVSE module just use an ESP32 as it's µC and provide Wifi out-of-the-box? (Even an ESP8266 should be powerful enough I think?)
Why seperate the 2? Are there safety concerns or are there actual technical reasons?
Or has just nobody yet found it worthwhile to redesign the openEVSE main board so drastically?
The text was updated successfully, but these errors were encountered: