TK.

The formula is wrong, where did you found it? You need to add an additional part to v_out which depends on the adjusting current and the voltage drop at the pot voltage Why troubleshooting section? Are you not able to reach the 8V? I can select the voltage between ca. 5V and 10V. A higher pot value would make adjusting more difficult. What is the input voltage of your MF module? Best Regards, Thorsten.

Are all the jumpers at the programming port J3 closed? Best Regards, Thorsten.

Of course, the jumpers at the programming port should always be closed. They are only for programming via JDM or MBHP_BURNER Without these jumpers, your core will be powered from the MIDI connection, and this cannot work reliable So, is the upload working again with the jumpers? Best Regards, Thorsten.

Something that is new to me is, that some blocks can be uploaded correctly. Does this happen randomly? Or are these always the same blocks? Could it be a problem with the power supply? The PIC18F452 consumes (a little bit) more, since it runs at 40 MHz... especially during flash programming. Means: during code upload In general multiple "F0 F0 F0 F0" indicate, that the core has been reset several times. This can happen on: - no enough power - USART receive overrun error (unlikely so long the PC interface is working) - USART frame error on received bytes (can happen if the PC interface is running at a slightly incorrect baudrate) The rest of the bytes behind F0 which don't match with a common upload request could be related to a driver quirk on the PC MIDI interface. But it can be ignored, because the previous bytes where already wrong Best Regards, Thorsten.

So, if it has worked before, there is a high chance to detect the problem by going through the MIDI troubleshooting list: http://www.ucapps.de/howto_debug_midi.html Which tests are working, which not? Best Regards, Thorsten.

Could you please copy&paste all messages which are print by MIOS Studio within the upload window? Best Regards, Thorsten.

Sidenote: I already tried to help Shum via email, but without much success. So - if anybody else has an idea? Best Regards, Thorsten.

My proposal is to let these caps on the core module, and to bypass the outer pin holes of the 7805 (which is not mounted) as well as the pin holes of the rectifier (which is also not connected), so that all caps are routed to 0V/+5V This results into less noise at the digital line -> better sound capabilities! Best Regards, Thorsten.

Ich verwende keine Abschirmung, klappt trotzdem ;-) Gruss, Thorsten.

No, this is wrong. The modulation matrix provides two different modes. In one mode, it shows the connections between the source and targets. This display is always correct, you can switch to a slave and you will see the connections made for the slaves. Then there is a new feature which I've quickly implemented based on a suggestion from a user. It shows the current (modulated) LFO and ENV values in realtime. You can see the waveforms sweeping! This is always a very nice attraction when you show the MBSID to your friends. Of course, these sweeping values can only be known by the PIC at which the engine is running, therefore you can only see the master values If you don't like this feature, just switch to the normal mode! Best Regards, Thorsten.

Ooof, your J2 connections at the SID module are looking very error prone! Best Regards, Thorsten.

Yes, the matrix is only a supplement. You could even control the modulators without any control surface, if the core module is connected to a PC, and you are using the JSynthLib editor, or a program which allows you to send MIDI Controllers Best Regards, Thorsten.

Meinst Du wirklich Pin #25, oder Pin #6 des SID (dort wo vorher der Oszillator angeschlossen war). Dieser Pin muss nun mit PIC Pin #17 verbunden werden - siehe Schaltplan, dort habe ich es beschrieben. Damit in Zukunft nicht noch mehr Leute darueber stolpern, habe ich bereits eine neue Core und SID PCB Version in der Mache. Deshalb wird die MBHP_CORE und MBHP_SID Seite momentan auch nur stiefmuetterlich gepflegt - das wird sich aendern Warum: die Details stehen hier http://www.midibox.org/forum/index.php?topic=5748.0 Kurzbeschreibung: wenn PIC und SID Takt asynchron zueinander laufen, kann es vorkommen, dass bei einem Schreibzugriff auf das SID Control Register das Gate getriggert wird, obwohl es bereits geloescht war. Gruss, Thorsten.

Yes, the transistor will work with both voltages without danger Best Regards, Thorsten.

Hi, the most common error which are made are wrong interconnections between SID and CORE module - note that on the old PCB versions, the two 8pin ports are not connected 1:1. At the MBHP_SID module webpage you will find some diagrams which show the wiring (e.g. mbhp_sid_c64_psu.pdf), and at the MIOS download page you will find an mbsid_interconnection_test which allows you to test all cables to the SID module Is this test passing? (Test procedure is described in the header of main.asm) Best Regards, Thorsten.

You've got mail Best Regards, Thorsten.

I want to start with the implementation in autumn 2006, I assume that the final release will be ready very fast if everything is planned properly (this document and the long time span until the start). Most features which are listed here have already been evaluated in MIDIbox FM, MIDIbox SEQ and MIDIbox SID-D, so that I don't expect difficulities. Since MBSID V2 will be almost hardware compatible, I don't know if it really makes sense to wait - just start with MBSID V1, and upgrade later Best Regards, Thorsten.

Maybe there is an internet cafe close to your location where you are able to download all the required packages for 1..2 EUR? Best Regards, Thorsten.

MIDI doesn't provide handshaking, this means: it's not enough to send the bitstream, you need some error correction or a second level protocol in order to ensure data coherency Best Regards, Thorsten.

No, you need to download the MPLAB toolchain from the microchip homepage as well in order to assemble the source code. The resulting .hex file can be uploaded with MIOS Studio Best Regards, Thorsten.

I also think that this is because of a missing heatsink - the two LCD backlights make the 7805 really hot, sooner or later the voltage will drop much below 5V, and this resets the chip Exit button: it should work, you will get into the menu Drum mode: the future MBSID V2 will offer more possibilities, but I don't plan to enhance the drum mode. Instead I'm planning a more general way to assign values to the layers, which makes the drum mode obsolete. (as Moxi has mentioned - check the wishlist -> http://www.ucapps.de/midibox_seq_v3_wishlist.html :) Best Regards, Thorsten.

Rio, I think that you've just missed all the infos I've already written down here: http://www.ucapps.de/midibox_sid_v2_wishlist.html Best Regards, Thorsten.

Changes in cs_menu_io_tables.inc are only required when you've built a Control Surface, and when the control elements (rotary encoders, buttons, LEDs) are not connected to the original pins which are documented in my connection diagrams. In general: so long you are building a MIDIbox which doesn't differ with my own hardware, then you normaly don't need to change the sources, and you can use the precompiled .hex files Perl: I think you don't really need it for MBSID so long you already have MIOS Studio and Java, is this the case? Your "problem" with internet bandwidth brought me to the idea, that somebody could compile a CD which contains all tools which are required for MIOS based applications. It could be distributed via mailorder. Unfortunately I don't have that much time to do such things in parallel to all the other stuff, but maybe somebody else feels motivated? Writing docs: this would be really great, especially because I think that you will see the projects more from the user, and not from the developer side. This should result into a much more understandable documentation for normal MIDIbox users who don't have the technical background knowledge. The Wiki is predestinated for such "user manuals" - regardless how much will be contributed, it makes me and all the users happy :) Best Regards, Thorsten.

I think that even driving a matrix with let's say 1024 buttons (via 1 DOUT and 4 DINs) is not impossible, it's only a question of RAM consumption and desired latency Best Regards, Thorsten.

Hallo Pico, ich glaube, dein Projekt wuerde auch die Allgemeinheit interessieren! :) Solche Messstreifen sind schon etwas feines, wie hoch ist die Aufloesung? Und wieviel kosten sie? Man koennte sie bspw. als Ersatz fuer Motorfader hernehmen :) Gruss, Thorsten.