TK.

Hi Justin, L1 is a small coil and absolutely required to get the DC converter working. And yes, the MAX chip has to be supplied with 5V. However, since your LCD module already comes with a converter, you don't require this circuit. Just measure the output voltages if they are ok... Best Regards, Thorsten.

Hi Kejace, check that your MIDI interface is working: loopback the MIDI Out of your PC to the MIDI In of your PC and send a SysEx dump by using the "Send/Receive SysEx" function of MIDI-Ox. The number of sent bytes must match with the number of received bytes. If it doesn't match, search for a new driver for your MIDI interface/sound card. If not available, you can possibly fix this problem by lowering the Low Level Output Buffer size (normaly set to 2048 ) and by increasing the output delay (normaly set to 0 ms) in the MIDI-Ox SysEx configuration menu check the polarity of your MIDI cable (the MBHP_CORE schematic http://www.ucapps.de/mbhp/mbhp_core.pdf) shows the rear view of the MIDI socket) check the polarity of the protection diode D1 check the supply voltage of the optocoupler IC2 between pin #5 and #8: 5V check the output voltage between pin #5 and #6 of IC2: 5V (caused by the 1.2k pull-up resistor R6) try the MIDI-In tests: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1055726526 Best Regards, Thorsten. FAQMARKER

Yes, in sync mode the wavetable rate controls the MIDI clock divider. So far as I remember the required value for 16th notes is 123 Best Regards, Thorsten.

Du lagst schon richtig, der Markierungsring (egal in welcher Farbe) befindet sich an der Kathode, und diese ist im Schaltplan mit einem Strich markiert. Hier: http://avi.dezines.com/mbhp/info.html gibt es uebrigens eine weitere Ansicht vom Core-Modul (US Version), in der die Polaritaet der Diode klar zu erkennen ist. Gruss, Thorsten.

The pinning of your encoder could be different. If you don't own a datasheet, just try all possible combinations. Best Regards, Thorsten.

If the sync function hasn't been activated in the patch, it has to be enabled by sending CC#125 to the right channel with value 1, 3 or 7 Example: B0 7D 01 (hexadecimal form) See also the SID CC implementation table. Logic Configuration: open Options->Song Settings->Synchronization, click on the MIDI tab, and select the MIDI interface(s) which should send the clock Best Regards, Thorsten.

Which operating system are you using? It should regognize the new USB device immediately after you plugged it into the socket. If not, there must be a bad junction between the USB pins of the cypress chip and the socket. Check also the crystal and the reset inputs. Best Regards, Thorsten.

This is a hardware related topic. This cannot be done without removing existing features due to memory limitations. I can send you the source code (-> request it via EMail), but please note that I don't support the PIC16F projects anymore. PIC16F programming definitely makes no fun, especially the PIC16F MIDIbox firmwares are everything else than expandable since I had to use a lot of dirty programming tricks to get so much functions as possible into the small memory. Several people who tried to integrate new functions finally gave up. If you want to do the right step, if you want to program new functions without so much effort like for the old PIC16F firmwares, then switch to MIOS! Best Regards, Thorsten.

Hallo Wolfgang, die Diode dient quasi als Schutzmassnahme um den Optokoppler vor Verpolung zu schuetzen. LEDs koenntest Du ebenfalls multiplexen (bspw. 64 LEDs an zwei Shiftregistern), oder auch direkt an die DOUT pins anschliessen, falls Dir die Programmierung des entsprechenden Drivers zu kompliziert erscheint. Wenn eine LED direkt an einem DOUT angeschlossen ist, kann man sie besonders bequem umschalten: MIOS_DOUT_PinSet0 oder MIOS_DOUT_PinSet1 Beim Multiplexen muss man die Ansteuerung selbst in die Hand nehmen, so wie in den "leddigits*" Beispielen, oder auch in der MIDIbox LC und der MIDIbox SID Applikation. Egal ob gemultiplexed oder nicht, es sollte sich jeweils ein Widerstand im Signalpfad befinden, eine LED sollte niemals direkt mit 5V betrieben werden! leddigits_16.pdf: ja Du hast Recht - danke fuer den Hinweis - fixed Gruss, Thorsten. P.S.: Meine Adresse habe ich Dir gerade per Forum-Mail geschickt.

Please read the comments in the main.asm header and open all files which are mentioned there to understand the purpose and the configuration possibilities. Best Regards, Thorsten.

It must be the resistor or the appr. junctions Best Regards, Thorsten.

fixed Best Regards, Thorsten.

No idea, I've no schedule for my sparetime... ;-) Best Regards, Thorsten.

No idea, I've no schedule for my sparetime... ;-) Best Regards, Thorsten.

So here the extracts: 1: use a multiplexer or use two AND gates and switch the lines with a free pin of the core module 2: PIC Rx -> XG Tx, PIC Tx -> XG Rx, PIC ground -> XG ground 3: don't mix analog with digital wires 4: the maximal length of the whole shift register chain shouldn't be longer than 1m. Longer lines could also work, but I cannot guarantee this -> try it out! 5: quality... 8: required for analog signals only 9: use MIOS_BANKSTICK_CtrlSet to address the BankStick, the manufacturer guarantees 1 million write cycles for every single byte, but in practice it's even more (10 million+++) 10: has to be evaluated by yourself. Suggestion: save the most frequently used parameters of all channels in RAM, and the more exitic parameters (Fx setup, drum parameters) in BankStick 12: all logic circuits require a reset for a proper startup Best Regards, Thorsten.

Yes, this is possible by changing the addressing scheme (please do some experiments with the circuit first in order to understand how it is working... it took me 15 minutes to write this example, but I don't want to explain all variations, because this would take hours) Best Regards, Thorsten.

Does anybody have a copy of my answers from yesterday? Best Regards, Thorsten.

from ToFiC (check also his homepage for more pictures: http://monsite.wanadoo.fr/kasper_korrils/ He wrote that this is the prototype, but it already looks cool! :)

Hi Ian, which error messages do you mean exactly? Best Regards, Thorsten.

Hallo Wolfgang, die Informationen zur MIDIbox LC sind quer ueber das Forum verteilt ;-) Hier gibt es Photos: http://www.midibox.org/midibox_lc_photos/ Gruss, Thorsten.

Ok, das erklaert alles. Dein COM Interface wandelt die Baudrate von 38400 Baud (PC-Norm) auf 31250 Baud (MIDI-Norm) um - die Daten treffen also schneller ein, als sie ueber die MIDI Leitung weitergesendet werden koennen. Wenn der Hersteller keine Flusskontrolle vorgesehen hat, kann es schonmal vorkommen, dass bei der Baudratenwandlung der Eingangsbuffer ueberlaeuft, und somit Daten verloren gehen. Abhilfe: MIDI-Ox dazu bringen, dass waehrend der Uebertragung regelmaessig eine "Atempause" eingelegt wird - probiere mal verschiedene Werte fuer den Low Level Output Buffer (16, 32, 64, 128, 256, ...), und das Delay (1 mS - 20 mS) aus. Gruss, Thorsten.

With the MIDIbox Link concept you can cascade as much MIDIboxes as you want - the problem is the protocol defined by Mackie. It knows only "one channel" for transfering the control data. Programs like Logic Audio, Cubase, etc. are searching for one unit per port only, they are not prepared for handling more than one unit with a single MIDI In. So you see: it's software limited, but not by MIDIbox... no chance for a workaround, unless you would ask the big companies for help (but we all know the update policy of them :-/) However, if you see no chance to add additional MIDI In/Outs to your computer (Btw.: the MBHP_USB interface provides two In/Out ports), you can still use the linked boxes as generic controller. Best Regards, Thorsten.

Sende mal ein Ping-Kommando zum Core (F0 00 00 7E 40 00 0F F7), wenn etwas zurueckkommt, laeuft MIOS, und das Display ist nicht richtig angeschlossen. Falls nichts zurueckkommt, ueberpruefe das MIDI-Interface Deines PCs: den MIDI-Out zum MIDI-In zurueckfuehren, MIDI-Ox Sysex Tool starten, ein beliebiges .syx File starten und auf Send/Receive klicken - es muessen genausoviele Bytes ankommen wie gesendet wurden. Gruss, Thorsten.

Exactly! :) Every character set which consists of 256 characters allocates 2k, so you could store 8 different sets in flash and assign it to different scanline sections. A synchronization between multiple cores isn't realistic for this application. Main reason: the "goto" instruction which is required to poll a flag or a signal takes two cycles. This results to a 1-cycle error which will be visible on screen (jittering scanlines). It was a challenge to solve the jitter problem in the existing code - fortunately I found a solution which compensates the error (-> H_SYNC macro) For external, asynchronous signals a deterministic compensation isn't possible. Best Regards, Thorsten.

Hope that you take into account the the Mackie Protocol requires a dedicated MIDI port for every "Logic Control" Unit? Best Regards, Thorsten.