TK.

Alright - so you could power the AOUT_LC in this way. Only ground and the digital lines need to be connected with the core - does it help? Best Regards, Thorsten.

The goal should be to determine, if the noise is comming from the power lines between MBSID and filterbox, or from the digital lines. Yes, a connection diagram would help Best Regards, Thorsten.

This nice little box has been made by Jack, he wrote: Jack - they are here (and soon in the gallery :)) The case looks really great, are they only available with the appr. hard disc drive?

What happens, if the SID output is not connected to the CEM input (clamp CEM audio input via 1k resistor (or so...) to ground) Best Regards, Thorsten.

Do you hear the same noise, if J1:Vs, SO, SC and RC are connected to ground, and Vd to +5V (in other words: all digital input pins connected to ground) Did you stuff the jumpers at J3? What happens, if you remove the TL072, and control the CEM directly with the 12bit output (-> Pin 3 of the TL072 socket) Best Regards, Thorsten.

Hallo, zunaechst einmal wuerde mich das sehr optimistisch stimmen, denn hoechstwahrscheinlich wird der MAX525 nichts abbekommen haben. Nun geht es nur noch darum, den MIDI In zu debuggen. Unter http://www.ucapps.de/howto_debug_midi.html findest Du hierzu eine Menge Tips, fange am besten mit den Punkten unter "If nothing happens, your MIDI-In is possibly not working:" an. Auf dieser Seite gibt es eine Menge Schaltplaene fuer Testschaltungen - selbst fuer den Optokoppler ist etwas dabei. Gruss, Thorsten.

Hi Alex, the random patch generator script contains a routine which allows you to write a MBSID compatible .syx file based on named parameters. This function could be re-used for patch converters (however, the input format must be known...) Best Regards, Thorsten.

Hi Jerry, I just have noticed, that this is an error in the cmios.h file - replace "extern void MIOS_Delay(void) __wparam;" by "extern void MIOS_Delay(unsigned char delay) __wparam;" and it should work Be careful with MIOS_Delay(), because it will block the MIDI parser for incoming events. Once the user task is delayed by more than 20 mS, a buffer overrun could occur. Normaly I don't use MIOS_Delay at all (only for debugging), and prefer the use of a timer Best Regards, Thorsten.

Hi Julian, what happens, if you connect the ground and +5V line of the AOUT_LC module directly with your PSU (or port J2) instead of CORE::J6? Especially for the ground line this makes sense (the PSU ground pin should also be used as starting point for the ground for the CEM module - starlike wiring!) Best Regards, Thorsten.

Hi Frank, regarding the USB PIC, I will send you a PM (some new things happened :)) I'm impressed that you spent the effort for implementing the HUI emulation in assembler, even the MM and LC (preliminary) are available in C in the meantime... However, so far I remember, there is only one function which handles the cursor for CLCDs, thats LC_CLCD_Msg_CursorUpdate. Only if LCD_MSG_D, 0 is set, the extra wide spacing is used, otherwise the normal spacing. But there is a big problem: the display buffer for incoming characters is only 128 bytes, 2x80 bytes consume 160 byte memory, thats too much. This means, that you have to change several other routines in lc_clcd.inc, where I cannot give you a solution immediately. I guess the whole file needs to be rewritten, most parts can be removed, some (less) need to be added. If this sounds too confusing, then check this version: http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip, it's easier to read :) Best Regards, Thorsten.

Fuer Slaves ist der integrierte SSP ein Muss, fuer Master ein "nice to have". Wenn die Pins noch nicht belegt sind, macht es auf alle Faelle Sinn, zunaechst einmal das integrierte Peripheral zu verwenden, bevor man auf Software ausweicht. So kann man bspw. ein neues Datenpaeckchen vorbereiten, waehrend das vorige versendet/empfangen wird. Ich selbst bediene externe schieberegister ausschliesslich via Software, weil die SDI/SDO/SCL Pins meistens belegt sind - soviel macht das auch nicht aus - bei der MBSID hatte ich mal den Einsatz des MSSP als letzte Massnahme zur Performancesteigerung gedacht, doch viel ist da im Vergleich zur momentanen Softwareloessung nicht mehr rauszuholen. Tip: code aufrollen, auf keinen Fall eine Schleife zur Uebertragung der einzelnen Bits verwenden.... Gruss, Thorsten.

Hallo Pico, danke fuer den Tip! Nun haette ich mein eigenes WinXP doch nicht neu installieren brauchen, nachdem der Treiber einer Pinnacle USB TV Karte den PC waehrend des Starts zum Absturz gebracht hat Gruss, Thorsten.

Hi Ilmenator, I'm happy that the C wrapper finally animates more people to realize application by themself :) To display messages: they are described here: http://www.ucapps.de/mios/mios_sysex_implementation.txt With lcd-command 01 the LCD won't be cleared, which means, that the fader information will still be visible If it is required, that the message vanishes once a fader has been moved, then you need to add a call to MIOS_LCD_MessageStop() to the AIN_NotifyChange hook If you want to print the message permanently, then you need a more sophisticated sysex handler. A (more complex) example can be found in the MIDIbox MM application Best Regards, Thorsten.

Yes, it seems that I oversaw this at the time I included the keytracking feature. This parameter has shifted the Mode and Channels entries one to the right, which means, that the table in cs_menu_io_tables.inc has to be adapted accordingly I will fix this with the next release. It could take some days, since I will also change the license... Best Regards, Thorsten.

Hi Billy, "digital pots" are provided by some manufacturers in form of integrated chips. I cannot tell you, which one is the best, because I never used such ICs by myself. But so long they provide a serial interface (SPI), they could be controlled from a MIDIbox CV with small software changes in cv_aout_lc.inc (just only the byte encoding has to be changed). Is there anybody who could recomment a certain digital pot type? Best Regards, Thorsten.

Rio has added a bunch of new fine patches to the preset library - thank you! :-) The current preset package can be downloaded from http://www.ucapps.de/midibox_sid.html If you want to contribute your own creations to the library, don't hesitate to send me the files in .syx or .patchlib format Best Regards, Thorsten.

yes, just take the MIDImon application as an example. In j5_din.inc, function USER_J5_DIN_NotifyToggle you could branch directly to USER_DIN_NotifyToggle, it has the same parameter interface. By adding an offset to WREG and MIOS_PARAMETER1 (e.g. 0x80), the buttons will get their own unique IDs. But so long no DIN modules are connected, you don't need to take care about this (the ID is 0x00..0x07) Best Regards, Thorsten.

Hi Robin, nice to read about the good progress! :) For tremolo I would propose to write a seperate function without any parameter (like void SendTremolo(void)); This function can get the current pot value with 'MIOS_AIN_Pin7bitGet(xxx)' (where xxx is the pot number, a constant), and the value of the two buttons with 'MIOS_DIN_PinGet(yyy)' (where yyy is the button number, also a constant). This function has to be called from the AIN and DIN hook whenever the pot or button values changes. The advantage of this single function is, that the code exists only once - this prevents inconsistencies. 420 lines within a function are really a lot, but so long it's easy to read, I would let it like it is. You could try to generalize functions which are oftenly used. E.g. if Note events are sent, write a function SendNote(chn, note, velocity) instead of calling MIOS_MIDI_TxBufferPut three times. Such functions not only improve the readability, but also the quality of your code, because they prevent a certain types of programming errors (e.g. that at one place only two bytes instead of three will be sent) Best Regards, Thorsten.

Do you know the CE/GS/etc. licenses, which are required for all electronical devices which are sold within the european union? Doing EMC tests in special laboratories isn't that cheap. However, before somebody gets me wrong: I still don't accept your plans before you've really demonstrated your contributions, my statements made yesterday are still valid (http://www.midibox.org/forum/index.php?topic=6216.msg38370#msg38370), and I will propably switch to a better license which matches better with my intentions. A techniqual answer (because this is the main intention of this forum instead of starting flame wars): You propably need another PIC with more ADC channels in order to avoid jitter problems (biggest problem here: all PICs with more than 8 channels have an integrated EUSART, and this peripheral is buggy). You will also notice an increased latency caused by the higher number of conversions to scan all pins, and the memory consumption will be higher (which means: less room for features). Best Regards, Thorsten.

Just write a mail to mike, he has the .brd file Best Regards, Thorsten.

Thats really strange, I know that the schematic is correct (e.g. because Mike made a PCB based on this schematic, and it works fine). Concerning serial/parallel connections: the SDA and SCL pins have to be connected together, I guess that this is still the case on your module? You should be able to disconnect a wire in the chain in order to check, which one is causing the problem? Best Regards, Thorsten.

Yes, but it's hard to estimate, if you are earning more from your business than giving back. Worst case: not you, but maybe the next guy who requests for permission sells hundreds of MIDIboxes over Ebay, but gives zero support. I'm not sure if the community is ready to reply to an increased number of newbie postings like "how to send a certain sysex event" or "I want feature xxx - asap!". So long this project is focused on DIY, the support effort regulates by itself (a little) to a range of people with technical skills. Do you see the point? Best Regards, Thorsten.

Ich habe Michael vor ein paar Wochen ueber die Aenderungen schonmal vorab informiert, er wuerde sie uebernehmen. Allerdings sollten wir warten, bis die ersten Leute die Boards getestet und fuer gut befunden haben. Tim wird zwei Versionen releasen: eine Single und Double Sided - letztere produziert er selbst, die Single Sided ist eher fuer Michaels PCB Prozess geeignet Gruss, Thorsten.

Are you able to write anything into a BankStick? If not, two or more connections of your BankStick board might be swapped. What happens, if a single BankStick is connected -> directly <- to the core module (not using a special board, but maybe only a socket with some wires going to J4) Best Regards, Thorsten.

Great! :) This is no "topics solved" board like the Troubleshooting section, but you will get it in this way: [tt] / / / Solved! \ / \/ [/tt] Best Regards, Thorsten.