Jump to content

Scan matrix 32x32 (1024 buttons)


QBAS

Recommended Posts

This is mostly for custom use, for egzample if you need 17x18 matrix you can use

only some pins (not all).

the diagram is the same like TK relase but four times bigger (longer chain)

http://www.ucapps.de/mbhp/mbhp_scan_matrix1.pdf

please use DINX4 and DOUTX4.

rows go to DINX and counting is the same like pin on board.

Counting on DOUTX4 is here:

first      SR pins 7 - 0  =  our  24 - 31

second  SR pins 7 - 0  =  our 16 - 23

third      SR pins 7 - 0  =  our  8 - 15

fourth    SR pins 7 - 0  =  our  0 - 7

I hope it is clearly.

The program put outside sysex string: F0 #ROW  #COLUMN #VALUE F7.

Link to comment
Share on other sites

  • 5 months later...
  • 2 months later...

QBAS,

Your old wiki address http://www.midibox.org/dokuwiki/doku.php?id=qbas does not work.  Do you have a new link to the matrix code?

I have received core and I/O kits from smashtv and will beginning assembly of the matrix with three keyboards, stops, pistons, etc., etc., and will keep you posted when ready to run the tests you recommended.

Thanks,

Johnc

Link to comment
Share on other sites

hey qbas

ive been trying to write the code to expand the examples to 16x16 and been unsuccessful so far. looking at your code though, it seems we approached it quite differently > i will try and test it out tomorrow. i've only got 8x12 matrix at the moment, but theoretically it should work on smaller matrices yes...?

it's too late in the evening right now, but hopefully some success soon...

trent

Link to comment
Share on other sites

just been playing with the code, and it works well - few problems though which i think stem from the lack of debouncing. i tried to migrate the code into C but alas it hasn't worked as seemlessly as hoped (i have a much easier time working with C code).

hardware was 8x16 switch matrix using 2xDOUT and 1xDIN

i assume you left the debouncing out, as it would consume too much processor power for all the buttons, however on second thought, maybe my problem is not debouncing... i will get back to you about it.

nonetheless, it works *thumbs up*

t

Link to comment
Share on other sites

@*jOi~

I cut debouncing since most of my projects with matrixes was keyboards.

What hardware are you use? What kind of problems are you meet?

tried to migrate the code into C

I stopped learn C - I can`t help with it.

hardware was 8x16 switch matrix using 2xDOUT and 1xDIN

This code was prepare to 4xdin and 4xdout modules. I dont know how it will be work with smaller setup.

Of course any kind of customization can be done, but I`m not prepare (yet) configuration definitions.

i assume you left the debouncing out, as it would consume too much processor power for all the buttons
  no - i just no needed this with keyboard, and I used this timer for velocity counter.
Link to comment
Share on other sites

  • 4 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...