esp32 with camera and tft display ov7670 fifo factory

I CAN WALK AGAIN! yaaay.. Back in the lab making videos.This video is the first of a miniseries showing how to interface a camera to a microcontroller (ESP32...

The parts used here are the LOLIN32 microcontroller. Any ESP32 board can be used. The code is currently independent of the actual processor, so you can use also different platforms.

The camera is the cheap OV7670 with FIFO (AL422b). The camera supports up to VGA resolution but the FIFO can only store 3MBit. This is just sufficient for QQVGA or section of higher resolutions.

The “real-time” output is done on the 1.8″ SPI TFT display. Due to the single data line, the update rate is really limited. To be able to run the display on 3.3V the jumper on the back side must be closed.

The pin connections of the devices can also be found in the code. The definitions can be changed except for MOSI and SCK for the SPI interface which is native on these pins on the ESP32. Using other microcontrollers, the corresponding native SPI pins have to be used.

There are some limitations configuring the pins of the ESP32. Pins 34, 35, 36(VP), 39(VN) are read-only. Those can’t be used for I2C, the clock (XCLK) or TFT signals. Pins 0, 2 and 5 are used as boot signals. Those should not be used as inputs to avoid problems while programming. Pin 5 is also attached to the LED on the LOLIN32 board. Pins 6-11 (if available) are a no go since those are wired to the SPI flash memory connected to the ESP32.

[{"id":"9ecc75dd.22e2e8","type":"mqtt in","z":"5a254896.947618","name":"","topic":"home/camera1","qos":"1","broker":"171132c7.ece67d","x":168.8333282470703,"y":222.0666732788086,"wires":[["784e5a67.89db04"]]},{"id":"6bd0fd9c.4f3c14","type":"ui_template","z":"5a254896.947618","group":"d960fd60.7c918","name":"","order":0,"width":"6","height":"5","format":"","storeOutMessages":true,"fwdInMessages":true,"templateScope":"local","x":612.83349609375,"y":222.0667266845703,"wires":[[]]},{"id":"784e5a67.89db04","type":"function","z":"5a254896.947618","name":"camera iframe","func":"msg.template = \"<iframe frameborder="0" width="100%" height="100%" src="http://\" + msg.payload + \""></iframe>\";\nreturn msg;","outputs":1,"noerr":0,"x":408.83337783813477,"y":222.20002460479736,"wires":[["6bd0fd9c.4f3c14"]]},{"id":"171132c7.ece67d","type":"mqtt-broker","z":"","broker":"localhost","port":"1883","clientid":"","usetls":false,"compatmode":true,"keepalive":"60","cleansession":true,"willTopic":"","willQos":"0","willPayload":"","birthTopic":"","birthQos":"0","birthPayload":""},{"id":"d960fd60.7c918","type":"ui_group","z":"","name":"Camera","tab":"e694697d.4bec28","order":1,"disp":false,"width":"6"},{"id":"e694697d.4bec28","type":"ui_tab","z":"","name":"Camera","icon":"dashboard","order":5}]

This project shows how to record images with the ESP32 and the OV7670 camera without FIFO. An SPI TFT display is supported and a basic web server provides the images in the local network.

To get more details about the camera registers and timings please check out the project using the FIFO version and the complete playlist on this series.

The camera is the cheap OV7670 without the FIFO. The camera supports up to VGA resolution.  However, we are not able to fit a whole VGA frame into the memory of the microcontroller.

The “real-time” output is done on the 1.8″ SPI TFT display. Due to the single data line, the update rate is really limited. To be able to run the display on 3.3V the jumper on the back side must be closed.

The pin connections of the devices can also be found in the code. The definitions can be changed except for MOSI and SCK for the SPI interface which is native on these pins on the ESP32.

But there are some limitations. Pins 34, 35, 36(VP), 39(VN) are read-only. Those can’t be used for I2C, the clock (XCLK) or TFT signals. Pins 0, 2 and 5 are used as boot signals. Those should not be used as inputs to avoid problems while programming. Pin 5 is also attached to the LED on the LOLIN32 board. Pins 6-11 (if available) are a no go since those are wired to the SPI flash memory connected to the ESP32.

Next time i have time to work on the I2S/camera code, i promise to make easier to understand and add some comments. In the meantime, here"s the high level overview of I2S usage:

Once camera is configured over SCCB, it starts sending image frames over its parallel output interface (known as DCMI). This interface contains a clock signal, a parallel data bus (usually 8-bit, but sometimes 10- or 12-bit), and at least two signals indicating frame and line boundaries, HREF and VREF (some cameras use HSYNC, VSYNC). Image frames consist of lines, and each line consists of pixels. Each pixel is represented using one or more bytes, depending on pixel format (color representation). HREF indicates when the pixels produced by the camera are valid, and VREF indicate when lines of pixels are valid. Difference between HREF and HSYNC is that HREF is high when pixels are valid, while HSYNC is normally high and goes low between subsequent lines. Same for VREF/VSYNC. Many cameras have registers which allow the function of output pin to be chosen between VREF/VSYNC and HREF/HSYNC. Some cameras also have registers to invert these signals.

I2S peripheral of the ESP32 can work in parallel mode, where it will sample and store parallel input data. It may be helpful to understand that I2S peripheral consists of two parts: the peripheral itself, and the DMA engine. These two parts are connected using a FIFO. The logic of operation of I2S peripheral in camera mode is as follows:

We see that SM_0A0B_0C0D mode provides highest storage density, placing 2 8-bit values into a single 32-bit word. The other two modes place 1 8-bit value into each 32-bit word, with the slight difference that SM_0A0B_0B0C also repeats every value by placing it into the low half-word of the adjacent 32-bit word.

Why do we need this odd SM_0A0B_0B0C mode though? Well, even though it wasn"t originally intended to be used in camera mode, SM_0A0B_0B0C turns out to be useful in cases when camera pixel clock is higher than 10 MHz. In this case, I2S peripheral can not receive the final sample in the line before HREF goes low. This is a slight quirk of I2S hardware of the ESP32. To work around this quirk, we set RX_EOF_NUM to be one less than the real number of bytes per image line, and enable SM_0A0B_0B0C mode. Because of the way in which data is duplicated in this mode, the last 32-bit word written into FIFO will contain both the byte number RX_EOF_NUM - 2 and the final byte, RX_EOF_NUM - 1 (if we count them starting from 0).

Assume an imaginary case when the image is 16 bytes wide. At or below 10MHz, we can use SM_0A0B_0C0D or SM_0A00_0B00 sampling mode, and set RX_EOF_NUM = 16. In case of SM_0A00_0B00, the FIFO will receive 16 32-bit samples:

Next, here"s the case when PCLK is > 10MHz, and SM_0A0B_0C0D mode must be used. RX_EOF_NUM must be set to 15, and the FIFO will receive 15 32-bit samples:

As you can see, the last byte of the image line (u15) was stuffed into the 14th sample. This is not very convenient, but we still can live with this, and this method allows I2S parallel mode to work up to 20MHz PCLK.

In the code this arrangement is called "high speed mode", or "hs_mode". Note/TODO: the code may actually be simplified so that the knowledge of this oddball mode doesn"t trickle into DMA line filters (described later)... this will make the workaround much more self contained and less confusing to the reader.

Next up: DMA engine. As mentioned above, DMA engine is connected to I2S using a FIFO. I2S puts samples into the FIFO. DMA engine reads samples from the FIFO and writes them into ESP32"s DRAM. Where in DRAM does it write them to, though? This is controlled using DMA descriptors. Each DMA descriptor is a small structure (in C language sense) which contains information like:

The structure is called lldesc_t (for "linked list descriptor", because DMA descriptors form a linked list) and is defined in "rom/lldesc.h" header file.

Because DMA descriptor length field is only 12 bits long, we can store an integer up to 4095 bytes in there. Because DMA operates on 32-bit words, that limits the length of DMA buffer to 4092 bytes. Normally we would configure DMA to fetch data from I2S peripheral in chunks, each chunk containing a single image line. However if the line needs more than 4092 bytes to be stored (taking the overhead of the chosen sampling mode into account), it won"t fit into a single DMA buffer. In this case the code in camera.c uses multiple DMA buffers per line, so that each buffer is shorter than 4092 bytes.

When the application starts receiving the frame, it prepares a linked list of several DMA descriptors, with each DMA descriptor pointing to its own DMA buffer. Each DMA descriptor also points to the next DMA descriptor. Once DMA engine is done with a DMA buffer represented by a single DMA descriptor, it loads the next DMA descriptor and starts filling the next buffer.

The final DMA descriptor points to the first DMA descriptor, so that all the DMA descriptors form a ring. DMA engine will keep running while I2S keeps sending it bytes using a FIFO. The total number of bytes which I2S will acquire is written into RX_EOF_NUM register at the beginning of the frame.

Each time DMA engine fills a DMA buffer, I2S interrupt (IN_DONE) is triggered. Interrupt handler (i2s_isr) does some arithmetic to figure out which DMA buffer has been filled, and puts the pointer to the corresponding DMA descriptor into a queue (data_ready). On the other side of the queue, a task (dma_filter_task) is waiting. The objective of this task is to transform the contents of a single DMA buffer (which has RX_EOF_NUM 32-bit samples) into the correct image pixel format. Images can be stored in different formats, such as RGB565 (16 bits per pixel), RGB888 (24 bits per pixel), grayscale (8 bits per pixel), YUV 4:2:2 (16 bits per pixel) and others. dma_filter_task calls a format-specific function (such as dma_filter_grayscale) to extract the needed bytes from I2S samples and store them into the output image buffer (framebuffer).

For example, consider a case when camera is sending data in a YUV format. Y stands for luminance (brightness), U and V stand for two color components. Here is the data layout which camera sends out:

Here one pixel of the image is represented using two bytes: one brightness component and one color component. Note that the two color components are shared between adjacent bytes. This is called color component subsampling, it is done in order to reduce the amount of data to be transferred, taking advantage of the fact that humans are more sensitive to spatial changes in brightness than spatial changes in color. Effectively, color subsampling reduces resolution of color components of the image.

After I2S peripheral performs sampling using SM_0A0B_0C0D mode (assuming that PCLK is <=10MHz), the following samples will be written into the FIFO (and from there, into DMA):

These bytes will be stored into DMA buffer by DMA engine. To produce a grayscale image from this buffer, DMA filter function needs to extract the 3rd byte from each sample, and store these bytes into the output frame buffer:

Comments on the above and corrections are welcome. This description possibly has to be moved into the repository itself, eventually. For now I have left out the description of JPEG mode, as in JPEG mode the concepts of "lines" and "framebuffer" are less obvious.

Seguir una dieta «low carb» es una de las estrategias más frecuentes empleadas en la pérdida de peso. Pero, ¿es necesario? Cuando se clasifican alimentos

"Upper layer" main development board contains ESP32-PICO-D4 SiP, battery connector & charger circuit with LiPo charge status LEDs, Reset & pull-up IO0 buttons, and a green LED on GPIO4.

Clone of the SparkFun ESP32 Thing board. Compact ESP32 based development board with battery connector, and the typical development board component accoutrements.

Version 2.0 of this board (1) corrected polarity labeling on bottom silk-screened battery symbol and (2) changed the LiPo battery connecter direction.

Development board/module with ESP-WROOM-32 module, USB-to-UART, Reset & Boot (IO0) buttons, Li-ion battery connector & charger, two Grove connectors, LED on IO2, and three indicator LEDs.

The ESP32-LyraTD-MSC Audio-Mic HDK (hardware development kit) combines the ESP32-LyraTD-MSC ("audio-mic development board") with a secondary "top" board.

The ESP32 touch sensor development kit, ESP32-Sense Kit, is used for evaluating and developing ESP32 touch sensor system. ESP32-Sense Kit consists of one motherboard and multiple daughterboards. The motherboard contains a display unit, a main control unit and a debug unit. The daughterboards have touch electrodes in different combinations or shapes, such as linear slider, wheel slider, matrix buttons and spring buttons, depending on the application scenarios. Users can design and add their own daughterboards for special usage cases.

Features an xBee socket with switchable VCC voltage (3.3 V or 5 V), so 2G (SIM800) and 3G (SIM5360) xBee modules will work on it to provide cellular network access.

ESP-WROOM-32 based development board with SH1106 OLED display (128×64 pixels), RJ-45 Ethernet connector, CAN-bus connector, Micro USB connector, USB-to-UART bridge, LiPo battery connector and charging circuit.

Board with MEMS Microphone (ICS-43434) and class-D amplifier embedded 1-channel DAC (Maxim MAX98357A); intended for Amazon Alexa experimentation and development.

ESP32 development board with ePaper display, TI PCM5102A DAC, ICS43434 MEMS Microphone, CP2102N USB-to-UART bridge, microSD card slot, and LiPo charger.

Circular board with ESP-WROOM-32 module, Ethernet (LAN8720A), stereo audio CODEC (WM8978), microphone, 3.5 mm audio receptacle, USB-to-UART bridge (CP2104), Micro USB connector, and SD card slot.

Has column-similar/redundant dual-row connections along the longest sides for easier stand-alone use without a breadboard (but still could be used with a breadboard).

2× Ethernet (optional), 1× Serial Port RS-232/485, OLED 0.96″ 128×64 (optional), power supply with UPS (optional), U.FL (I-PEX) antenna mount(s), and ExCard extension modules support.

SPI0 is permanently reserved for cache access to the flash chip. SPI1 is connected to the same pins via an arbiter and is used to write to flash. You can use SPI1 to also write to other peripherals connected in parallel with the flash (but with another /CS), however, this is tricky to implement because it means you can"t simultaneously access flash anymore. Thats why it"s not in the driver yet.

The esp32 first tries to initialize as a station connecting to an existing wifi network. If it succeeds, you can then open a web browser with the url specified as the IP address of the station http://192.168.1.99

When you connect, the server will transmit a javascript web page from the SPIFFS flash file system and your browser will execute it. The javascript code requests an image, the ESP32 responds by triggering a single camera frame capture to the on-board FIFO, and then reads out and transmits the binary data of the QVGA (320x240) YUV image. The javascript code translates the data into RGB pixels and paints an HTML canvas on your browser page. The whole process is repeated every few seconds to update the image.

If unable to connect to an existing WIFI network, the esp32 will set up as an access point with SSID "ESP32Cam". In this case, first connect to this network, then open your browser and set the url to http://192.168.4.1. Everything else follows as above.

I have a module set up for a negative VSYNC, though in my case, the fifo WRST pin is on the interface connector and has to be connected to VSYNC. And it has a 12MHz oscillator for the OV7670 pixel clock. So it appears to be different than the common examples I"ve seen. Maybe that was why it was so much cheaper (~ $10) ! Anyways, for this module you need to ground the PWDN and OE pins, connect WRST to VSYNC, pullup RST to 3V3 with a resistor (I used 22K) and pullup SCL/SDA pins to 3v3 (I used 4.7K). The STR pin is unconnected. You can find the pin connections to the ESP32 in OV7670.h. I used only pin #s lower than 32 to optimize the set and clear gpio pin functions.

There are lots of examples of code on the net with OV7670 register setups (it"s mostly undocumented registers :-( ). I was only able to get QVGA YUV and RGB565 images working - no luck with VGA. Maybe something to do with the peculiarities of this particular module"s schematic and clock frequency.

Execute "make menuconfig" and set serial flasher com port and baudrate. In OV7670fifo Configuration, set your existing wifi access point SSID name and password. If you are planning to use the esp32 camera as an AP, this is not required.

/components/spiffs_image/image sub-directory. This needs to be done only once, unless you decide to modify the javascript code to do something different - e.g. display monochrome images, do edge detection etc.

Execute "make flash monitor" to build and flash the application code. You can verify the camera initialization and station/access point initialization on the serial debug monitor terminal. The console baudrate is set up as 230400 baud to speedup transmitting of camera frames over the serial port when checking for correct OV7670 register setup. Uncomment #define CAMERA_DEBUG in main.c for this purpose. You will find appropriate python scripts in the toplevel directory for debugging.

Comment out #define CAMERA_DEBUG to run in normal webserver mode. The LED connected to ESP32 pin 21 will flash everytime a new camera frame is captured by the browser.

ESP32 CAM Based Video Surveillance Robot Over WiFi | Ai-Thinker ESP32-CAM Arduino IDE | Ai-Thinker Camera ESP32-CAM in the Arduino. ****************************************************************** If You Want To Purchase the Full Project or Software Code Mail Us: svsembedded@gmail.com Title Name Along With You-Tube Video Link Project Changes also Made according to Student Requirements http://svsembedded.com/ è https://www.svskits.in/ M1: +91 9491535690 è M2: +91 7842358459 ****************************************************************** 1. WiFi Controlled Robot Car Using NodeMCU | V380 Live Camera Monitoring System, 2. ESP32 CAM WiFi Camera Module with Antenna, 3. ESP32 CAM With Pan and Tilt Servo Mount Assembly & Joystick, 4. ESP32 CAM: Video Streaming from RC Car, 5. ESP32 Camera Robot FPV, 6. ESP32 tutorial : Robot controlled with an Android App over WIFI, 7. esp32 Wifi camera demo with face recognition, 8. ESP32 WiFi Robot, 9. ESP32 wireless camera DIY | ESP32-CAM Tutorial, 10. ESP32 with Camera and TFT Display (OV7670, FIFO), 11. ESP32-Cam – Quick Start, 12. ESP32-CAM Camera for Arduino IDE, 13. ESP32-Cam Case with swivel arm, 14. ESP32-CAM Detect Color (Tracking.js), 15. Arducam Mini 2MP SPI Camera Module for Arduino Tutorial, 16. Wireless Surveillance Robot Using Mobile Camera || Chandrabotics, 17. Web Server Controlled Robot, 18. Arduino Based Surveillance Robot with Video Streaming, 19. Arduino DS WiFi Camera Robot - Assembly and Presentation, 20. Arduino Wireless Surveillance Robot 2020, 21. Automatic Security Camera - Motion Detection Camera, 22. Build an Android App to preview the visuals from an IP camera, 23. DIY 3D Printed WiFi Camera Rover based on ESP32 Arduino - The Scout32, 24. DIY Home Surveillance System (Part 2) : RPi IP Camera Display, 25. DIY Surveillance camera with ESP32 CAM, 26. Editing Camera Web Server HTML Source Code for the ESP32-CAM, 27. ESP 32 CAM - Tracking and data logging movements, 28. ESP 32 Camera Streaming video over WiFi |Getting Started with ESP 32 CAM board, 29. ESP 32 Camera with PIR Motion detection via Home Assistant and ESP Home, 30. ESP32 CAM - 10 Dollar Camera for IoT Projects, 31. ESP32 Cam - IP camera on the cheap, 32. ESP32 CAM | Google Vision - AI Camera, 33. ESP-32 Cam + Arduino IDE = IOT Surveillance Car : Arduino Projects For Beginners, 34. Esp32 cam + Blynk, 35. ESP32 CAM Arduino Compatible Wireless Camera Module, 36. ESP32 CAM et servomotor, 37. ESP32 CAM Face Detection Door Lock System, 38. ESP32 CAM Face Recognition Door Lock System, 39. ESP32 CAM Getting Started | Face Detection, 40. ESP32 CAM Surveillance Robot, 41. ESP32 CAM Tutorial | Ai-Thinker | Sathish Deva, 42. ESP32-CAM Face Recognition and Video Streaming with Arduino IDE, 43. ESP32-CAM Face Recognition for Access Control, 44. ESP32-CAM Flashlight enable, 45. ESP32-CAM FPV Wifi Controlled Arduino Tank, 46. ESP32-CAM Hardware modification for Flash LED, 47. ESP32-CAM How to enroll faces using images saved in SD card and recognize face automatically, 48. ESP32-CAM OTTO ROBOT, 49. ESP32-CAM RC CAR, 50. ESP32CAM RC Car Build - ESP32 Camera Test, 51. ESP32-CAM Remote Control Car with Onboard Camera, 52. ESP32-CAM Servo trajectory simulation, 53. ESP32-CAM Surveillance Camera (Home Assistant Compatible), 54. ESP32-CAM Tutorial | LCSC.COM, 55. ESP32-CAM USB-UART PCB, 56. ESP32-CAM Video Streaming and Face Recognition with Arduino IDE, 57. ESP32-CAM Video Surveillance Robot, 58. ESP32-Cam: color detection, 59. ESP32-CAM: Simple AI Robot (Object Detection | Object Tracking | Lane Tracking), 60. ESP32-CAM: Simple Surveillance RC Car, 61. ESP32-CAM| Email Captured Photos stored in SPIFF memory. |NO SD card required, 62. ESP8266 (WiFi) + Camera Tutorial CODE with trig Board & ArduCam, 63. Face Tracking Robot using an ESP32-CAM, 64. Homemade Wi-Fi Fish Feeder With Camera (ESP32-Cam), 65. How to make a Spy camera using ESP-32 cam module, 66. How to make a video camera from the ESP32 module, 67. How to Make Arduino ESP8266 WiFi Robot Car | Controlled with Application, 68. How to Make Your Own Affordable Home Kit Security Camera, 69. How to program ESP-32 cam using Arduino UNO, 70. iRobbie-A video surveillance ESP32-CAM remote controlled robot, 71. Make wireless CCTV camera using Action cam | Arduino project, 72. MOTION TRIGGERED IMAGE CAPTURE AND EMAIL : Using The ESP32-CAM Board And PIR Sensor, 73. one more ESP32 CAMERA by m5stack | Best video streaming ESP 32 so far | ESP32 CAM, 74. OV7670 Camera Module With Arduino Step By Step, 75.Image Recognition for Arduino & Raspberry Pi, 76. Raspberry Pi Remote Camera with motionEyeOS - Build a Surveillance System, 77. Simplified Arduino reversed engineered esp32-cam sketch - ESP-WHO, 78. Smart Door Bell using ESP32 Cam/ESP-EYE & Blynk, 79. surveillance spy robot using camera and GSM or women safety patrolling robot using Arduino

OV7670 image sensor, small size, low voltage, providing single-chip VGA camera and image processor all the features. Through the SCCB bus control, you can output the entire frame, sub-sampling, taking a variety of windows, etc.

Resolution 8 affect the data. The product is VGA image up to 30 frames / sec. Users can fully control the image quality, data formats and transmission.

Omni Vision image sensor applications unique sensor technology, by reducing or eliminating optical or electronic defects such as fixed pattern noise, prop tail, floating powder, etc., to improve image quality, get a clear and stable color image.

This library enables you to use ISR-based PWM channels on AVR ATmega164, ATmega324, ATmega644, ATmega1284 with MCUdude MightyCore, to create and output PWM any GPIO pin

This library enables you to use Hardware-based PWM channels on Arduino AVR ATtiny-based boards (ATtiny3217, etc.), using megaTinyCore, to create and output PWM to pins.

This library enables you to use ISR-based PWM channels on Arduino AVR ATtiny-based boards (ATtiny3217, etc.), using megaTinyCore, to create and output PWM any GPIO pin.

Small low-level classes and functions for Arduino: incrementMod(), decToBcd(). strcmp_PP(), PrintStr, PrintStrN, printPad{N}To(), printIntAsFloat(), TimingStats, formUrlEncode(), FCString, KString, hashDjb2(), binarySearch(), linearSearch(), isSorted(), reverse(), and so on.

Cyclic Redundancy Check (CRC) algorithms (crc8, crc16ccitt, crc32) programmatically converted from C99 code generated by pycrc (https://pycrc.org) to Arduino C++ using namespaces and PROGMEM flash memory.

Write decimal numbers, hex numbers, temperature, clock digits, characters, and strings to the seven segment LED modules supported by the AceSegment library.

Date, time, timezone classes for Arduino supporting the full IANA TZ Database to convert epoch seconds to date and time components in different time zones.

Useful Arduino utilities which are too small as separate libraries, but complex enough to be shared among multiple projects, and often have external dependencies to other libraries.

Fast and compact software I2C implementations (SimpleWireInterface, SimpleWireFastInterface) on Arduino platforms. Also provides adapter classes to allow the use of third party I2C libraries using the same API.

Enables Bluetooth® Low Energy connectivity on the Arduino MKR WiFi 1010, Arduino UNO WiFi Rev.2, Arduino Nano 33 IoT, Arduino Nano 33 BLE and Nicla Sense ME.

ESP32 + LwIP ENC28J60, including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

ESP32 + LwIP W5500 / ENC28J60, including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

ESP32 + LwIP W5500, including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

(ESP8266 + LwIP W5500 / W5100(S) / ENC28J60) Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

Simple Async HTTP Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of AsyncTCP library for ESP32/S2/S3/C3, WT32_ETH01 (ESP32 + LAN8720), ESP32 using LwIP ENC28J60, W5500, W6100 or LAN8720.

Simple Async HTTP Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of AsyncTCP libraries, such as AsyncTCP, ESPAsyncTCP, AsyncTCP_STM32, etc.. for ESP32 (including ESP32_S2, ESP32_S3 and ESP32_C3), WT32_ETH01 (ESP32 + LAN8720), ESP32 with LwIP ENC28J60, W5500 or W6100, ESP8266 (WiFi, W5x00 or ENC28J60) and currently STM32 with LAN8720 or built-in LAN8742A Ethernet.

Simple Async HTTP Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of AsyncTCP_RP2040W library for RASPBERRY_PI_PICO_W with CYW43439 WiFi.

Simple Async HTTPS Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of AsyncTCP_SSL library for ESP32/S2/S3/C3, WT32_ETH01 (ESP32 + LAN8720), ESP32 using LwIP ENC28J60, W5500, W6100 or LAN8720.

Simple Async HTTPS Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of AsyncTCP_SSL library for ESP32 (including ESP32_S2, ESP32_S3 and ESP32_C3), WT32_ETH01 (ESP32 + LAN8720) and ESP32 with LwIP ENC28J60, W5500 or W6100.

Fully Asynchronous UDP Library for ESP8266 using W5x00 or ENC28J60 Ethernet. The library is easy to use and includes support for Unicast, Broadcast and Multicast environments.

Fully Asynchronous UDP Library for RASPBERRY_PI_PICO_W using CYW43439 WiFi with arduino-pico core. The library is easy to use and includes support for Unicast, Broadcast and Multicast environments.

Fully Asynchronous UDP Library for Teensy 4.1 using QNEthernet. The library is easy to use and includes support for Unicast, Broadcast and Multicast environments.

ESP32 + LwIP LAN8720, including WT32-S1, ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

This library provides a low-level facility for context switching between multiple threads of execution and contains an implementation of asymmetric stackful coroutines on an AVR micro-controller.

The last hope for the desperate AVR programmer. A small (344 bytes) Arduino library to have real program traces and to find the place where your program hangs.

This library enables you to use Hardware-based PWM channels on AVR-based boards, such as Nano, UNO, Mega, Leonardo, 32u4, etc., to create and output PWM.

This library enables you to use ISR-based PWM channels on AVR-based boards, such as Mega-2560, UNO,Nano, Leonardo, etc., to create and output PWM any GPIO pin.

Enable inclusion of both ESP32 Blynk BT/BLE and WiFi libraries. Then select one at reboot or run both. Eliminate hardcoding your Wifi and Blynk credentials and configuration data saved in either LittleFS, SPIFFS or EEPROM.

Simple Ethernet Manager for MultiBlynk for Teensy, SAM DUE, SAMD21, SAMD51, nRF52, ESP32, ESP8266, RP2040-based (Nano_RP2040_Connect, RASPBERRY_PI_PICO) boards, etc. with or without SSL, configuration data saved in ESP8266/ESP32 LittleFS, SPIFFS, nRF52/RP2040 LittleFS/InternalFS, EEPROM, DueFlashStorage or SAMD FlashStorage.

Simple Blynk Credentials Manager for STM32 boards using built-in LAN8742A Ethernet, LAN8720, ENC28J60 or W5x00 Ethernet shields, with or without SSL, configuration data saved in EEPROM.

Simple GSM shield Credentials Manager for Blynk and ESP32 / ESP8266 boards, with or without SSL, configuration data saved in LittleFS / SPIFFS / EEPROM.

Simple WiFiManager for Blynk and ESP32 with or without SSL, configuration data saved in either SPIFFS or EEPROM. Enable inclusion of both ESP32 Blynk BT/BLE and WiFi libraries. Then select one at reboot or run both. Eliminate hardcoding your Wifi and Blynk credentials and configuration data saved in either LittleFS, SPIFFS or EEPROM. Using AsyncWebServer instead of WebServer, with WiFi networks scanning for selection in Configuration Portal.

Simple GSM shield Credentials Manager for Blynk and ESP32 / ESP8266 boards, with or without SSL, configuration data saved in LittleFS / SPIFFS / EEPROM.

Simple Async WiFiManager for Blynk and ESP32 (including ESP32-S2, ESP32-C3), ESP8266 with or without SSL, configuration data saved in either LittleFS, SPIFFS or EEPROM. Now working with new ESP8266 core v3.0.1 and ESP32 core v1.0.6

Simple WiFiManager for Blynk with MultiWiFi Credentials, for Mega, SAM DUE, SAMD21, SAMD51, nRF52, STM32F/L/H/G/WB/MP1, Teensy, RP2040-based RASPBERRY_PI_PICO, etc. boards running ESP8266/ESP32-AT shields. Configuration data saved in EEPROM, EEPROM-emulated FlashStorage_STM32 or FlashStorage_SAMD, SAM-DUE DueFlashStorage or nRF52/TP2040 LittleFS.

Simple WiFiManager for Blynk and ESP32 (including ESP32-S2, ESP32-C3), ESP8266 with or without SSL, configuration data saved in either LittleFS, SPIFFS or EEPROM. Now working with new ESP8266 core v3.0.0 and ESP32 core v1.0.6

Simple WiFiManager for Blynk and Mega, UNO WiFi Rev2, Teensy, SAM DUE, SAMD21, SAMD51, STM32, nRF52, RP2040-based boards, etc. using WiFiNINA shields, configuration data saved in EEPROM, FlashStorage_SAMD, FlashStorage_STM32, DueFlashStorage, nRF52/RP2040 LittleFS

An Arduino library that takes input in degrees and output a string or integer for the 4, 8, 16, or 32 compass headings (like North, South, East, and West).

CRMui3 WebFramework build a web app (Web UI) for ESP8266 and ESP32 in your project in minutes! / CRMui3 WebFramework для esp8266 и esp32. Позволяет быстро и просто создать веб интерфейс для настройки и управления устройством.

DDNS Update Client Library for SAM DUE, nRF52, SAMD21/SAMD51, STM32F/L/H/G/WB/MP1, AVR Mega, megaAVR, Teensy, RP2040-based RASPBERRY_PI_PICO, WT32_ETH01, Portenta_H7, etc. besides ESP8266/ESP32, using ESP8266-AT/ESP32-AT WiFi, WiFiNINA, Ethernet W5x00, ENC28J60, LAN8742A or Teensy NativeEthernet

AS7341 is a 11 channel visible light sensor, which can measure 8 wavelengths of visible light, suitable for color detection, light color temperature detection and other scenes(SKU:SEN0365)

This Bluetooth module features Bluetooth/U-disk/TF-card playback, and Bluetooth call function, supporting simple and clear serial port control function, BLE pass-through, and SPP pass-through functions(SKU:DFR0781)

Library to detect a double reset, using EEPROM, DueFlashStorage, FlashStorage_SAMD, FlashStorage_RTL8720, FlashStorage_STM32 or LittleFS/InternalFS. For AVR, Teensy, SAM DUE, SAMD, STM32F/L/H/G/WB/MP1, nRF52, RP2040-based Nano_RP2040_Connect, RASPBERRY_PI_PICO, RTL8720DN, MBED nRF52840-based Nano_33_BLE, Portenta_H7, etc. boards. Now using efficient FlashStorage_STM32 library and supporting new RP2040-based Nano_RP2040_Connect, Portenta_H7, RASPBERRY_PI_PICO and STM32 core v2.0.0

Directly interface Arduino, esp8266, and esp32 to DSC PowerSeries and Classic security systems for integration with home automation, remote control apps, notifications on alarm events, and emulating DSC panels to connect DSC keypads.

This library enables you to use Hardware-based PWM channels on Arduino AVRDx-based boards (AVR128Dx, AVR64Dx, AVR32Dx, etc.), using DxCore, to create and output PWM.

This library enables you to use ISR-based PWM channels on Arduino AVRDx-based boards (AVR128Dx, AVR64Dx, AVR32Dx, etc.), using DxCore, to create and output PWM any GPIO pin.

Small and easy to use Arduino library for using push buttons at INT0/pin2 and / or any PinChangeInterrupt pin.Functions for long and double press detection are included.Just connect buttons between ground and any pin of your Arduino - that"s itNo call of begin() or polling function like update() required. No blocking debouncing delay.

Arduino library for controlling standard LEDs in an easy way. EasyLed provides simple logical methods like led.on(), led.toggle(), led.flash(), led.isOff() and more.

OpenTherm Library to control Central Heating (CH), HVAC (Heating, Ventilation, Air Conditioning) or Solar systems by creating a thermostat using Arduino IDE and ESP32 / ESP8266 hardware.

ESP32 (including ESP32-S2, ESP32-S3 and ESP32-C3), ESP8266 WiFi Connection Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

Light-Weight MultiWiFi/Credentials Async WiFiManager for ESP32 (including ESP32-S2, ESP32-S3 and ESP32-C3) and ESP8266 boards. Powerful-yet-simple-to-use feature to enable adding dynamic custom parameters.

Start serving a local webpage if cannot connect to WiFi, also include Buffer for to WiFi client to prevent small packets with partial messages being sent.

This library providing the possibility to call a function at specific ESP32 Control module.This library support all version of ESP32 Control module,ERS ,E1.0

This library providing the possibility to call a function at specific ESP32 Control module.This library support all version of ESP32 Control module,ERS ,E1.0

A library for driving self-timed digital RGB/RGBW LEDs (WS2812, SK6812, NeoPixel, WS2813, etc.) using the Espressif ESP32 microcontroller"s RMT output peripheral.

ESP32LitePack, M5Lite, A lightweight compatibility library. Support Devices:M5StickC, M5StickC Plus, M5Stack BASIC, M5Stack GRAY, M5Stack FIRE, M5Stack Core2, M5Stack ATOM Lite, M5Stack ATOM Matrix, M5Stack ATOM ECHO

Simple library for sending and recieving booleans, bytes, integers, and float variables over UDP. The esp32 can be connected to a wifi network or create its own hotspot.

ESP32 + LwIP ENC28J60, including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

(ESP32 + LwIP W5500 / ENC28J60), including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager, with enhanced GUI and fallback Web ConfigPortal.

This library enables you to use Interrupt from Hardware Timers on an ESP32, ESP32_S2, ESP32_S3 or ESP32_C3-based board to create and output PWM to pins.

ESP32 + LwIP W5500, including ESP32-S2, ESP32-S3 and ESP32-C3, Connection and Credentials Manager using AsyncWebServer, with enhanced GUI and fallback Web ConfigPortal.

Simple WebServer library for AVR, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52, SIPEED_MAIX_DUINO and RP2040-based (RASPBERRY_PI_PICO) boards using ESP8266/ESP32 AT-command shields with functions similar to those of ESP8266/ESP32 WebServer libraries

WizFi360/ESP8266/ESP32-AT library for Arduino providing an easy-to-use way to control WizFi360/ESP8266-AT/ESP32-AT WiFi shields using AT-commands. For AVR, Teensy, SAM DUE, SAMD21, SAMD51, STM32, nRF52, SIPEED_MAIX_DUINO and RP2040-based (Nano_RP2040_Connect, RASPBERRY_PI_PICO, etc.) boards using WizFi360/ESP8266/ESP32 AT-command shields.

WiFi/Credentials Manager for nRF52, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, RP2040-based Nano_RP2040_Connect, RASPBERRY_PI_PICO, etc. boards using WizFi360/ESP8266/ESP32-AT-command shields with fallback web configuration portal. Credentials are saved in EEPROM, SAMD FlashStorage, DueFlashStorage or nRF52/RP2040 LittleFS.

Light-Weight WiFi/Credentials Manager for AVR Mega, SAM DUE, SAMD, nRF52, STM32, RP2040-based Nano_RP2040_connect, RASPBERRY_PI_PICO boards, etc. using WizFi360/ESP8266/ESP32-AT-command shields. Powerful-yet-simple-to-use feature to enable adding dynamic custom parameters.

Library to detect a multi reset within a predetermined time, using RTC Memory, EEPROM, LittleFS or SPIFFS for ESP8266 and ESP32, ESP32_C3, ESP32_S2, ESP32_S3

Library to configure MultiWiFi/Credentials at runtime for ESP32 (including ESP32-S2, ESP32-S3 and ESP32-C3) and ESP8266 boards. With enhanced GUI and fallback web ConfigPortal.

Light-Weight MultiWiFi/Credentials Manager for ESP32 (including ESP32-S2, ESP32-S3 and ESP32-C3) and ESP8266 boards. Powerful-yet-simple-to-use feature to enable adding dynamic custom parameters.

Simple Ethernet WebServer, HTTP Client and WebSocket Client library for AVR, AVR Dx, Portenta_H7, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52 and RASPBERRY_PI_PICO boards using Ethernet shields W5100, W5200, W5500, W6100, ENC28J60 or Teensy 4.1 NativeEthernet/QNEthernet

Simple TLS/SSL Ethernet WebServer, HTTP Client and WebSocket Client library for for AVR, Portenta_H7, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52 and RASPBERRY_PI_PICO boards using Ethernet shields W5100, W5200, W5500, ENC28J60 or Teensy 4.1 NativeEthernet/QNEthernet. It now supports Ethernet TLS/SSL Client.

Simple TLS/SSL Ethernet WebServer, HTTP Client and WebSocket Client library for STM32F/L/H/G/WB/MP1 boards running WebServer using built-in Ethernet LAN8742A, Ethernet LAN8720, W5x00 or ENC28J60 shields. It now supports Ethernet TLS/SSL Client.

EthernetWebServer_STM32 is a simple Ethernet WebServer, HTTP Client and WebSocket Client library for STM32F/L/H/G/WB/MP1 boards using built-in Ethernet LAN8742A, LAN8720, Ethernet W5x00 or ENC28J60 shields

Simple Ethernet library for AVR, AVR Dx, Portenta_H7, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52 and RASPBERRY_PI_PICO boards using Ethernet shields W5100, W5200, W5500, W5100S, W6100

Simple Ethernet Manager for Teensy, SAM DUE, SAMD, nRF52, ESP32 (including ESP32-S2/C3), ESP8266, RP2040-based Nano_RP2040_Connect, RASPBERRY_PI_PICO, etc. boards. Config data saved in ESP LittleFS, SPIFFS or EEPROM, nRF52 LittleFS, EEPROM, DueFlashStorage or SAMD FlashStorage.

Simple Ethernet Manager for STM32F/L/H/G/WB/MP1 boards with Ethernet LAN8720, W5x00, ENC28J60 or built-in LAN8742A shields, with or without SSL, configuration data saved in EEPROM. With DoubleResetDetect feature.

ezTime - pronounced "Easy Time" - is a very easy to use Arduino time and date library that provides NTP network time lookups, extensive timezone support, formatted time and date strings, user events, millisecond precision and more.

ESP32 VGA, PAL/NTSC Color Composite, SSD1306 ILI9341 ST7789 Controller, PS/2 Mouse and Keyboard Controller, Graphics Library, Graphical User Interface (GUI), Sound Engine, Game Engine and ANSI/VT Terminal

A library for implementing fixed-point in-place Fast Fourier Transform on Arduino. It sacrifices precision and instead it is way faster than floating-point implementations.

The FlashStorage_RTL8720 library aims to provide a convenient way to store and retrieve user data using the non-volatile flash memory of Realtek RTL8720DN, RTL8722DM, RTM8722CSM, etc.

The FlashStorage library aims to provide a convenient way to store and retrieve user"s data using the non-volatile flash memory of SAMD21/SAMD51. It"s using the buffered read and write to minimize the access to Flash. It now supports writing and reading the whole object, not just byte-and-byte.

The FlashStorage_STM32 library aims to provide a convenient way to store and retrieve user data using the non-volatile flash memory of STM32F/L/H/G/WB/MP1. It is using the buffered read and write to minimize the access to Flash. It now supports writing and reading the whole object, not just byte-and-byte. New STM32 core v2.0.0+ is also supported now.

The FlashStorage_STM32F1 library aims to provide a convenient way to store and retrieve user"s data using the non-volatile flash memory of STM32F1/F3. It"s using the buffered read and write to minimize the access to Flash. It now supports writing and reading the whole object, not just byte-and-byte. New STM32 core v2.0.0+ is supported now.

FTP Client for Generic boards such as AVR Mega, megaAVR, Portenta_H7, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52, RP2040-based (Nano-RP2040-Connect, RASPBERRY_PI_PICO, RP2040W, etc.), ESP32/ESP8266 using Ethernet

The GCodeParser library is a lightweight G-Code parser for the Arduino using only a single character buffer to first collect a line of code (also called a "block") from a serial or file input and then parse that line into a code block and comments.

Basic to advanced line following, intersection detection, basic motor control, battery monitoring, gripper control, and basic collision detection with the Gobbit robot.

Enables GSM/GRPS network connection using the Generic GSM shields/modules. Supporting ESP32 (including ESP32-S2, ESP32-C3), ESP8266, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52, RP2040-based boards, etc.

Arduino library for the Flysky/Turnigy RC iBUS protocol - servo (receive) and sensors/telemetry (send) using hardware UART (AVR, ESP32 and STM32 architectures)

This library provides an interface to control a stepper motor through Infineon’s Stepper Motor Control Shield "KIT_XMC1300_IFX9201" with h-bridge IFX9201 and XMC1300 microcontroller.

Treat PCF8574, MCP23017 and Shift registers like pins, matrix keypad, touch screen handler, button press and rotary encoder management (switches) on any supported IO (including DfRobot & Joysticks) with event handling, interchangable AVR/I2C(AT24) EEPROMs.

This library uses polymorphism and defines common interfaces for reading encoders and controlling motors allowing for easy open or closed loop motor control.

LiquidCrystal fork for displays based on HD44780. Uses the IOAbstraction library to work with i2c, PCF8574, MCP23017, Shift registers, Arduino pins and ports interchangably.

LittleFS for esp32 based on esp_littlefs IDF component. Use esp32 core-provided LITTLEFS library instead of this one when available in future core releases.

An all in one, easy to use, powerful, self contained button library so you can focus on your other code! Includes Debouncing, Avoids Delays, multiclicks and allows you to decide what happens at the beginning and end of Short, Long, Hold and Shifts so you can create a intuative and responsive experience.

This library enables you to use ISR-based PWM channels on RP2040-based boards, such as Nano_RP2040_Connect, RASPBERRY_PI_PICO, with Arduino-mbed (mbed_nano or mbed_rp2040) core to create and output PWM any GPIO pin.

Arduino library for MCP4728 quad channel, 12-bit voltage output Digital-to-Analog Convertor with non-volatile memory and I2C compatible Serial Interface

mDNS Library for ESP32, ESP8266, nRF52, SAMD21, SAMD51, SAM DUE, STM32F/L/H/G/WB/MP1, Portenta_H7, AVR Mega, RP2040-based boards, etc. using Ethernet W5x00, ESP WiFi, WiFiNINA or ESP8266-AT shields

This library enables you to use Hardware-based PWM channels on megaAVR-based boards, such as UNO WiFi Rev2, AVR_Nano_Every, etc., to create and output PWM.

This library enables you to use ISR-based PWM channels on an Arduino megaAVR board, such as UNO WiFi Rev2, AVR_Nano_Every, etc., to create and output PWM any GPIO pin.

Replace Arduino methods with mocked versions and let you develop code without the hardware. Run parallel hardware and system development for greater efficiency.

Library to detect a multi reset, using EEPROM, DueFlashStorage, FlashStorage_SAMD, FlashStorage_RTL8720, FlashStorage_STM32 or LittleFS/InternalFS. For AVR, Teensy, SAM DUE, SAMD, STM32F/L/H/G/WB/MP1, nRF52, RP2040-based Nano_RP2040_Connect, RASPBERRY_PI_PICO, RTL8720DN, MBED nRF52840-based Nano_33_BLE, Portenta_H7, etc. boards. Now using efficient FlashStorage_STM32 library and supporting new RP2040-based Nano_RP2040_Connect, RASPBERRY_PI_PICO and STM32 core v2.0.0

Connects to MySQL or MariaDB using ESP8266/ESP32, WT32_ETH01 (ESP32 + LAN8720A), nRF52, SAMD21/SAMD51, STM32F/L/H/G/WB/MP1, Teensy, SAM DUE, Mega, RP2040-based boards, Portenta_H7, etc. with W5x00, ENC28J60 Ethernet, Teensy 4.1 NativeEthernet/QNEthernet, WiFiNINA modules/shields or Portenta_H7 WiFi/Ethernet. W5x00 can use Ethernet_Generic library. ENC28J60 can use either EthernetENC or UIPEthernet Library.

This library enables you to use ISR-based PWM channels on an nRF52-based board using Arduino-mbed mbed_nano core such as Nano-33-BLE to create and output PWM any GPIO pin.

This library enables you to use ISR-based PWM channels on an nRF52-based board using Adafruit_nRF52_Arduino core such as Itsy-Bitsy nRF52840 to create and output PWM any GPIO pin.

The library for OpenBCI Ganglion board. Please use the DefaultGanglion.ino file in the examples to use the code that ships with every Ganglion board. Look through the skimmed down versions of the main firmware in the other examples.

OpenDevice is a set of tools and APIs to build solutions for the "Internet of Things" like home automations systems, robotics, smart city, energy monitoring, security, sensor monitoring

A library written in C++ to encode/decode PDU data for GSM modems. Both GSM 7-bit and UCS-2 16 bit alphabets are supported which mean, in practice, you can send/receive SMS in any language (including emojis).

Simple Async HTTP Request library, supporting GET, POST, PUT, PATCH, DELETE and HEAD, on top of Portenta_H7_AsyncTCP library for Portenta_7, using Vision-shield thernet or Murata WiFi.

This is a library aiming at implementing pid control to control the position of a DC motor with feedback from quadrature encoder using speed control driver that accepts PWM input. It is a multifunctional program with extra feature of tuning the gain parameters and very useful for robotic enthusiast in wheeled robots

his library enables you to use Hardware-based PWM channels on RP2040-based boards, such as Nano_RP2040_Connect, RASPBERRY_PI_PICO, with either Arduino-mbed (mbed_nano or mbed_rp2040) or arduino-pico core to create and output PWM to any GPIO pin.

This library enables you to use SPI SD cards with RP2040-based boards such as Nano_RP2040_Connect, RASPBERRY_PI_PICO using either RP2040 Arduino-mbed or arduino-pico core.

This library enables you to use ISR-based PWM channels on RP2040-based boards, such as ADAFRUIT_FEATHER_RP2040, RASPBERRY_PI_PICO, etc., with arduino-pico core to create and output PWM any GPIO pin.

The most powerful and popular available library for using 7/14/16 segment display, supporting daisy chaining so you can control mass amounts from your Arduino!

Provides methods to retrieve instant and peak values from the ADC input. The Arduino library SensorWLED splits the input from a varying analog signal from the ADC into components, i.e., provides the capability of a sample-and-hold circuit.

A user interface through the serial channel (menus, sub-menus and command execution), with support for navigation through the menu hierarchy and online help.

Enables smooth servo movement. Linear as well as other (Cubic, Circular, Bounce, etc.) ease movements for servos are provided. The Arduino Servo library or PCA9685 servo expanders are supported.

An associative container used either as a list or btree without needing std lib, and a concurrent circular buffer. Works from AVR/Uno upwards to ESP32, mbed etc

Use the low-power high-resolution ICM 20948 9 DoF IMU from Invensense with I2C or SPI. Version 1.2 of the library includes support for the InvenSense Digital Motion Processor (DMP™).

The VL6180 combines an IR emitter, a range sensor, and an ambient light sensor together for you to easily use and communicate with via an I2C interface.

The ZX Sensor uses infrared light to determine the distance from an object and where the object is located on the X axis (between IR LEDs), available from SparkFun Electronics

This is a library aiming at implementing pid control to control the speed of a DC motor with feedback from quadrature encoder. It is a multifunctional program with extra feature of tuning the gain parameters and very useful for robotic enthusiast in wheeled robots

Statistic, Sum, Max, Min, Sq_Sum, Arithmetic Average, Geometric Average, RMS Average, Ext RMS Average, Bubble Sort, Median, Standard Deviation, Standard Deviation Error, Coefficient Factor, Average, Stream, Regression, Slope, Data, Analyse

Enables reading and writing on SD card using SD card slot connected to the SDIO/SDMMC-hardware of the STM32 MCU. For slots connected to SPI-hardware use the standard Arduino SD library.

BufferedPrint stream for efficient networking. ChunkedPrint for HTTP chunked encoding. ChunkedStreamReader for HTTP chunked decoding. CStringBulder builds a c-string with Print class methods. StringReadStream to wrap string as Stream. And printf() function with formatting string from F macro.

Menu library for Arduino with IoT capabilities that supports many input and display devices with a designer UI, code generator, CLI, and strong remote control capability.

Adds tcUnicode UTF-8 support to Adafruit_GFX, U8G2, tcMenu, and TFT_eSPI graphics libraries with a graphical font creation utility available. Works with existing libraries

This library enables you to use Hardware-based PWM channels on Teensy boards, such as Teensy 2.x, Teensy LC, Teensy 3.x, Teensy 4.x, Teensy MicroMod, etc., to create and output PWM to pins. Using the same functions as other FastPWM libraries to enable you to port PWM code easily between platforms.

This library enables you to use ISR-based PWM channels on Teensy boards, such as Teensy 2.x, Teensy LC, Teensy 3.x, Teensy 4.x, Teensy MicroMod, etc., to create and output PWM any GPIO pin.

A library for creating Tickers which can call repeating functions. Replaces delay() with non-blocking functions. Recommanded for ESP and Arduino boards with mbed behind.

This library enables you to use Interrupt from Hardware Timers on supported Arduino boards such as AVR, Mega-AVR, ESP8266, ESP32, SAMD, SAM DUE, nRF52, STM32F/L/H/G/WB/MP1, Teensy, Nano-33-BLE, RP2040-based boards, etc.

A simple library to display numbers, text and animation on 4 and 6 digit 7-segment TM1637 based display modules. Offers non-blocking animations and scrolling!

Really tiny library to basic RTC functionality on Arduino. DS1307, DS3231 and DS3232 RTCs are supported. See https://github.com/Naguissa/uEEPROMLib for EEPROM support. Temperature, Alarms, SQWG, Power lost and RAM support.

Monochrome LCD, OLED and eInk Library. Display controller: SSD1305, SSD1306, SSD1309, SSD1312, SSD1316, SSD1318, SSD1320, SSD1322, SSD1325, SSD1327, SSD1329, SSD1606, SSD1607, SH1106, SH1107, SH1108, SH1122, T6963, RA8835, LC7981, PCD8544, PCF8812, HX1230, UC1601, UC1604, UC1608, UC1610, UC1611, UC1617, UC1638, UC1701, ST7511, ST7528, ST7565, ST7567, ST7571, ST7586, ST7588, ST75160, ST75256, ST75320, NT7534, ST7920, IST3020, IST3088, IST7920, LD7032, KS0108, KS0713, HD44102, T7932, SED1520, SBN1661, IL3820, MAX7219, GP1287, GP1247, GU800. Interfaces: I2C, SPI, Parallel.

True color TFT and OLED library, Up to 18 Bit color depth. Supported display controller: ST7735, ILI9163, ILI9325, ILI9341, ILI9486,LD50T6160, PCF8833, SEPS225, SSD1331, SSD1351, HX8352C.

A rotary encoder library that allows the callback of up to 9 different functions representing the same number of different encoder events. These different functions can be associated with events like press rotate and long press among many others.

RFC6455-based WebSockets Server and Client for Arduino boards, such as nRF52, Portenta_H7, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, Teensy, SAM DUE, RP2040-based boards, besides ESP8266/ESP32 (ESP32, ESP32_S2, ESP32_S3 and ESP32_C3) and WT32_ETH01. Ethernet shields W5100, W5200, W5500, ENC28J60, Teensy 4.1 NativeEthernet/QNEthernet or Portenta_H7 WiFi/Ethernet. Supporting websocket only mode for Socket.IO. Ethernet_Generic library is used as default for W5x00. Now supporting RP2040W

Light-Weight MultiWiFi/Credentials Manager for Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52, RTL8720, etc. boards running Generic WiFi (WiFiNINA, WiFi101, ESP8266-AT, ESP32-AT, etc.) modules/shields. Powerful-yet-simple-to-use feature to enable adding dynamic custom parameters.

Enables network connection (local and Internet) and WiFiStorage for SAM DUE, SAMD21, SAMD51, Teensy, AVR (328P, 32u4, 16u4, etc.), Mega, STM32F/L/H/G/WB/MP1, nRF52, NINA_B302_ublox, NINA_B112_ublox, RP2040-based boards, etc. in addition to Arduino MKR WiFi 1010, Arduino MKR VIDOR 4000, Arduino UNO WiFi Rev.2, Nano 33 IoT, Nano RP2040 Connect. Now with fix of severe limitation to permit sending much larger data than total 4K and using new WiFi101_Generic library

Simple WiFiWebServer, HTTP Client and WebSocket Client library for AVR Mega, megaAVR, Portenta_H7, Teensy, SAM DUE, SAMD21, SAMD51, STM32F/L/H/G/WB/MP1, nRF52, RP2040-based (Nano-RP2040-Connect, RASPBERRY_PI_PICO, RASPBERRY_PI_PICO_W, ESP32/ESP8266, etc.) boards using WiFi, such as WiFiNINA, WiFi101, CYW43439, U-Blox W101, W102, ESP8266/ESP32-AT modules/shields, with functions similar to those of ESP8266/ESP32 WebServer libraries.

Simple WiFiWebServer, HTTP Client, MQTT and WebSocket Client library for Realtek RTL8720DN, RTL8722DM, RTM8722CSM boards using WiFi. Supporting WiFi at 2.4GHz and 5GHz

Universal Timer with 1 millisecond resolution, based on system uptime (i.e. Arduino: millis() function or STM32: HAL_GetTick() function), supporting OOP principles.

Right now I"m working to integrate the data plotter and the image viewer features in the main repository of qSerialTerm. Everything should be ready by next week.

In particular, you should check that you are receiving correct data using the default configuration. Then, test that your SCCB interface is working, you should be able to read the OV7670 registers and see their default values.

When doing the YCbCr -> RGB conversion, be sure to use floats/double when carrying out the operations and then limit the obtained R, G, B values between 0 and 255.

Dang not sure how I missed that one. I was using integer. Even with that change I did not get good color image. I had to use register settings I got from Linux driver to get a good image. Not sure why.

About qSerialTerm, it is a quite useful program. The only reason I have not used is that I would have to compile the program myself. That means I have to setup the whole QT environment. Untill now all my time was used up in debugging the camera.

I"m getting a "correct" color image using the above conversion equations, in the sense that the image doesn"t get distorted. But the colors are no good, because instead of green I see magenta and so on.

I have tested the conversion equations against Octave"s rgb2ycbcr function, and it works fine. Maybe the OV7670 follows another conversion standard?. I have also tried switching Cb <-> Cr without any noticeable change in the color output.

We currently have an OV7670 which correctly gives us test patterns, however gives us terribly saturated images with completely incorrect colours. Are you able to share those register settings, or some us advice about how to set this device up for normal looking images? Thanks very much,

I am currently working on real time image processing using FPGA. For that i am using OV7670 camera module. I have got real time video but with wrong colors(mostly magneta color). Can you please mail me the correct color settings?

if I want to use an external clock, do I have to connect the oscillator between XCLK and ground directly or do I need to add a capacitor in series (XCLK - oscillator - cap - GDN)? If yes, which value for the capacitor?

I have a ceramic resonator @ 16Mhz (http://it.rs-online.com/web/p/risonatori-ceramici/5266154/), but it has 3 pins instead of two. Searching on google I"ve seen the the the central pin must be connected to the ground, but I"m stuck with the others two.

Ceramic resonator require an active oscillator circuit. These active oscillators are usually integrated inside microcontrollers, and you have access to it via two pins usually labelled OSC_IN and OSC_OUT.

The OSC_OUT pin won"t have enough current drive and no clock will be produced. This implies that neither your microcontroller nor the OV7670 will work.

I"m using BeagleBone with QNX. But BeagleBone seems not provide an external clock. If I use an external oscillator (crystal) do I have connect one pin to the XCLK and one to the ground without capacitors?

I"ve just found a pin with an external clock on BeagleBone... :) (my fault!) In this case I suppose I have to connect the pin directly to the XCLK (sharing the same GND). Right?

The STM32 F2/F4 microcontrollers have a DCMI peripheral that simplifies the data reception from the camera. I don"t know if the BeagleBone have something similar.

i have interfaced ov7690 with stm32f4 and PIC. i get data in both rgb565 and yuv422 and reconstuct the image . but the image is not so good. u can look my post at

What do you mean with "the image is not so good"? Are you getting a clear image with the wrong colors or are you getting random pixels? Does the grayscale (only the Y channel) image looks clear?

AFAIK in YUV422 mode, getting the right colors with the OV7670 requires some heavy calibration, as stated by brijesh in his/her comment; but the grayscale version should look clear like the image I posted.

Hi Jorge, nice page you have here, seems you have been studying quite a fair bit on OV7670. I am also working on something similar but using AVR uC instead (Atmega16/32) with OV7670 FIFO version and works pretty well.

I am using YUV mode and using the YUV422 equations give me a pretty good looking image, a bit soft but not bad (http://thinksmallthings.wordpress.com/2012/11/03/ov7670-yuv-demystified/).

I"am unable to read proper image data, SCCB works fine for me and I can read registers, but for example when i"m reading frames with my lens covered i get some random numbers - where as you wrote there should be 128 0 pattern. I"m using camera mode with FIFO buffer embedded. Could you send me your code for reading frames ? Or will you be able to help me with this ? I"m using STM32F103VC

I haven"t used the OV7670 FIFO version and I used the STM32F4 which has a Digital Camera Interface (DCMI) that the STM32F1 doesn"t have. That"s the reason my code won"t really help.

Make sure you are supplying a correct clock (12-24 MHz) to the OV7670 XCLK pin. The SCCB works WITHOUT the XCLK, so a working SCCB doesn"t guarantee a working parallel interface (D0-D7).

I"ve just tried to get SCCB working on my OV7670 (like yours: no FIFO) and it looks like it doesn"t work at all until I connect clock source to XCLK pin. After successful test implementation (got 0x80 from 0x01 register etc) i tried to disconnect XCLK signal and it simply stopped working. So it seems to me that XCLK is necessary for SCCB operation.

In the module I use, (ov7970 without fifo) the DVDD pad (core voltage) is simply filtered to ground via capacitor thus ov7670 will generate 1.8 from DOVDD. This requires the DOVDD to range from 2.45V to 3V.

The (blue) model I used in this post has internal LDO regulators. You must have the (black?) model that is wired directly. I have also used the latter with a 3.3V supply and a series Schottky diode.

You need to drive the XCLK pin with a clock signal to make the OV7670 parallel interface (D0-D7) work to get any image data out of it. Also a user reported here that driving the XCLK pin is also necessary to get the SCCB interface working.

Wow, Jorge, it looks like your post has struck a chord with a number of users! If I may throw another question into the fray, I am thinking about using a microprocessor (thinking mbed, but not sure yet) to sample from multiple OV7670s. I don"t need to capture every frame from every camera, just be able to grab a picture from camera 1, then from 2, etc. at whatever rate the processor can manage. Any thoughts on how one might do this with some sort of bus, or would this require a separate processor for each camera?

(1) Hooking multiple OV7670s to the same uC will require a digital circuit to act as a multiplexer and will increase the capacitive load of the logic lines (XCLK, D0-D7), which can degrade or totally corrupt the data.

(3) The OV7670 outputs raw data, that means each frame of 640x480 color pixels equals a minimum of 600 KiB (YUV422 format). This implies you can"t keep one frame in the uC RAM memory (usually less than 200 KiB), so you"ll need to stream the frame to a bigger memory as soon as possible.

I have only the following parts which are OV7670 and Arduino uno board. I wrote my code and I have to cheange the clock function code to either read or write in the registers of the camera"OV7670". But, I can"t get any response from the camera.

You got me there. I