NowI try to connect it to the Espruino-Web-IDE, but without success. Because I use Linux, I've followed the instructions to add my user to plugdev group and re-login to get this new permissions active.
Incidentally, I've had moderate success with the ESP-12E, at the expense of a massive time commitment but abandoned it's use as it is not an official supported board, and has too few I/O to be practical for my projects under development. caveat emptor
I've still ordered a bunch of esp-Chipsets before I was aware that Espruino exist. So I wan't first go with this stuff, instead of buying additional Stuff like Pico or other thinks.
Because I'm at the very beginning of this hobby... You know what I mean?
Regarding the four steps outlined in post #3, step 2 and 3 are basically the same thing, unless creating a custom build, but uploading/flash of Espruino loads the Espruino interpreter, which is easily accessed using the WebIDE.
Yes, and you'll really grasp it's ease of use with the code file upload panel and command line console input to send immediate commands. Along with the 'debugger' the environment is much faster than attempting the same using Arduino for instance. Limited debug - code, compile, fix syntax, edit, compile, fix logic, wash , lather, rinse, repeat within that environment.
Yes, the authors of the Espruino environment constantly struggle with how to earn an income supporting eagar users such as yourself, while keeping the entire works open-source. Then how to appease the unpaid end-users providing forum support, such as this thread. Although the ambition to start with other devices is understood by all, should it take more than the weekend to get the device you have up and running, IMO you will be light year ahead with an official supported device. I was in your shoes three years ago attempting to do more with less, but found the amount of time required to refactor all the tutorials and forum examples just isn't worth the ten additional dollars or so for an official board. I suppose if you are in your twenties, and 'short on money but long on time', it may be a fun and inexpensive learning experience. But, should you be like myself, 'closer to pushing up lillies than from birth to ones twenties', then time is the limiting factor. (unless you know of someone selling 'time') I have learned that the amount of effort wasted required to make the mods to the tutorials in an attempt to save a few dollars with an off brand board - Just Isn't Worth It!!
My first exposure was with the Pico. Plug-n-go. I had a wild idea that using an inexpensive ESP8266 would solve some coding time. You'll see in those initial threads however, I burned up a ton of time proving myself wrong. Tough to own up to!! I also have learned by getting involved in helping others in the forum is the fastest way to get up and running. While that may seem far feteched, yes I made a few suggestion blunders along the way, but it forces one to 'look the stuff up'. After doing it for quite a while now, I have an innate ability to remember where I 'saw' that documentation, speeding not only assisting others, but also knowing where to get a tid-bit to solve an issue I've had.
In the mean time, while not an ESP8266, get started with some programming using the emulator on the Bangle. Just came across this '8-Ball' demo another individual is working on.
It's not a perfect solution, or even a substitute for coding on the device you currently have, but it does provide some basic interaction to get the juices flowing!!
If I start the ESPruino Web-IDE and connect the Chip, I see that the Chip output something... all the time:
But uploading the example-blink-Script doesn't work. Returend Prompt not detected - upload failed. Trying to recover...
Do you have a tiny test-script for me to upload something?
Is there a documentation to see which commands are supported for the different Chip-types like esp-01, esp-01s, esp32-cam, node-mcu and so on?
I like the low price of ESP-01, but I don't quite like to use it in my project because its design always make me feel like that I'm dealing with an unfinished product. Over the past a couple of months, out of necessity for one of my project, I was forced to spent some time to figure out a better way to use ESP-01 as a WiFi shield.
When you using an ESP8266 as an Arduino, you flash the ESP-01 with Arduino sketch, which overrides the AT-Command firmware and upload it with Arduino core firmware, and allow the ESP-01 to be like a stand-alone Arduino.
By default ESP-01 shipped with the firmware that accept AT-Command via a low-speed serial interface, this is quite different from other WiFi SoC's approach, such as uBlox or TI SoC, where SPI is used for interfacing between the host and the WiFi module, allow tighter integration with the host. Although SPI is a serial interface itself, however, it allows very high speed data exchange simultaneously. Even the nRF24L01 module (from Nordic Semiconductor) which has the same form factor and number of pinouts as ESP-01 utilised SPI interface.
I started my project by trying to communicate with ESP-01 using AT Commands with an STM32 Blue Pill as my host. It is painful dealing with AT Command set because it was designed for human-computer interface in the early 80', where user type in various AT commands on the terminal console, the computer echos a human readable string on the screen, the return data from your AT commands are not well structured and has various length, sometime you received "Send Ok", sometime it is just "Ok", if you asked for IP address, it comes back with a string like "+CIPAP_DEF: 192.168.0.100", as the results, the host has to write a lot of codes to parse different message structures for various situations. To extend the AT Commands for handling today's internet protocols such as TCP, UDP, HTTP and even SSL is just seems to be far stretching. This problem can be solved with a well-written library, however, Ai-Thinker is a hardware company, it probably expecting that Espressif - the maker of ESP8266EX will take care the software. Espressif only provide the AT-command firmware and documentation, and leaves the users to develop the library to handle the parsing of AT-command acknowledgements.
Since writing the parser for various AT commands acknowledgements is tedious, over the past several years, many have tried. The most popular library for ESP-01 AT-command is WiFiEsp, it is however has not been actively maintained since around 3 years ago, and the developer mentioned that he no longer have time to maintain the library. Another library WiFiEspAT requires you to upgrade the ESP-01 firmware to v1.7, and as far as I can tell, all the ESP-01 that you could purchased from Aliexpress or most of the Chinese e-commerce vendor today in 2020 are still shipped with AT Command Firmware v1.1 that was released 4 years ago, you will for sure need to first upgrade the firmware before you could using the library, so it is not for users who are new to ESP-01.
Half way through of writing my own library, I encountered a library that is well-written with a lot of code comments and quite stable to use. It is however only support HTTP web client, and does not support web server functionality, but this works for me as in most of the IoT applications, you get the data from sensors and send it through a web client to a gateway. So I forked the library and modified it to make it works for STM32 Blue Pill, along the way, I also discovered a bug in parsing the http response packet, so I fixed and host my version of the library LiteESP8266Client at my github. I also wrote another web client example code of using library with a public-accessible web server so it is easier to test during the development without need to worry about setup a server first. To make the code easy to test for my github users, I replaced the actual sensor access with a hard-coded data to simulated the sensor data for the POST request.
This works well if I only send the request to a web server that does not require SSL. But where else nowadays that a web server still using plain HTTP? My project requires the data to be sent to a web server with HTTPS access. This make me to drop what I have done and switch to use the ESP-01 as an Arduino.
Using ESP-01 as an Arduino is as easy as using any other Arduino boards. ESP8266 Core for Arduino provides probably the best documentation among all the Arduino boards, with rich libraries and examples for IoT application development. I use the example code HTTPSRequest.ino that came with ESP8266 libraries with slight modification to suit my requirements, and it works well.
The one on the left is ESP-01 and the one on the right is ESP-01S. Visually, ESP-01 has two LEDs near the PCB antenna, a Blue LED connects to Tx line (GPIO1) and a Red LED as a power indicator. ESP-01S however only has one Blue LED and it is connected to GPIO2 instead. The ESP-01S also added two extra pull-up resistors that you can see between the ESP8266EX chip and the header pins. One of the pull-up resistor is connected between CH_PD and 3v3(VCC) pins.
My experiences in buying ESP-01 online told me that never trust the images you saw on the e-commerce websites from those Chinese sellers, they almost never publish the SPI memory chip capacity information. The image they shown could be an ESP-01 but you are getting an ESP-01S instead or vice versa.
To upload the Arduino sketch to ESP-01 requires a little bit of works on wiring. First, for ESP-01 where it does not have the built-in pull-up resistor on CH_PD pin, you will need to either add a pull-up resistor between CH_PD and 3v3, or connect it directly to 3v3, I personally prefer to solder a 3k-ohm resistor to the pin as you see in the picture so that I don't need to worry about whether I'm dealing with an ESP-01 or ESP-01S.
It will be easier to put ESP-01 into programming mode by adding two push button switches between ground and GPIO0 (Flash button) and RST (Reset button) pins respectively. The two buttons however do not required for normal operation of ESP-01.
3a8082e126