philetaylor

No problem, I use Windows 7 x64 and the standard toolchain works fine! Cheers Phil

Hi. Do you know what type of SD card it is? I committed some changes to the SD driver last month to support MMC and SDHC cards which may not be in the pre-compiled mass storage.hex. 4GB cards are often SDHC ones so this may be the problem? Cheers Phil

It isn't a 'big' problem if the last two digits aren't 0. Basically, when you upload MIOS (using MIOSStudio) you can select a "Device ID" which is the last 2 digits of the PIC ID. The PIC will only respond to requests that contain the correct ID. So you will have to keep trying until you find it! Once you know the correct ID, you can change it using the change_id application which is described here Cheers Phil

That will teach me for replying on something that I know very little about :) I didn't know that, I thought that MB64 supported CV outputs? (from setup_midibox64.asm) ; enable access to the AOUT module via Port J10 #define DEFAULT_ENABLE_AOUT 0 #define DEFAULT_NUMBER_AOUTS 8 #define DEFAULT_ENABLE_AMUX 0 Anyway the OP can safely ignore everything I said about AOUT and listen to seppoman, he knows much more than me about it! :) Cheers Phil

Hi. Yes you will want to leave the PIC ID's at "0000 0000 0000 0000" unless you are a: Connecting CORE's together, b: using an LCD other than standard clcd, c: using an MBHP_LTC module instead of standard MIDI ports or d: using an MBHP_IIC module as the primary MIDI port. For CV outputs, you need MBHP_AOUT_XX modules. There are three types, the standard AOUT, the LC and NG. They all have different properties, and you are best to choose which you need by reading the info on http://www.ucapps.de/ Each one contains 8 AOUT/CV outputs (apart from the LC which has 2) so for 16 CV's, things get a bit more complicated as they can't be daisy-chained (like the DIN/DOUT modules). I believe that you would need 1 x AOUT and 1 x SHX8 (sample and hold module) which would give you up to 64 CV outs with Midibox64 but there is no kit available for SHX8 modules so you would need to get the PCB made yourself..... For power, as the CORE has a 5v Regulator, any 7.5-9V 1A PSU would be suitable, there is a circuit for a bipolar psu in the MBHC_AOUT page if you need +/- 12V CV's. Cheers Phil

I forgot to mention, I only made 1 mistake (one of the bi-colour LED's reversed!) it really is a testament to your design skills wilba! Thanks to you and fussylizard for the bulk order, and of course to TK for creating the whole thing :) One point, rather than use wires to connect the datawheel encoder, I managed to bend the pins through 180 degrees and connect them through the back of the PCB. You need to be very careful but it worked for me! Cheers Phil

Well the postman really cheered me up this morning my delivery from fussylizard has arrived. So much for cleaning and tidying the house, today has been MB Seq building day! The result is: I couldn't think of a more appropriate synth to put in the rack with my MB Seq than my trusty old D-110, I had forgotten how good that bass is (it was used on Toms Diner) I haven't put it in the case yet but that monitor speaker is a useful stand for the CORE32 !!! Cheers Phil

Hi, There isn't really such a "thing" as a midibox... MIDIbox is a collection of DIY (do it yourself) hardware devices, there are sequencers, synths (SID and FM), control surfaces, mixers etc etc. The key is that generally people are expected to buy the individual kits for the different MIDIbox modules and build them. If you have no experience building electronic devices, there are lots of people here who will be happy to help. Cheers Phil

Yes that will do it! luckilly feeding 5v (from USB) into a 7805 will probably give you about 3.5-3.7v out so it shouldn't kill the STM32 but a stable 3.3v is really needed! Good to hear that all is well. Cheers Phil

Hi. 7805's do tend to get very hot at 12v especially without a heatsink, I wouldn't be surprised if you get a thermal cutout... There is a switch mode voltage regulator available from http://www.dimensionengineering.com/DE-SW050.htm which is pin compatible with the 7805 "but" it is pretty expensive, $15. The spec says it will work up to 30V !!! Cheers Phil

Yes I very nearly did that! Be very careful when removing the connector. I would take each pin out seperately as you don't want to break any tracks.... Phil

I had exactly the same issue with this one and it took me quite a while (and plenty of wasted IDC plugs) before I figured it out! Phil

Hi. That sounds to me like the display has power but has not been initialized yet. The KS0066 should be compatible with the HD44780 which the MIOS32 clcd driver was designed for so it should work fine. When you compile the 020-lcd tutorial, what do you have MIOS32_LCD set to? This MUST be "clcd" for the driver to work. If it is not that then I would check your wiring for a fourth time! I assume you have the LCD connected to J15A NOT J15B. All of the names on the datasheet that you attached match the J15 names so you should be difficult to make a mistake but it is worth checking again! As you have already discovered, powering a CORE32 from USB while an LCD backlight which draws ~200mA is also connected is not a good idea, I would use external power! FYI The CORE32->CLCD wiring diagram is here Thanks Phil

I won't say that it was particularly easy to get it to compile but 99.9% of the thanks should go to TK for actually writing the plugin. All I did was fix a few platform specific issues and hit "Build" (well nearly ) Phil

You can also use MIOS32_MIDI_SendDebugMessage() to send messages to the MIOSStudio Terminal window if you haven't got an LCD. Cheers Phil

Strange... It should work. I assume you are using a DOUTx4 module and have the LED connected between the output and ground as per this diagram I am at work at the moment so I can't try it myself! Cheers Phil

AFAIK, almost all of MIOS8 is currently working in MIOS32 (and quite a lot more!) DIN/DOUT are certainly working (or the MB_SEQ_V4 wouldn't be usable!) Cheers Phil

I would add one caveat to what Julian said, the MIDIbox MF module controls the motor but it also relies on the CORE receiving the analogue 'position' from the track of the fader otherwise it won't know where the fader is (and won't know when to stop the motor!) so you would need dual track faders, one that connects to your exisiting fader connections and one that connects to AIN ports on your CORE or AINx4. Cheers Phil

A quick Google search reveals this: http://forums.m-audio.com/showthread.php?14110-SL-10-6-2-FW410-Problem-with-Outgoing-Sysex-messages It does look like there is a problem sending Sysex in the 1.9.2 and 1.9.3 drivers with Snow Leopard! Cheers Phil

The most common cause of a corrupt MIOS is a partially uploaded app. If the app started uploading it is possible that your computers MIDI port couldn't keep up with the sysex transfers and that is why you started getting checksum errors. What type of midi interface are you using? It isn't one on the "MIDIbox blacklist" is it?? http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist lists the interfaces that don't work properly with MIDIbox, usually because they can't handle sysex very well! Cheers Phil

I forgot to mention, also try going through this process to debug your CORE/MIDI connection: http://www.ucapps.de/howto_debug_midi.html Cheers Phil

Hi. The "block character screen" just means that the LCD has power but has not been initialized. The fact that you are getting an upload request every 2 seconds means that the MIOS bootloader is running but you may have erased/corrupted MIOS, as it isn't booting. This isn't a problem but you will need to (re)upload MIOS to the CORE before you can upload the SID app again. I don't think that you have fried anything but it is worth checking all connections! Cheers Phil

Hi. The MIDIbox_SEQ_V4 uses a similar feature for an animated logo display on startup. Character LCD's have 8 user definable characters which is why you will notice that no more than 8 different special characters are displayed on screen at the same time. In fact all of the standard MIDIbox fonts already have the 'bargraph' characters defined so a simple "spectrum analyzer" display (like in the second half of the video) can be quite easily achieved. With a bit of creativity you can do some quite impressive effects but for full 'pixel' level control you really need a graphical LCD! Cheers Phil

Hi Welcome to the community! Technically MIOS32 supports 128 digital inputs. It can handle 16 shift registers on the DIN chain, each one supports 8 digital inputs (each DIN module contains 4 SR's). It could support more but this hasn't been tested (AFAIK) and according to TK's comments in mios32_srio.h may require additional buffering due to the length of the SRIO chain. Having said that, in the rgb_led_controller mios32_config.h file I noticed this comment: // number of scanned SR registers on SRIO chain // default value 16 (see mios32_srio.h) // Knöpfli uses max. 256 DINs, that is 32. #define MIOS32_SRIO_NUM_SR 32 So I guess up to 32 SR's (256 DIN channels) could be supported! The standard AINx4 (analogue module) supports up to 32 pots so only one would be required. Yes the CORE32 from Smash comes pre-soldered and pre-loaded with the MIOS32 bootloader so MIOSStudio can be used to upload your application. Cheers Phil

The HD44780 is about as standard as you can get. It is fully supported by MIOS8 and MIOS32 (in fact it is the default driver - clcd) Have you looked at ucapps.de? This page will help: http://www.ucapps.de/mbhp_lcd.html You should be able to find wiring information in the above link as well. Cheers Phil