Buttons not working - Matrix channel

Testing/Troubleshooting
,
1

So it wouldn’t be a change of season without Mongrol breaking something. I got sick of the Orange case and its sneaky ways of making me always write circus music and I replaced my SEQv4 into a black case. On the way I’ve broken all the buttons on M3. What’s the traditional way of troubleshooting a matrix channel?

(I’m specifically asking instead of working it out myself to get it recording on the forum for others.)

  • So far I’ve identified the buttons not working.

  • Looking in the MBSEQ_HW.v4 file I can see the following

    SR Pin BUTTON_STOP M3 5 BUTTON_REW M3 4 BUTTON_PAR_LAYER_C M3 6 BUTTON_GP11 M3 0 BUTTON_GP12 M3 1 BUTTON_TRACK_SEL M3 3 BUTTON_UTILITY M3 2

Which are exactly my broken buttons.

What next?

2

If it’s a row of the matrix, I think the problem is on the sink side. Are LEDs out in the trig buttons, pause and GP 13/14?

3

Nope. All those LED’s are working. LED’s on GP11/12 are broken (along with the buttons).

4

Whoops, wrong row.

LEDs out on GP11/12,  rewind and stepview?

 

It points to a bad 595 chip (U7) or broken connection somewhere. You might even find reseating the IC helps.

5

Replaced U7. No luck. Is there a wiring schematic somewhere other than the Wilba.pdf thats in the shape of the CS?

6

Fixed. Cable wasn’t in right. Thanks Lat.

7

Nice!

8

Maybe an addendum; what was the issue? Still a faulty 595 and a loose cable? Or was the original okay? If anything wasn’t plugged in properly I’d think nothing would be working.

9

Cable wasn’t fully seated into the socket underneath the CS. While it looked like it was in, it was at  very slight angle meaning that channel wasn’t made.