Jump to content

analogue900

Members
  • Posts

    6
  • Joined

  • Last visited

    Never

About analogue900

  • Birthday 01/01/1

Profile Information

  • Gender
    Not Telling

analogue900's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. You're so helpful, it's heart-warming. ;) turns out it was 2 wires mixed up. Actually, now that you mention it... I seem to remember looking at that page... ;D Yep, done that. It was a flaky socket. Should have soldered that optocoupler directly to the board. I hate it when Paul Schreiber is right (he's the guy making MOTM...)... he's got a very strong opinion on certain topics - IC sockets is one of them. Anyway, I got it to work. Got mbseq v3 uploaded and the 2 displays show the content as shown on TKs website. (http://www.ucapps.de/midibox_seq_manual.html) - there it is... I knew, I'd seen that website before. ;D Time to test some encoders and pushbuttons. Thanks for all the help (and the fun)! Best, Dino
  2. Thanks! Were you using the midi ports on the core module ? I think I read somewhere in the docu that the system automatically detects which ports are hooked up. I also see the black boxes on the top row of the right display. In the meantime, I've hooked up the left display and it shows some text during startup - although some characters are missing. It says something like MIOS 1.9 and then READY (with the R missing).... not sure if this is due to a loose connection in the display wires or what not... Anyway, the thing still isn't responding to any midi signals. Also, Styrd, thanks for pointing me to the wiki! I hadn't seen this. But I'm using a PIC bought from smashtv a couple weeks ago, so according to TK's notes I should be eusart-bug-free. If anybody has some troubleshooting tips, that would be much appreciated! Best, Dino
  3. Hi all, I'm in the middle of building my mbseq v3 and I was wondering if it's possible to drive the core using the built-in midi ports during development? If I'm reading this correctly the eusart bug shouldn't be a problem anymore on the newest pics, right? Reason I'd like to drive it like this is I'm waiting for some parts for the midi-iic module. So far, I've hooked it up and I do see the sysex request from the core (that's the upload request for MIOS, right?). But when I try to upload a hex file I don't get any response from the core.... Best, Dino
  4. Yeah, thought about that. But I wanna avoid this due to the wiring nightmare. The more I think about this front panel thing, the more I realize that a couple of screws won't really bother me - I'm much more worried about this thing being (mechanically) stable without having to individually wire every encoder, button and LED. Dino
  5. LOL! After having lurked for weeks I was betting I'd get answer like this. ;D That's quite OK though. I am browsing some of the other topics to get more ideas. Thanks for letting me know. I'm sourcing parts right now. I found some nice push buttons w/LEDs at Mouser - they look a bit like the old buttons used by Roland (JP-8) and I love those. They're just insanely expensive (>$3/pc). The problem is the buttons should have the same depth as the encoders when both are mounted on the same PCB... Thanks again for the ideas and hints! Dino
  6. Hi all, I'm starting to build a midibox seq3 to control some of my boxes (9090, a home-built 808 clone (without seq), based on MIOS and some synths). Before diving into construction and design of the box and the frontpanel I wanted to ask (I guess TK, specifically) if there's some good pictures around how people mount the PCB boards (for the buttons and pots) and the LCDs behind the frontpanel. I've been looking at the pics linked at the bottom of the mbseq3 page... TK, how robust is this setup? I noticed quite a few screws on the front panel; does this do the trick/ After having built some diy modules already, the mounting of buttons and LCDs is starting to give me real headaches. Thanks in advance Dino
×
×
  • Create New...