Building a Touchable Keyboard

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|678\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Hardware and Technology -> Building a Touchable Keyboard
Page : 1 2 Prev 3 4 Next 5
Mon, 02 Sep 2019, 09:26
spinal	New screen came,just got to figure out how the touch screen works... -=-=- Check out my excellent homepage!
Mon, 02 Sep 2019, 09:27
rockford	You'll have that sussed/bust in no time!
Mon, 02 Sep 2019, 11:42
spinal	Your kidding, so far today I've managed to get either the screen to work, but once the touch panel starts working the screen no longer works ____TFT______ _Pro Micro_ [ ] T_IRQ -[1.5k]- o A2 [ ] T_DO -------- o 14 (MISO) [ ] T_DIN -------- o MOSI [ ] T_CS -[1.5k]- o A1 [ ] T_CLK -------- o SCK [ ] MISO -------- o N/C [ ] LED -------- o VCC [ ] SCK -[1.8k]- o 15 (SCK) [ ] MOSI -[1.8k]- o 16 (MOSI) [ ] DC -[1.8k]- o A0 [ ] RESET -[1.8k]- o VCC [ ] CS -[1.8k]- o 10 [ ] GND -------- o GND [J2][ ] VCC -------- o VCC --v \|edit\| Hmmmmm, it seems I need to re-init the screen after every successful touch-read... that's not helpful. -=-=- Check out my excellent homepage!
Wed, 04 Sep 2019, 05:14
spinal	Hmmm, slight snag, it seems that the screen and touch module communicate at different speeds. I wonder if it would be enough to change the clock speed when swapping the CS, or if I need to be more drastic and try to read the touch panel resistance directly.... -=-=- Check out my excellent homepage!
Wed, 04 Sep 2019, 07:00
Jayenkai	Do you NEED the touch input to be that sensitive?
Wed, 04 Sep 2019, 14:43
spinal	Fixed, not a case of sensitivity, more a case of working or not working... Anyway, resetting the SPI bus speed when trying to draw to the screen has fixed the problem... void useTouch(){ digitalWrite(TFT_CS, HIGH); digitalWrite(CS_PIN, LOW); } void useTFT(){ digitalWrite(CS_PIN, HIGH); SPI.setClockDivider(SPI_CLOCK_DIV2); digitalWrite(TFT_CS, LOW); } --v right, now back to that joystick issue. Here's a diagram,because I got bored... -slight over-site, it needs a resistor on the touch CS pin also (the purple one that goes to A1) -=-=- Check out my excellent homepage!
Thu, 05 Sep 2019, 01:42
rockford	Told you you'd suss it!
Thu, 05 Sep 2019, 02:01
spinal	The good part is, I have 10 pins free for the joysticks. So I might not even bother with multiplexing them. -=-=- Check out my excellent homepage!
Thu, 05 Sep 2019, 18:22
Jayenkai	Watched this, and thought of your project.. -=-=- ''Load, Next List!''
Mon, 09 Sep 2019, 04:57
spinal	I've half soldered it together, ran out of time. Anyway, screen and touch working also the fire buttons of both joysticks. Only thing left is the eight wires for the directions then to work on the software. Best part, nothing fried and all (current) connections were correct first time! -=-=- Check out my excellent homepage!
Mon, 09 Sep 2019, 05:13
Jayenkai	Awesome! Go Spinal
Mon, 09 Sep 2019, 09:17
rockford	We never doubted you for a second
Tue, 10 Sep 2019, 11:01
spinal	Had to swap the pin numbers around as I forgot the the Arduino is upside down on my board. Now I just need a keyboard routine ðŸ˜ \|edit\| touch sensitivity is wildly inaccurate. Looks like I'll be forced to use the IRQ pin from the screen to detect touches rather then assume them based on the pressure reading, which fluctuated between 0 and 4000 quite randomly. An LED on the IRQ pin seems to be quite accurate, so I need to go back to the old joystick idea as I have exactly zero I/O pins left. -=-=- Check out my excellent homepage!
Thu, 12 Sep 2019, 11:17
spinal	Broke screen, project on hold.
Thu, 12 Sep 2019, 13:36
Jayenkai	Oh, fuck...
Thu, 12 Sep 2019, 15:50
rockford	What did you do - power issues or sat on it?
Fri, 13 Sep 2019, 02:57
spinal	Touch screen had some dirt under it, causing the readings to go a bit wonky. I tried to clean it with a little success, tried to clean it some more which resulted in complete failure. Not to worry I thought, I have a spare as the one that got delayed in customs finally showed up. So instead of starting over with the build, I tried to remove the screen from the front of the circuit and leave the whole back (Arduino, joysticks etc) in tact. But putting the spare screen onto the pre-built device resulted in destroying the connector. I don't know if I have enough spare parts to rescue the project and I'm not ordering onther screen, that was frustrating enough the first time. -=-=- Check out my excellent homepage!
Fri, 13 Sep 2019, 04:02
Jayenkai	Oh no But I can totally sympathise with the "hitting a roadblock" scenario. One thing can really put a dampener on things, Perhaps a nice rest from thinking about it, might help. -=-=- ''Load, Next List!''
Fri, 13 Sep 2019, 15:35
Krakatomato	I have to admit that I didn't really have that much interest in this project, but that certainly doesn't mean I didn't want you to succeed. As such, please let me know what parts you require. It's quite possible that I have spares and I'm happy to send on for you to make the most of. //Andy
Sat, 14 Sep 2019, 08:46
spinal	Well, screen not fixed. Project cancled. I'm not going to go asking people for spare parts for this, I will however, write up the processes I used and managed to get working during the various stage. It seems that getting the particular screen and touch panel working at the same time (or even at all) appears to be a huge stumbling block for Arduino users, so I'll share that process at least. -=-=- Check out my excellent homepage!
Sat, 14 Sep 2019, 11:47
spinal	Here is a quick example of using the ili9341 TFT that comes with a touch screen on an Arduino - ____TFT______ _Pro Micro_ [ ] T_IRQ -------- o A2 [ ] T_DO -------- o 14 (MISO) .---[ ] T_DIN o MOSI \| [ ] T_CS -[1.5k]- o A1 \| .-[ ] T_CLK o SCK \| \| [ ] MISO -------- o N/C \| \| [ ] LED -------- o VCC \| '-[ ] SCK -[1.8k]- o 15 (SCK) '---[ ] MOSI -[1.8k]- o 16 (MOSI) [ ] DC -[1.8k]- o A0 [ ] RESET -[1.8k]- o VCC [ ] CS -[1.8k]- o 10 [ ] GND -------- o GND [J2][ ] VCC -------- o VCC --v Using the following two libraries I was able to use both the TFT and Touch screen at the same time. https://github.com/PaulStoffregen/XPT2046_Touchscreen https://github.com/Bodmer/TFT_ILI9341 The trick to getting both parts of this screen working together rests in remembering to reset the SPI speed for each device. Connect both the touch screen and TFT to the hardware SPI pins of the Arduino and remember the following when using - #include <SPI.h> #include <XPT2046_Touchscreen.h> #include <TFT_ILI9341.h> #define INTERRUPT_PIN A2 #define CS_PIN A1 XPT2046_Touchscreen ts(CS_PIN); // Param 2 - NULL - No interrupts TFT_ILI9341 myGLCD = TFT_ILI9341(); // Invoke TFT library void useTouch(){ // swap the SC pins to switch between TFT and Touch digitalWrite(TFT_CS, HIGH); digitalWrite(CS_PIN, LOW); } void useTFT(){ // reading the touch screen changes the SPI speed, so we need to change it back every time we use the TFT screen digitalWrite(CS_PIN, HIGH); SPI.setClockDivider(SPI_CLOCK_DIV2); digitalWrite(TFT_CS, LOW); } void setup() { Serial.begin(9600); pinMode( INTERRUPT_PIN, INPUT_PULLUP); Serial.println("Starting LCD Screen"); // Setup the LCD myGLCD.init(); myGLCD.setRotation(1); myGLCD.fillScreen(0); Serial.println("Starting Touch Screen"); // touch screen ts.begin(); ts.setRotation(1); } void loop() { useTouch(); if(digitalRead(INTERRUPT_PIN)==LOW) { TS_Point p = ts.getPoint(); Serial.print(p.x); Serial.print(","); Serial.print(p.y); Serial.print(","); Serial.println(p.z); penX = map(p.x, TS_MINX, TS_MAXX, 0, myGLCD.width()); penY = map(p.y, TS_MINY, TS_MAXY, 0, myGLCD.height()); useTFT(); myGLCD.drawPixel(penX, penY, pgm_read_word(&charset_Tiles_pal[ 1 ])); } --v -=-=- Check out my excellent homepage!
Sat, 14 Sep 2019, 12:43
Jayenkai	Good grief. .. No wonder the DS needed both an Arm7 and an Arm9 to keep things going! Have you considered strapping two Arduino together? -=-=- ''Load, Next List!''
Sat, 14 Sep 2019, 13:14
spinal	If I hadn't killed 2 screens, this would have worked out just fine. Although an Arduino isn't fast enough to do anything special with the screen, drawing a keyboard once in a while would have been no problem. Also I got the 2 c64 joysticks reading from the same set of pins without issue. So... Yeah... -=-=- Check out my excellent homepage!
Fri, 20 Sep 2019, 10:54
spinal	semi-related... this looks interesting... https://github.com/geaz/simplyRetro-Z5 -=-=- Check out my excellent homepage!
Fri, 20 Sep 2019, 11:09
Jayenkai	I'm happy enough with my GPDxd, thanks. Still not happy with the GPDWin, though. God damn, that fan is so bloody loud!! -=-=- ''Load, Next List!''
Sun, 22 Sep 2019, 09:19
Jayenkai	Hmmm.. Going back to this kind of thing... Linkage Thinking in the opposite direction.. How plausible would it be to remove the touchpad from this, replace it with a simpler screen, and create the device within its shell? (Quite cheap, too) -=-=- ''Load, Next List!''
Page : 1 2 Prev 3 4 Next 5