TK.

FYI: MBHP Projects -> MIDIbox SID -> Control Unit Btw.: the menu navigation has been implemented on a way which allows to reuse the code for other synthesizers. Maybe I should release a "MIDIbox TC V2" with a prepared menu structure for some favourite VST instruments. :) Best Regards, Thorsten.

Hallo, na da laeuft ja wirklich schon ziemlich viel! Super! :) ja, die ungenutzten analogen Eingaenge sollten auf Masse gelegt werden, ansonsten wird die Firmware permanent MIDI-Daten senden, weil die Spannung an den an den Pins quasi "undefiniert" ist und sich dadurch immer wieder Werteaenderungen ergeben, die von der MIDIbox dann brav weitervermittelt werden. Nach Deiner Beschreibung wuerde ich aber vermuten, dass entweder die Potis oder die AIN module nicht richtig angeschlossen sind. Am besten ueberpruefst Du mal mit einem Messgeraet, ob vielleicht einer der Masse/+5V Anschluesse der Potis und AINs keine Verbindung zur Versorgungsspannung hat. Visuell kann man das natuerlich auch checken, aber das dauert meistens laenger ;-) Gruss, Thorsten.

Hi, the LEDs can be accessed by the same events which have been assigned to the buttons. Unfortunately it isn't possible to control them by alternative MIDI messages, unless you are using a BankStick (in this case the LED events are always the events which have been stored in internal memory), or the MIDIO128 firmware --- or MIOS of course ;-) Best Regards, Thorsten.

Hi Dan, it seems that I've removed this pdf by fault - also on my harddisc :-( So it could take some days until I find the time to create the diagram once more. However, the required interconnections can already be found in the MF schematic. The simplest test program for the MF module is the "mf_calibration" application. Touch sensors: I don't own panasonic faders, therefore I cannot say if there is a solution Best Regards, Thorsten.

Yes, thats a good tip. It seems that there is an soldering error in the power supply section. Under http://www.ucapps.de/howtodebug/test_tx.hex.zip you will find a test program which just sends a MIDI event every second. Best Regards, Thorsten.

It's a great pity! :-( If you own a C64, you could test the SID with the computer, otherwise I see no chance without a PIC. However, when I look into my shelf which is full of electronical components I see a lot of PIC16F877-04 which I got as samples from a german distributor. He sent me the 4 MHz version by fault but never wanted them back. I used two of them some weeks for my SID modules (overclocked!), but now I've replaced them by PIC18F452. Since I've no use for these PIC16F chips anymore, I could give you one for free, just email your postal address :) In the meantime you should try to find the root cause for this failure, so that it never happens again! Best Regards, Thorsten.

In the meantime I noticed that the DIP version of this chip has been discontinued. It seems also that the availability is not so good as expected (see the http://www.findchips.com results). But at the Beyond Logic page a short introduction about an upcoming PIC18F device with integrated USB support can be found - well, this will be the solution! :) The USB interface allocates some pins which are used by the core module for other functions, but at least a "MBHP USB" module just only for the data transfer (and maybe also as reduced MIDIbox core) could be created. Estimated price: about 15 Euros! :) Now we only have to wait for the release of the PIC18F2450 . There is already a firmware available for this derivative, which can be extended for MIDI transfer very easily! Best Regards, Thorsten.

Well, how about a code generator which generates the PIC assembly instructions which are necessary to map and process data streams. Could also be provided with a graphical user interface. But this won't be my job (too much effort) Best Regards, Thorsten.

Hi Dan, Currently this option isn't supported, therefore you have to connect the MIDI INs of the other SIDs to J11:MI and J11:Vs As soon as the "through" option is available, the slave SIDs have to be connected to J11:MO instead so that the control surface is able to insert additional events. Please don't start with the panel before I've finished my own panel (I will begin in 1-2 weeks). I don't expect problems, but if I notice that the handling could be improved by adding more buttons (or encoders/pots), the layout could be completely changed. Yes, definitively! I just have finished "Step A" of the control surface (see download section, documentation will follow this evening). It's so flexible, that every parameter (also wavetables!) can be edited by using some buttons and an optional rotary encoder (for faster data entry). It supports 2x16, 2x20, 2x40 LCDs w/o loss of any possibilities Everything else will be optional stuff for an improved direct access to the parameters. Best Regards, Thorsten.

Yes, thanks for the tip! I will try it also :) Best Regards, Thorsten.

thanks! :) Best Regards, Thorsten.

COOL! An USB controller in a handy DIP package with IIC interface (the same protocol which is used by the BankStick) Maybe this is the solution - especially because MIOS already supports IIC. It is possible to connect multiple IIC devices in parallel! MIOS_USB_* :D Best Regards, Thorsten.

Hi Dan, thats ok, the concept allows to load the application also into the MIDIbox LC (or into a PIC18F based MIDIbox64) so that you can control the SIDs from another MIDIbox via remote ;-) Best Regards, Thorsten.

Hi Phil, yes, thats correct. Rotary encoders are now handled like buttons and have to be connected to the J9 DIN chain. Once the DIN pins have been assigned to an encoder, USER_DIN_NotifyToggle will not be called for these pins anymore. USER_ENC_NotifyChange will be called instead. So far as you don't use the AIN multiplexers, a graphical LCD or a SID module, RC0-5 are free. My suggestion is to add the scanning routine to USER_SR_Service_Finish, this routine is called on every update cycle for the DIN/DOUT chain (update period can be lowered to 1 ms). It guarantees that no event get lost. The timer hook could be used for higher sampling periods. Best Regards, Thorsten.

MIOS has a user hook called "USER_DIN_NotifyToggle" which is called on every change. Generating On/Off data is a piece of cake - see the AIN DIN DOUT example :) Best Regards, Thorsten.

thanks SB :) And thanks also for the warning - yes, I was wrong, the I/PT derivative has another package and is not compatible to the MBHP Core module! Best Regards, Thorsten. P.S.: I had no problems with ordering more than 5 parts, it wasn't clear if Microchip means "5 pieces" or "5 different chip types", so I just tried it ;-)

Hi Kyo, every encoder allocates 2 digital inputs, with 56 rotary encoders you could only add 16 additional buttons Ok, alternatively you could plug some buttons to the analog pins, but this would require a AIN module (since more than 8 analog inputs are needed for this solution) Best Regards, Thorsten.

Hi Dimitris, first question before I write 1k of infos which you already know: did you download the Logic Control Manual from the Emagic site? Because this manual comes with a description of all "button IDs" Best Regards, Thorsten.

Hi Dan, fine that it works! :) No, this release doesn't provide the control surface handling, this has to be done when my own hardware is ready (could take 2-3 weeks). You could modify sid_ain.inc. SID CC's can be controlled with the SID_CCIN_Set function. However, in the meantime I had the idea for a very flexible minimal control unit which is similar to MIDIbox TC, but much faster in the handling (it's a mix between the VST parameter handling of Logic Control and the F-key handling of a HP48 calculator ;-)) and it will provide several hardware options: 2x16, 2x20 or 2x40 LCD, 8 buttons, 6 buttons/1 encoder, 8 buttons/1 pot, etc. So, if you want to control your SID(s) directly without a computer, it could be a good idea to continue with the MIDIbox TC example. I will release the interim solution possibly tomorrow :) Best Regards, Thorsten.

Really great price! :) Best Regards, Thorsten.

Hi Matteo, now you will find some more informations about MIOS under Concepts->MIOS->Introduction which should explain the reasons, why the MIOS concept is more useful than the PIC16F solutions :) Best Regards, Thorsten.

Yes, I've ordered 3x24LC256, 3xPIC16F877 and 3xPIC18F452 I/P, the package was delivered via FedEx directly from Taiwan and I haven't payed any cent! :) Best Regards, Thorsten.

Hi Kyo, yes, you have to use two core modules for this setup, but it will work :) I would use one single core, 4xDINX4, 4xDOUTX4 as "MIDIbox Link Forwarding Point" (at the begining of the MIDI chain) only for the encoders and LED rings, and a second core as "MIDIbox Link Endpoint" for the rest. An AIN module is not required, since MIOS supports also unmuxed (non-multiplexed) access to the ADC. The appr. configuration has to be made in the initialization routine: ;; initialize the AIN driver ;; use 8 faders movlw 8 call MIOS_AIN_NumberSet ;; don't use the AIN 4051 multiplexers call MIOS_AIN_UnMuxed I will provide a test application for 64 encoders and LED rings in the next days. Best Regards, Thorsten.

Hi Dan, I've just added a MIOS introduction to my homepage which should make the concept clear. ;-) 4x40 LCD: sure - will work. But you have to enhance the application by yourself, so that it prints more or less usefull messages on the additional space. Thereafter you can send me your modifications so that I can release it with the official version. Best Regards, Thorsten.

Hi Matteo, you should follow the other postings, because I don't want to repeat myself every time... ;-) PIC16F: funny, but a lot of limitations. All of my PIC16F firmwares get the best out of this controller, but it is very hard to add even more features PIC18F: more memory, faster CPU, less limitations, same price. Order some free PIC18F452-I/P at Microchip, exchange the 20 MHz crystal by a 10 MHz crystal and you are ready for the next generation! :) Best Regards, Thorsten.