How did Wilba do it? SEQ V4 CS with only 6x74HC165 & 2x74HC595

[Hawkeye]

... considering a standard DIN module uses 4x74HC165 and provides "only" 32 ins (but ~90 are required)

... and a standard DOUT module uses 4x74HC595 and provides "only" 32 outs (but ~60 are required)

The pdfs on ucapps.de gave me no clues, as "only" the standard pinning is mentioned, which is fine, but how would i realize dual color step leds for example?

I guess the keywords are "button matrix" and "led matrix", pointers are very welcome...

I found the respective matrix configurations in the wilba/mbseq_hw.v4 file, but don´t understand the associated necessary wiring yet...

thank you very, very much!

Peter

Edited November 2, 2010 by Hawkeye

[TK.]

Compare http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fhwcfg%2Fstandard_v4%2F

with http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fhwcfg%2Fwilba%2F

Maybe Wilba can give you a schematic for the matrix wiring, I only did the programming ;)

Best Regards, Thorsten.

[Hawkeye]

kthxbai :)

edit: within an hour Wilba sent me the scheme... better than sliced bread :), thx!

Edited November 3, 2010 by Hawkeye

[Duggle]

kthxbai :)

edit: within an hour Wilba sent me the scheme... better than sliced bread :), thx!

Yup, I got mine too! thanks v.much Wilba!

[jerd]

Wilba, could i have a schematic for the matrix wiring too? Thanks.

[Wilba]

MB-SEQ-CS_combined.zip

[jerd]

Thanks! Finally figured it out, Dos Equis time!

[tashikoma]

Hi MByers

i've got all the parts for finish a MBseq :frantics:

i was thinking building the WILBA's control surface in DIY mode (veroboard) :whistle:

but i realise the WILBA CS is matrix wiring.

can i build it with standard DOUT and DIN for all switchs and duo leds?

or i need to do the matrix switching?

thanks

[findbuddha]

Have a read here: http://ucapps.de/mid..._manual_hw.html

And in the hwcfg folder of the Seq application download.

The matrix isn't needed for a control surface for the sequencer, it just makes it more compact / use less shift registers. The matrix should be achieveable with regular DIN/DOUT modules.

[Hawkeye]

yes, it works, you can also have a look at this thread, beginning here:

where a custom interface is built on veroboard without a matrix.

Greets,

Peter

[tashikoma]

yeah!!!! thanks Peter !!!:D

Edited August 3, 2011 by tashikoma

[ArnoNym]

Ciao all,

since this is my very first post here in the forum, I want to say a big T H A N K Y O U guys for this awesome stuff. Almost everything is well documented and it makes fun to fiddle with these DIY projects.

I am currently building my own SEQ V4. The STM core is running well, together with SD card and displays. Everything worked straight on. No need to post questions up to now ...

Now I am thinking about the user interface. I want to have reduced cable spaghetti, so I am interested in the matrix stuff. I want to describe here how I think it is working. Please any enlightened people correct me, if I have misunderstood something:

Talking about hwcfg/wilba vs. his schematic (Esp. thank you for that, Wilba :wink: !):

BLM8X8_DOUT_GP_MAPPING 1

This "1" points to U7 - 1st output SR where OUT0-OUT7 is connected? I can specify with the number in "SR" for each button, which of outputs OUT0-OUT7 is connected? like:

BUTTON_PLAY 18 5

18 => pin6 - DOUT6 ?

BLM8X8_DIN_SR 2  

The "2" points to U2 - 2nd input SR where IN8-IN15 is connected? I can then specify with "Pin" which of IN8-IN15 is used for specific button? like:

BUTTON_PLAY 18 5

5 => IN13 ? Similar for the LEDs:

BLM8X8_DOUT_CATHODES_SR 1 

The "1" also points to U7 - same SR like GP_MAPPING is used for LED matrix? Could be a different one?

BLM8X8_DOUT_LED_SR 2

This "2" points to U8 - 2nd output SR where DOUT8-DOUT15 is connected?

Some additional questions:

1) Header 3 for Beat LED, usage of OUT15A is specified anywhere? Or just OUT14A+1? Or dualLED not used / implemented / "fake" ?

2) Encoder always use 2 successive inputs (like IN6/IN7), whereas only IN6 is specified in hwcfg file?

3) What about IN40 for knobs / IN41 for datawheel? Is this specified in hwcfg file? Sorry, I did not get the magic behind this. :logik:

Thanks for any comments, suggestions, answers.

Cheers,

ArnoNym