TK.

Hi, the 1.2k resistor is used to pull-up the open drain output of the 6N138. It's strange that the circuit works w/o power, because the optocoupler should electrically isolate the core module from the MIDI Out of your computer - the only possible current source. Did you mount the 6N138 in the right direction? Did you remove the 6N138 when working with the gameport? Best Regards, Thorsten.

Hi William, search for digital pots with 3-wire interface (SPI), example: http://www.maxim-ic.com/DigitalPotentiometers.cfm they can be daisychained like it has been done for the DIN and DOUT modules. So in fact only latency requirements limit the number of addressable devices per chain. The aout_example_v1_4.zip under MIOS->Download demonstrates, how to control multiple devices via SPI this circuit will kill you, once more than 4 bit resolution is required ;-) Best Regards, Thorsten.

Hi, > thanks for that great debug-sheet!!! I hope that it will provide so much checks in the future that everybody will be able to locate the errors w/o searching in the forum for hints :) > What´s exactly to measure at RA4 ? The resistor should be 1k > instead of 10k. My core voltage is 5.09 V and at RA4 i > do have 0.1V. You are right, this was an error in the schematic. The voltage level at RA4 isn't for interest. Although it's nice to know that it's 0V, this means that the bootstrap loader has switched on the output driver (and therefore: that the PIC is running). > The LED on RX pin lits, but doesn´t flicker when receiving > a sysex-stream. The voltages on the 138 are ok. how about > checking the optocoupler by connecting 5V/0V over 220Ohm > to the input? a good idea! I've added a new item to the list Is this test working: http://www.ucapps.de/mbhp/mbhp_core_midiin_debug2.gif If it does, there must be a problem with the optocoupler > Also the 1:1 connection to the gameport doesn´t solve the problem. Could be a driver problem - the gameport of my old mainboard also never worked under Windows, but only under Linux... ;-) > I think it is perhaps a wrong mios/bootstrap combination? No, the bootstrap loader works independent from MIOS > I downloaded bootstrap 1.1b and mios 1.4, wrote the bootstrap > with ID 0 to the pic. And you receive "F0 00 00 7E 40 00 01 F7" which indicates that the device ID is set correctly (with another device ID, for example 0x42, you would receive F0 00 00 7E 40 42 01 F7) > When sending the sysex to the pic, he doesnt react. my midi > interface is good, too (send/rec-sysex). ??? Now you will find another new item which demonstrates how to loopback MIDI w/o PIC. This helps you to ensure that the hardware itself is working ok > Is there another possibility to check midi-in, perhaps i can upload > a tool via jdm? this would be more complicated and fault-prone than using the boostrap loader > in addition: midiox says with the input "port" is sometimes > --- and sometimes xxx I know this effect, must be an imperfection in MIDI-Ox > one more: i´ve soldered the 10mhz osc inside the pic-socket, > but this shouldn´t make any problems. Your bootstrap loaders sends a proper request, so the PIC is running fine. So, check out the two new tests under http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

Hallo Peter, mit MIOS laesst sich der Bildschirm relativ einfach zentrieren, fuer ein 2x24 Display muessen folgende Zeilen unter USER_Init eingefuegt werden: USER_Init movlw 0x04 movwf MIOS_PARAMETER1 movlw 0x44 movwf MIOS_PARAMETER2 movlw 0x18 movwf MIOS_PARAMETER3 movlw 0x58 goto MIOS_LCD_YAddressSet Gruss, Thorsten.

Servus Lemonhorse, die PIC16F Version werde ich in Zukunft wahrscheinlich nicht mehr erweitern - zu aufwaendig. Die naechsten anstehenden Features lassen sich sowieso nur mit der PIC18F Version realisieren (analoge Outputs, selektierbarer BankStick, verschiedene Split und Layerfunktionen). Damit eruebrigt sich Frage 2 (bei der PIC18F Version werden keine Abstriche gemacht). Zu Frage 1: die Unterstuetzung eines 4x20 LCD ist von meiner Seite nicht vorgesehen - meine eigene Hardware steht und wird sich auch nicht mehr aendern :) Die Displays der PIC18F Slaves werden folgende Info zeigen: das passt auch auf ein 2x16 LCD :) Gruss, Thorsten.

Hi, you can change the direction by inverting the incrementer value in USER_ENC_NotifyChange. Example (not checked) USER_ENC_NotifyChange ;; inverting the incrementer: ;; if negative: incrementer = NOT incrementer ;; if positive: incrementer = (NOT incrementer) + 1 comf MIOS_PARAMETER2, W IFCLR MIOS_PARAMETER2, 7, addlw 1 movwf MIOS_PARAMETER2 ;; continue... Best Regards, Thorsten.

Hi, there are some examples in mb64_meta.inc But the virtual midibox doesn't support meta events, so you have to build a real one, first Best Regards, Thorsten.

Don't worry, another device ID is meant here which isn't essential. You can disable this dummy warning somewhere in the IC-Prog preferences. Best Regards, Thorsten.

Did you also try the MIDI In/Out ports of your PC? Best Regards, Thorsten. P.S.: the MIDI troubleshooting guide has been updated: http://www.ucapps.de/howto_debug_midi.html

...although it's cheaper than my 240x64 LCD. But it will require a seperate controller (or MBHP core module) + dedicated driver. And the contrast is possibly very bad... Best Regards, Thorsten.

Hi Nenad, seems to be a low-cost encoder, the spec doesn't say if it is detented or not... I wouldn't buy it. Why not purchasing a best-quality ALPS STEC16B03 for ca 2 EUR @ http://www.schuricht.de? However, rotary encoders are not supported by the PIC16F based MIDIbox64, they require a fast decoding routine which is only provided by PIC16F MIDIbox16E, or by MIOS of course. Best Regards, Thorsten.

Regarding your hardware setup: yes, this will work. The number of connected pots can be defined in the main.asm header, and for the DIN chains it doesn't matter. Best Regards, Thorsten.

Yep - sooner or later... ;-) Best Regards, Thorsten.

I found a solution - direct links are working again. Best Regards, Thorsten.

Sure - check the "generic remote" module, and see also http://www.midibox.org/users/dimitris/midibox_cubase_setup/index.html Best Regards, Thorsten.

Maybe sooner or later - but currently I've other priorities... so if somebody with programming skills feel interested: the changes have to be made in mb64_buttons.inc and mb64_leds.inc. The easiest way would be to switch between different DIN and DOUT maps depending on the state of a dedicated DIN. Best Regards, Thorsten.

Lieber nicht, bevor sie verdampfen ;-) Am besten baust und testest Du die MIDIbox schrittweise (Modul fuer Modul). So weisst Du, wo Du zu suchen hast, falls mal etwas nicht auf anhieb funktioniert. Gruss, Thorsten.

Fine fine, so send it to ik@midibox.org so that this FAQ will be part of the portal :) There is only one error: > make sure u have the latest sid_init.inc file it isn't sid_init.inc, but sid_ain.inc (http://www.ucapps.de/tmp/sid_ain_enhanced.zip). This file should also be uploaded to the portal - I won't support it in the future (means: I don't want to try it out with every new SID release) Best Regards, Thorsten.

Hi, the DINs are scanned every milisecond, so if the pulse width of the clock out isn't long enough, then you could use an external monoflop to enlarge the pulse. Better solution: take a look into the j5_din_v1_3.zip example, it explains how dedicated input pins can be captured. It's not limited to J5, you can use any free IO pin. The example shows, how to hook the capturing routine J5_DIN_Update to the SRIO driver, but you can also call it from USER_Tick for a higher update rate. 300 uS should be adequate enough. The J5_DIN handler will call USER_J5_DIN_NotifyToggle on every change which is comparable with the common DIN_NotifyToggle callback. Of course, you can send CC events from this function. Powersupply: balanced supplies should be seperated from digital units, so I cannot suggest to mix these voltage domains. Best Regards, Thorsten. P.S.: I will move this topic to the MIOS section since it's especially interesting for programmers.

Latency is no issue. And since I don't want to repeat myself every month, there is now a new entry in the FAQ, see QA35 Best Regards, Thorsten.

The first snapshot has been rolled out ;-) Steve: I discontinued the PIC16F version since it wasn't flexible enough. I'm using the MIOS based version by myself to turn the MIDIbox LC into a generic controller (w/o rotary encoders, this will be solved with the MIDIbox NG application) Best Regards, Thorsten.

No, the MIDImon allocates 3 DOUT registers of a DOUTX4 module. You don't need an additional core, e.g. the MIDIbox64 application allocates 8 DOUT registers maximum (=64 LEDs), this means that the remaining 8 DOUT's are free and can be used for other purposes. Just integrate the MTC module (see Concept->MIOS->Download led_digits_mtc_v1_3.zip file mtc.inc) into your project. Best Regards, Thorsten.

Fuer MIDIbox LC solltest Du auch kein anderes Display verwenden, nur ein KS0107/KS0108 basierendes Display bietet die optimale Performance. Leider kenne ich keinen Haendler, der dieses Display anbietet (andererseits: viele Distributoren stellen ihre Lagerlisten leider nicht ins Internet). Meins ist von Reichelt, d2k hat denen das letzte Displaytech 64240A abgekauft, seitdem ist es aus dem Angebot verschwunden :-( Anmerkung: das Displaytech 64240B ist uebrigens nicht kompatibel, es enthaelt einen anderen Controller mit horizontaler Ausgabe der Bytes (-> low performance) Gruss, Thorsten.

Hallo, am besten faengst Du von vorne an, um Dich langsam aber sicher in das Thema einzuarbeiten. :) Welche Hardware hast Du schon, laeuft der Core bereits? Ist ein Display angeschlossen, hast Du bereits MIOS und eine Testapplikation aufgeladen? Gruss, Thorsten.

Hallo Kay, per Software geht das leider nicht, und ich kann auch nicht empfehlen, das LCD-Modul zu oeffnen, weil es danach sehr schwierig werden wird, es wieder so zu schliessen, dass alle Pins Kontakt haben. Hier ein paar allgemeines Infos zu den unterschiedlichen Display Typen: http://www.lcd-module.de/deu/knowhow/knowhow.htm Gruss, Thorsten.