tft lcd fritzing quotation

I don’t think inkscape is quirky, I get along with it quite well considering I am a newbie at it. I think the inkscape to Fritzing interaction needs work and I think most of the problems can be solved on the inkscape side of things.

This is slightly misleading in that copper1 is actually under copper0 not silkscreen, but the order should be silkscreen, copper1 with copper0 as a group under copper1 (at present copper1 and copper0 are reversed.) I don’t know of any problem this causes other than Fritzing will prefer to select silkscreen if it is the lowest group (thus a warning rather than an error.)

While this shows as an error (because in schematic it likely is one), in this case it is ignorable, because Fritzing will use the center of the pin as the termination point as was intended. Technically you can and should remove the connectorxterminal elements in breadboard, but it won’t hurt anything. repeats for all the pins on breadboard.

With that done and no major problems, load the part in to Fritzing and test it. This is to catch errors that the script can not (such as a terminalId existing but being in the wrong place). Here is a sketch of a typical test:

Resize and rescale to the proper scale. Copied in the connectors from pcb view via copy/ paste in Inkscape. Resized the tft display to fit inside the connectors (In real life it doesn’t but the connectors won’t work in breadboard that way). Added a rectangle as the underlying board. Resize regroup save and done.

Ungroup, resize rescale. Changed the pin designations to match the board and arrange them to match breadboard. Run the part through the part checking script to catch any typos or errors, zip it to an fzpz and test it in Fritzing (including generating and checking the gerber output). Looks fine, so post it.

Other answer - export your Fritzing breadboard to an image and then use your favorite graphics editor to add your images. Of course, they won"t be part of your schematic or board layout.

Fritzing does have a Parts Editor, and you are supposed to be able to create your own parts. But the documentation is scarce and what does exist is not entirely accurate in my experience.  I gave up trying years ago.

Personally I think that Fritzing is an abandoned project, it hasn"t been updated for over three years and it never made it to version 1.0. Which is really sad as it had a lot of potential.

Hi guys, over the past few tutorials, we have been discussing TFT displays, how to connect and use them in Arduino projects, especially the 1.8″ Colored TFT display. In a similar way, we will look at how to use the 1.44″ TFT Display (ILI9163C) with the Arduino.

The ILI9163C based 1.44″ colored TFT Display, is a SPI protocol based display with a resolution of 128 x 128 pixels. It’s capable of displaying up to 262,000 different colors. The module can be said to be a sibling to the 1.8″ TFT display, except for the fact that it is much faster and has a better, overall cost to performance ratio when compared with the 1.8″ TFT display. Some of the features of the display are listed below;

TheTFT Display, as earlier stated, communicates with the microcontroller over SPI, thus to use it, we need to connect it to the SPI pins of the Arduino as shown in the schematics below.

Please note that the version of the display used for this tutorial is not available on fritzing which is the software used for the schematics, so follow the pin connection list below to further understand how each pin of the TFT display should be connected to the Arduino.

In order to allow the Arduino to work with the display, we need two Arduino libraries; the sumotoy TFT ILI9163C Arduino library which can be downloaded from this link and the popular Adafruit GFX Arduino library which we have used extensively in several tutorials. Download these libraries and install them in the Arduino IDE.

For today’s tutorial, we will be using the bigtest example which is one of the example codes that comes with the sumotoy ILI9163C Arduino library to show how to use the TFT display.

The example can be opened by going to File–>Examples–>TFT_ILI9163c–>bigtest as shown in the image below. It should be noted that this will only be available after the sumotoy library has been installed.

Next, an object of the ILI9163c library named “display” was created with CS and DC parameter as inputs but due to the kind of display being used, we need to include the pin of the Arduino to which the A0 pin of the TFT display is connected which is D8.

In this Arduino touch screen tutorial we will learn how to use TFT LCD Touch Screen with Arduino. You can watch the following video or read the written tutorial below.

As an example I am using a 3.2” TFT Touch Screen in a combination with a TFT LCD Arduino Mega Shield. We need a shield because the TFT Touch screen works at 3.3V and the Arduino Mega outputs are 5 V. For the first example I have the HC-SR04 ultrasonic sensor, then for the second example an RGB LED with three resistors and a push button for the game example. Also I had to make a custom made pin header like this, by soldering pin headers and bend on of them so I could insert them in between the Arduino Board and the TFT Shield.

Here’s the circuit schematic. We will use the GND pin, the digital pins from 8 to 13, as well as the pin number 14. As the 5V pins are already used by the TFT Screen I will use the pin number 13 as VCC, by setting it right away high in the setup section of code.

I will use the UTFT and URTouch libraries made by Henning Karlsen. Here I would like to say thanks to him for the incredible work he has done. The libraries enable really easy use of the TFT Screens, and they work with many different TFT screens sizes, shields and controllers. You can download these libraries from his website, RinkyDinkElectronics.com and also find a lot of demo examples and detailed documentation of how to use them.

After we include the libraries we need to create UTFT and URTouch objects. The parameters of these objects depends on the model of the TFT Screen and Shield and these details can be also found in the documentation of the libraries.

So now I will explain how we can make the home screen of the program. With the setBackColor() function we need to set the background color of the text, black one in our case. Then we need to set the color to white, set the big font and using the print() function, we will print the string “Arduino TFT Tutorial” at the center of the screen and 10 pixels  down the Y – Axis of the screen. Next we will set the color to red and draw the red line below the text. After that we need to set the color back to white, and print the two other strings, “by HowToMechatronics.com” using the small font and “Select Example” using the big font.

Background: I"ve built a handheld (paragliding) flight computer using Teensy 3.0, a GPS module, accelerometer/magnetomer, SD card driver, and rotary encoder. I also have 16x2 LCD display, but will probably ditch it for a 2" TFT. I"m currently using a piezo buzzer, but look forward to getting some better audio output capabilities as you keep up development on the Teensy software. I want to use a small amplifier and speaker for better quality. Due to the nature of my project, I want to move toward getting these components on a PCB fairly soon. My soldered modules are working okay, but it"s clearly a sub 1.0 project and not very durable. I"ve got about a month left before I finalize my hardware and should be ready as soon as I figure out which TFT I want to use. I"ll probably power all of this with a li-poly battery. I intend to submit my code and design to your website when I"m finished.

Question: Do have any Fritzing designs for Teensy 3.0? I"m not an engineer and prefer the simplicity. Are there any other tools you recommend. I intend to drill holes to solder Teensy 3 into my project.

2 Contents Articles 1 Comparison of single-board computers 7 Fritzing 22 List of boards and compatible systems 23 References Article Sources and Contributors 54 Image Sources, Licenses and Contributors 55 Article Licenses License 57

5 3 Official boards Further information: List of boards and compatible systems The original hardware is manufactured by the Italian company Smart Projects. Some -branded boards have been designed by the American company SparkFun Electronics.[2] Sixteen versions of the hardware have been commercially produced to date. Example boards Diecimila in Stoicheia Duemilanove (rev 2009b) UNO Leonardo Mega Nano Due (ARM-based) LilyPad (rev 2007) Shields and -compatible boards make use of shields printed circuit expansion boards that plug into the normally supplied pin-headers. Shields can provide motor controls, GPS, ethernet, LCD, or breadboarding (prototyping). A number of shields can also be made DIY. Example shields Multiple shields can be stacked. In this example the top shield contains a solderless breadboard Screw-terminal breakout shield in a wing-type format Adafruit Motor Shield with screw terminals for connection to motors Adafruit Datalogging Shield with a SD slot and Real-Time Clock chip

22 Comparison of single-board computers 20 Gumstix Overo EarthSTORM + Summit Yes Yes Yes DVI compatible Hackberry A10 Yes Partial DVI incompatible Hiapad Hi-802 Yes Hummingboard Intel NUC MarsBoard A10/A20 New Yes Yes Yes RGB, LVDS pads Composite in/out, VGA MarsBoard RK3066 Yes Yes Yes RGB MinnowBoard MiraBox MK808 MTB025 MYIR MYD-AM335X Yes Yes Yes LCD header Netduino Plus 2 Nitrogen6x Header 3.5 mm, HDMI Yes DVI compatible 3 screen options Parallel RGB Nvidia Jetson TK1 Yes Yes Yes LCD header ODROID-U3 3.5 mm, HDMI micro HDMI ODROID-X2 Yes 3.5 mm, HDMI Yes OLinuXino A10 LIME Yes LCD header OLinuXino A13 base / WIFI Yes Yes LCD header VGA OLinuXino A13 MICRO Pads Yes LCD header VGA OLinuXino A20 LIME Yes LCD header OLinuXino A20 MICRO Yes Yes Yes LCD header VGA 6-pin 1.25 mm step connector Ouya Yes PandaBoard ES Yes 3.5 mm jack, HDMI Yes LCD header DSI, DVI-D (non-standard plug) pcduino Lite Yes pcduino v2 Yes pcduino3 Yes Yes LCD header pcduino3nano Yes PC Engines APU Radxa Rock 3.5 mm, HDMI, S/PDIF 1.4 AV output Raspberry Pi Yes Yes DVI compatible Composite video Rikomagic MK802 / MK802+ / MK802 II HDMI Partial DVI incompatible RIoTboard Yes 3.5 mm, HDMI Yes Yes Snowball Yes Yes

23 Comparison of single-board computers 21 TBS 2910 Matrix Yes Yes UDOO Yes Yes Yes LCD header Ulite 3.5 mm 3.5 mm HDMI 1.4 Optional DVI-D VIA APC 8750 Yes Yes Yes VGA VIA APC Rock Yes Yes Yes VGA VIA EPIA-P Yes Yes Mini-HDMI VGA Wandboard Yes 3.5 mm, S/PDIF Yes expansion board Zealz GK802 Yes Name Mic In Audio Out HDMI LVDS Other Video Out tes ^DVI compatible HDMI signal can be converted to DVI by passive adapter. ^DVI incompatible HDMI signal not convertible to DVI by passive adapter. Watch out for HDMI screens that require DVI signalling. References [1] / www. pcengines. ch/ apu. htm [2] / www. pcengines. ch/ apu1c. htm [3] / www. pcengines. ch/ apu1c4. htm [4] / github. com/ laanwj/ etna_viv External links iqjar.com: An overview and comparison of single board micro computers ( / iqjar. com/ jar/ an-overview-and-comparison-of-todays-single-board-micro-computers/ )

24 Fritzing 22 Fritzing Fritzing Software Developer(s) Interaction Design Lab Potsdam Stable release 0.9.0b / July 14, 2014 Operating system Type License Website Mac OS X, Linux, Windows EDA GNU GPL v3 (software) CC-BY-SA (component images) [1] / www. fritzing. org/ Fritzing is an open source software initiative to support designers and artists ready to move from physical prototyping to actual product. It was developed at the University of Applied Sciences of Potsdam. Goals The software is created in the spirit of Processing and and allows a designer, artist, researcher, or hobbyist to document their -based prototype and create a PCB layout for manufacturing. The complementary website helps to share and discuss drafts and experiences as well as to reduce manufacturing costs. In other words, they make electronic items from your design. Fritzing"s schematic view Fritzing can be seen as an electronic design automation (EDA) tool for non-engineers: the input metaphor is inspired by the environment of designers (the breadboard-based prototype), the output is offering nearly no options and is focused on accessible means of production. Component images are distributed under CC-BY-SA, which will also be the license for any generated breadboard views. Breadboard view of a simple circuit, drawn with Fritzing. Circuit diagram of the same circuit.

25 Fritzing 23 References [1] What license is Fritzing released under ( / fritzing. org/ faq/ #documentcontent) FAQ External links Wikimedia Commons has media related to Fritzing. Official website ( / www. fritzing. org) List of boards and compatible systems This is a non-exhaustive list of boards and compatible systems. It lists boards in these categories: Released under the official name "shield" compatible Development-environment compatible Based on non-atmel processors Where different from the base feature set, compatibility, features, and licensing details are included. Official versions Many versions of the official hardware have been commercially produced to date: Name Processor Format Host interface I/O Release date tes Processor Frequency Dimensions Voltage Flash EEPROM SRAM Digital Digital Analog (kb) (kb) (kb) I/O (pins) I/O with PWM (pins) input (pins) Zero [1] kb ATSAMD21G18 48 MHz USB 3.3 V 256 up to 16 kb by emulation 32 kb May 15, 2014 Yùn [2] Atmega32u4, Atheros AR MHz, 400 MHz 2.7 in 2.1 in [ 68.6 mm 53.3 mm ] USB 5 V 32 kb, 16 MB 1 kb, 0 kb 2.5 kb, 64 MB Yún is September the 10, 2013 [3] combination of a classic Leonardo (based on the Atmega32U4 processor) with a Wifi system on a chip (SoC) running Linino, a MIPS GNU/Linux based on OpenWrt.

29 List of boards and compatible systems LilyPad ATmega168V or 8 MHz ATmega328V 27 wearable 2 in 51 mm V October 17, 2007 This minimalist design is for wearable applications. Pro [4] ATmega168 or 16 MHz 2.05 in 2.1 in UART Serial, FTDI ATmega328 [ 52.1 mm I2C(TWI), 53.3 mm ] SPI 5 V or 16/32 0.5/1 1/ V Designed and manufactured by SparkFun Electronics for use in semi-permanent installations. 4 in 2.1 in 8U2 Mega [ mm MAX3421E ADK 53.3 mm ] USB Host 6.5 in 2.4 in 32u4 ATmega2560 Atmega32u4 16 MHz 16 MHz Esplora Mega 5V July 13, V December Analog [ mm 10, mm ] joystick, four buttons, several sensors, 2 TinkerKit inputs and 2 outputs, LCD connector ATmega32u4 16 MHz Micro 0.7 in 1.9 in 5V [ 17.8 mm vember 8, mm ] This was co-designed by Adafruit. ATmega168 (Pro) Mini (Pro uses ATMega328) 8 MHz 0.7 in 1.3 in 5 V or (3.3 V model) [ 17.8 mm 3.3 V or 16 MHz 33.0 mm ] August 23, 2008 (5 V model) This miniature version of the uses a surface-mounted processor.

34 List of boards and compatible systems 32 SainSmart UNO R3 ATmega328-AU SainSmart Development board compatible with UNO R3 Controller: SMD MEGA328P-AU; A6/A7 port added; 3.3 V/5 V supply voltage and I/O voltage switch. AVR-Duino TavIR Another /Mega compatible board. Brasuíno Holoscópio Based on the Uno with rearranged LEDs and reset button, mini-usb connector, and altered pin 13 circuitry so that the LED and resistor do not interfere with pin function when acting as an input. The Brasuíno was designed using KiCad, and is licensed as GPLv2. ChibiDuino2 ATmega328 TiisaiDipJp Japanese compatible kit using Uno board setting. Includes two mini-b USB sockets, 1602 LCD socket, 5 V or 3.3 V power selection, breadboard area. Cosmo Black Star ATmega328 JT5 layout-compatible board. Based on the Duemilanove. CraftDuino Manufactured and sold by RoboCraft Team.

43 List of boards and compatible systems 41 Jeede ATmega328P JeeLabs Low-cost, low-size, radio-enabled -compatible board running at 3.3 V. Inspired by the Modern Device RBBB (above) with a HopeRF RFM12B wireless module and a modular I/O design supporting a wide range of interfaces. LCDuino [14] ATmega328P Geppetto Electronics LEDuino A combination of an ATMega328P and an i2c based RGB backlit LCD interface (software compatible with the Adafruit RGB LCD shield), along with a USB serial programming interface done as a "backpack" module for the LCD. A board with enhanced I²C, DCC decoder and CAN-bus interfaces. Manufactured using surface mount and sold assembled by Siliconrailway. Moteino [15] ATmega328P LowPowerLab [16] An SD-card size wireless-enabled breadboard friendly compatible board running at 16 MHz/3.3 V. It can mate with either an RFM12B or RFM69W/HW/CW transceiver from HopeRF, allowing very low cost wireless communication (also available without a transceiver). Programmable from the IDE through an FTDI cable/adapter, or directly through the USB interface (Moteino-USB revision). Moteino runs DualOptiboot, [17] a custom version of Optiboot that allows wireless programming when external FLASH memory is present. NavSpark Venus822 (Leon3 SPARC V8 compatible, 100 MHz 32-bit RISC) SkyTraq The modified IDE allows the compiled user sketch to be uploaded onto the processor either with or without the proprietary GNSS software. NavSpark has 17 GPIO pins, which include two UARTs, 1 I²C, 1 SPI, 1 PWM, and a trigger. The first UART is usually used by the GNSS software to output NMEA 0183 data, although this can be disabled. This UART communicates over USB through a PL2303 serial converter and the transmit output is also made available on a pin. A 1 pulse per second signal is produced on a dedicated pin when a valid fix has been made. There is a GPS-only version, a combined GPS/GLONASS version, and a GPS/Beidou version. An adaptor board adds a JST connector for a lithium-ion battery, a charger for the battery, and a microsd card slot connected to the SPI pins. NB1A An -compatible board that includes a battery backed up real-time clock and a four channel DAC. Most -compatible boards require an additional shield for these resources.

46 List of boards and compatible systems 44 SODAQ ATmega328P SODAQ SODAQ, an Compatible Solar Powered sensor board The Raspberry Pi-sized SODAQ board is built for Solar Powered Data Acquisition. It is fitted with a Lipo charge controller and 12 Grove sockets for plug and play prototyping. It runs at 3.3 V and 8 MHz. It also comes with a DS3231 Real Time Clock and 16 Mbit serial flash for data logging. Its "bee" socket can use a range of different modules, like Xbee, RFbee, Bluetoothbee and GPRSbee to make the board communicate. Specifications: Power supply by LiPo battery (3.7 V) or via Micro USB connector Solar charge controller with JST connector for Solar Panel up to 2.5W Battery Monitor DS3231 Real Time Clock and Temperature sensor, clock backup powered by LiPo battery On/Off switch. With the switch in Off position the solar charge circuit is still active and the RTC clock is still powered. ICSP programming header Sparrow ATMega328P Open Home Automation Spider Controller Stickduino Teensy and Teensy++ Teensy 3.0 compatible board designed specifically for RF mesh network experiments. It features 10 IOs, an 10 pin ISP programming connector, a connector for a standard LCD display (in 4 bit mode) and a connector for an 2.4Ghz RF module. Mega compatible board designed specifically for robots requiring large numbers of servos. A built in 3 A switchmode power supply allows servos to plug directly into the board. Pin spacing allows making custom shields from standard prototype board. Similar to a USB key. A pair of boards from PJRC.com that run most sketches using the Teensyduino software add-on to the IDE. A very small board from PJRC.com based on the Freescale MK20DX128VLH5 32-bit ARM Cortex-M4 48 MHz CPU. It has 34 I/O pins; 128 kb of flash; 16-bit ADC; UARTs, SPI, I²C, Touch and other I/O capability.

52 List of boards and compatible systems 50 Goldilocks [27] FPGA Thin Layer Embedded [28] Goldilocks has three UNO Shield compatible sockets and a "helix_4" FPGA Module with Altera Cyclone IV FPGA, DDR2 DRAM, fast SRAM, serial Flash, a MEMs oscillator, power supplies and an Atmel ATSHA204 Authentication IC/EEPROM. The "helix_4" module is notable for castellated edge connectors; it"s designed to be "soldered-down" to a subsequent PCB development. Breadstick [29] FPGA Thin Layer Embedded [28] Breadstick has one UNO Shield compatible socket, 43 GPIO to pin HDRs for breadboarding, and a lower power "helix_4" FPGA Module with Altera Cyclone IV FPGA, fast SRAM, serial Flash, a MEMs oscillator, power supplies and an Atmel ATSHA204 Authentication IC/EEPROM. The "helix_4" module is notable for castellated edge connectors; it"s designed to be "soldered-down" to a subsequent PCB development. References [1] / arduino. cc/ en/ Main/ BoardZero [2] / arduino. cc/ en/ Main/ BoardYun [3] / blog. arduino. cc/ 2013/ 08/ 21/ updating-about-arduino-yun-and-arduino-robot/ [4] arduino.cc ( arduino. cc/ en/ Main/ BoardPro) [5] / www. freetronics. com/ collections/ arduino/ products/ etherten [6] / www. freetronics. com/ collections/ arduino/ products/ ethermega-arduino-mega-2560-compatible-with-onboard-ethernet [7] / www. freetronics. com/ collections/ arduino/ products/ usbdroid [8] / www. freetronics. com/ collections/ arduino/ products/ eleven [9] / www. freetronics. com/ collections/ arduino/ products/ kitten [10] / www. freetronics. com/ collections/ arduino/ products/ etherdue-arduino-due-compatible-with-onboard-ethernet [11] / www. freetronics. com/ collections/ arduino/ products/ arduphone-arduino-compatible-cellphone [12] / dimitech. com [13] / www. bhashatech. com/ boards/ 128-freeduino-nano. html [14] ( www. geppettoelectronics. com/ search/ label/ LCDuino), LCDuino blog [15] lowpowerlab.com ( lowpowerlab. com/ moteino), All about Moteino [16] lowpowerlab.com ( www. lowpowerlab. com/ ) [17] ( github. com/ LowPowerLab/ DualOptiboot) DualOptiboot [18] / learn. adafruit. com/ introducing-trinket [19] / www. adafruit. com

But hey, enough is enough. I’m going to integrate this mechanism into the homeGraph.ino sketch – and expect to achieve at least 3 months of run time on 3x AA (i.e. an average current consumption of under 1 mA total, including the GLCD).

The code has become a bit long to be included in this post – it’s available as homeGraph on GitHub, as part of the GLCDlib project. I’m still amazed by how much a little 200-line program can do in just 11 KB of flash memory, and how it all ends up as a neat custom gadget. Uniquely tailored for JeeLabs, but it’s all open source and easy to adapt by anyone.

The first obvious step is to turn off the Graphics Board backlight – a trivial change, since it can be done under software control. With the dark-on-light version of the GLCD this is certainly feasible, since that display is still quite readable in ambient light.

Right now, the LaOS firmware drives the steppers, using a Gcode interpreter adapted from gbrl, and includes support for Ethernet (TFTP, I believe) and the SD card. It also requires the I2C control panel. As a result, you can send a “job” to this thing via VisiCut, and it’ll save it on the SD card. The I2C-based control panel then lets you pick a job and start it. Quite a good workflow already, although there are still a fair number of rough edges.

Hardware might become too bulky or slow or power-consuming to keep using it, or it might mechanically wear out. But I can still hook up a 40-year old scope and it’ll serve me amazingly well. Even when measuring the latest chips or MOSFETs or LCDs or any other stuff that didn’t exist at the time.

BTW, if you’re looking for a DIY design which is coming along very nicely, check out the EEVblog episode list, where Dave Jones has over half a dozen fascinating videos about how he is designing a really nice Arduino-compatible power supply, with all the bells and whistles you might be after: finely programmable voltage and current range, an LCD display, rotary switches for adjustment, etc. Here’s the first one in the series.

Don’t get me wrong: technically that’s an astonishing achievement. It’s not just copying a few bytes and setting a few pixels. It’s (always!) performing the emulated-persistence trick – because with persistence turned off, I still see a glitch every few seconds, which means that the LCD display is showing the glitch for a substantial fraction of a second – much longer than the 1 µs (or even 500 µs) sweep rate would suggest. Besides, you can see that fading is also implemented, so it’s not just drawing pixels but actually fooling around with color intensities.

Fritzing is an open-source initiative to support designers, artists, researchers and hobbyists to work creatively with interactive electronics. We are creating a software and website in the spirit of Processing and Arduino, developing a tool that allows users to document their prototypes, share them with others, teach electronics in a classroom, and to create a pcb layout for professional manufacturing.

Update 2: I realised that this is a 20-pin LCD screen and re-reading the datasheet and some online tutorials I switched digital wire connections to pins to the LCD 7-10 (DB0-DB3) - same result and then 11-14 (DB4-DB7) - garbled output, shown below. Still no idea what is wrong.

I did not buy it at that place, but mine looks the same, and the price was similar. I think it was called Sainsmart ..... They are available from many vendors. I just ordered a larger one for comparison and solving the dependencies of pysical resolution of the LCD vs. logical view at the controller interface.

My first approach was an Arduino Mega and a prebuild interface board. The UTFT Arduino library worked, but the interface board was lousy. I had to do so much rework on that board, that at the end it looked like a warfield.

The general Project: I want to set-up a battery operated info-device, which will be activated by an PIR sensor. Since the standby current of the Arduino board is pretty high, I had to switch it off. So I made a little extra board with an ATTiny, the PIR sensor and a PMOS transistor to switch the power. It worked, and had a standby current of about 150 µA, most of that consumed by the PIR Sensor, but it looked not nice. With PyBoard"s low standby current and fast wake-up times, that all can be combined in a single unit. And, since PyBoard runs at 3.3 V, I just have one power level, compared to the 5V and 3.3 V with the Arduino, even if the TFT has to be switched off for power saving. And the SD card is faster. And ...... I may add an ESP8266 for showing a web page too. I have a handfull of them in my drawer. But thats at the far end. Mechanical design comes first.