TK.

The MBSID should show the patch name at the second line, this name should be updated whenever you send a new patch with JSynthLib. But the "wrong character" problem is very new to me - it also seems that characters are missing (but this could be a sideeffect) - not sure if this effect can happen if datalines are swapped Best Regards, Thorsten.

(ich kann diese grosse Latenzzeit irgendwie nachvollziehen ;-) Gut zu wissen, dass man sich wieder Hoffnung machen darf! Gruss, Thorstem.

Hallo Pearl, die C version von MBLC wird kein Grafikdisplay unterstuetzen - fuer mich war es damals ziemlich viel Aufwand, diese spezielle Option (die nur von extrem wenig Leuten verwendet wird) einzubauen, und ich moechte die ganze Arbeit nicht nochmal tun. Gruss, Thorsten.

[x] please publish some samples :) Best Regards, Thorsten.

I'm confused, did you read the FAQ? I enhanced the answer there especially for you! Best Regards, Thorsten.

alright, I've received the source code, but cannot see any dependency between BankStick and the VFD driver - the implementation of the driver is very good and shouldn't cause problems. So, I've no idea what could go wrong here Are BankStick accesses the only problem, or is anything else also not working? Best Regards, Thorsten.

This MIDIbox SID was made by pwx The big question: which case did he use for his design? :-) (here a link to the large view: http://69.56.171.55/~midibox/midibox_gallery/pwx1_large.jpg

Yves built this really clean and stable controller Not only the panel looks nice, check especially the internals - respect from my side! :) More pictures can be found at this webpage: http://perso.wanadoo.fr/yves.rouquier/midibox/photo.html

nicht nur das, der Driver waere wahrscheinlich viel umstaendlicher zu programmieren, sprich: mehr Codespeicher wird verbraucht, sprich: weniger Platz fuer zusaetzliche Synth Features, und das wollen wir doch alle nicht, oder? ;-) Gruss, Thorsten.

Hi, it doesn't matter which MIDI events are sent, due to the large MIDI output buffer which is provided by MIOS (a FIFO), the timings are very relaxed once an (button toggle) event has been determined Best Regards, Thorsten.

Hi Steve, so far I can see, the order is just reversed: OLD NEW 0: 12 5 1: 13 4 2: 14 2 3: 15 1 4: 1 15 5: 2 14 6: 4 13 7: 5 12 thats an easy change, just add following lines below the USER_AIN_NotifyChange label in main.asm: USER_AIN_NotifyChange ;; reverse order of pin numbers in MIOS_PARAMETER1[2..0] movlw b'00000111' xorwf MIOS_PARAMETER1, F [/code] (hope it works) Best Regards, Thorsten.

Hi Moritz, the details can be found in the PIC18F452 datasheet, which can be downloaded from the Microchip page. Chapter 14.5 describes the PWM module, it also contains some hints for the configuration. I just have noticed, that only Timer2 is allocated - this means, that there are no MIOS specific restrictions. Best Regards, Thorsten.

so, the hardware seems to be ok, then it must be a problem with the VFD driver. I don't know Seppoman's implementation, could it be that it uses register addresses, which are normaly reserved for the MIOS or the MBSID firmware? Or in other words: which addresses are used by the driver? Best Regards, Thorsten.

Please forgive me, that I'm not able to give you an sufficient reply to all your questions/assumptions. I even don't find the time to complete the layout of MBHP_BURNER, which should replace MBHP_JDM due to all these strange problems (I'm neither the designer of the JDM circuit, nor the programmer of IC-Prog, therefore it's also VooDoo for me... the MBHP_BURNER design and the P18 programming software are much more "straight-forward") :-/ Most of the effects you described (even the strange ones like the slowly dropping voltage at the clock pin) are normal (I don't know why, I only know that this doesn't hurt, since the clock is normaly toggled very fast), but: this seems to be the problem. The MCLR voltage must be stable during programming - maybe your two 9V blocks are not strong enough? Do you have a 15..20V PSU, or two PSUs which could be combined? Best Regards, Thorsten.

Just have a look into mios_reset.inc, what do you see? Two goto instructions at the same address (the BSL replaces the first one by a goto to itself) It doesn't matter if you replace the first goto (two 16-bit words) by two NOPs, or by another goto... Without loosing too much words: the BSL is not required to boot MIOS Best Regards, Thorsten.

Hi, I've added some comments to the FAQ: http://www.avishowtech.com/midibox/wiki/index.php/Question%20and%20Answers#QA10 Best Regards, Thorsten.

it's not required to alter the (default) tables of mios_tables.inc, you can let it like it is. I guess that it's a different problem that I noticed today during the programming of the EG see also the comment in eg.c: // eg0_int.LAST_GATE = eg0.GATE; // doesn't work with SDCC v2.5.0 [/code] it seems that a direct bit copy won't be handled properly by the compiler. This means, that also following line in map.c: [code] aout_gates.G0 = midi_note[0].GATE; cannot work. Could you please try the following modification (in map.c) aout_gates.G0 = midi_note[0].GATE ? 1 : 0; [/code] and if this doesn't work, try: [code] if( midi_note[0].GATE ) aout_gates.G0 = 1; else aout_gates.G0 = 0; Best Regards, Thorsten. P.S.: I must admit that I'm currently not able to test the gate function by myself, since my AOUT board is within a screwless box, which cannot be opened so easily. I've no external plugs for the gate outputs...

Hi Pilo, the source code of the BSL is part of the mios_v1_8_src package However, you only need to add two NOPs at 0x0000, and the program should start without the bootstrap loader Jidis: maybe such a generic sysex tool could be part of MIOS Studio (sooner or later) Best Regards, Thorsten.

Hi Stefan, could it be, that the VFD consumes so much power, that the core supply falls to <5V? This could evtl. explain, why the BankStick cannot be accessed properly. Which voltage do you read between the various Vs/Vd pins (ground/+5V) when the VFD is connected, and when not... (Solution for this case: either a seperate 7805 for the VFD, or a stronger PSU) Best Regards, Thorsten.

Hi Moritz, how many motors should be controlled? The PIC contains two special hardware peripherals for PWM generation, one is not allocated by MIOS and can be used for any purpose (e.g. the MBSID application uses this module to generate a 1 MHz clock with 1:1 duty cycle) The second one is free, if the application doesn't need the USER_Timer process Best Regards, Thorsten.

Hi, v1.1 is now available, it provides two 16bit LFOs (instead of 8bit), and an envelope generator. My hope is, that the next additions are implemented by you! :) Moxi: of course, you can add up to 128 gate outputs by using shift registers. I don't want to support J5 outputs by myself, since this could lead to a short circuit if somebody enables such an option so long analog pots are connected to J5 Best Regards, Thorsten.

Maybe you've overseen that the MBSID Sidplayer gets use of the SIDstation protocol, that the support for this protocol is a propratary extension of SIDPLAY1, and that the source code of this version is not available. Do you expect that somebody develops a new SIDPLAYer based on your wishes? Then please say this clearly (so that I can say clearly that I've no interest in spending any more effort for this toy - maybe somebody else?) Best Regards, Thorsten.

Hi Dave, such a touch sensor feature is already provided by MIOS, you don't need additional digital logic. More informations can be found here http://69.56.171.55/~midibox/forum/index.php?topic=1544.0 Best Regards, Thorsten.

Great! So, only Martin's issue is still open. Martin: could it be that there is a syntax error - you can check this in main.err Important: there must be at least one space character before each instruction, otherwise it will be interpreted as a label Best Regards, Thorsten.

So long you can live with static MIDI event assignments, and without a "toggle" feature, it's easy to extend a MB64 or MB64e to 128 buttons and LEDs. The ain64_din128_dout128_v1_3 application give you some inspirations (read the comments) Best Regards, Thorsten.