The idea is a MBHP module which interfaces to a standard PC QWERTY keyboard (anyone can get these 2nd hand cheap or free) and produces IIC slave output to connect to IIC bus of 18F MIOS core.
This way a user can have a reletively hugh array of dedicated midi event triggers for very little cost or construction effort. The module plus DIN keyboard socket could be added to many (any?) existing MidiBox.
I imagine that the module would output an array of bits or event messages which the MIOS Core would translate and include in the MIDI output stream. In this way the great diversity of user requirements is satisfied by modifying the MIOS host (the core application). Â
The module code itself should not be particularly complex and should not require user customisation.I imagine a Core PCB “stuffed” with a 16F877 would surfice. In fact the layout could be simpler than that of the core.  If customisation is neccessary (it probably isn’t) then the module could  itself be MIOS 18F.
The QWERTY keyboard could be spraypainted a new colour and decals or other custom labels to replace the existing key markings.
Possible uses:
Midi Remote - dedicated application shortcuts and functions
Nice idea! Should be pretty easy to do, I guess. I could really use a module like this, as I have a huge amout of QWERTY keyboards sitting around here. I would use them as program changers…
A MBHP Universal-Shortcut-Keyboard-Interface for all kinds of Midievents - a lot of options for every Midibox-Maniac  :D
I got some old PC keyboards too… Â ;D Â ;D Â ;D
…e.g. Â Midibox SID controllable by keyboard, a rotary encoder (datawheel, endless pot) Â + LCD Â
I’m highly interested!
Addendum:
The module code itself should not be particularly complex and should not require user customisation.I imagine a Core PCB “stuffed” with a 16F877 would surfice. In fact the layout could be simpler than that of the core.  If customisation is neccessary (it probably isn’t) then the module could  itself be MIOS 18F.
Year - it would be usefull to take the normal MBHP Core Module (with a new “MIDIBox-Keyboard Firmware” for the 16F877 or 18F452) - the Core Module is already tested, available and provides a lot of useful connectors - the LCD-Connector is a nice feature especially for working with a Keyboard [“special funktions” & future options]…
There a different ways an I idea like this could go.
One approach is to make it a subsystem that is as transparent as possible. This means that it interfaces to an existing Midibox without any modification to the (host) Midibox firmware.
This way all display/setup and other functionality as to how the keys are used is up to the Midibox firmware as it is currently implemented.
The way I can see of doing this is to have a small say PIC16F84 application scanning the keyboard codes as per the project link above. The PIC then loads a 64bit serial/serial shift register with the keyswitch states which are in turn shifted into MIOS by the normal DIN operation. The 4517 is a low cost dual 64bit serial in/out shift register in DIP16 package.
would this be possible to implement usig the commodore 64 keyboard?I’m sure more ppl than me have a few lying around after SID Extraction.could even build it into the case, and maby add a few pots and small lcd?just an idea, as i hate to throw things away…(and since starting my sid project i have actually used some things i kept because “i might be able to use it one day”)
@arumblack: Nope, not without BIG modifications on the C64 keyboard. It’s not a IIC device. If you look at your keyboard, there are many cables going to the motherboard. I think it’s some multiplexed matrix system or so behind there…
The keyboard adpator I’m planning at the moment is to accept serial data from a standard PC AT Qwerty and convert it into IIC slave interface for connection to a MIOS core.
It will be based on the low cost PIC16F84 (18pin device),
programmable from a JDM. Once constructed it is unlikely that the firmware will ever need change. All user options and functionality are provided by the MIOS Midibox it is connected to.
If someother exotic keydevice is wanted, I suggest to cut tracks(!) and wire keyboard switches to DIN module(s).
I’ll be oherwise very busy for a few weeks, then I expect to implement it quickly. I’ll post back here when more news.
would this be possible to implement usig the commodore 64 keyboard?I’m sure more ppl than me have a few lying around after SID Extraction…
Liked the idea so much I made one. Had a C64 keyboard leftover from my MBHP_SID project.
I wrote it for a PIC16F628 (or you can use a 16F84, but the 16F628’s are only $2.50 USD), also needed a demultiplexer ( DM74LS138 ) so you can have a 8 by 8 matrix. This Makes the whole thing very cheap to make.
I don’t know MIOS well enough yet, but I’m sure you could do the 8 by 8 matrix on the core module. You wouldn’t even need a multiplexer (unless you wanted to save pins)
Right now I just have the keys mapped to midi notes and patch changes, but I’m thinking of making it more complex.
I can post more details later if people are interested.
How complicated it would be to add support for a mouse? Or yet better, two mice?
I have demonstrated in few places (this year at Pixelache, and Assembly) a way to utilise an optical mouse to read the movement of a turntable (that is scratching).
My app used second mouse plugged into a USB port, but since Windows allows only one mouse pointer, the mouse is occupied to the scratching limiting the possible UI. So, a midi version would be nice
The con with this method is that there will be more latency (compared to the mouse straight at USB port), which is really bad. I’m not sure though how bad the latency would be.
But generally speaking, the optical mouse is really great, since you can use it to read pretty much anything that moves (yeah, you can have a jog wheel big as a your table if you wish .