Have done that but privately only during college years in the 1960:es.
PCB involves the etching of copper and I don't want to do that anymore.
(Back then we did it in the campus toilet room and I think we poisoned the system...)
Have done that but privately only during college years in the 1960:es.
PCB involves the etching of copper and I don't want to do that anymore.
(Back then we did it in the campus toilet room and I think we poisoned the system...)
These days you can get some machine in china to do it for you. Ok shipping does cost, and 5 piece minimum usually, but all in all the prices are not unreasonable. Like that it becomes a software learning and some ordering. I shouldn't work with chemicals either i think.
Now a bit further on the ESP-01 track and I will need to hook up the ESP-01 for programming...
I have power supplied from a 2xAA battery box with built-in power switch, so I can start it using the switch.
I am assuming that in order to actually program the f/w I need to pull GPIO-0 to ground during reset so the ESP goes into programming mode, right?
And the serial tx/rx lines have to be connected to my USB-Serial (ttl) converter.
If I do that will the device now be recognized by the programming function (from Arduino or PlatformIO)? Or must I first remove the gnd short on GPIO-0 after power is applied and the RST is released?
Ideally I don't want to add any extra circuitry not needed for the ESP-01 to work.
After programming and when switched OFF/ON it is supposed to be in deep sleep all the time only to be awaken on the reed switch pulling RST to GND for about 100 ms.
There will be one initial run when power is applied as discussed earlier.
Then it does its thing and goes back to deep sleep....
I have set up the MQTT monitoring of the topic it will post to so I believe it is ready to go once I get the firmware on board.
Yes.
Yes, do observe the logic voltage levels though. An ESP-01 is not 5v tolerant (don't let it be told otherwise) so if the logic levels of the programmer are 5v you should use a voltage divider to reduce them.
No it will be in programming mode.
Normal operation will resume once you have GPIO 0 pulled HIGH or free-floating (as well as GPIO 2 & GPIO 1(TX) btw) and the ESP goes through a power cycle.
Should work, Only down side i can think off is that OTA firmware updates can not be managed this way, but that is a minor detail.
I believe all this was explained in you other similar topic
You should not use RST as I explained.
Not done that way for MANY years! Impossible to make a board with such fine pitched traces as needed for some ICs. Now all boards are stripped of all copper. The pattern for the copper is laid down in graphite so it is conductive and then the copper is plated back on top of the graphite pattern. Then more processing to finish the board.
I AM way old...
Did my initial PCB:s for transistor designs in the 1960:es...
I must have missed the explanation somehow. What was it you suggested to do instead ?
Because quite frankly, normally speaking one sets a timer to 'wake up' the ESP8266 from deep sleep, GPIO 16 gets wired to RST, and when the timer expires, GPIO does exactly that, go LOW and pulls RST LOW and this results in the wakeup of the ESP8266. Of course on an ESP-01 GPIO 16 is not exposed, but since wake up is anyway required upon a physical switch being pressed (okay a reed-relay being triggered but essentially the same thing) , what essentially is required is RST being pulled LOW momentarily.
So explain to me what is wrong with that method and what do you think should be done instead ?
That because it's in his other topic on the same subject as I have already pointed out
If there is a duplicate topic, that should be flagged as such, so the moderators can merge it and all information is available to all the people taking part in the conversation. imo the responsibility for alerting the moderators lies with the more experienced forum users or the OP. Regardless of that, i just went thru the tread, but i could not find any explanation by you on why not to use RST pin to wake up the ESP, which is the statement you make in this thread. I will put in the request for a merger with the moderators.
Doesn't really matter as @BosseB seems to have ignored any of my recommendations
It is not possible to have several threads with the same subject AFAICT.
In any case I have not done that so I am also wondering what you are talking about.
I've flagged it anyway, the moderators will have a look and possibly merge the 2.
The issue is of course that even if the topic name is not exactly the same, the project you are seeking assistance and support for is the same. The responses from people in that other topic are not directly visible to people in this one and vice versa which can and will cause duplicate responses and questions, which generally is not efficient and wastes time of people here that are mostly just trying to help (some have some other personal agenda relating to their ego but that is a different matter) and therefore it is against forum rules. (and can be really annoying as is the case here) @jim-p seems to be sure he has already answered your question, i can not find his answer, so i can not refute his response, and most likely he does not want to go into detail again because he knows that he does not have a valid point anyway.
I am going from the pint of view that you are going to test your setup before you plant it on the roof, and as i saw someone recommending a bit of de-bounce circuitry, i am going to second that advice. A smallish Capacitor hafway between 2 pullup resistors in series and GND will probably suffice, and you can play with the capacitor size for best resuls. If the expected pulse is 100ms, your de-bounce should be somewhere in the vicinity of 10-60ms to make sure the ESP comes alive again, but doesn't get multiple resets. I do not share @Railroader concern that a half boot will cause issues, if re-booted again, The ESP takes more than 100ms to go through it's boot cycle, but the cleaner the better.
Seems to be the same project
Seems to be the same hardware
Seems to be the same software.
You seem to be asking the same questions.
I would call it similar
Look harder, read ALL the posts
i do agree with that, but...
So why didn't you just flag it so the moderators can deal with it ?
you are clearly even more lazy than me.
Personally the only thing that i thought of last night was that on most ESP-01 units there actually already is a 10K pullup resistor to RST. This would make the de-bounce circuit i suggested not very effective. As i said before, the whole thing should work anyway. If you do want to use a de-bounce circuit, you can of course locate that 10k resistor and remove it, or move the circuit to the EN pin (aka CH_PD) and see if that works for you.
It has always seemed to me that those pins are duplicates, and although they probably serve a different purpose, it actually doesn't really make sense to have both exposed on an ESP-01, i can think of a few other pins i would rather have exposed.
@BosseB don't get put off by people like Jim. Just focus on the project. I think you should have all the info you need to get it working.
@BosseB or especially people like @Deva_Rishi
Let's let the OP decide who is helpful and nice and who isn't.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.