Skip to main content

Talking to your ESP8266 Chip (Wired and Wireless Methods)

In my previous post, I mentioned how to setup our chip ESP8266 NodeMCU.
As a convention throughout the industry, we should have our chip printed "Hello World!" for us.
Firmware had already been installed on our chip. So, the only thing we need is to talk to our chip via Serial Communication Protocols.

I'll categorize communication protocols in two groups: REPL and WebREPLREPL stands for Read Evaluate Print Loop.

In the REPL section, I'll be talking about PuTTY and TeraTerm and in WebREPL section I'll  be talking about only WebREPL sw.


1- Wired REPL Methods

i) PuTTY:


Figure: A new Serial Session is opened thru PuTTY.



Figure: Python Scrips (Hello World)



ii) TeraTerm:

Figure: TeraTerm Serial Connection Settings



Figure: Python Scrips (Hello World)



2- Wireless REPL Methods: 

i) WebREPL:

Using any of the REPL options above (PuTTY or TeraTerm), first we need to install weprepl library onto chip.

import webrepl_setup

Follow the instructions and reboot device afterwards.

Figure: Importing webrepl library using a PuTTY session


Connect your PC to ESP8266 Wifi Access point with the password you've just defined in above steps just like you connect to any Wifi access point. Now you are connected to the Wifi of your Chip. Cool!


Figure: Connection to Wifi Access of ESP8266 Chip



Now, open local or online WebRepl:



Connect to default IP: ws://192.168.4.1:8266/
Type your password when prompted...There we go.

Figure: MicroPython scripts using local WebREPL


Figure: MicroPython scripts using online WebREPL

To summarize, both wired and wireless communication methods with our chip is mentioned in this post. You are totally free to choose whichever is most convenient for you.

Happy MicroCoding !

Comments

Popular posts from this blog

How to change Country/Region of App Store in iOS 10.0.2 on iPhone?

When you moved to any country other than your original country, you need to change the region/country settings of your iPhone/iPad so that you are able to download the apps specifically published for that country/region. 1- Open Settings App. 2- Tap on “iTunes & App Store”. 3- Tap on Apple ID: 4- Tap on “ View Apple ID ”. 5- Then sign in into your iTunes store either with your AppleID/Password or Touch ID . 6- Then, your iTunes account is opened as follows… Tap on " Country/Region" 7- Tap on “ Change Country or Region ”. 8- Select your current country or region from the list. 9- Then tap on “ Agree ” to agree with the Apple Media Services Terms and Conditions. 10- Tap again on “ Agree ” on the pop-up. 11- Now, Billing information on your account is displayed. Insert 3-digit security code at back of your credit card and tap on “ Next ” again. ...

Automatic Cover Letter Generator & Job Application Tracker & Active Contact List Manager (3 in 1)

In this post, I will mention about my current personal project that I have been using to manage and organize my job application process. Name of this project is " Automatic Cover Letter Generator & Job Application Tracker & Active Contact List Manger (3 in 1) ". Automatic Cover Letter Generator (ACLG) part automatically generates Cover Letters, Job Application Tracker (JAT) part helps me out track and organize my job applications and Active Contact List Manager (ACLM) part helps me build my own customized contact list. All of the three parts are good helpers for any job seeker.      MOTIVATION 1- Automatic Cover Letter Generator As a widely accepted analogy, a resume is like an ambassador to your potential  employer; a cover letter is like a bridge between your resume and the employer to introduce you and your resume. As a matter of fact, your cover letter is your very first contact with your potential employer. Knowing the importanc...

STORY: Most Challenging Bug

It was an embedded software running on a specific hardware. Software was consisting of different modules for each task. The functionality that I was testing was related to two different modules which are written by two different developers. Required functionality was not working and test was failing consistently. Then, we debugged the Module-1 with Developer-1, Module-1 seemed to work properly. Then, we debugged the Module-2 with Developer-2, Module-2 also seemed to work surprisingly. Of course, each developer was blaming the other developer for the fault : ) Then I suspected about my own test case and re-reviewed and inspected it again, but test case also seemed as OK. Afterwards, we suspected about the software testing tool and debugged it with the developer of the test tool. Not surprisingly, test tool also seemed to work properly : ). Ooopsss. What is next? The next suspicious guy was the data buses between test tool and the software/hardware. Then we checked data...