123
-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|498|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Hardware and Technology -> Building a Touchable Keyboard

Page : 1 2 Prev 3 4 Next
Posted : Friday, 30 August 2019, 12:28
Jayenkai
Indeed, I wouldn't have a flamin' clue!

Most Excellent work!

-=-=-
''Load, Next List!''
Posted : Saturday, 31 August 2019, 09:19
steve_ancell
spinal Don't be impressed just yet, nothing does anything at the moment

Over all the years I've seen you on the forums, you have always just got on with what you do and have never been afraid of failure. If that's not impressive then I don't know what is!
Posted : Monday, 02 September 2019, 09:26
spinal
New screen came,just got to figure out how the touch screen works...

-=-=-
Check out my excellent homepage!
Posted : Monday, 02 September 2019, 09:27
rockford
You'll have that sussed/bust in no time!
Posted : Monday, 02 September 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



|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!
Posted : Wednesday, 04 September 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!
Posted : Wednesday, 04 September 2019, 07:00
Jayenkai
Do you NEED the touch input to be that sensitive?
Posted : Wednesday, 04 September 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...


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!
Posted : Thursday, 05 September 2019, 01:42
rockford
Told you you'd suss it!
Posted : Thursday, 05 September 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!
Posted : Thursday, 05 September 2019, 18:22
Jayenkai
Watched this, and thought of your project..

-=-=-
''Load, Next List!''
Posted : Monday, 09 September 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!
Posted : Monday, 09 September 2019, 05:13
Jayenkai
Awesome!
Go Spinal
Posted : Monday, 09 September 2019, 09:17
rockford
We never doubted you for a second
Posted : Tuesday, 10 September 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!
Posted : Thursday, 12 September 2019, 11:17
spinal
Broke screen, project on hold.
Posted : Thursday, 12 September 2019, 13:36
Jayenkai
Oh, fuck...
Posted : Thursday, 12 September 2019, 15:50
rockford
What did you do - power issues or sat on it?
Posted : Friday, 13 September 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!
Posted : Friday, 13 September 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!''
Posted : Friday, 13 September 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
Posted : Saturday, 14 September 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!
Posted : Saturday, 14 September 2019, 11:47
spinal
Here is a quick example of using the ili9341 TFT that comes with a touch screen on an Arduino -



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 -



-=-=-
Check out my excellent homepage!
Posted : Saturday, 14 September 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!''
Posted : Saturday, 14 September 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!
Page : 1 2 Prev 3 4 Next