TK.

Really accurate work! :) Best Regards, Thorsten.

R2 is an older revision, so it has to be connected like described at the _old page. There is an interconnection test application available, which you can use to ensure that you made everything right. Best Regards, Thorsten.

All serial connections from MBHP_SID::J2 1:1 to MBHP_CORE::J10, only CS# has to be connected to a seperate pin of the core (propably MBHP_CORE::J14) - thats all. By connecting the CS# line of the second SID together with the CS# line of the first SID, you are already able to play both SIDs the same time (with the same parameters...) Best Regards, Thorsten.

I think that even without automation feature, this is a really useful circuit, because it saves you from buying an expensive mixer just to merge multiple audio outputs! Thanks Altitude for testing this (I haven't commented the circuit and layout, since it just looks good! :) Could you please bring this into the Wiki once you are happy with the result? Best Regards, Thorsten.

Hi Tim, I'm using a detented panasonic encoder for the datawheel of my MBSEQ (therefore it is DETENTED and not DETENTED2 in mios_tables.inc) - it works very stable since two years. Thats all I can say. But Alps are pretty good as well. The detends are very important for the sequencer for exact value adjustments - yes, non-detented are better for MBSID/MBFM (only exception: the datawheel should be detented) Best Regards, Thorsten.

no problems from the programming side, but do you have C skills? Best Regards, Thorsten.

As stated in the wishlist, a first release cannot be expected before next year, some other projects should be finished before. Best Regards, Thorsten.

A second AOUT_LC module is not supported, this is documented in the ChangeLog (which you've translated ;-). Therefore you will see the previous values of the first two outputs at the second two outputs again Best Regards, Thorsten.

This is really strange. Could you please post detailed step-by-step instructions how to reproduce this behaviour? 1) power-on MIDIbox 2) press select button 1 3) scroll with the encoder completely to the end of the main menu page 4) press 5th select button Is this how you are trying it, or is there something between step 1) or 2) (or between the other steps?) Best Regards, Thorsten.

Hi Tim, just want to mention, that it could be, that your encoders are not connected correctly. Just try the three different pinning combinations, one should work much better. Best Regards, Thorsten.

It works with my MBSID, with and without BankStick. Does anybody else notice the same effect? Best Regards, Thorsten. P.S.: are you using the latest release?

Hi Gerald, this is not possible with MBSID, there is not enough space for the translation table Best Regards, Thorsten.

I've developed an algorithm which can reproduce the bug on a deterministic way (see also this article: http://forum.microchip.com/tm.aspx?m=85120), but it requires a second core (with another program which is not described in this article), and a scope to catch the triggers. However, there is an easier, but not so deterministic way: enable the MIDI merger, and send & receive a large SysEx dump with MIDI-Ox. When you compare the dump (function provided by MIDI-Ox) you will sometimes (!) see additional zero bytes Best Regards, Thorsten.

Could you please contact Mike and inform him about this error? (I also see, that one pin of R8 is open... compare it with the original layout to see how it should be connected) Best Regards, Thorsten.

Ok, so: MIOS and bootloader are up-to-date, you propably never need to update them anymore. Now it's time to debug the LCD. Infos can be found here: http://www.midibox.org/dokuwiki/doku.php?id=lcd_module_liquid_crystal_display On the other hand: if you can't wait to get some sounds out of the SID and want to troubleshoot the LCD later - just upload the MIDIbox SID application, and connect the SID module Best Regards, Thorsten.

I must say, that this is exactly what I've expected, therefore I urged you to doublecheck the gameport MIDI in this way - mainboard based MIDI interfaces are sometimes not reliable, don't know if this is related to the chipset, or to the windows driver. Therefore you can find this info at the bottom of the troubleshooting page, but most people just ignore this hint, and expect the problem somewhere else... don't know, how this "trouble" can be avoided... To the upload errors: this behaviour is correct (invalid address), everything works well. Just read this thread again, look especially for the hints given for the mios v1.9 and bootloader v1.2 update procedure. Please read also the README.txt file of the MIOS update package Best Regards, Thorsten.

So, this means you can try a direct connection to the gameport like described here: http://www.ucapps.de/mbhp/mbhp_midi_gameport.gif Note the the optocoupler has to be removed from the core board! Direction of the Diode: just compare it with the original schematic, which is available at the MBHP_CORE page Best Regards, Thorsten.

Could you please also answer my questions? Otherwise I've no clear view of your issue. Best Regards, Thorsten.

Nein, weil ich weiss, dass er in meinem Fall nicht weiterhilft - der PIC ist ja nicht ausschlieslich mit dem Datentransfer beschaeftigt, sondern soll auch noch andere Dinge tun. Ich habe diesen Workaround mit dem Microchip Support ausdiskutiert, nachdem ich den Bug reported hatte - in meinem Fall hilft er nicht weiter. Es hat viel Ueberzeugungskraft gekostet (drei Reports verteilt ueber mehrere Monate mit Beispielprogrammen und Oszi-Snapshots), bis der Silicon Bug als solcher akzeptiert wurde. Und scheinbar wurde er ja nun zumindest fuer den PIC18F4620 und aehnlichen Derivaten gefixed, beim PIC18F4550 kann es also nicht mehr lange dauern... Gruss, Thorsten.

For those who are interested, the stereo version: http://www.midibox.org/midibox_seq/mbseq_v3_demo1.mp3 Best Regards, Thorsten.

We will see, I've enough MIOS code for a validation under realworld conditions ;-) Best Regards, Thorsten.

This could be a problem around the offset pots P2 and P4, maybe the -12V connections are missing? Best Regards, Thorsten.

Hi Tim, in normal mode, the encoders should increment without skipping values. The right place to setup this is mios_tables.inc (which you've already found). Did you also try the DETENTED and DETENTED2 setting? Even when you encoders are non-detented, the results could be better. An oversight can be found here: Best Regards, Thorsten.

INFO: It turned out that the new chip revision still contains the EUSART bug, therefore this article is obsolete. The original article was: ------------------------------ So, PIC18F4620: according to a recently published errata sheet (http://ww1.microchip.com/downloads/en/DeviceDoc/80282a.pdf), Microchip has finally released a new B4 silicon, where the EUSART bug is fixed. These are really good news for all future MIDIbox projects, because this means that in some months PICs will be available where the MBHP_IIC_MIDI module won't be required as a workaround solution for a reliable MIDI Out port anymore! My proposal is not to buy PIC18F4620 devices yet until some of us have verified that the right revision is available in the appr. shops. In general I think it makes sense to wait until november to ensure, that older revisions are out of stock, thereafter we could try the new one (the revision number can be checked with a program). Maybe companies like Mouser or Farnell could also be asked via email or phone before... For those who cannot wait, they can also use in future the combination of CORE and IIC_MIDI module - it works perfectly, but increases the complexity (-> lower success rate for electronic newbies) A new revision of PIC18F4550 (USB device) has not been announced yet. Best Regards, Thorsten.

Die Firmware ist fertig, ich finde aber keine Zeit, das ganze Geraffel zu dokumentieren. Der letzte Snapshot von Maerz liegt unter http://www.ucapps.de/tmp/mbhp_usb_pic_snapshot.zip Gruss, Thorsten.