TK.

Natuerlich ist der 1.2k Pull-Up wichtig (Du kannst auch 1k nehmen) Hast Du noch mehr Komponenten ausgelassen? Gruss, Thorsten.

Diese Warnings sind normal, ignorieren. Mit den wenigen Angaben weiss ich nicht, woran es liegen koennte... eigentlich sollte das nicht passieren, egal ob Du irgendetwas falsch gemacht hast oder nicht, ist also eher ein robustness Problem. Wie hast Du das LCD angeschlossen, wie hast Du das CAN Interface angeschlossen? Gruss, Thorsten.

Hallo, wenn der alte Bootloader installiert war, und Du unabsichtlich das falsche .hex File erwischt hast, koennen beliebige Dinge passieren. Auch ein Checksummen Fehler kaeme dann in Frage, doch ohne weitere Analyse (sprich: auslesen des Flashspeichers) kann man das nicht so genau vorhersagen, da undefinierter Programmcode ausgefuehrt wird. Ansonsten kommt es zu diesem Fehler, wenn bspw. der Treiber des MIDI Interfaces eine Macke hat, doch ich nehme mal an, dass Du einen anderen PIC erfolgreich programmieren kannst. Im Grunde hilft hier nur noch Neuprogrammieren mit einem PIC Programmiergeraet. Falls Du keins hast, und auch niemand in Deiner Naehe eines besitzt, kannst Du mir den PIC einfach via Post zuschicken - wuerde Dich lediglich das Rueckporto kosten Gruss, Thorsten.

The clock signal cannot be measured with a common measuring instrument (you would need a scope...), but if you want to ensure 100% that the connection is available, just unplug the PIC/SID and use your multimeter in ohmmeter mode (0 ohm between the PIC->SID pin means: connected...) Best Regards, Thorsten.

Yes, the output current is not high enough for a headphone, an amplifier is required. Did you already check the clock connection between core and SID module? The SID won't run without. Do you have a V2 or V3 core module, a V2 or V3 SID module? There are small differences, which are documented at my website! Best Regards, Thorsten.

Sven: the jumping on slow movements could be related to the PWM values you are using. The MBHP_MF page discusses this topic in detail http://www.ucapps.de/mbhp_mf.html For 2x24 LCDs you need to adapt the large_screen_cursor_map[] in lc_lcd.c (note that there is a "#if MBSEQ_HARDWARE_OPTION" branch at the top - ignore this, use the map in the #else branch instead) Within the large_screen_cursor_map, each character of the message sent by the host is mapped to a position on your LCD. So far I remember, this mapping will only be used in Page 2 and 3 (initial display page can be changed in main.h) Best Regards, Thorsten.

Have a look into Wilba's schematics for his MB-6582 (-> http://www.midibox.org/dokuwiki/doku.php?id=wilba_mb_6582&s=6582), , he uses transistors as current sink. This only requires a small change in the firmware (outputs connected to transistors need to be inverted) Best Regards, Thorsten.

moved to the "MIDIbox of the Week" section. I like the clean case and the lovely buttons. :) Best Regards, Thorsten.

Should be fine, but I'm not 100% sure Best Regards, Thorsten.

Hi Enrico, I think that a LED matrix is less important than all buttons of the original panel layout. Sure, in general you could control all functions from the already existing keys, but it isn't ergonomic. Especially the GP buttons below the LCDs are important, they have different functions depending on the menu context - so, you have to see the text exactly above the button, otherwise your sequencer will be nearly unusuable, as it is too time consuming to find the right key to the appr. function which is displayed on LCD, which is far away! I think that the only buttons of MBSEQ which maybe could be removed are Metronome and Scrub - everything else is heavily used during a session Best Regards, Thorsten.

Hi Johnc, is it a common DC motor with two inputs? Then it could work. You can doublecheck this by supplying the motor with 5..10V DC, it's especially important that the motor changes the direction when the polarity is swapped. Best Regards, Thorsten.

Thanks for the little shock in the evening - I'm wide awaken again ;-) Yes, note A outputs 440 Hz (the scope jitters between 439.5 and 440.5, but this is a common measuring problem, don't panic!) Best Regards, Thorsten.

Hallo, beachte bitte, dass es auch eine verstaendlichere C Version der MIDIbox LC gibt (nach midibox_lc_v2_0_alpha suchen) Ja, NUMBER_SHIFTREGISTERS bezieht sich auf die maximale Anzahl der Register im DIN oder DOUT Zweig, je nachdem, in welchem sich mehr Register befinden. Sie werden parallel bedient um Zeit zu sparen, deshalb diese Abhaengigkeit. Gruss, Thorsten.

I've already written a v1_to_v2 patch converter script, but the resulting sounds need some finetuning, as the scaling of some parameters like LFO rate and depth is not identical between the two MIDIbox versions. I'm planning to release an overworked "vintage bank" soon. Best Regards, Thorsten.

The "First Steps" guide with some sound programming examples + new MP3s is now available under: http://www.ucapps.de/midibox_sid_manual_fs.html Best Regards, Thorsten.

So, you are not using the small transistor pre-amp of the MBHP_SID module before connecting it to your TDA7052 based amp? This could be the reason! Best Regards, Thorsten.

No, I was wrong - the version is up-to-date WR# should be 0 when ModWheel #14 is sent, it should be 5V on any other ModWheel value (see main.asm header) Best Regards, Thorsten.

Hi Alex, it is not required to remove the SID for this test. MIDI-Ox provides a control panel, from where you can easily send a specific ModWheel value. Reg. ModWheel value #14: I just have noticed, that there seems to be an error in the released test application - within the SID_SetPin14 function in main.asm, SID_SR_LAT_WR is set and not cleared (therefore CS# is propably always 0). I'm sure that I fixed this months ago, but it seems that I forgot to upload the new version Best Regards, Thorsten.

Ok - to summarize the findings of the last days: 1) there is digital noise when the MBSID firmware is running 2) there is no digital noise when the testtone firmware is running 3) the digital noise sounds like register accesses to the 74HC595 (in my ears...) 4) you still hear the noise, when the audio output of the SID is shortened So, the conclusion is clear: as previously assumed, there is a problem with the transistor amp circuit. Maybe some kind of crosstalk between the 74HC595 signals and the amp circuit. You don't hear this noise with the testtone application, as register accesses are only done during the initialisation phase. The MBSID firmware can access the registers periodically. I guess that you already checked the transistor circuit visually, and you are not able to find an error here. So, my proposal: desolder the components of this circuit, clean the PCB, solder them again Thats propably the fastest solution. Best Regards, Thorsten.

No, but nice idea. I can consider this in one of the next releases. Best Regards, Thorsten.

Hi, the problem with CNY17 is, that there are also parts which are "so weak" that a low pull-up resistor leads to a bad signal. This effect is propably caused by the manufacturing tolerance (german: "Exemplarstreuung"). Ca. 5 years ago, we had the situation that everybody who bought a CNY17 from Reichelt reported good results with 1.8k, but everybody who purchased the optocoupler somewhere else had to adapt the resistor value to 2.2k (and not to a lower value). Other people reported, that the optocoupler was only working with specific MIDI instruments. At the end I decided to replace this optocoupler by a one with integrated amplifier -> the 6N138 So, I can only highlight it again: don't use a CNY17 Best Regards, Thorsten.

P.S.: habe gerade nochmal die Suchfunktion des Forums verwendet, um nach aehnlichen Faellen zu forschen. In den letzten Jahren ist der Fall zweimal vorgekommen. Einmal war es der Optokoppler, beim zweiten Mal wurde einfach ein neues Core Modul aufgebaut (doch vermutlich war es ebenfalls der Optokoppler) Gruss, Thorsten.

Frame Error ist ein Flag, das vom USART gesetzt wird, wenn das Start-Bit zu frueh empfangen wurde. Hierfuer kommen drei Ursachen in Frage: entweder laeuft das PC Interface zu schnell (unwahrscheinlich), oder der PIC zu langsam (wahrscheinlicher), oder die Flanken am Ausgang des Optokopplers sind nicht steil genug (noch wahrscheinlicher). Das Problem liegt also entweder am Optokoppler+Beschaltung (Exemplarstreuung? Probiere mal einen kleineren Pull-Up an pin #6 - aendert sich was?), oder an der Quarzschaltung (wo hast Du den gekauft? Welche Kondensatoren verwendest Du?) Im Software Loopback Test wird dieses Flag nicht ueberprueft, hier kann man den Effekt eigentlich nur erkennen, wenn man einen groesseren SysEx Dump uebertraegt. Dies wuerde erklaeren, warum er bei Dir (scheinbar) laeuft. Gruss, Thorsten.

Connect it like the first one. Only exception: the CS# line of the second SID (right audio channel) needs to be connected to J14 of the core module Best Regards, Thorsten.

Hi *, the long-awaited MBSID V2 public beta test is starting now - more info + feedback here: http://www.midibox.org/forum/index.php?topic=9457.0 Best Regards, Thorsten.