Shop OBEX P1 Docs P2 Docs Learn Events
3.5" LCD Touch Screen on the Activity Board — Parallax Forums

3.5" LCD Touch Screen on the Activity Board

dmkmediadmkmedia Posts: 9
edited 2015-06-25 00:02 in Propeller 1
i have a 3.5" LCD Touch Screen what i did buy for the raspberry pi and now my project is building up i now need it on the activity board
can anyone point me in the right direction on where i can find spin code to get me up and running


Specifications

LCD Type TFT
LCD Interface SPI
Touch Screen Type Resistive
Touch Screen Controller XPT2046
Colors 65536
Backlight LED
Resolution 320*480 (Pixel)
Aspect Ratio 02:03
Power Consumption TBD
Backlight Current TBD
Operating Temp. (℃) TBD

Interface

PIN NO. DESCRIPTION
1, 17
3.3V
Power positive (3.3V power input)
2, 4
5V
Power positive (5V power input)
6, 9, 14, 20, 25
GND
Ground
11
TP_IRQ
Touch Panel interrupt, low level while the Touch Panel detects touching
18
LCD_RS
Instruction/Data Register selection
19
TP_SO
SPI data output of Touch Panel
22
RST
Reset
23
LCD_SCK / TP_SCK
SPI clock of LCD/Touch Panel
24
LCD_CS
LCD chip selection, low active
26
TP_CS
Touch Panel chip selection, low active

3, 5, 7, 8, 10, 12, 13, 15, 16
NOT USED


i will be using spin for this project and hoping to integrate this as a user menu system with on screen keyboard
to tell the truth i think this may be the worse bit of my project as i have all the things in the right place just left this until last

so far i have the power hooked up and thats it im not sure where to go next

i did format this so it looked ok but after pressing submit its all gone back bunched up if you need clarification on the pins let me know

Comments

  • Duane DegnDuane Degn Posts: 10,588
    edited 2015-06-24 18:15
    dmkmedia wrote: »
    i did format this so it looked ok but after pressing submit its all gone back bunched up if you need clarification on the pins let me know

    The formatting gets messed up if you don't use code tags.

    Use "Reply With Quote" to see how I added them here. Sometimes the formatting is preserved even if it doesn't show up. I figure this time the formatting was not preserved since I doubt your original text looked the text below.
    Specifications

LCD Type	TFT	
LCD Interface	SPI	
Touch Screen Type	Resistive
Touch Screen Controller	XPT2046	
Colors	65536	
Backlight	LED	
Resolution	320*480 (Pixel)
Aspect Ratio	02:03	
Power Consumption	TBD	
Backlight Current	        TBD	
Operating Temp. (℃)	TBD	
 
Interface 

PIN NO.	            	              DESCRIPTION
1, 17 -----	              3.3V	 ------                   Power positive (3.3V power input)
2, 4	 -----                      5V------                     Power positive (5V power input)
6, 9, 14, 20, 25-----	GND	    -----                 Ground
11	-------                    TP_IRQ	-------             Touch Panel interrupt, low level while the Touch Panel detects touching
18	------                    LCD_RS	-------             Instruction/Data Register selection
19	-------	                     TP_SO--------	             SPI data output of Touch Panel
22	-------                       RST	     -------               Reset
23	-------              LCD_SCK / TP_SCK	 -------    SPI clock of LCD/Touch Panel
24	-------                   LCD_CS-------	             LCD chip selection, low active
26	-------                     TP_CS--------	            Touch Panel chip selection, low active

3, 5, 7, 8, 10, 12, 13, 15, 16	------            NOT USED

    You should be able to fix the text if you want.

    The thread in the following link is about a LCD which uses the "XPT2046" controller.

    http://forums.parallax.com/showthread.php/110134-2.4-quot-320x240-TFT-Prop-based-display-module

    It has been a while since I've read the above thread. I don't know if the display requires a buffer in RAM to hold the contents of the screen or not. I often struggle to find room for display buffer RAM in my touchscreen projects. I usually end up using a second Propeller as a graphics slave.

    One of my more ambitious touchscreen projects was my robot remote. I used two Propellers on it and I kept the contents of the various screens on a SD card.

    I will likely want to use a touchscreen with my FONA but I'm not sure which screen I'll use.

    I have one of these from Adafruit:

    https://www.adafruit.com/products/2478

    There appears to be a driver for this screen here:

    http://forums.parallax.com/showthread.php/154703-Read-bmp-image-from-SD-to-Display-ili9341.-Done-in-spin-but-very-slow
  • dmkmediadmkmedia Posts: 9
    edited 2015-06-24 22:37
    well this one is going with the FONA as well...... Reading back on your posts my project is very similar to your other FONA project
    but i have a button that will work over a large distance and send GPS location as well.

    but it was all designed in python at first then it became too big for the PI alone so i added an UNO then i needed other hardware it was going to be to hard to fit everything in then i needed a place to store WAV files so i came across the activity board

    and now i'm on a steep learning curve in spin trying to work out how to fit all the bit together.. its turning into a headache.. but for some twisted reason

    IM LOVING IT

    the problem is i'm starting to have dreams about the coding problems and hardware fitting together
    then i wake up at 5AM wanting to carry on from the following day its turning in to an obsession
  • dmkmediadmkmedia Posts: 9
    edited 2015-06-25 00:02
    here are some images from the project inside you can see the propeller activity board with an high power RF transceiver with the FONA and the screen wires
    for now the FONA main wires are detached to avoid damage while i am testing the screen

    and the front image the red dots mark the area i have managed to get working with the screen only 2.4 inches not the full 3.5

    24nek4k.jpg
    The hand held RF button has two buttons for two actions. and i have managed to get over 1000 mtrs from it

    21179ea.jpg
Sign In or Register to comment.