deletemeplease

I had the same problem recently, only I had MIOS v1.5. Email Thorsten as he has to provide specific firmware.

Yes that makes perfect sense. Thank you. OK I'll give it a shot. I've read the readme, and don't really understand the implementation, but I think I should be able to search for that just fine. My switches have just arrived so I think it's testing time! Great stuff. I'll work on the switches first as the LCD is probably helpful for that. Thanks again :)

I can't believe I didn't think of using decimal. I always try and overcomplicate things lol. I like the layout of this define and switch. It's very clean and straight forward. I think this is the way to go. I'm a little unclear about sending parameters to a function. Would the following work? void sendProgramChange(unsigned char sendProgramChange) { MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(sendProgramChange); // Program Number 12 MIOS_MIDI_EndStream(); } Or do I need to ensure that my unsigned char is different from the function name? I presume it's correct to do this as a void, as I don't particularly need any code output? Oh really? Thats very interesting indeed. I'd rather get away from using din/dout boards to save space. Is this difficult to code? Any functions I should be looking into? Knowing what I'm looking for might make it easier to search the forum. Thats a good point. The manufacturer of the box I'm trying to control states that the first scene is in fact patch 0, so I think I'm ok. Shouldn't be difficult to test. So you would actually recommend using the value as hex in my case?

Hi. I'm trying to plan out my controller in my head and figure out the code as I go along. Below are my two questions, skip to the end of the post if you need more info about my project. Question 1) I need to send a program change message, value 12. Which of the following is correct? MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(0x12); // Program Number 12 MIOS_MIDI_EndStream(); OR MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(0x0C); // Program Number 12 MIOS_MIDI_EndStream(); I'm pretty sure its the second, but I thought I'd check. Question 2) I have 6 buttons, I want 4 of them to send program changes, and the other two are more complex so lets tackle the first four first. How do I set these up in the ain64_din128_dout128_v2c example? Can I create an array like the following. Please forgive my syntax, I only know a little objective-c, so I realise the syntax is probably massively wrong: static unsigned char switches[4] = { 0x00, 0x06, 0x0C, 0x12 }; And use MIOS_DIN_PinGet to say - "Pin 2 was pressed, select location 2 from the array". Then is it possible to store this hex result as a variable which i can use in a MIDI stream request? More information about my project It's a simple MIDI box. 1x core, with PIC18F452, 1x DINx1, 1x DOUTx1. 6x buttons, 6x LEDs. The first 4 buttons send different program change messages, the last two buttons send CC#. On first press they send value 127, on second press they are toggled to value 00. I'm quickly realising I'm in way over my head, but everyone has to start somewhere right?

You don't have to use Xcode, it's just a nice way to edit projects using C. I personally tweak projects ib TextWrangler and then use the make command in terminal.

In case anyone is struggling to compile their apps, here's what I do. Edit your project files in Xcode (or TextWrangler if you prefer something lighter), save your files, then open Terminal.app. Now type 'cd ' (without the quotes, but including the space. Now drag your project folder from Finder onto the terminal window. Now hit your return key. This will tell terminal that we want to use this folder as our root folder. Finally type 'make' and hit enter. A couple of moments later you have a .hex file which can be uploaded with MIOS studio.

OK I've had some time to think, and plan out another layout. This one has fewer cuts, and I could make this even smaller. I like the look of that prototyping board you suggest Nebula. I need to make this as small as possible, as I'm making a MIDI bank switch for my guitar effects box, and I want to cram it into as small a space as possible. Even the small Core board is looking massive!

Yes, true, but I don't really have time to etch myself. Plus I have a cupboard full of photo chemicals, and I don't think my girlfriend would be happy with ferric chloride in there too! I couldn't seem to find prices for fabrication in the UK. Is it worth doing? I would prefer a PCB really.

Yes good point. The main reason i positioned the IC as I did was to enable the +5v line to run under the IC uninterrupted.

I've designed a veroboard layout of DOUTx1. I've never made my own veroboard layotu before so is anyone able to double check it and make sure I haven't made any obvious mistakes? I'm using this schematic.

Just a quick update, I emailed Thorsten, and he's sent me a .hex that will update both the bootloader and MIOS in one go. No programmer necessary. This is definitely the route to take if you are impatient like me, and do not read the README file properly. :frantics: ALL FIXED NOW!

Cheers nILS.. It'll will be solved if I can find my JDM in my box room. Not looking forward to searching for that. Yes I haven't been around here for about 7 years :) I'm sure everyone will become well acquainted with me again as I ask further stupid questions, and solve them after 30 minutes. It shows that I haven't been here for a while as even the bootloader has been updated! There was a point when I thought that would be impossible! In fact my poor little PIC18F452 is looking decidedly ancient. Really impressed with the new MIOS32 interface, looks very tasty indeed. Take it easy buddy.

OK apparently I should have read all the way to the bottom of the Readme file. I think I still have the old v1.1 bootloader. Where can I find the v1.2 bootloader? I still have an old JDM programmer somewhere in the house! Never mind. I found it *facepalm*

I built a midi box years ago (6-7 years ago to be precise). I've now come to repurpose the PCBs, and thought I'd update to the latest MIOS. I had previously been running MIOS v1.5, and went to update to v.1.9g today, but encountered a problem. The upload gets to about 92%, then stops. Upload aborted due to error #5: Write access failed (invalid address range). Any suggestions? PIC18F452 Core V2 All wiring appears ok.

Well i sat down, determined to make my box work last night, and so i connected pot 14 to ground, and that stopped the random ain data (WOO!). Then i put mios 1.5 on it, and it wouldnt boot up :o, so i tried again from another computer and it worked ::), then i uploaded a tweaked mb64 (with 24 pots and 16 buttons) and it works great! The only problem now is that my buttons are behaving strangely. One of the buttons connected to J5 is jittery as can be seen from the MIDI data below 0003768F 1 -- 96 30 7F 7 C 3 Note On 000376BD 1 -- 96 30 00 7 C 3 Note Off 000376DF 1 -- 96 30 7F 7 C 3 Note On 00037700 1 -- 96 30 00 7 C 3 Note Off 00037745 1 -- 96 30 7F 7 C 3 Note On 0003776F 1 -- 96 30 00 7 C 3 Note Off 00037791 1 -- 96 30 7F 7 C 3 Note On 000377B2 1 -- 96 30 00 7 C 3 Note Off This repeats for quite some time, unless i press the button then it stops. The button is connected to D6 of J5. Is the source of this problem a faulty button? When i press or release the button it fails to send a note on or off event.. hmm.. ;D

Personally i'd use pots instead of encoders.. less hassle :). You only need encoders if the device your controlling supports them e.g. pro tools, cubase etc. Instead of sending a direct number like pots - 0-127, they send + or -, so the amount changes on the device being controlled. I guess your microkorg doesnt respond to encoders so theres not much point using them! I dont know if that made any sense :-/, but they are alot more expensive too.. If you're just starting out, i recommend making a box with 16 pots, 8 buttons, a 2x16 LCD (for debugging). You'll only need a core, an AIN, and a DIN. I did this first and once i got it to work i added another row of pots and more buttons! Have fun mate!

erm.. good question ::) I got all my pots wired up so the left and right tags are connected to J7, and all i did was snip the middle wire of pot 14.. so the middle connector (that goes to A5 pin of J2 of the AIN). So i guess its not grounded is it :o stupid me.. I'm really looking forward to going back to uni and investigating this problem! I want to get my box working so i can make some filthy sounds in reason/reaktor :) (i just got a new soundcard y'see).. anyway.. i digress! HAPPY NEW YEAR Y'ALL!

Hi guys! Hope you all had a good christmas, and i hope you'll have a good new years! Right.. i moved my working midi box from the EcoBox into a shiny new metal box. I soldered on an extra 8 pots, and 8 encoders. Now i get random data sending from AIN number 14, which i subsequently disconnected, but the data still kept coming in. Now i remember i had this problem before, due to not connecting up J6 on my AIN.. I'm quite sure that i didnt alter this when moving the boards to another box - but i havent got the box in front of me to check. Is there anything else that could be causing this - noting that the device still sends random data on AIN 14 when nothing is connected? Hope you havent missed me and my silly newbie questions ::)

OH DUDE! i totally forgot about that sorry! You just kinda disapoeared off the face of the planet!

Hey nILS! I hear ya.. havent done anything to my box in a while (last thing i did was put it in a new box at the end of summer). And i get random ain data on pot 14.. havent got time to sort it :-/ Hope everything else is going well buddy.. Pulse

I ordered boards from him, and they were great. They came pretty fast, and where of a good quality. But yeah, watch out for oxidation - As you leave the boards they start to look dirty and become harder to solder onto. So order them once you are sure you've got all your parts and are ready for a monster soldering session! Have fun!

uclaros - thanks! I couldnt think of how to explain it properly. It would be nice to have buttons that do that.. it'd make using reason even more enjoyable. Just a little off topic, but i've noticed i'm losing more an more time playing with reason. Take last night for example, i just opened it to have a jam for 15 mins at about 9pm. Then i looked at the clock and it was 3am!!! I can just get lost in there!

Hey durak, firstly i like your design! Heres a couple of answers to your questions. Contrast pot - i think it is important, i used a trim pot for mine. its like a normal pot but instead of being large like normal pots its very small, you can only change values using a screwdriver, this meant i could mount the trimpot directly on my Core module. About using your box with reason - this is why i built a midi box, but you have to carefully look at the midi implementation chart .pdf manual that should be installed in the same directory as Reason. Basically, the buttons like the example you used (looks like the mod env routing to me ;)) dont actually perform like buttons. Instead you have to send a CC (continuous controller) value e.g. cc#7 value 127 for the top setting. I dont think i explained that very well, but if you automate some changes then open up the sequencer lane to view the automation, it should become aparent what value corresponds to which setting. As for the mute / solo, i'm not sure whats wrong there. I know the mute/solo functions of the mixer need to be triggered by midi keys e.g. C1, again this information can be found in the implementation chart. If you want the buttons to be triggered so that first press = on, second press = off, you'll need to set that in mios. I'm afraid i can't help you with that, but i'm sure someone else could ;) Sorry for the long post, i hope it makes sense! ::)