Rednas

The missing code is the one that connects pin 487 to the right midi message. The most versatile way would be in the same way as MIDIO128, which uses an ini file with the right code, which can be uploaded to the PIC. If this can be made, we have the option to use up to 1024 buttons. Ideal for midification of organs.

I think I found the activation code for the notes. It's the function SM_NotifyToggle at the bottom of sm_fast.inc and currently is only capable of sending sysex codes to check the row, number send. This needs editing for our applications.

My setup isn't ready yet, so I haven't looked into the code, but should do so within two weeks. Take a look here: http://www.ucapps.de/mbhp/mbhp_scan_matrix1.pdf It looks like you can leave (or better must leave) the 220 Ohm resistors of the DOUT out. Wish I looked at that before, since mine are already in. The replacement of the diodes can be in two ways, and you can set SM_SWAP_CR accordingly. As you made it now, that value should be changed to 1. For your setup it is 4 times this one, with 4 different DIN's. I should check what influence not having the other 3 DOUTs or alternatively, not using them will have on the messages send. It should have no influence, but i'm not sure how it's works in total.

I don't know about the analog part, but for the digital part, I suggest an 8x8 matrix for each part. For your setup you need 1 DOUT (8 outputs) and 4 DIN (32 input). So instead of the 8 to 3 selector, you connect those 8 lines to a different DIN.

There is an 8x8 matrix by Thorsten, and i think a 16x16 (equals 4 8x8) and a 32x32 by QBAS. I'm looking at the last one for midification for a virtual organ setup. And maybe even get to the point to have it as easy as MIDIO128 using an ini file. Then the analog input can still be used for the drawers i guess.

Hello. How far did you get with this? Is it already possible to add own midi code to the program? I'm working an a setup with a 32x32 matrix, which can also be used as test setup, and to have it like MIDIO128 would be great.

I just added 36 resistors to my first DIN module. Would be easier if I didn't have to do that :)

I hope to get on to this this weekend, either 32x32 or a smaller matrix. I found out that the link to the SM 32x32 doesn't show when you're not logged in though.

Thnx a lot. That clears everything. Caps stands for capacitors ofcourse. It seems my core dates from december 2004, before this discussion has started. I'll be sure to mount some in, when i find them. And some for the other modules too.

Hello, After almost two year break i wanted to continue with my MIOS project, and found an old V2 core. It is almost finished, but i'm missing the Bypass Caps. What are those? From the construction manual. Add also the two additional Bypass Caps on the bottom side of the PCB as close to the power inputs of the PIC as possible. They improve the power integrity. Rednas

Hi I try to build the midimerger with the old PIC. I got all the stuff and soldered most part but i tried to build it without external powersupply. What i do is I use the power on the cable from one of my keyboards. The other is still isolated with an optocoupler (6N138). This should work fine. The problem is I connect the data cable directly to the PIC. But normally the databit is 0 if data is sent. This will light up the led in the optocoupler, so the optocoupling works and gives a 1 to pic. Is this true? And should i just set either an inverter or an optocoupler between data and PIC to solve this problem. Thnx for answering. yours Rednas

Sensor analog output --> Midibox analog input But scaling is needed. Where do you want to use it for? Continuous distance --> analog needed Two steps -> First analog to digital converter. Have the right digital output pin(s) connected to some Digital input (Din).

Congratulations from me too. I'm still in the middle of building a midiorgan myself, rather than midifying a complete one. Got two manuals and pedalboard working so I can play, now the fancy stuff like preset button, stop pullers, swell pedals and 3rd (and 4th?) manual. Fot other people who want to do this too: there still is a scanning matrix under construction, think I'll finish in the next few weeks if I have time, so you need only 1 Din, 1 Core, 1 Dout for about 512 inputs.

Hi The link at your web page is wrong. You put *.html there but it's *.htm. A mistake I also made... Bye Rednas

When do you need the matrix?

More ideas. MIOS is equiped with a midi sendbyte routine, which will send a byte on the right pin to midi-out. What you have to do is alter this routine to let it send data to a shift register (Dout), and when all the data is in the shift register you have to clear another pin to let the other side know you are sending a midibyte. I don't know yet how to do this, but if you are an experienced PIC programmer maybe you do. Another idea is to put a shift register at midiout, but to control it you need at least two pins.

I think what you need is a MIDI core with one DOUT module, and maybe a DIN. (DOUT and DIN not fully stuffed with pics). You can use the DOUT as parallel interface. I don't know how parallel interfaces work, but isn't it something like you set the parallel pins and the other end will accept the code if a some 'receive' pin is set? So the program should set pins according to what midimessage is set. In this way you can use MIOS code (that's for PIC18F452) and will have to write an application that will transform midiin data to DOUT data. But as I said, I don't know how parallel works so I don't really know how to do this. I just took a look at http://computer.howstuffworks.com/parallel-port1.htm Pin 1 of the parallel port has normally a level between 2.8 and 5 volt, but will drop if data has to be sent. Pin 2-9 carry the data bytes. So first you have to assign the data bytes to a DOUT, and then drop 'Pin 1' below 0.5 volt. I don't really know how it all works, but DOUT uses shift registers, which is fine for the data, but this way it's hard to maintain Pin 1 at high voltages if Pin 1 is part of DOUT. MIOS can handle midiindata and the DOUT module, but you will have to find a way to keep pin 1 high, until DOUT is set. I hope this helps somewhat. Are you using the parallel port of a PC as an MIDIinport? If so I think other people are interested and it would be nice if you can publish your result at this website somewhere. Yours Rednas

I don't know if encoders are matrix compatible. Maybe with extra programming. Otherwise you will need at least two cores I think, one for encoders, one for buttons. The buttons can be done with MIDIO128 (need more pcb's and more wiring but can be made right away) or a 16x8 matrix, if it is ready soon enough, or if you can program one. You could also use a 'slow' matrix (maybe even 8x8 and less buttons for a while) until the sooperfast is ready. It won't change your wiring and updating MIOS can easily done via MIDI :-)

After all it seems like black looked like grey, because of the background, so my resistors are 10 k. I never thought of measuring with a multimeter to measere the resistances to put the right one in the right place. Well, you learn from your mistakes right? ::) Rednas

I also like to use a matrix to create enough inputs for an organ console and just started building. Therefore I will need to superfast version, but not until I build in the keyboards. I'm using normal keyboards with midi for that now. I will have ready within two weeks I think two rows of 16 pushbuttons, for which the input can be varied between 4 values and creating a 4x32 matrix (part of 16x32) in this way. I also can use a 8x16 matrix first until the superfast matrix is ready, the latter I suggested to program myself if JimHenry is to busy. So with any luck and if I have enough time an superfast 16x32 or a slow 16x8 will be ready within a few weeks. I'm not sure though that the superfast will have the ability of AIN, although I think I read somewhere that it does. I als don't know what te 32 encoders use, but a bigger matrix will hopefully available soon.

If you don't need a keyboard, you do not have to do it superfast i guess and then extending the first matrix to 16x8 or 8x16 will give you the matrix you want and you still can use the rotary encoders I think. If you cannot program two cores would also do the trick, both with an 8x8 matrix and rotary encoders

Thanks guys, I already send Claudia an e-mail. Rednas

Mios already has an implementation of an 8x8 matrix. JimHenry is currently working on a 16x32 matrix, for the huge amount of witches the midiorganplayer uses (two or three keyboards, pedal board stop switches, prestet switches...) I think in this there will be room to asign a midi message to each key before burning it to PIC. Not as easy as MIDIO128 in the beginning, but good enough and easier to program. You can probably use part of this matrix connections for the commodoreC64 if the C64 also uses an 8x8 diode matrix. Or if you can't wait use the 8x8 matrix implementation. I think I'll go and find out what this C64 is (I'm not a SID builder) and take an extra look in my keyboards :-) )

Hi I've ordered some stuff from Claudia, but I got resistors of 15k instead of 10k for my core module. (They look the same in bad lighting) Should that be a problem, or is this new? Thanks Rednas

Another idea use: Dutch: glasvezel Deutch/english? glassfiber I don't know if you've got to use a led or a laser for this one, but you've got to transform the midibytes into lightpulses, transport them through glassfiber and than transform this back. This is like a long range optocoupler, normaly used to isolate the midiapparatus. (6N138 if I'm not mistaking)