[EN] WiFiClient
After mentioning the ESP8266WiFi class in the previous article. This time, let’s learn how to use the WiFiClient class to write programs on the client side that link to a service or server.

After mentioning the ESP8266WiFi class in the previous article. This time, let’s learn how to use the WiFiClient class to write programs on the client side that link to a service or server.
This article discusses the SPI bus functionality of the Arduino framework for use with the STM32F030F4P6, STM32F103C8, STM32F401, esp8266 and esp32. The operation of this bus requires at least 3 intercommunication cables: SCLK, MISO. and MOSI for transmitting the clock signal between the sender and the receiver. It serves to receive information from the sender. and used for sending information to the recipient.
From the use of 3 signal lines, it is found that data can be transmitted and received simultaneously. This is different from I2C bus communication that uses only one SDA cable to communicate. At the same communication speed, the SPI bus will receive and transmit data without waiting for an idle line, while I2C will have to wait for idle. With this in mind, SPI can send/receive data faster.
In addition, SPI uses a method to select the destination to communicate by instructing the endpoint to know by sending a signal to the SS pin of the terminal. Therefore, when connecting to multiple devices, SPI requires a larger number of pins to operate, while I2C uses device identification to communicate with each other by still using only one SDA cable, which saves more pins.
This article describes the methods of Wire.h, a class for communicating with devices over an I2C bus that uses two signal wires called SDA and SCL to transmit data between them. We have quite a number of articles about this type of communication and used as the main bus to develop devices by yourself and run through the bus, for example, articles on using esp8266 to connect to Arduino Uno or using esp8266 with stm32f030f4p6, etc.
This article is to learn how to use the Pin class which is a subclass in the machine class of Micropython for use with ESP8266 or ESP32 microcontrollers.
Random numbers in Python use the random class, but microcontrollers don’t support as much randomness as in computer systems, so Micropython supports different commands depending on the chip type. This article discusses how to use random with esp8266 and esp32 microcontrollers, which are instructed to just generate random numbers and configure the random seed as follows.
This article takes a detailed look at the Micropython machine.RTC class. The main function of this class is designed to be an RTC (Real-Time Clock) inside the microcontroller for storing date and time. It is more convenient when used with ESP8266 or ESP32 chip because NTP can be accessed to read the date and time from the internet and then store the value into the RTC to enable the accuracy and do not require frequent internet access to read the values again. This saves the use of external RTC circuits as well.
This article describes how Adafruit’s DHT Sensor library is compatible with all Arduino-compatible architectures, making it easier to deploy DHT sensors for humidity and temperature readings across multiple platforms. This article has tested with ESP32, ESP8266, Arduino UNO and stm32f103c and found that it can be used without modifying the code in the working part or having to modify the source code to make it compatible with the platform.
This article describes programming to use the DS1302 (Figure 1), another RTC (Real-Time Clock) IC (previously written to PCF8583 in Python and Arduino C++). And it is a module that is popular for beginners because it is a module in the learning kit of Arduino, IoT, 37-Sensors or 45 Sensors, etc.
From a Python article on how to use pcf8583 as an RTC (Real-time clock) board, we have rewritten the code for Arduino’s C++ programming with esp8266, esp32 and stm32.
This article describes the interrupt and intercept principle with MicroPython, experimented with ESP8266 and ESP32 as a guide to programming an external event response without waiting for the work in progress completed first.