TK.

Hi Ole, does it also happen when the LCD backlights are not connected? Then it's definitely a thermal issue, caused by the too high voltage before the 7805 (7..8V would be better) Note: a core module can be supplied even with 12 or 15V at J1, but only if the power consumption is low enough, so that the 7805 doesn't get too hot. The two BLs, and also the LEDs, consume so much power, that a better fitting PSU is required. Best Regards, Thorsten. P.S.: before you buy a new PIC (I don't think that this is a problem!), consider to buy a PIC18F4620 and PIC16F88 (for MIDI out), so that you can use the new MBSEQ V3 firmware :)

fixed.

It's the MIDIbox of Klingen (he informed me about the upcoming article some weeks ago) -> http://www.midibox.org/forum/index.php?topic=4902.0 Best Regards, Thorsten.

Hi, It's a B4 (due to a bug in the application the wrong letter will be displayed) And here the bad news: I also got a B4 from Microchip some weeks ago, it turned out that the EUSART bug still exists. Microchip has released an incomplete errata sheet! I reported this mistake and only got this "typical" answer from the support guys: My hope was, that they update the errata sheet quickly, so that I can take it as a reference - but nothing happened yet! However, I haven't found the time to update all the relevant webpages at ucapps.de and in the wiki again - but the consequence is, that the MBHP_IIC_MIDI workaround will be required for the next years! Best Regards, Thorsten.

-> www.edrum.info Best Regards, Thorsten.

The core sends an upload request, but doesn't receive any SysEx block, therefore doesn't respond with an acknowledge. It's very likely, that the MIDI In port is not working -> the MIDI troubleshooting guide will help http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

thats correct. In theory you could use optocouplers for the Rx/Tx line of the MAX232 in order to decouble the PC from the core module, but I cannot give you a schematic for this, this would have to be worked out by yourself. Thats interesting, this might explain why the driver hangs up? Maybe because an incomplete event which was received due the "shortened" Rx line (sidenote: it's not completely shorted, because the optocoupler output is open drain - but the signal level at the Rx input of the PIC will be lowered). So - does it work more stable without the optocoupler, then you found a solution. If not, the RS232 link just doesn't work quite well with your PC, and either the LTC circuit has to be enhanced, or a common MIDI connection has to be used. Best Regards, Thorsten.

ja ich weiss nicht so ganz, wie ich die Frage verstehen soll. Nein, der MIDI Out vom Core arbeitet beim PIC18F4620 unzuverlaessig, und sollte deshalb nicht verwendet werden. Der Optokoppler ist fuer MIDI In - das Ausgangssignal des Optokoppler kann nicht direkt auf einen MIDI Out gelegt werden... Gruss, Thorsten.

Hi Ryan, sounds like a windows driver issue - a friend had a similar problem with his MIDI interface, it also locked up when heavy MIDI traffic was sent (or received). Fortunately there are two other RS232 drivers available (Roland and Kawai) - did you try them also? Jittering pot values are a general problem when the circuit is not galvanically decoubled from the PC, therefore for MIDI an optocoupler is normaly prefered. Does anybody know some measures, how to reduce the additional noise? I'm not an analog expert... (please write this into the Wiki) Best Regards, Thorsten.

See http://www.midibox.org/forum/index.php?topic=5860.0 Best Regards, Thorsten.

It could be somehow possible to realize a mixed C/ASM simulation, but why do you want to simulate the 2 second startup of bootloader/MIOS (which takes some minutes), just to execute this tiny routine? So far I remember, I copy&pasted the assembly routine into a dummy .asm file, and simulated it directly Best Regards, Thorsten.

The diodes prevent a short circuit when more than one button of the same row is pressed, so they are important. 1N4001 is a little bit oversized, 1N4148's are fine Best Regards, Thorsten.

Nein, die MIDI INs koennen nicht genutzt werden, das bidirektionalle MIDI Routing wuerde den Core zu sehr auslasten - umso einfacher ist der Aufbau der MBHP_IIC_MIDI Schaltung (bspw. kann der Optokoppler weggelassen werden). Das Weiterleiten von eingehenden MIDI Events ist derzeit nur auf den Default Port (welcher im PIC ID Header festgelegt ist) moeglich - hierzu im MIDI Menue den Merger einschalten. Gruss, Thorsten.

Hallo Christian, Option 2) waere moeglich, wuerde aber nichts aendern. Ich denke, dass Punkt 1) eher wahrscheinlich ist - evtl. hast Du uebersehen, dass der Link Button gedrueckt werden muss, um den Kontakt zu den Slaves herzustellen? Per default ist der Link deaktiviert, um eine evtl. Rueckkopplungsschleife mit externer MIDI Software zu verhindern. Der Link kann nach dem Einschalten auch automatisch aktiviert werden, wenn in main.asm das #define CS_MENU_DEFAULT_LINK auf 1 gesetzt ist. Gruss, Thorsten.

Hi Toni, after only one posting in this forum I cannot say if I've a good feeling about your venture or not. In general I'm always surprised, that people are asking for my permission before publishing all the design documentation to the public, or just presenting their completed MIDIbox and helping others to build the same, before thinking about selling it to non-DIYers. This is not the spirit I want to support. Best Regards, Thorsten.

Could you please exactly describe, what you've already tested? Your question is a little but unspecific... in general I would say: read the walkthrough, it helps! Best Regards, Thorsten.

Hi, it depends on your application - bitbanging requires to disable interrupts. The baudrate is very slow, much slower than MIDI. If something is received via MIDI while your function sends out a 4800 baud stream, data loss can happen at the receiver side - if you are sure, that nothing will be received, than I don't see problems here... Best Regards, Thorsten.

Hi Alkex, really great idea and especially good "execution" (I mean: nice panel! :) Best Regards, Thorsten.

This is propably the smallest MIDIbox SID with Step A Control Surface ever made! :) Doug wrote:

Potiwerte haben eine Aufloesung von 10bit, und somit einen Wertebereich von 0..1023 7bit erhaelt man, indem man den Wert dreimal nach rechts shifted: (pin_value >> 3) Damit liegt der Wertebereich dann zwischen 0..127 Alternativ kann man so wie ranger930 die MIOS_AIN_Pin7bitGet() Funktion verwenden, die macht das gleiche Gruss, Thorsten.

Beim naechsten LCD bitte supervorsichtig sein. Damit die Kabel nicht durcheinander kommen, kannst Du ein Flachbandkabel auch in drei Teile teilen (Stromversorgung/Backlight, E/RS/RW, D0-D7), und diese dann schrittweise mit dem LCD Interconnection Test ueberpruefen und dann am LCD anloeten Gruss, Thorsten.

I don't the pinout, but please don't make too much experiments by swapping the pins, this can damage the LCD very quickly! There is a LCD interconnection test application available at the MIOS download page, have you already tried it? Best Regards, Thorsten.

Thanks, I added them to the list A datasheet for the YMZ263-F is available on the web (unfortunately all sites I found require a registration), however, MMA capabilities doesn't sound that interesting... Best Regards, Thorsten.

... it's part of the MIOS update package, just have a look into the pic18f4620 folder Best Regards, Thorsten.

Hi Charsten, some people have created PCB layouts in the past, these are a good templates for vectorboards. Best Regards, Thorsten.