-
I am able to connect via COM3 to my ESP8266, flashed with 1.87, 115000 baud, but cannot see replies to the text sent to device. Please advise on how to resolve
ERROR: RECEIVE ERROR: {"connectionId":14,"error":"frame_error"} Disconnect callback... >>> Disconnected >>> Connecting... Set Slow Write = true [object Object] Connected [object Object] Found a prompt... great! >>> Sending... ---> "echo(0);\nconsole.log(\"<\",\"<<\",JSON.stringify(process.env),\">>\",\">\");echo(1);\n" Sending block "echo(0);\nconsol", wait 50ms Sent Sending block "e.log(\"<\",\"<<\",", wait 50ms Sent Sending block "JSON.stringify(", wait 50ms Sent Sending block "process.env),\">", wait 50ms Sent Sending block ">\",\">\");echo(1)", wait 50ms Sent Sending block ";\n", wait 50ms Sent >>> Sent WARNING: No result found - just got "" Device found (connectionId=15) >>> Connected to port COM3
-
I've solved the problem. I now can write applications that allow ESP to get it's SSID/pass from the users. Might later add ability to "scan" available AP's, but content with this for now.
Feel free to share:
https://github.com/wga22/esp8266/blob/master/espurino/AP_test.js -
-
I am in the last stages of testing my project, code is here.
To power a ATX power supply put the GPIO2 to pin 16 on ATX power supply and this will turn it on.
-
-
-
@Gordon - safe to assume it requires "reset" to be connected to GPIO16 to work?
-
I found a project on github with similar goals. My "goal" will be to merge in a folder with same code, but for Espurino/ESP8266.
github-wifimanger -
-
Can someone direct me to an example using ESP8266 as access point? As near as I can tell, I am unable to get DHCP to return an IP address for my phone. It doesn't stay connected long enough for me to get to the 192.168.4.1 page.
Here are what my settings look like:
>wifi.getAPIP(); ={ "ip": "192.168.4.1", "netmask": "255.255.255.0", "gw": "192.168.4.1", "mac": "1a:fe:34:da:70:c8" >wifi.getAPDetails() ={ "status": "enabled", "authMode": "wpa2", "hidden": false, "maxConn": 4, "ssid": "will", "password": "password", "savedSsid": null, "stations": [ ] }
-
-
Has someone put into their project a way to initially have their device first run as a host / access point and receive wifi information for subsequent bootup into client/station mode?
This is similar to how you first setup a chromecast to go onto your wifi. Application of this would be to allow your "station device" to be deployed to different wifi routers.
-
-
New code updated
https://github.com/wga22/esp8266/blob/master/espurino/landscape.jsCode for sleeping until the sunset, based upon the wunderground API:
if(nHoursTilSunset > 0) { //add 15 minutes from sunset var nMinutesTilSS = weather.moon_phase.sunset.minute - weather.moon_phase.current_time.minute + 15; var nSleepTime = (nHoursTilSunset*nMilisPerHour) + (nMinutesTilSS*60000); setMode("sleeping until sunset", "Turn on lights", nMilisForLights); setTimeout(turnOnLights, nSleepTime); }
-
-
This project is to build a "modern" landscape light timer from an ATX power supply.
The purpose/features that make this "better" than common setup using a wall timer are:
- Easier ownership - user never has to change the timer to a new time between seasons.
- Efficient - power for ESP8266 chip is less than that consumed by mechanical timer.
- Cost effective - ATX power supplies are readily available, and effecient ones are far more inexpensive than professional 12v lighting equipment power supplies.
- Unique - features ability to turn on/off from webpage (IOT friendly). you can even expose port 80 to internet to control from internet (how many times have you wanted to run your landscape lights from other location (cough, cough)? )
- Fun - for those like me, ability to write code to solve a problem is fun.... (answering critics who say too complex).
- Flexible - ESP Web IDE is still accessible when deployed, so new code can be added easily.
Software design:
The application is written to pull sunset info from wunderground for my location. It then determines how long until sunset, and sleeps. It then runs for predetermined number of hours, turns off, and repeats again the following day.
A webserver is also run on port 80 that allows review of system status, turning on the lights, etc.
The latest version of the software can be found at
https://github.com/wga22/esp8266/blob/master/espurino/landscape.js
Hardware design:
Simple. The ESP8266 is running off of the 5V standby line (via buck converter down to 3.3). The "green" signal line, on the ATX, is pulled to ground via "D4" digital line on the ESP8266, across a 10k resistor to turn on the ATX supply.Pardon the "in progress" look. Still doing testing.
- Easier ownership - user never has to change the timer to a new time between seasons.
-
-
I am thinking the issue is with the wiring of the flasher board I made. I am able to flash with no problems. In run mode, however, doesnt seem to be able to connect to the web ide (used to do with no problems).