The nett effect is serial0 can be used for monitoring on PC USB, serial1 or2 or 3 can be used for comms between arduino and ESP8266 to issue the AT commandsĪrduino Uno and a separate FTDI serial to USB breakout board. ![]() Be sure to score a line to separate the copper strips from shorting the adjacent pins.ĮSP8266 and Arduino needs 2 serial comms either 1 hardware 1 software or 2 hardware serial.Īrduino Mega is preferred because of the 4x hardware serial. This is made of a 4x4 veroboard, PCB headers, and jumper header. It runs off 3.3v only can be powered off arduino's 3.3v pin or a separate supply with 3.3v and 500mA. for the context/background info of this setup: Ġ. Check out the 2nd last page for the source code that uses RGB LED as indicator instead of softserial. Yours truly recommends Arduino Mega with ESP8266, using either logic level shifter or voltage divider, and Serial Monitor.Īssuming you only have an ESP8266 and an Arduino, trying to make ends meet without another FTDI breakout board for the softserial, you are not out of luck. The parameters relevant to this setup areĬhoice of "matching" baudrate (e.g 9600, 57600, 115200) for 2 sets of serial comms: ESP8266Arduino, and ArduinoUSB serial monitor (hardware serial or software serial)Ĭhoice of 5v and 3.3v bridging circuitry between Arduino and ESP8266Ĭhoice of Arduino Mega or Uno, that affect the availability of serial comms Due to unforeseen err in documentations/writeups, the following parameters that worked were result of bruteforced effort.Ĭheck out an 2016 update on using ESP8266 the ESP-01 variant without Arduino Mega or Uno by using a DIY maker IoT board URL here: Ĭheck out an 2016 update on the latest offering of the big brother of ESP8266, the ESP32 to be released in 2016 URL: There are a few parameters that will make or break this setup. If you are interested on what doesn't work, read between the lines or skip the steps below till the "what works /does not work" section. To save you from the frustrating moments, let's cut the chase and go straight to what works. ![]() ![]() From a seeming "easy" writeup on the SEEEDstudio official guide, it took many hours trying to troubleshoot the setup to make it to work. After scouring the Internet to find some leads on why the setup via "official" guide has failed, the good reads discovered are placed in the references section. This might discourage the faint-hearted from "looking harder" at the problem. User's posts in discussion forums are good, but the bits and bites of (usable) information are hidden in the troves, hiding deep inside irrelevant comments/posts. For any open source products to be successful or adoption en masse by the "makers"/ "DIY-ers" / "dev" / "etc" an up-to-date and accurate documentation or quick start guide has to be provided.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |