Search the Community

after 6 months of blood. sweat and tears, 20m of ribbon cable, a ton of parts soldered, screwed and glued - it’s (almost) done! this midibox build-up is intended to use it for what ever i like. it can be a midi controller for music applications, sequenzer, modular controller, video mixer, lightning desk etc… the sky is the limit! still this is a first test controlling some moogs and plug-ins with open lab's stagelight. thanks to the midibox community for the competent help and documentation. SPECS: CPU - Midibox NG on STM32F4, 4 x DIN, 4 x DOUT, AINSER64, AOUT_NG, MIDI IO - Intel NUC 3.5 GHz Dual Core i7, 32 GB RAM SCREEN - 21.5“ capacitive HDMI touchscreen 1920 x 1080 px - 16 x OLED displays 128 x 64 px HARDWARE - 17 x endless encoder with push - 16 x blue LED buttons - 16 x RGB LED buttons - 6 x bank buttons - 4 x function buttons - resistive XY joystick with push - 2 x 60mm faders EXTENSIONS - 8 x CV out - 2 x DIN MIDI I/O - 32 x analog IN (for pots, faders, sensors) - 32 x digital I/O (for encoders, switches, leds) - HDMI port for 2nd monitor, beamer (4K) - 2 x USB3 in ports (NUC) - 1 USB out port (switch for internal/external cpu) - modular voltage out +/- 12v, 5v all the best roberto ps. how to embed YouTube videos? i dort get it... P.P.S: moderator fixed this

You're welcome. The connection to the stm32f4 is

hei searching for a supllier (EU/Austria) for a SD-Slot - like on STM32F4 Core, or even better would be a micro-SD - slot - because i have a size & price topic! i also need a Footprint/lib for it - Eagle or Kicad - or any other Format which can be easy converted to KICAD (thats what i use) --- so anything that is in the standart library of these programs - and is available in EU i found @reichelt https://www.reichelt.de/Connectoren-fuer-Speicherkarten/3M-SDRSMT2MQ/3/index.html?ACTION=3&LA=446&ARTICLE=224937&GROUPID=7432&artnr=3M+SDRSMT2MQ&SEARCH=sd%2Bsockel&trstct=pos_10 and its looks pretty much like the STM32F4 cores socket... (happy that they have a slot now!) Then the interconnection to the core for me is not clear, @latigid on i think you can help - since you have expierience whith your wcore, http://wiki.midibox.org/doku.php?id=wcore_res-sd i have this pin-out: dont know if it is right up to now, and one -i- not connected yet - the CS maybe --- maybe total wrong what i have done... the datasheet from reichelts socket is: qest: are the pinout-Numbers of a Slot Normed? (like on a XLR-Plug, or a Midi-Connector?)

this video 2 my midibox stm32f4 disc

thanks for the time and attention I am a less experienced midibox user, in indonesia, i have built a system midio128 control midi keyboard / organ controller modification organ and button panel button with stm32f4 will and i have followed all the instructions from de ucaps also but when i input hex bootloader filehttp://www.ucapps.de/index.html?page=mios32_bootstrap_newbies.html, also hex midio v3 .19 on lcd 2x 20 has not appeared as in the picture like this, but i have set it like the one in for midi player via sd card module please help it especially regarding mios 32 hex file for midio 128 v3 http://www.ucapps.de/mios32_download.html bundle package like the one in hex seq 4 file for sequncer as i have explained and i sent the picture through this midibox forum this video update :

Thanks for creating a separate topic! Two questions: * Do you see any debug outputs in the MIOS Studio console, when starting up MBNG? * After MBNG has started (even with the display looking bad), can you enter any commands in the MIOS Studio console? E.g. typing "help" should show you a summary of available commands. These two questions should allow us to determine, if MBNG is running properly or is having problems at startup. If the app is not running, please double-check that you are using the correct STM32F4 hex from the midibox_ng.zip package that you downloaded from ucapps. You can also try to put default.ngc and default.ngl in the root directory of the sd-card. These files are provided in the cfg/default directory of the midibox_ng.zip. When the default.ngc is loaded, it should log that in the MIOS Studio console. Good luck! Peter

Does anyone have any info for the MB909 sequencer for the 9090 TR-909 clone. I need to know how it was connected to the STM32F4 core board as I only have a wiring diagram for the LPC17 core. Thanks

how to geti want like this set stm32f4 disc for mbng core with scs

* Did you load the STM32F4 specific version of MB_NG? Other firmwares for other (older) cores might not work. * What are the startup messages in the MIOS Studio console? There should be some DEBUG output when starting MB_NG. * Do you have an SD card with any configuration files inserted?

i have built the stibl stc32f4disc midibox correctly and after upload mios studio hex program also seq v4 already appear on my lcd 2x20 with brand not hd447780 (hitachi) but i try to insert mb ng through mios not show in my lcd i please give in suggestion , whether the lcd does not match the driver in mb ng or there is a system that must be in input as shown in my picture

Hi, I think I found a bug. I am on V4+.095 with the STM32F4 core. The "Duplicate FX" only works if the receiving channel is different to the one the track is set to. This would make sense if it is set to the same port, but not if set to a different port. So my track is outputting on Out 3, channel 2, I want to duplicate to Out 1, channel 2. Doesn't work, only if i set the duplicate destination to 1, 3, 4 etc. I actually want to use the Duplicate FX to send CC feedback to a NG controller with 2 LRE8x2, so obviously the controller receives on the same channel as it sends. Is there a smarter way to achieve this? Like this you still need to configure anew for each pattern (or make a Preset for each one). Edit: If you set "Additional Channels" to more than 1, the channel with the same number is included, too, but obviously the next one too.

This Settings in "mios32_config.h" are working for 0-7A (5a,5b) - i am on a stm32f4 #define MIOS32_AIN_CHANNEL_MASK 0x00ff // AIN define the deadband (min. difference to report a change to the application hook) #define MIOS32_AIN_DEADBAND 31 //7Bit

I, sorry my stm32f4 not disply after flash mb ng firmware

Maybe it is related to the cable bring a USB A type cable and you need the B cable: http://midibox.org/forums/topic/19105-stm32f4-communication-issues-with-mios-studio-no-usb-midi-available/#comment-166624

Hi all, I received my STM32F4 board in anticipation of building my SeqV4. I flashed the bootloader with ST-LINK on Win7 x64, and then used MIOS Studio to upload the SeqV4 application. From there, MIOS Studio doesn't want to talk to my STM32F4 anymore -- it sees 4 Midi ins and 4 Midi outs from the Seq, but no combination of those four ports will let me talk to it -- it says 'no response from device' or something similar. The bootloader fail-safe mode works (holding the USER button down on reset keeps it in the bootloader). But I can't communicate to it while it's actually running the Seq app. I think this is because of the known Win7x64 USB MIDI driver issues. But I find " The GM5 driver is currently not supported for the MBHP_CORE_STM32F4 module, but it's planned to provide it in future!" on the MIOS32 download page... so this driver won't help in this situation? I'd like to keep the four USB Midi In/Outs because I'll be using this thing with Linux mostly, but I can't get MIOS_Studio working on my Arch Linux install at the moment. The pre-compiled version didn't work, and compiling it from source caused me some GTK errors that I haven't sussed out. I'd also like to be able to update the Seq App in the future without having to disassemble my device to get to the button... Any help? I'll probably continue debugging the MIOS_Studio app on Linux to avoid Windows as much as possible, but I thought I'd ask here if there were any suggestions.

I was looking for something else and I found this: https://github.com/openAVproductions/openAV-stm32f4/tree/master/03_float

So, digging around a bit, if I wanted to build the Mongbox version of the SeqV4 (that is, no modifications), I'd need: - 1x STM32F4 Core board - 2x MIDI IO boards - 1x Wilba CS board Plus all the gubbins to fill those boards out. And the STM board to plug into the core. And 2x screens. Sound about right? Just making sure I'm not missing anything here. (Also, sorry for derailing my own thread...)

#Update 1: working now, did forgot to solder the R33 resistor network on the bottom PCB under the STM32F4 eval board... silly me This tends to happen quite a lot to me when i have half finished projects lying around everywhere. So LCDs do work sweetly, but do not know exactly if the wilbas frontpanel is correctly working, seems quite random some of the led pattern, but i will have to look into that when i finish ubilding. Hello, as i did finish my MidiBoxSid a while ago, I did follow the advice of some other member here and looked into the MidiSeq v4. So i simply ordered all the stuff, or had it at home anyway. Now i am running in some issues, which are probably easily solved by some of you guys who already have one: So My MIOS32 bootloader did flash on my STM board easily without trouble, I can also detect and upload the MidiSeq newest firmware, and it is read by the MIOS studio software, it says 1 minor issue was detected while flashing, but also states that it could be solved whatever that means, so I think everything might be ok with the Code. I can also open the MIOS file viewer and see that something is stored on the sd-cardm so I assume everything is working properly, right? Now I did attach the Wilbas Frontpcb and the 2 LCDs, some from newhaven ordered via mouser, they run on 5V and the rest should also be connected fine :) at leats i do hope so right now, I did go thru the cabling quite a lot since it is kind of tricky since it is mirrored and stuff. When I connect the USB cables for power then the backlight is lit on both, but i only get dark rectangles on the upper collumn, I thought maybe the midibox logo or version number should appear and so on, so something is not working right yet. So here the big question? Do i have to configurate something else? The LCDs should work without any Front-PCB attached, right? since they are not connected whatsoever. Why do my LCDs not show the right things, maybe wrong LCDs, but I assume mouser is only providing the "right" ones. maybe some file missing on the sd-card, but it should simply work without the sd-card, right? I mean for testing something should be printed on the LCDs? MIOS Studio is stating that the right seque code is detected, so there should not be a problem with that, maybe i simply flash the bootloader again later and go on form there, check all the ICs. And last question, the J8/9 cable, goes 1:1 to the mirrored plug form the frontpanel, or does it have to be mirrored just liek the LCD type??? This is specially confusing to me since it is not clear if SI is supposed to go on SI, or like ususally in communications, SI is going to SO! Kind of tricky to document too,but luckily nothing be damages if this connection is wrong it simply wont work. Thanks for reading and probably helping. cheers.

The SEQ V4+ (antilog) hardware is validated and we have some PCBs available, although the mechanism of the shop etc. is not quite ready. The last piece of the puzzle is the case, which is still in progress from Adrian. If you want something ready-to-go, with all through-hole compenents etc., then go for the Wilba version (contra: there's no ready-made case available and CNC-routed panels are quite expensive). SEQ V4+ features should be compatible with all STM32F4 versions; this includes both the Wilba and antilog variants. if you don't mind waiting a bit and want a "high-quality" solution/enhanced hardware suited to the current SEQ workflow, then the SEQ v4+ is the right way to go. it does involve SMT soldering, although it is not super difficult being 1206/SOIC. The Wilba version is certainly more straightforward in terms of the main control surface. the case from Adrian will make a "complete unit," hence we wait to see what Adrian brings :)

Ok, I tried the attached firmware on STM32F4 as well as LPC1769 (also the matrix). They both work! Thanks! :-)

Mkii will not work with the lpc17 unless the software is updated. The coding for the matrix setup is missing from the published app for the lpc17 as it is for the version 1 sequencer lite. Setting the config file with matrix settings returns errors. You can see the errors from mios studio. The app on the wiki mkii is only for the stm32f4. I built one a while back and was looking to use it with my lpc core as well but have not had the time to stumble through updating the code. If you get it working please post the update I would be happy to test it out as I have not built a case yet and the LPC would allow for a smaller case over the STM Core. Would also be interested in a case if you come up with something I have started on an acrylic top but have not been able to get back to it in a while. I wanted clear acrylic so you could see the print on the board as labels. My thought was it would be a cheap affordable case that way. Happy to share what I started on the case but honestly it is not far along I just had the holes on the top laid out. I was still trying to figure out placement as the board holes do not quite line up with the holes on either core for how I was trying to mount it. That is where I got stuck and the full sequencer became available again and I just have not gotten back to the light version to finish it.

Hi, I'm trying to get my MBSEQv4L mkII working. The MkII page says (at the start) that it is for use with both LPC17 and STM32F4 boards. Has it been certified that it works also on an LPC17? I'm asking because while the MkII board works ok with my STM32F4 (firmware 088), it doesn't work ok with the LPC17 (firmware 086) I have. The firmware 088 available on the MkII page (end of page) is only for STM32F4, while the MIOS32 download page offers firmware only for LPC17, and its version is 086. At first I tried to use the MkII board with a STM32F4. Everything was working except for midi in. Midi out was ok, as well as MIDI in via USB. The MkII page says that if there's problems with midi in, make a change in a session file. I did, but it didn't help. What is the midi in problem that requires changing the default session settings? Anyway, because I couldn't get the midi in working, I tried the MkII board with an LPC17 (firmware 086, the latest one available). However, now the MkII board worked only partly. The cursor LEDs (the red ones) were not lit at any point even though the seq was running, nor could I switch gates on. But it seemed like I could select bar, sequence etc., only that I couldn't switch gates on. Whether that was a problem with just the LEDs (so that a gate gets switched on/off, the LED just doesn't incidate it), or with the buttons as well, I couldn't tell because midi in/out were not working.

thx for the testpin hint ... lcds still not working ... cant test them, have to made new cable, but dont have any connectors anymore... this will have to wait.... but got 16xOLEDs working on the stm32f4 (also with the knowledge with the testpin)

I do not see it documented anywhere for the stm32f4. I believe you are going to have to define it. have you tried this in mios studio console: testlcdpin e3 1 -> sets E3 to ca. 3.3V set this first so you get voltage testlcdpin e3 0 -> sets E3 to ca. 0V Set this to toggle the pin voltage off to verify your pin This should be working on the E1 and E2 pins for sanity check on J15. You should be able to look around with your meter for what pin is being enabled and disabled if it is configured already. I believe it is not and you will need to configure it in the code and compile for the additional functionality you are after. If you look in the SVN at: /trunk/mios32/stm32f4xx/mios32_board.c http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2FSTM32F4xx%2Fmios32_board.c I think you will find what you need to update there. It looks as E 3 and E 4 is not set there. You just need to determine your pin assignments and set them. Someone a little more familiar may be able to say if you need to set something anywhere else as well. I believe you will have to also add in E 5 and E 6 since you want 6 displays but that is just adding the additional lines of code for the enable lines. Not sure if you will need to make those changes anywhere else in the code as well. There is still the question of if you need to shift the voltage from 3.3 to 5 volts as well. once you have the pins you want working you will know better if you need to do that once you have enable lines working. A 74hct08 or 74hct245 may be better than a 595 since you are only looking at a 4 additional displays you should not have to multiplex the enable lines via a 595. There are plenty of available pins you can use for enable lines already. You could use a small transistor as well for the voltage conversion but the ic is likely to do a better job and take up less space. Transistor my be viable while you are testing things to get that first display working. I am a beginner on the programming so can not help you much more there.