FantomXR

Hey Jo! Thanks! I think, this would be possible. But this is a huge modification on the pcb. So... I would prefer a solution on the software-side ;-) But if this is not possible, of course I would modify the pcb. Thanks, Chris

I attached the electrical schematic how I think it's correct. Are there any chances to get it running with KB?

New test results: I checked the pcb of the keybed. It seems that the pcb is prepared not to be used with the foil-cables only. Next to the foil-connector there are smd pads. I think, that I could add a standard micromatch-connector to the board. This made it easy to see, which pins are connected to something. Because I don't have a micromatch-connector here, I added a standard 20pin ribbon cable. I realized, that there are a lot of pins left open. As you can see in the pic the top row (which should normally contain the row-signals) has no traces except for the last two pins (pin 1 is most right). I removed the rubber contacts to see where the traces are going to. The lower row of the connector leads to the makes and brakes, the top row to the diodes. I connected pin 1 and 3 of the right side (MK5 and BK5) directly to the DIO to O5 and O4 of J4. Result: I can get the first eight keys of the right half working with the correct note-output: C#3 - G#3. But now I don't know where to connect the other pins. I tried to connect MK6 and BK6 to MK0 and BK0. This leads to the problem mentioned above: The triggered notes are starting at a-1. So: C#3, D3, D#3, E3, F3, F#3, G3, G#3, a-1, b-1, etc. Connecting MK6 and BK6 to O3 and O2 of J4 don't have any effect. And again: Adjusting din_key_offset has also not effect. The fact, that I can trigger C#3-G#3 without connecting any rows of the right half leads to the assumption, that there this will might not function correctly without adjusting the firmware. Any tipps how to proceed? Thanks! Chris

Hi Jo! The schematic is from a 5-page-datasheet about the TP/100. I think it has more something to do that studiologic let fatar produce a specific design which fits their acuna electronis (my TP/100 is a sparepart from an acuna). I already checked it... the connections are wrong! It has nothing to do with reversed pins ;) As soon as I wrote it down correctly I will post the informations here.

I disassembled the PCB from the keybed so I can see the connections and the traces on the pcb. Conclusion: I am right. The pinout of the right side is totally different. I will write it down and check the it again.

Okay! After some other tests I think, the diode-matrix-layout / pinout of the keybed that I have is not correct. I attached the layout and the pcb-layout I created to build an adaptor. Everything should be fine. but it isn't. I experimented with single pin-to-pin connections. When I connect the 1st and the 3rd pin of the left side to O7 and O6, the 2nd pin to I0 of J3 and I play the lowest note MIOS Studio outputs the correct note which is a-1. If I now do exactly the same connections with the right side and press the according key (which should be the black key right next to C-3) I would also expect, that MIOS Studio outputs a-1 but nothing happens. I tried other keys, but none of them are sending values. I think that my adaptor (pin 1 is most left) should work if the pinout in the schematic is correct. If you have time, maybe you can look over it...

Hey, I tried it with your project.hex. Same here. Mysterious... Why should it have something to do with the hardware connections, when the changes in the software don't work. Hm.... okay... I will check all connections again...

The result is: Changing din_key_offset=x doesn't have any impact on the played notes. It stays with a-1. I will update my svn and check what you suggested. I will build an app with VARIANT=1 and =0 and try both. //edit: Okay: With VARIANT=1 I get absolutely no notes out of the keybed. With VARIANT=0 same thing as mentioned above (stays at a-1). //edit: BTW: It's a TP/100 I'm checking with. But this shouldn't be a problem. I have the diode-matrix-layout and build an adaptor. I doublechecked the connections... here should everything be fine.

I tried different and random numbers from 0 to 32. Nothing is changing. It stays at a-1. Maybe something is swapped. I'll try tomorrow, if the starting key of the left half changes by putting another number behind din_key_offset=x. But the left half is working perfectly... and the right half is working too, it's just the wrong starting point ;) Do you may have an old revision of the KB-app? I could try to upload an old one.

Hi TK, thanks for getting back to me. I used the original MB_KB from ucapps.de So, if you didn't activate it by default, it should be turned off.

Hey people, I need to adjust the starting note of the right half of my keyboard. Here is the code from NG: It seems, that the din_key_offset parameter is not working. It doesn't matter which number I insert, the resulting key# is the same everytime. The right half is far too low. It starts at a-1 and not at C#-3. I first tried KB, but same here. Any tipps? Thanks, Chris

Nice one! Thanks for the comment!

Hey, I never worked with Sysex yet, but now I want to control an oberheim synth which only reacts on Sysex. It's clear to me how to send a defined Sysex string with a button. But how to send the same string with increasing / decreasing values with a pot? Can anybody point me in the right direction? Thanks! Chris.

Hey, thanks for getting back to me! It has nothing to do with latency or miliseconds. It has something to do with the way a real organ acts. This is bundled with the playing-style. For example: A typical style is, repeating the same note very fast. This is only possible, if you don't need to push the key all the way down to fire a note-on. Regarding your question: Any velocity value is okay and would work. So, I don't know, how TK designed the MB_KB velocity-function. If I switch off the velocity, is the note fired with the "brake" or with the "make"? I'm still waiting for my TP/8O so I can just test it. It would be very luxuary if its possible, so switch off the velocity with a simple switch (set the keyboard to "organ mode"). This may work with NG, but the resolution of the velocity with NG is not sufficient for me (with LPC17) if I really need velocity. That's why I use MB_KB.

PM sent

Es gibt natürlich sowas hier: http://www.seeedstudio.com/depot/8-pin-dualfemale-jumper-cable-150mm-5-PCs-pack-p-99.html?cPath=44_47 ist allerdings die einzige Quelle, die ich für solch konfektionierte Kabel gefunden habe. Und 15cm ist nun auch nicht das Längste der Welt...

Ich finds super! Gute Idee! Leider hast du dich von den praktischen Flachbandkabelverbindern verabschiedet. Jetzt geht doch die Zeit, die durch das Auflöten der Teile sparst, flöten, wenn du die Kabel konfektionierst, oder?

Hi Philip, it shouldn't be a big deal to do this. For me it's more complicated and time consuming to build the case :) Anyway: If you want velocity, you should go and use the KB-app and not the MB_NG. I tried both and with NG the velocity resolution is pretty low. So I just get maybe 10 or 15 different velocitys instead of 127. That has something to do with the scan speed. KB scans a lot faster. With that said you need a second core that handles the controllers. You should also check, if your drawbars are really potentiometers. I have two sets of drawbars here and both are switches! In my case I needed to connect the drawbars and the busbar in a switch-matrix. But this works really fine. Good luck with your project and keep it up! It indeed makes fun ;)

Dann nimm doch die BRDs von TK. Die sind öffentlich, nur eben auf einen Layer ausgelegt. Das sollte man aber doch relativ leicht anpassen können.

Ich finde die Idee auch gut... und 3-5€ für ein fertig bestücktes Modul sind schon super. Dennoch sehe ich es wie ilmenator: Ich würde bei einer festen Anwendung auch probieren, die Bedienelemente und die Teile für die Scan-Routine auf eine Platine zu bringen, was auch den Verkabelungsaufwand deutlich reduzieren würde. Dass die Encoder direkt mit der Frontplatte verschraubt werden, sehe ich da eigentlich nicht als Problem Das Löten geht doch eigentlich, besonders bei so kleinen Modulen und bei Verwendung von Widerstandsnetzwerken, relativ schnell von der Hand. Autorouting ist Mist! Nimm die Hand... das Bild oben sieht ja schon ein wenig... verwirrend aus. Das sollte wohl besser gehen. Gibt es eigentlich *.brd Files zu den DIN / DOUT Modulen? Ich meine die Designs von Tim.

Are you sure, that you have to take 500pc? I asked for some encoder caps and they sell them individually... as far as I remember.

Hey people, I want to use a fatar TP8/O for playing organ sounds. As every keybed, it has two switches to calculate the velocity. Is there an option, that allows to fire a "note on" already when the first switch is pressed? Real hammond organs do react very fast. You don't have to press down the key a lot to play a note. This would be nice :) Thanks, Chris

Yes, they look pretty nice. But it's $50 for a display... pretty much!

They look awesome! Where did you buy those? At Raystar direct?

I used Elecrow a few times now. The prices are good, quick production and shipping. The quality fits also my needs.