fritzing ips tft display quotation

I’m mostly finished a modification of the adafruit part to convert it to this. I’m done for tonite and busy tomorrow but a part should be along soon (only pcb and the fzp file to finish). I found board dimensions (if not hole nor header placement which are just guesses) on ebay so it won’t be quite correct unless you can measure the placement of the holes and the pins with calipers but it should do the job. The adafruit part looks to be the alternate layout for this same display (only 10 pins in…

These are nice displays but slow with graphics on an UNO, they recommend only text with the UNO boards due to memory. I tested the graphics on the UNO (Official) and the Elegoo variant UNO boards, both function the same.

I’m mostly finished a modification of the adafruit part to convert it to this. I’m done for tonite and busy tomorrow but a part should be along soon (only pcb and the fzp file to finish). I found board dimensions (if not hole nor header placement which are just guesses) on ebay so it won’t be quite correct unless you can measure the placement of the holes and the pins with calipers but it should do the job. The adafruit part looks to be the alternate layout for this same display (only 10 pins instead of 16, different mounting holes and board size).

Please do note that the Arduino shown in the image above is the classic Arduino Nano. I have this, because there is no library for Maker Nano RP2040 yet inside the Fritzing.

OK here is a part for the display and a basic explaination of what I did to create it. First the part (if you unzip the fzpz file you will have the fzp file and svg files that make up the part) .The breadboard svg is what a svg to load in to parts editor to edit needs to look like.

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.

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:

Doing that points out the problem. The diameter of your pads is slightly too small, they are around 0.075in (when they should be 0.078in) and the stroke width is 20.00025558. If I reset the diameter to 0.078 and the stroke-width to 20, the holes will be the correct 0.038in. However changing the diameter via the tool bar will move the center of the pad slightly (causing misalignment) so the trick to do is to change the w and h parameters to 0.078 in the tool bar and then record the radius from the xml editor window (which will be 29.) Now undo the w and h changes to restore the pad to its original position and instead change the radius from its current value to 29. This changes the diameter relative to the center of the circle leaving its x y position the same which is what we need in this case. As a side issue the radius is currently an ellipse not a circle (because of floating point roundoff during the rescaling) and thus has a rx and ry in xml editor. We want to change both to be 29 which will make it a circle with r=29 again. Then change the stroke-width to 20 and you are done. Alternately you can do the scale mathematically like this to calculate a new radius and stroke-width at the current scale (but I find rescaling easier):

A campaign was launched on Crowdsupply for Newt, which is a battery-powered, always-on, wall-mountable display that can go online to retrieve weather, calendars, sports scores, to-do lists, quotes. Newt is powered by an ESP32-S2 microcontroller which enables you to program with...

Adafruit feather boards have been successful in fulfilling the demands of the maker community. Yet another Adafruit ESP32-based TFT panel-mounted feather board with the support for CircuitPython or Arduino. Onboard IPS TFT color display gives you the flexibility to work on a 240 x 135...

We have seen a lot of variations of the ESP32 throughout its life cycle. At Morpheans, the lack of boards for the ESP32-S2 triggered them into making their own take on the board. Then, the MorphESP 240 was born! An ESP32-S2 based board with a high-resolution IPS, colorful display built...