I'm trying to use the coroutine code that is already written for my system by creating a cooperative threading mini-system to simplify my code. For that it would be extra nice to be able to override the delay function when running inside a coroutine from the normal delay to the coroutine switching out. For this I need to make the delay function a weak symbol. Will such a change be acceptable for the project?
Obviously, I'd be happy to contribute the cooperative threading as well
Obviously, I'd be happy to contribute the cooperative threading as well
It joined my wireless network because I can ping it but serial montior has no output and it should be printing out that it's connected
I'm using a Wemos if that makes a difference
@geman220 Yes, the output of Serial.print (...........) should be visible on the Arduino serial monitor and any other serial connected device like for instance 'Coolterm'. The error message you got means that the Arduino IDE with, esp8266 Arduino installed, cannot sync to the ESP8266 module. This can be due to the ESP not being in the correct mode for flash programming or the TX Rx incorrectly connected. Another issue if the WEMOS is like the nodeMCU is to make sure you select the correct board in the Arduino tools menu. If you have selcted generic 8266 then it will not flash a nodeMCU type board correctly. Also if trying to download using the nodeMCU format you need to have CTS and RTS lines correctly connected to GPIO 0 and reset on the ESP8266 module. There are loads of posts about these connections via a bit of Google searching.
void connectWifi() {
if (WiFi.waitForConnectResult() != WL_CONNECTED) {
resetPins();
WiFi.mode(WIFI_STA);
while (WiFi.waitForConnectResult() != WL_CONNECTED) {
WiFi.begin(WIFI_SSID, WIFI_PASS);
Serial.println("Connecting to wifi...");
}
Serial.print("Wifi connected, IP address: ");
Serial.println(WiFi.localIP());
}
}
I didn't set a baud in the sketch
That works and it connects because I can ping. If I disconnect my ESP I can't ping. So I'm pinging the correct device
No I didn't know I had to do that =(
Most of my work so far was in reading i2c sensors, and these take time to provide the data (anywhere from 10ms to 100msec), there is no point to hold off other processes and since I need to read several sensors (temp & humidity or several adc lines) there is a state I need to keep and switch based on. This makes the code far more complex compared to a coroutine.
There is indeed an extra cost of stack switching for the coroutine but I'm willing to pay for that. If my approach is accepted the normal user will have no cost whatsoever as he will not override the delay function, but for me I can use any library even if it calls delay inside my coroutine as I will replace the delay and check if it is in a coroutine now and use my coroutine delay which will switch away and return when the time has come to continue.
consider exposing another function like CoDelay ().
@Makuna but then I need to modify every library I use, I can do that and will if the weak symbol is not acceptable, it's just a bit more tedious and requires a review of each library I integrate. I'm not espousing making everyone use such a threading library as it requires some care, but given the right care it makes other code simpler and easier to follow. Which means I can care once for the hard part of the threading and coroutine and later on enjoy easier development.
I'm too lazy to work hard to code a state machine for each sensor I want to monitor :-)
I'm also used to using coroutines elsewhere and find them very appealing
If anyone can point me in the direction of what I'm doing wrong I'd be very appreciative. My ultimate goal is to have my Wemos subscribe to a topic and turn a servo based on a message published to that topic. My Wemos is connecting to my WiFi and it is connecting to the MQTT broker. I have a topic /log and /status and when I send a message to the command topic the Wemos is responding correctly in the log topic with "Command [command] received". In my status topic the Wemos is reporting "Connected" once it's rebooted. The problem I'm obviously having is making the Wemos turn the servo when a specific command is received. I'm new to this and I thought what I had would work, but obviously it's not. Also for some reason my Serial monitor refuses to work. If anyone can take a look at my code it would be a massive help, thanks. https://www.pastery.net/hxerce/
Works now
I have a full rotation servo, I have it working and it's turning open/close perfect. The servo is turning my blinds open/closed essentially, but since it's a continuous rotation servo I thought of a possible problem. If the blinds are fully closed and the message is sent to close the blinds the servo will obviously attempt to make a rotation, but will be unable to. Is there a way to read the servo position say at the open position, and recall that position? So that I could, in theory make the blinds recall the "safe" position before making another rotation? This way if the blinds try to rotate closed and are already closed the servo will first move to the safe position then close. Is something like that possible? I read into servo.read() but it doesn't seem like that will work.
Could I attach like a paper clip to the servo in the down position, make it hit something metal, wire it to the esp and measure continuity?
So when the metal is touching don't spin
@/all I'm planning to ask each person who contributed to this esp8266 core for a permission to relicense the code under Apache 2.0 license.
This obviously excludes any code inherited from arduino.cc, and any libraries which were not originally written in the scope of this project.
The reason behind this request is to reuse esp8266 code in the upcoming ESP32 core. I would like to make it easier for people to use this new core in commercial projects.
This obviously excludes any code inherited from arduino.cc, and any libraries which were not originally written in the scope of this project.
The reason behind this request is to reuse esp8266 code in the upcoming ESP32 core. I would like to make it easier for people to use this new core in commercial projects.