-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more stability for ESP8266 #113
Conversation
Hi @bogde, parts of the changes submitted by @el3ctrician look like they are related to #29 and the corresponding part of the documentation
I would recommend removing the non-timing-safe variant completely from the code as it keeps on popping up here, especially as the ESP MCUs are gaining more and more popularity, which leads to different attempts in solving the crashes experienced there. See also #76 and maybe others. Thanks, |
Commit was merged. Thank you! |
Hi @bogde, that was quick, thanks for merging this! However, I really would aim at finally removing the problematic constructor altogether and especially would amend the ESP8266 example accordingly. While I recognize that the initialization call to May we humbly ask whether you would accept a respective pull request from us also emphasizing the breaking change in the documentation appropriately? It would be a kind of an early spring cleanup maybe ;]. Thanks, |
sure, i'm totally fine with that! |
Dear Ahmad, thanks already!Assuming you might exactly know what we are talking about, I would be very happy if you would take this as I will be traveling on the weekend. Just was rambling around here to check whether @bogde would even consider this change. BackgroundIn the advent of modern libraries for reading the HX711 ADC (which we are also interested in), I really would like to give the well known HX711 library by @bogde here some love as it is still the canonical place to go when reading the HX711 ADC and has a huge audience already. While we successfully run this library on ESP8266 MCUs already, I would especially like to go into checking compatibility with the ESP32 in the long run. So I thought about bringing this topic up here. So, if you would like to spend some time on this library, we would appreciate this very much, @el3ctrician. With kind regards, |
Dear Ahmad, while being at it, may I humbly ask you to make the busy loops around the code safe for ESP usage by properly feeding the watchdog? Issues like #120 and friends also seem to come up here frequently. Thanks in advance, |
Hi Bogdan and Ahmad, just wanted to let you know that we managed to make a start in the dry dock [1] (branch "spring-cleaning") by pulling in various pieces from the issue tracker of this library as well as a fork supporting ESP32 already (https://github.com/lemio/HX711/). We will follow up letting you know whether this will actually compile (we didn't do yet) and if it will actually work on real hardware (unfortunately, we don't own any ;]). Edit: Code compiles now and in order not to spam this further, I've diverted a future discussion to #123. With kind regards, P.S.: For the records, we are also tracking this at [2]. [1] https://github.com/hiveeyes/HX711/tree/spring-cleaning |
in case of esp8266, calling the begin in constructor causing the esp to crash see this issue and this also
added some illustration example also and a keywords file