fritzing ips tft display factory

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.

And here’s what we designed! The BrainCraft HAT has a 240×240 TFT IPS display for inference output, slots for a camera connector cable for imaging projects, a 5 way joystick and button for UI input, left and right microphones, stereo headphone out, a stereo 1 Watt speaker out, three RGB DotStar LEDs, two 3 pin STEMMA connectors on PWM pins so they can drive NeoPixels or servos, and Grove/STEMMA/Qwiic I2C port. This will let people build a wide range of audio/video AI projects while also allowing easy plug-in of sensors and robotics!

MOSI, SCK, GPIO #25, CE0 - These are the display control pins. Note that MISO is not connected even though it is a SPI pin because you cannot read back from the display

SCL, SDA - I2C data for the STEMMA QT / Qwiic connector. Not used by buttons or display. Can also use with Grove sensors with an adapter cable. Great for quickly adding sensors or accessories with plug-and-play.

There"s two ways you can use the 1.54" 240x240 display on the BrainCraft HAT. For machine learning purposes, the advanced method is the way to go, so that"s what we"ll be covering in this guide.

The easy way is to use "pure Python 3" and Pillow library to draw to the display from within Python. This is great for showing text, stats, images etc that you design yourself. If you want to do that, the BrainCraft HAT has a pretty close layout to the Adafruit 1.3" Color TFT Bonnet including the same type of display and a joystick, though the pinouts are slightly different. If you choose this option, You can skip this page and view the Python Setup page for instruction for that display.

The advanced way is to install a kernel module to add support for the TFT display that will make the console appear on the display. This is cute because you can have any program print text or draw to the framebuffer (or, say, with pygame) and Linux will take care of displaying it for you. If you don"t need the console or direct framebuffer access, please consider using the "pure Python" technique instead as it is not as delicate.

Besides the display, audio, and fan, this board has quite a few other useful features on it that can be controlled through Python. We"ll go through those and how to control them in Python.

You can make this prop wrist-computer for cosplay, or for general ‎stylishness all the time. Swap graphic screens on the beautiful round ‎rectangle IPS TFT display with the directional buttons, move the ‎cursor with the joystick, look rad.‎

This diagram shows the display wired to the Feather via the Tripler. ‎This illustration has the display off to the side for clarity. On the real ‎board you"ll use the header to connect the display to the board with ‎this wiring in place.‎

You can build a 3D printed, wrist-mounted case for your Pip-Boy ‎‎2040. A nylon watch strap will allow you to adjust it for a perfect fit -- ‎or you can use Velcro strips to secure it to a costume jacket or rad ‎cyber armor.‎

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):

This is the 900 MHz radio version, which can be used for either 868MHz or 915MHz transmission/reception- the exact radio frequency is determined when you load the software since it can be tuned around dynamically.We also sell a 433MHz version of the same radio chipset!And if you don"t need LoRa radio,we have plain 900MHz packet radios as well