TK.

Hi Nenad, it seems that there are some weak (bad soldered) connections on your board, because the MIDIbox runs totally "uncontrolled". Ok, let's do it step by step. LCD and PIC are working - fine - so you could use the test programs provided under Concepts->MB Hardware Platform->Test Programs in order to test every module seperately. This allows you to identify the root cause(s) step by step. Start with the AIN test program, thereafter with the button test (even if no DIN module is connected) in order to check if there are any floating inputs. I think that this already will give you some hints for the failures. Thereafter you can continue to debug the LTC --- the LEDs *must* flicker when any MIDI event is sent or received. If the LTC has not been connected properly, the core will receive a lot of random MIDI events from the floating MIDI In input - they will be forwarded to MIDI Out by the MB64 merger --- check this by connecting the 1.2k resistor (Core:R6). Thereafter no random MIDI event will be sent anymore. Best Regards, Thorsten.

Hi Zetor, congratulations! :D You can use the 15V power-supply for both, the core and the SID module. As less than 100 mA are drawn by the core circuit, the 7805 shouldn't get too hot. I'm also using just one power-supply for my two SID boxes. Best Regards, Thorsten.

Problem is that there are currently no IIC EEPROMs (those with a 2-wire interface) with more than 32k. However, the Microchip EEPROMs offer three chip select inputs, so that up to 8 chips connected in parallel can be addressed. This results into a large memory space of 256k... but since only special 24256 devices provide this feature, and since I don't own this types, it's not supported by the MIDIbox. RAMs: I don't know affordable IIC RAM devices. For common SRAM chips a lot of connections have to be made: i.e. a 128k SRAM needs 17 address lines, 8 data lines and 3 control lines... the number if wires could be reduced by using a latch like known from 8051 devices, and the data bus could be shared with the LCD bus --- but this would result into a design far from the (easy-to-solder) MBHP Best Regards, Thorsten.

No, it isn't ok, it must be exactly 10.0000 MHz, otherwise the MIDI baudrate will not be cannot be achieved Best Regards, Thorsten.

Du benoetigst das MPLAB ICE. MPLAB C18 habe ich noch nicht ausprobiert, aber dahinter versteckt sich soviel ich weiss sowieso nur eine Demo-Version des (teuren) C-Compilers. Ansonsten solltest Du Dir mal das Datasheet und das Manual herunterladen: Products->Microcontrollers with analog capability->28-40/44 pin 2k-16k word (3.6k-32k bytes)->PIC18F452->PIC18Fxx2 datasheet sowie Engineers Toolbox->Reference Manuals->PIC18C MCU Family Reference Manual Gruss, Thorsten.

Hi Christoffer, Bullshit! :( You are the second user who killed his PIC on this way; it wasn't a good idea to add this junction near by the power supply input :-/ I will add a note to the core page that the J2 pinheader should not be mounted if it isn't used. Best Regards, Thorsten. P.S.: great that the SID still is ok!

Great, so everything has been solved! If Quenzer sends me a display, the driver will be part of the upcoming MIOS (MIDIbox Operating System) :) Best Regards, Thorsten.

Hi Dan, it seems that I miss your design idea - it's nice & compact - great - and can be realized much easier than my MBLC (-> faster success! :) - just one suggestion: if the encoders don't include a button. you should add some below the display or somewhere else, because these are one of the most important buttons for the HUI menu navigation. LEDs are not required for these buttons. Maybe it's a good idea to use the minature ones... Another note: with the first release (probable in two weeks) only one 18F core will be required for 128 inputs (buttons and encoders), 128 outputs (LEDs and LED rings) and the graphical LCD & it will also be possible to connect up to 64 pots. I've planned to organize the data structures on a different way like known from the PIC16F MIDIboxes. With MBNG up to 256 different MIDI events can be defined and assigned to buttons, LEDs, pots, encoders, etc. independently. An example configuration: 128 buttons and 64 LEDs (assigned to the MIDI events of the first 64 buttons), 32 encoders, 32 LED-rings (assigned to the MIDI events of encoders) and 64 pots... For LC emulation the buttons/LEDs are more important, so here another example configuration: 9 encoders, 8 LED rings, up to 110 buttons, up to 96 LEDs and up to 64 pots/faders (NOT motorfaders!). Don't ask me how I calculated this, it will be clear with the first release... ;-) Motorfaders will require an additional core like before. I would prefer conductive knobs, even if these faders don't come with a touch track. Best Regards, Thorsten.

Hi Emanuel, my tip: http://www.piclist.com Especially the beginners projects: http://www.piclist.com/techref/piclist/begin.htm Best Regards, Thorsten.

Hi Steve, here are some snapshots - I'm working with this setup for PIC16F877 and PIC18F452 since some weeks and never got a programming error :) Although I own a PICstart Plus kit from Microchip, I switched to the JDM since IC-Prog works faster (especially on PIC18F's which can be programmed within 30 seconds) Best Regards, Thorsten.

The MIDIbox MF controls the motors with a pulse wide modulated voltage. Not all parameters like pulsewidth, duty cycle, acceleration are adjustable yet, I choosed these values based on my observations with the Alps faders. I will add a calibration menu for these parameters when I find the time... Touch Sensor circuit: see http://www.ucapps.de/mbhp/mbhp_din_touchsensors.pdf Alps faders are coming with an additional pin for a direct connection between the fader knob and the capacitive input circuit. Best Regards, Thorsten.

Hi Christoffer, fine fine - yes, you can use it without the risk of damage. But note that EL foils have a lifetime of just only some thousand hours. So maybe you should add a switch in order to activate the backlit when you really need it. Best Regards, Thorsten.

Hi Serum, maybe it's better when you just send me the LCD so that I can setup the driver (see http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1043023674) HD61830, SED1330F and KS0108 seems to be the most popular ones, if these three LCD types are working, we have the best options... :) Best Regards, Thorsten.

Hi Dan, yes, thats the contrast pot. In difference to small dotmatrix LCDs the graphic LCDs normaly need a negative voltage at V0. Fortunately the 64240A already includes a voltage converter, which has to be connected via the 10k pot to V0. Note also that this LCD has 4 Chip Select lines, which have to be connected like shown here: http://www.ucapps.de/mbhp/mbhp_glcd_64240a.gif Did you already send your order to Reichelt? If not here an important hint: for the 40 MHz system clock the PIC18F452 needs a 10 MHz crystal which will be quadrupled internally by a PLL - the PLL works only with factor 4 and not with factor 2 :-/ Best Regards, Thorsten.

Hi Christian, yes, it is - just select the Mackie Control ID (#14) instead of the Logic Control ID (#10) and Cubase SX will regognize the controller :) I haven't tested it by myself, but Frank did it with success. Best Regards, Thorsten.

Hi Quenzer, the data bus is a little bit different and the display requires an additional negative voltage, so that a small DC converter circuit has to be built which shifts the voltage level to -25V. However, it isn't impossible to adapt this really cheap LCD to the MBLC, but the driver will be different. If there is nobody with programming skills who would like to buy this LCD and would write the driver, just send it to me and I will do it --- normaly this can be done within a hour... Best Regards, Thorsten. P.S.: a Space Invaders PlugIn for MIDIbox NG would be a cool idea ;-)

Here some uncommented photos which should give some hints for your own construction and should give an impression about the effort. I suppose that an experienced DIYer can build a similar box in between 2 weeks, unexperienced DIYers maybe need longer, but since the box can be enhanced step by step the first success (Cubase or Logic regognizes the MC/LC device) should come within one day, and the rest is just a matter of time... http://www.midibox.org/midibox_lc_photos/ Note that my version is very compact, most has been build on vectorboards, because on this way I was able to vary the size of the modules. For the guys who are able to etch boards by themself: make it easier than me and layout also the boards for the buttons, encoders, etc. & feel free to publish your layouts! :) Another important suggestion: don't order a panel before you've prepared the boards for the encoders/buttons/LEDs, and before you are able to measure the dimensions in order to ensure that everything fits fine. Because nothing is worse than an expensive panel with too big or small slots and holes! (I had luck ;-)) Thats all for today... :) Best Regards, Thorsten.

Hi Dave, ok, since the IBK10 can send SysEx controllers, I will integrate this feature into the SysEx handler, since this allows to cascade sequencers and to address the appr. pot with the device number. The data structure of MB64SEQ is different from MB64, it cannot be edited by Serge's Editor. But fortunately Serge gave me the tools which allow me to modify the editor by myself so that I think that a MB64SEQ editor could be provided soon. Best Regards, Thorsten.

Hi, :) Christoffer: the push buttons are from Reichelt, order number "DT_6" (the big ones) and "TASTER 3305B" (the small ones) Steve: yes, I'm nearly out of space, therefore I'm searching for a new flat since some weeks, because currently the whole stuff is in my livingroom and I have to put it away when I get visitors so that they don't stumble over the gear ;-) Mostly they are confused, they've no idea for what these boxes could be useful to and change the topic quickly before I start to talk about the newest features ;-) Best Regards, Thorsten.

Unfortunately not --- because the LC emulation is limited by the host software, and if it doesn't support more encoders or joysticks, there is no chance to add them to the HUI. The only mod you can make is to replace the motorfaders by encoders (thats the cheaper variant) However, on the other hand I'm very satisfied with the new possibilites and don't think that more encoders are really required. Here an example: This is the common view. Panorama is controlled by the encoders, volume by the motorfaders. Now I push the "Assignment: Track button" and get a assign menu I push the V-Pot #8 button to enter the setup values which are now under control of the encoders. Another example: I push the "Assignment: Instruments" button and get an oversight over my VSTi's I push V-Pot button #6 and can control the VSTi parameters with the encoders... The handling is very fast - just two clicks to select a bank of parameters :) And with the "Bank +/-" button I'm able to scroll through the track-groups (8 entries per group) Note: the screen output is send by the host application and therefore is not under my control. I only interpret the incoming data streams and print them out... Best Regards, Thorsten.

These are 32 additional buttons for LC functions, MIDI remote commands and/or SFB events (Display mode switching, etc.) Here an update of the current status --- every part fits fine, but the modules have not been connected yet... next update on sunday :) Best Regards, Thorsten.

Unfortunately this is not supported by the MC/LC protocol. Every device requires a seperate MIDI In/Out :-( Best Regards, Thorsten.

Nein, Du benoetigst einen 10 MHz Quarz. Um sicherzusterzustellen, dass Du diesen seltsamen Wert nicht fuer einen Schreibfehler haelst, schreibe ich ihn gerne nochmal aus: zehn Megahertz... ;-) Der Grund: der interne Oszillator kann nur bis 25 MHz schwingen, im PIC18F ist jedoch auch eine PLL integriert, die die Frequenz vervierfacht. Leider ist dieser Faktor fest eingestellt, deshalb muss der Quarz ausgetauscht werden. Ansonsten sind alle Bauteile identisch mit der PIC16F Version. Gruss, Thorsten.

Hi Steve, did you select the correct processor type (PIC16F874 or PIC16F877)? Because this setting cannot be determined from the .hex file. If this wasn't the reason, could you please send me a snapshot from your IC-prog window? Best Regards, Thorsten.