TK.

you've got mail... since you plan to send me a T6963C based GLCD for a new MIOS driver, just send me this display too, so that I can search for the problem. Best Regards, Thorsten.

Following features have been added: metering events are now handled by the emulation button and LED functions can be assigned independently to the DIN/DOUT pins (-> lc_io_table.inc) some MIDIbox LC specific "special functions" are provided by the emulation which can also be assigned to DIN/DOUTs: Layer Hold/Toggle/Select: switches between two IO tables. Works like a shift (optionally "Caps-Lock") key on a computer keyboard. This saves some buttons (64 buttons/LEDs are enough for a usefull handling) Display Page Select/Next: selects between 4 different LCD layouts - see below LEDring metering Hold/Toggle/Select: allows to use the LED rings for level metering Due to the metering feature, some new display pages have been added, here an overview: This is the well know layout from the first versions This page displays additional horizontal meters at the top Here the big MTC and status digits are replaced by vertical meters Just another variation. The LEDring positions are displayed as virtual knobs. The last page is usefull if the LEDrings should be used as level meters (hmmm... maybe an animated gif would demonstrate the nice show effect better ;-)) The position & font/icons of the "display elements" (host message, MTC digits, meters, knobs, etc...) can be changed in lc_glcd.inc A new display page has also been added to the CLCD (character display) option, based on the ideas by Axel. However, I expect that it has to be changed again due to the new metering feature ;-) Planned for the next release: external MTC display (LED digits) external LED meters enhancements for the CLCD option (e.g horizontal meters) Best Regards, Thorsten.

Bingo! No I forgot to integrate the top-level menu which only shows the bank name, patch number, MIDI channel and which allows to select the patch via encoder. I also forgot the save function --- will be added soon Best Regards, Thorsten.

Ok, I see. The text is wrong, but the interconnections are correct. So - did you try Pin RD0? Best Regards, Thorsten.

one after another... ;-) Best Regards, Thorsten.

Hi Kent, the layout look really great! But I would propose to mount 4 or 8 slave PICs on one board in order to reduce a lot of wiring effort. The junction to the core module should be 1:1 (same pinning like J5/J6/J7) to simplify the soldering. Also the pinning of the MIDI junctions should be the same like CORE:J12 and CORE:J13 so that connectors can be exchanged for testing if necessary. Best Regards, Thorsten.

Hi Dan, so it's clear - you still have the old schematic. Maybe the file cache of your browser loaded the old plan? CS1 -> Pin RD0 (J8:SO) is the correct connection Best Regards, Thorsten.

The easiest solution would be that you just start with the GUI, so that I can add the PIC code generator later. Best Regards, Thorsten.

Hi Pearl, yesterday I've integrated this function into the LC application in form of a "layer button". Release: maybe tomorrow (I want to add other features...) Best Regards, Thorsten. P.S.: locator buttons are not required, such a feature is already provided by LC :)

Doh! You are right! Ok, meters will be provided very soon! :) Best Regards, Thorsten.

Hallo Johannes, diese Bauteile haben keine Polaritaet. Beim Quarz sollte man lediglich aufpassen, dass die Beinchen nicht das Metallgehaeuse (oder gar die Leiterbahnen des PCBs) beruehren. Aufpassen muss man bei: ICs, Transistoren, Spannungswandlern, Dioden, LEDs, ElKos, 1MHz Oszillator des SID Modules, Steckern... Gruss, Thorsten.

Joysticks von einer RC Fernbedienung: dass ich darauf noch nicht gekommen bin (ok, meine RC Zeit liegt schon ein paar Jaehrchen zurueck ;-)) - klar, diese Joysticks sind ideal, weil sie meistens mit 10k Potis ausgestattet sind Gruss, Thorsten.

Der Optokoppler sollte eigentlich nicht daran schuld sein. Der Rx ist ja lediglich ein Eingangspin, der nicht treibt, und deshalb auch keinen Kurzschluss verursachen kann. Ok, bevor wir nun weitere Ursachenforschung treiben, probiere einfach den anderen PIC aus. Gruss, Thorsten.

Problem is that I don't know how to visualize it better. Let's take a look under my MB64 case: ;-) Best Regards, Thorsten.

Hi Kent, alright, a preliminary schematic can now be found here: http://www.ucapps.de/tmp/midi_router.pdf It's a simple master-slave design. Every slave acts as a IO device and provides a Tx buffer of 64 bytes and Rx buffer of 128 bytes. The slave firmware will be so simple, that it never has to be updated again, therefore a programming socket is not required. The brain of the system is a PIC18F based core which accesses the PIC slaves over a parallel bus. A handshake protocol (Request/Acknowledge scheme) ensures that only one PIC drives the bus at one time. Up to 8 slaves can be connected. The 100k terminators at the end of the bus ensure proper signals for fast accesses (like SCSI). The master core will cyclicaly request every slave for new data. Incoming data streams can be filtered, merged, converted and routed to any MIDI Out(s) Best Regards, Thorsten.

Without BankStick only one patch is available, which is stored in the internal 256 bytes EEPROM. Best Regards, Thorsten.

It doesn't matter, the master fader just have to send the MIDI event "E8 <low-byte> <high-byte>" However, if you want to have a 10-bit resolution, a PIC18F core is required Best Regards, Thorsten.

I haven't found the switch in Logic which enables the VU meter option of LC, can somebody help me? Best Regards, Thorsten.

three core modules, some DINx and DOUTx modules and software skills (or somebody who helps you to customize this controller...) Best Regards, Thorsten.

Hi Kieran, well, a simple 1-track/32-step sequencer has already been integrated (the Wavetable sequencer). However, a more complex sequencer should be possible, but it depends on the requirements. A 4-track TB303 style sequencer is very simple and could be added w/o problems. However, there is no place to store more than one pattern, so it would only be usefull for live sessions. A more complex analog style sequencer like MB64seq requires an additional core. Best Regards, Thorsten.

Hallo Stefan, probierst Du mal den RxTx-Test aus? http://www.ucapps.de/howtodebug/test_rxtx.hex.zip Er leitet die eingehenden MIDI events direkt an den Ausgang weiter - damit waeren zumindest die softwareseitigen Fehlerquellen (z.b MIDI Merger disabled und Device Nummer != 00) ausgeschlossen. Gruss, Thorsten.

Hallo Jens, folgende Dateien helfen weiter: http://www.ucapps.de/midibox/midibox_plus_16.pdf (Schaltplan) http://www.ucapps.de/midibox/mplus_pcb_v1.gif (PCB Quickview) http://www.ucapps.de/midibox/mplus_pcb_v1.brd (Eagle Datei, kann mit der Freeware Version eingeladen und ausgedruckt werden) Desweiteren helfen vielleicht auch die Fotos auf der MIDIbox Plus Seite weiter. Gruss, Thorsten.

This requires some kind of "radio button" function (means: one LED active at one time). With MIDIbox64 this can be implemented with meta events, with MIOS you just have to insert the code into an existing application (I can provide an example if necessary) Best Regards, Thorsten.

Fine - so it must be a minor problem. :) Power is ok, contrast also. Let's double check the CS lines, they must be connected to: CS1 -> Pin RD0 CS2 -> Pin RD3 CS3 -> Pin RC4 CS4 -> Pin RC5

My offer is still valid: if you send me a display for one week, I will setup a dedicated driver for MIOS Best Regards, Thorsten.