TK.

Ok, it works. :smile: At least on the breadboard: Schematics: MCP4922 version w/ external VREF: http://www.ucapps.de/mbhp/mbhp_aout_mcp4922.pdf MCP4822 version w/ internal VREF: http://www.ucapps.de/mbhp/mbhp_aout_mcp4822.pdf This big disadvantage of the chip: it has no serial output, therefore modules can't be chained, but need dedicated chip select lines instead. J19 provides only 2 CS lines, if more are required, additional IO pins have to be used - but not so many are available... Therefore it won't be a good choice for projects like MIDIbox CV (or CV2) But it will be a good choice for people who only need 2 (or maximum 4) channels. Best Regards, Thorsten.

If there is nobody else with a spare board, I will send you one of my boards which is already stuffed (I've 5 LRE8x2) +1 for these buttons, I like them more than the buttons that we are using for Wilba's MBSEQ Frontpanel. /Edit: unfortunately the cap height doesn't fit with the LCDs! Important: they need 9.5mm in diameter (I checked this with the .fpd files of my MBSEQ V2 and MBFM frontpanel) Otherwise it will be too difficult to fit them into the holes if they are not 100% accurately soldered (which is the normal case...) Best Regards, Thorsten.

Mit ein wenig .NGR Scripterei ist das kein Problem! :smile: Zunaechst die Buttons. Da es sehr viele sind, legst Du sie am besten in Baenke ab. Fuer jeden Kanal muesstest Du dann ein eigenes EVENT_BUTTON definieren (und die dann in die entsprechende Bank legen), so dass also 16x90 EVENT_BUTTON definitionen notwendig sein werden. Das ist mit ein wenig Copy&Paste jedoch auch schnell gemacht. Mit meta=DecBank und meta=IncBank kannst Du die Bank (und somit den Kanal) aendern. Mit fwd_id kannst Du die Tasterbewegung auch weiterleiten, bspw. an einen EVENT_SENDER, der dann die MIDI-Note sendet. Weil die Baenke bereits fuer die 90 Buttons verwendet wurden, musst Du die zweite "Bank-Gruppe" ueber .NGR Kommandos nachbilden. Das geht dann relativ einfach mit dem SET_ACTIVE kommando - hiermit kannst Du EVENTs aktivieren/deaktivieren, so wie es der Bank-Mechanismus normalerweise automatisch macht. Da Du fuer jeden Kanal ein eigenes EVENT_MF pro Fader definieren wirst, hast Du somit die verschiedenen Werte gespeichert. ist per default der Fall (value=0) Falls Dir das nun alles zu spanisch vorkommt, empfehle ich, dass Du Dich erstmal in das MIDIbox NG Manual einliesst: http://www.ucapps.de/midibox_ng_manual.html Gruss, Thorsten.

No problem, I planned to display the first scope at the first GLCD anyhow, and if only one GLCD is configured, the SCS will appear at the two lower lines. Best Regards, Thorsten.

Ok, try this one: http://www.ucapps.de/mios32/midibox_ng_v1_028_pre2.zip I hope that the performance of other features isn't affected so much, but I guess that you won't notice this in your application anyhow. Best Regards, Thorsten.

Meanwhile I got a MCP4922, and also found a suitable voltage reference for 0.30 EUR at Reichelt. Let me do some experiments with this chip first, it will be compatible to MCP4822 so that users have the choice. Best Regards, Thorsten.

I would prefer a single MBHP_CORE_LPC17 (or an upcoming MBHP_CORE_STM32F4) as well. It will save costs, and it will be much easier to program and debug. Due to the higher speed, you don't need the slave cores. Best Regards, Thorsten.

Hi Marxon, this was related to a (stupid) programming error. Could you please check if this version works better? -> http://www.ucapps.de/mios32/midibox_ng_v1_028_pre1.zip Best Regards, Thorsten.

I like Sneakthief's layout as it is. And I like Monokinetic's idea to split the upper elements into 3 parts (which will require 3 PCBs), so that builders can decide by themself, where to position them, and if they need them at all. E.g. if somebody doesn't want to spend the money for the OLEDs, he could replace this element by another GP button array (e.g. 5x3) at the left side. Or by a 4x2 pot array The SCS (CLCD + 6 buttons + rotary encoders) ensures compatibility to most other MIOS32 based MIDIbox projects, which becomes interesting once you want to try out a new application before planning a special case. For the MBSEQ project I defined the pin assignments for a 25pin sub-d: http://www.ucapps.de/midibox_seq/mbseq_v4_interconnections_lpc17.pdf The advantage: it can also break-out the SRIO chain, e.g. for the 64 additional gates (which btw. could also be made available for MBCV2, e.g. if somebody would like to trigger drum sounds). But the breakout cable has to be very short! I noticed instable CV values (or no function at all) with a cable which was longer than 50 cm. Longer distances could be achieved with differential line drivers, e.g. according to the RS-422 standard. Here an app note which describes this well: http://www.ti.com/lit/an/slyt441/slyt441.pdf Trying this out is still on my TODO list. Here are some suitable chips which are available at Reichelt: 4-line differential driver http://www.reichelt.de/ICs-M-MN/MC-3487-DIL/3/index.html?&ACTION=3&LA=446&ARTICLE=11346&GROUPID=5474&artnr=MC+3487+DIL&SEARCH=differential+driver 4-line differential receiver http://www.reichelt.de/ICs-M-MN/MC-3486-DIL/3/index.html?&ACTION=3&LA=446&ARTICLE=11345&GROUPID=5474&artnr=MC+3486+DIL&SEARCH=differential+receiver If I've success with this approach, I will change the 25-pin sub-d pinning accordingly (there are enough free & redundant pins available) Best Regards, Thorsten.

The centered CLCD looks even better! :) But I'm right-handed, and therefore would like to see the main encoder at the right side of the CLCD. In order to get the CLCD still centered, you could move the OLEDs to the left upper corner (the appr. buttons won't be used so often), and the 3x3 button array to the right upper corner (I guess that these buttons will be used very often). Best Regards, Thorsten. P.S.: we could design an alternative PCB for left-handed people! ;-)

Cool! Only complain: please replace "MIDIBOX" by "MIDIbox" I guess that such a generic CS could also be interesting for MIDIbox NG users. Therefore it makes sense to layout a frontpanel PCB for the upper part above the encoders (once enough people are satisfied with the available control elements of course). Best Regards, Thorsten.

The .svg files are now available at the Wiki page: http://www.midibox.org/dokuwiki/doku.php?id=tpd_pcb First I ordered black panels, but I made an error: I forgot to mirror the backpanel, so that the clean side is at the bottom (and not in the case): This is fixed this in the published .svg Another "imperfection" of the black version are the missing transparent windows for LED matrix and digits. I've no experience how to design them properly, therefore I created a complete transparent version, which is part of the .zip file as well And which I'm finally using by myself: As you can see, it's very important to wait for the frontpanel before soldering the 4 LEDs, so that they are fitting into the case. I haven't done this, and unfortunately also shortened the legs - I have to solder new LEDs to fix this. Anyhow, here the good news: I've a free christmas giveaway! :smile: If somebody is interested on the flawed black panels, then just send me a PM! Best Regards, Thorsten.

Thanks for the good starting point! :thumbsup: Actually a mixed CLCD/GLCD configuration is currently not supported by MIOS32, but now where I see how nice they fit together, I will enhance the LCD driver accordingly. This will require a MBHP_CORE_STM32F4 module, so that enough IO pins are available for both LCD types. However, due to the CLCD the 5th OLED display is redundant, please remove it. There are only 4 scope screens. I agree with Ilmenator, that common dimensions should be considered. Due to the LED rings it's probably better to use an acryl frontpanel (either transparent or matt) anyhow, otherwise it will be very difficult to mount the LRE8x2 (and all the drilling holes will be pretty costly) I don't have switches in my encoders, but I could provide this as an option to cycle between the assignments (banks). Buttons under each OLED are a good idea. We could use it the following way: press the button under the OLED, then a special menu page at the CLCD will appear which allows you to change the waveform assignment, oversampling, trigger point, etc.. with the main encoder. It makes sense to add more buttons. E.g. the two spare buttons could be used to increment/decrement the current CV channel. But I'm sure that people would also like to have dedicated buttons for - a "fast" button (for the encoders) - encoder bank +/- (for the case that they don't have inbuilt switches) - patch +/- buttons - Start/Stop sequencer (and arpeggiator) - store button to save the current patch - change directly to certain menu pages So, at least 8 additional buttons (user-configurable) Best Regards, Thorsten.

:thumbsup:

yes! Actually one of my LRE8x2 is already reserved for a MBCV2 in the case that we go for a "soft-assignment" :smile: But we should also consider a nice (and inexpensive) case from the beginning, so that CS layout and case dimensions perfectly fit together. The pots above the display is exactly, what I don't like on the Ambika CS design, because the display will be covered by your hand when you are tweaking the knobs - you don't see the adjusted value. You are right. And it especially has to be considered, that an iPad is wireless and not stationary, which means that you can remote-control MBCV2 while staying close to your synth (and not close to your MBCV...) The disadvantage is that we miss the "tactile feel". In the video you can see, that I sometimes have to move the virtual knobs very carefully to change the sound precisely, and to ensure that I don't touch the wrong knob. This requires a certain (counter productive) concentration on the UI that I don't like. So: an iPad is perfect for intuitive configuration, and to get a very good oversight about the available parameters. But during a live situation I would prefer real knobs which are assigned to the parameters I would like to tweak. I come to the momentary conclusion that following CS options are preferred: 1) at least the SCS for (cumbersome) access to all parameters: http://www.ucapps.de/midibox_ng_manual_scs.html (this is already implemented) 2) in addition, "soft-functions" which are assignable to encoders with LED rings and to analog pots & faders (I like all three options together! ;-) 3) optional 128x64 graphical LCDs, especially for the scope displays. Note that it's normally not possible to use CLCD and GLCDs in parallel, not at least because of the different HW interfaces. Therefore: if GLCDs are used, one of it will replace the 2x20 LCD of the SCS I relaxed the spec, the upcoming MBHP_CORE_STM32F4 has enough free IO pins, so that 1 2x20 LCD and OLEDs can be used in parallel. Open question: special buttons and LED functions? How should they be configured? Would it be important to assign multiple LEDs to a button, e.g. if somebody wants to cycle between different modes? And another topic: are dedicated buttons for a quick CV channel selection (1 of 8) helpful? (I guess: yes) Best Regards, Thorsten.

I haven't used MIDIbox SEQ for this demo... Best Regards, Thorsten.

Hi, could you please check, if the IIC MIDI port is working again with this version? -> http://www.ucapps.de/mios32/midibox_seq_v4_080_pre2.zip This is to ensure, that you are using the same IIC driver like at my side (recently I had to change something there due to a new compiler version). It means, that the IIC interface hasn't been detected (e.g. since it isn't powered, or not connected, or whatever...) If the 080_pre2 version doesn't work better, you could check the IIC communication with this test application: http://www.ucapps.de/mios32/iic_midi_v1_000.zip see README.txt for details Best Regards, Thorsten.

It's the Alientek OLED from Taobao: http://item.taobao.com/item.htm?id=6239945991 And I purchased it via Youbuy: http://www.yoybuy.com/en/ See also http://www.ucapps.de/mbhp_lcd.html Let's keep this in mind - but independent from such an option, how would the ideal MBCV2 CS look like? It's already running on a STM32F4 :) (and SmashTV will send me a prototype for the upcoming MBHP_CORE_STM32F4 module soon) The application is ca. 25% faster on a STM32F4. Best Regards, Thorsten.

Hi, I don't remember that I ever released a 1.8 firmware. MIDIbox V1 was based on a PIC16F877 - could you please look into the case and check the PIC type? Anyhow, the documentation for this variant can be found here: http://www.ucapps.de/midibox64seq.html and the latest firmware (v1.01) here: http://www.ucapps.de/pic16f_firmwares.html If you find a PIC18F452 inside, then it's probably a MIDIbox V2 Documentation: http://www.ucapps.de/midibox_seq_v2.html and the latest firmware (v2.4f) here: http://www.ucapps.de/mios_download.html yes, the old documentations only show the latest state. This has changed with MIDIbox SEQ V3 (and upwards), where the documentation is hosted on a subversion server, so that the history is available. Most PCBs are available here: http://www.midibox-shop.com You need: - a Core LPC17 PCB - a SEQ CS PCB (also called "Wilba's Frontpanel") - an AOUT NG PCB (for 8 CV outputs) For the gates you've to build a 74HCT541 based output buffer circuit on vero board as shown here: http://www.ucapps.de/mbhp/mbhp_core_lpc17_output_buffers.pdf Best Regards, Thorsten.

Sehr schoen! :) Die Touchbuttons sollten auf id=1001..1008 verfuegbar sein (so ist es im obigen Beispiel konfiguriert). Du koenntest nun MIDI events wie folgt generieren: # on touchsensor event (first id has been specified in the MF configuration above) EVENT_BUTTON id= 1001 type=NoteOn chn= 1 key=0x68 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1002 type=NoteOn chn= 1 key=0x69 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1003 type=NoteOn chn= 1 key=0x70 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1004 type=NoteOn chn= 1 key=0x71 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1005 type=NoteOn chn= 1 key=0x72 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1006 type=NoteOn chn= 1 key=0x73 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1007 type=NoteOn chn= 1 key=0x74 range=0:127 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id= 1008 type=NoteOn chn= 1 key=0x75 range=0:127 lcd_pos=1:1:2 label="^std_btn" Gruss, Thorsten.

Thanks for the feedback! :smile: Yes, a scope was also very important for me - not only for debugging... to understand what I'm doing. And since the implementation is so easy, it was on top of my wish list. :smile: It would be extremely helpful if you guys could help me to define the "standard" control surface for MBCV. Should it look like the frontpanel of an analog synth (like a Minimoog)? Or is a more generic surface with some displays and a battery of (software-asignable) encoders, potentiometers, buttons and LEDs more suitable? The biggest problem: MBCV2 is suitable for many use cases, therefore it will be very hard to find a good compromise for a single standard CS. It's probably better to prepare it for two different directions? Best Regards, Thorsten.

Ok, I will be very interested on the results! Meanwhile another version which should be even more stable: -> http://www.ucapps.de/tmp/mios32_test_app_lcd_ssd1306_LPC1769__20131215.zip I tested the changes at my side with the MBCV V2 application, see this video :) Best Regards, Thorsten.

Today in the MIDIbox labs :smile:

As long as you don't enable the sequencer, the MB808 firmware works this way. Best Regards, Thorsten.

Yes, CV is limited to 8 outputs. CV in is not supported, but a clock input might be available sooner or later. See also this topic: Best Regards, Thorsten.