noofny

Here's a couple - doesn't give away much but it's something for now...

Thanks! Yeah I've had a couple of peeps from here read the blog, which is one of those nice things that keeps you motivated to make it a good doco. Getting people to read a blog is not easy, but it makes a difference when you see it helps someone! I should be getting the top face plate in the next week so will post pics then too.

Yeah sure - until i finish I'm tracking the whole project with pics on http://noofny.blogspot.com Once done I'll put up on the wiki.

I hear ya - cheers for the replies. :-)

Ah, so I must have made an assumption that this was built into the MB64 app - it would make sense then that I'm getting ahead of myself here right?

Anyone got any ideas? I can't seem to get midilink to work...this are the steps I've taken of it helps; 1) Used the change_id tool as per instructions to set the device id to 0 on first core and 1 on the second. 2) Uploaded the MB64 application to each core (no modifications made to it). 3) Using vmidibox64 tool set the first core (device 0) as forwarding point. 4) Using vmidibox64 tool set the second core (device 1) as an end point. 5) Removed the optocoupler from the second core (but leave in on the first). 6) Connected MIDI in to the first core (device 0). 7) Connected MIDI out to the second core (device 1). 8) Connected J11-MO on the first core (device 0) to J11-MI on the second core (device 1) and the 2 grounds on J11. 9) Connected the LCD to the second core (device 1). 10) Connected some buttons to the first core (device 0) and pots to both cores. But she no seems to worky. MIDI signals generated by the first core are all making it through to my PC as per normal, so I guess in effect this is just like chaining the 2 cores using the MIDI in/outs - because the LCD is only displaying events generated by the second core that it is connected to. Also menu buttons are performing their roles, however the LCD again is not displaying anything for them. Everything else with both cores and all the setup is working 100%...and I've searched all over the forums but nobody seems to get this same problem. Do I need to modify the source of MB64 application? I've setup my dev toolchain and can compile the MB64 source but I've searched through the code and can't find what I would need to change here. Is this the way midilink between 2 cores is meant to work?

Do I need to recompile MIOS with the DeviceID set to 02 and upload that to Core2 ?

I have 2 cores each running MB64. Core1 has DeviceId=00 and is set to the forwarding-point, Core2 has DeviceId=02 and is set to the end-point. It all seems to be working fine except that the LCD which is plugged into Core2 (endpoint) is only displaying activity from that core and not both. Have looked around the forums but can't seem to work this one out - have I left something out?

I took some of my midibox for a spin tonight - hooked up 64 pots to one of the cores, configured it and opened up Ableton Live and went for a spin. Oh yeah! Might I say a huge THANKS to TK and all those involved in making this thing alive and keeping it available - looks like the dream of being able to make a decent controller is closer than I thought and more fun than I thought once you get stuff working! ROCK...ON. 8)

YES!! It was my soldering - it looks like one of the bypass caps was pressed down on the 5v rail - would explain the weird behavior.

Ok I fixed (2) by removing and re-soldering the ground wire to that pot. No more twittering for that and it registers the full range of values. There's something REAL funny going on with this first pot though. I just replaced it with a new pot and when i turned it up it lit up inside and has now burnt out. I am getting the standard 5v across pin 1 & 3 (5+ & gnd) and there doesn't appear to be any voltage coming up the middle wire from the AIN. It's the only pin that is doing this!! Has anyone else ever seen this?

Got the 2 AIN's connected up to the core and was pleasantly surprised that 99% of it worked! I have a couple of small issues though; 1) The first pot does not register at all. After diagnosing it is actually the first pin of the first AIN that is not registering. 2) Only when I turn up all knobs to 50% or higher, only 1 or 2 knobs twitter slightly and those ones only reach about 80% of their max value. I've checked my soldering and looked more at the circuit diagrams to try and understand but am a little lost where to go from here? Would love it if anyone can help out.

Posted some progress - channel strips and some overall pics. Been a busy weekend! 8)

I added an RSS feed to the blog so you can subscribe to it now, also added some download links for layout files. Got a fair bit done today but holding off posting until tomorrow when more is done. We had the most amazing electrical storm in the middle of me doing a bunch of soldering today - a couple of lightning hits came down very close so I stopped, unplugged the computers, modem, TV, etc, then continued soldering. Gotta have priorities.

Thanks Goblinz, yeah it's added a little more action to the project that's for sure! Cimo - Cheers also - yeah I wouldn't dream of doing anything until I get TK's & the community's approval...will be doing a bit more on the frame this weekend so hopefully get more posted in the next couple of days.

Cool. Don't worry - when I finish it I intend to copy the tutorial to the WIKI, just didn't want to have to post to 2 sites whilst I'm putting it together. It'll be a good backup too if the blog goes down. 8)

Hey thanks a lot :-)

Hi, I've started to publish the tutorial of a MB project I'm working on and was wondering if it's ok to publish the link here. Apart from enjoying the project, my intention was to give something back to the community, so I'm taking plenty of photos and documenting in as much detail as I can with my spare time. Anyway the link is here; http://noofny.blogspot.com I couldn't find where the best place was to publish the link - hope the tutorial may help or inspire someone. -Mike (noofny)

Indeed keep em coming - I'm learning so much in such a short time from this forum (and the project). Thanks again LyleHaze for taking the time and write such an awesome response. All the switches, pots and LED's arrive today so it's going to be a good busy weekend! 8) -Mike

Thanks! Yes it seems to be that way - lot of people arguing for and against. Thats exactly what I thought. I don't know if anyone can comment on what is classed as 'noisy' or 'acceptable' - would 75mV or ripple/noise on 5v rail and 150mV ripple/noise on 12v rail be considered good/bad, or is this a stupid noob question? Cheers

Hi all! I've been reading everyones helpful input in regard to using SMPS to power their MB's; http://www.midibox.org/forum/index.php/topic,2081.0.html http://www.midibox.org/forum/index.php/topic,10921.0.html Basically I want one that provides 12v for goosneck lamps and 5v for MB. There's 2 that sell here in Australia via Electus/JayCar which look OK but I know NOTHING about this subject, so was wondering if anyone could comment on these specs to help a decision (or talk me out of it altogether!). My MB is 2 MB64e's linked so no motofaders or anything too fancy, seems 1-2 Amps will be enough for the 5v rail to power the MB's so there should be plenty with these? Soanar - 60W - $65 AUD (34 EUR) Output 5v, Tolerance +-10%, Ripple/Noise 75mV, Current 0.3-6A Output 12v, Tolerance +-10%, Ripple/Noise 150mV, Current 0.2-4A MeanWell - 60W - $80 AUD (42 EUR) Output 5v, Tolerance +-2%, Ripple/Noise 75mV, Current 4A Output 12v, Tolerance +-2%, Ripple/Noise 150mV, Current 3A Am getting a lot of help from this forum and loving my first MB project so far! :) -Mike