TK.

Hi, you could control the CC parameters directly via pots in the following way: in sid_ain.inc you can insert a routine which branches to several routines depending on the moved pot. The routines have to forward the pot value to the CC handler by calling the SID_CCIN_Set routine. A simple example for one pot only: USER_AIN_NotifyChange ;; get 7-bit value of pot #0 movlw 0x00 call MIOS_AIN_Pin7bitGet ;; forward value to the CC handler ;; it expects: CC parameter number in WREG ;; CC parameter value in MIOS_PARAMETER1, so: movwf MIOS_PARAMETER1 ; save 7-bit value in MIOS_PARAMETER1 movlw 0x10 ; control CC #10h == Transpose V1/V2/V3 call SID_CCIN_Set ; call function return ; and exit AIN handler there are three examples in the download section which describe how more pots can be handled. And maybe one of the next SID firmware release will provide another example... Best Regards, Thorsten.

Hi Dan, yes, the A/K pins are not necessary to control the LCD. Hm.... you wrote: does this mean that the core is running with the same LCD type for both displays? This will not work, you have either to change the type setting in the ID field during burning the first-level bootstrap loader, or you have to add a MIOS_LCD_TypeSet function call to the LC_Init hook of the application. Best Regards, Thorsten.

Hi, currently I'm porting the MB64seq step by step to MIOS. It's not very difficult and it doesn't consume that much effort, but currently I haven't so much time for MIOS, therefore the final sequencer release can take some weeks. The menu interface is already running - the look&feel is 100% compatible to the PIC16F version, but the implementation is totally different - a more modular way which allows to add submenues (also hierachically) very easily. The menu can now optionally controlled by a data wheel (==rotary encoder) and via MIDI for a remote link. And it will be reused for the MIOS based MIDIbox64 and MIDIbox16E. The button handler now also supports control via MIDI, so that all functions are also controllable from another MIDIbox or from a computer based sequencer. The next step will be the sequencer engine, it will also redesigned on a modular way, so that multiple instances can run in parallel. Only the memory and the user interface will limit the number of tracks. Triggering patterns via buttons or program change messages is already possible with the PIC16F application, sure it will also work with the reimplementation. Programming MIOS applications: the example applications in the download section describe how to handle with the MIOS hooks. You will get a better understanding once you modified and tried it with a real existing box. Programming teams: maybe we should try this once all PIC16F applications have been ported, because they should provide a good fundament for improvements and customizations. Sampler or soundfonts: requires a lot of memory and a large data store device. I would prefer an old PC or homecomputer for this job, a PIC based (multichip) solution would be more expensive Best Regards, Thorsten.

Hi Dan, ok, with a PIC16F core you have to connect the LED rings to port J7, it should work w/o problems Best Regards, Thorsten.

It is similar to the display I got from Christian some time ago (DMF6104). I haven't found the time to write a driver yet, but it will be supported. I'm unsure about the performance, maybe it will be slower than the KS0108 type GLCD Best Regards, Thorsten.

Just a note: in a few days Tim aka SmashTV will offer premade PCBs, Kits and a PIC burning service in the US - more infos soon :) Best Regards, Thorsten.

Hi Gilles, MIDIbox16E only supports undetented encoders, MIOS supports detented and undetented types. Just show me a datasheet and the exact part number before you make the order Best Regards, Thorsten.

Hi, all DIN and DOUT connections are free configurable. In this way you can decide by yourself, if you want to have a full setup or a downstripped version with less buttons & LEDs. The configuration has to be done in main.asm (general settings), mios_tables.inc (encoder settings) and lc_io_table.inc (button & LED settings) Best Regards, Thorsten.

Hi Dan, the initialization is exactly the same - the display will be turned on with the "0x3f" command, thereafter you should see the pixels. Also the bus interface is exactly the same. Are you able to control the contrast? Do you see gray pixels? If not, the Vee->V0 connection via the pot has not been setuped correctly. You could also measure Vee against ground, should be ca. -10V. The level at V0 should be between -8V and -10V Another possible reason could be the reset line (remember the HD64240 problem?). The reset input should be tied to +5V. If this doesn't work, try ground (the datasheet doesn't make clear if the reset is inverted or not) Best Regards, Thorsten.

yes, the application registers all incoming LED status messages so that they are also saved during the alternative layer is active :) Best Regards, Thorsten.

Hi Dan, in this case the best solution is to set the BPM to "MIDI slave", so that the box synchronizes to the MIDI clock and starts/stops with the appr. controll messages which are sent by Logic. If the box doesn't receive the clock, you possibly have to enable this under Options->Settings->Synchronisation Settings Best Regards, Thorsten.

Hallo Johannes, ja, Du bist kurz davor :) Nun hilft es nur noch, die 5V Versorgungsleitung nachzuverfolgen. Irgendwo ist die Verbindung zum 7805 unterbrochen. Gruss, Thorsten.

Yes, the power supply doesn't deliver enough current. If possible just fade down the backlight Best Regards, Thorsten.

Hi Dan, not this isn't correct. The shift registers have to be defined in the main.asm file: ;; used by lc_ledrings.inc LEDRINGS_SR_CATHODES EQU 8 ; shift register with cathodes of the 8 LED rings LEDRINGS_SR_ANODES_1 EQU 10 ; first shift register with anodes of the 8 LED rings LEDRINGS_SR_ANODES_2 EQU 11 ; second shift register with anodes of the 8 LED rings note that here the shift registers are counted from 0. This means: number 8 is the 9th shift register in the chain Best Regards, Thorsten.

I didn't create my schematics with eagle, so they will not help :-/ However, the modules are so compact that you can just join them together - it will save a lot of effort! Best Regards, Thorsten.

In some menues the snapshot button is also used for other functions. But it's ok, you can use the "snapshot" function for restore and another for store, or you can hold the snapshot button 3 seconds in order to store the bank - the function itself is defined via "Special Function Button" event (some kind of meta event, see the appr. list for available functions) Best Regards, Thorsten.

I would prefer the EC24E, it costs the same but sends 24 pulses/rotation. In the catalouge it isn't clear if this is really a detented or non-detent type - however, if it is detented it will only work with MIOS Best Regards, Thorsten.

It will also work well with PIC16F877 :) Best Regards, Thorsten.

A very impressive layout :) Just a note: the touch sensors require an additional DIN shift register which can be connected at the end of the last DINX4 To the box layout: I would add at least one dedicated button for MIDIbox LC specific functions. Currently following functions are supported (see lc_io_table.inc): #define ID_MBLC_DISPLAY_PAGE0 0x80 ; switch to page 0 #define ID_MBLC_DISPLAY_PAGE1 0x81 ; switch to page 1 #define ID_MBLC_DISPLAY_PAGE2 0x82 ; switch to page 2 #define ID_MBLC_DISPLAY_PAGE3 0x83 ; switch to page 3 #define ID_MBLC_DISPLAY_NEXT 0x84 ; switch to next page #define ID_MBLC_SWITCH_LAYER0 0x90 ; switch to layer 0 (like radiobutton) #define ID_MBLC_SWITCH_LAYER1 0x91 ; switch to layer 1 (like radiobutton) #define ID_MBLC_TOGGLE_LAYER 0x92 ; like a "caps lock" key #define ID_MBLC_HOLD_LAYER 0x93 ; like a common "shift" key #define ID_MBLC_SWITCH_LEDMETER0 0x98 ; ledrings are working as normal #define ID_MBLC_SWITCH_LEDMETER1 0x99 ; ledrings are working as meters #define ID_MBLC_TOGGLE_LEDMETER 0x9a ; like a "caps lock" key #define ID_MBLC_HOLD_LEDMETER 0x9b ; like a common "shift" key just pick your favourite behaviour. I think at least a shift button with "hold" function should be used, this enables you to switch the LEDs and all other buttons (in later versions also the encoders and motorfaders) to an alternative layer. Best Regards, Thorsten,.

Hi Dan, this is one of the good ones - as you can see in the datasheet: it stores the pixels vertically. The command set is compatible, so it should work with GLCD mode 1 w/o problems. Would be great if you could ensure this :) 2) yes, this has to be programmed. No problem with MIOS so far, but requires some skills 3) if you want to use it as second GLCD: yes, a second core. For MIDIbox Link just connect the grounds together and MO of the "master core" to the MI of the "slave core". Thereafter the "master core" (your MIDIbox LC) can send special SysEx strings or similar to control the second GLCD via remote (but here again: implementation is easy - routine has to be inserted into the MIDI processor handler - but requires programming skills) 4) no, you would have to program an additional layer Best Regards, Thorsten.

not really, but for myself it's some kind of sport to get it running ;-) It's still usefull for applications which are more relaxed on timings. Best Regards, Thorsten.

Ok, der Optokoppler wird mit Spannung versorgt, aber liefert kein Signal. Nun mal die andere Seite testen: Die LED sollte nun nur dann leuchten, wenn MIDI-Daten empfangen werden. Je hoeher die Datendichte, desto heller. Falls sie nicht leuchtet, solltest Du nochmal die Polung der Diode vor dem Optokoppler ueberpruefen. Falls sich dann immer noch nichts tut, hilft vielleicht noch folgender Trick um die Funktion des MIDI-Interfaces am PC sicherzustellen: schliesse einfach den MIDI-Out an den MIDI-In (Feedback-Schleife) und sende mit MIDI-Ox ein beliebiges MIDI-Event (bspw. das virtuelle Keyboard aktivieren). MIDI-Ox sollte das Event anschliessend sowohl im Output, als auch im Input-Fenster anzeigen. Gruss, Thorsten.

Hallo Johannes, hast Du zufaellig eine LED zur Hand? Damit koenntest Du das MIDI-In Signal direkt am PIC testen: Fuer diesen Test loetest Du am besten zwei Kabel an die Unterseite des Core Moduls. Die LED sollte immer aufleuchten (Polung beachten: das kurze Beinchen ist die Kathode und muss ueber den Vorwiderstand an Vss angeschlossen werden). Solange nur vereinzelte MIDI-Events empfangen werden, tut sich nicht viel, bei einem laengeren SysEx Stream sollte die LED jedoch merkbar flackern. Solange die LED direkt am Rx Pin angeschlossen ist, wird der PIC uebrigens keine MIDI-Daten erkennen (die LED verbraucht zuviel Strom), aber Du kannst auf diese Weise feststellen, ob die Verbindungen zwischen dem MIDI-In Port und dem Rx Pin ok sind. Falls die LED nicht aufleuchtet, koenntest Du das Signal auch mal am Optokoppler ueberpruefen (Pin IC2:6). Falls da nichts rauskommt, ueberpruefe Pin IC2:8 (den +5V Eingang des Optokopplers - vielleicht kommt die Versorgungsspannung nicht an) Gruss, Thorsten.

The reason why I haven't started with a public PayPal account yet is that I want to prevent that people transfer much money to my account in the hope that I would do some individual extra work for them (developing a customized hardware or something similar). Sometimes it's really difficult to explain them that I only want to realize things which are interesting for myself, which brings the running projects forward and which helps me to improve my knowledge about electronic and software development. I guess that most of the people who are working on free stuff are thinking the same. The MIDIbox projects are just my personal contribution to the public domain, my "thank you" for the free stuff which I'm using for my own work. However, donations... hmmmm.... maybe somebody of you know the good old days before internet when public domain names requested to send them postcards. It would be nice to see some pictures of the country/state/city/township from where you are coming from. I'm also very happy with CDs from your own music or from your favourite artist (I remember: Steven started with it some months ago, and in the meantime I own a nice collection of special CDs, donated by MIDIbox users, which I mostly hear during my tinkering sessions :)) Best Regards, Thorsten.

Hallo Johannes, wie sieht denn Dein Powerswitch aus? Hast Du dafuer eine Bestellnummer? Mich wuerde es auch mal interessieren, wie man mit einem Schalter ein Netzteil ueberfordern kann. Zum MIOS upload: bei einem jungfraeulichen Chip ist es normal, dass der "Request for Upload" String alle 2 Sekunden gesendet wird. Waehrend des Uploads sollten jedoch Acknowledges erscheinen. Vermutlich ist der MIDI-In nicht richtig angeschlossen (polung pruefen) Gruss, Thorsten.