• Content count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About Highcooley

  • Rank
    MIDIbox Newbie
  • Birthday 03/25/1982

Profile Information

  • Gender Male
  • Location Switzerland

Recent Profile Visitors

1,072 profile views
  1. Project: MiniMoog Voyager Style Midi Synth

    It is finally done, my Midibox NG powered analog synth hardware is finished. Usually, it runs pretty smooth with some occasional hiccups. Unfortunately, the power supply is off by almost half a volt on the +15V rail, so I have to re-tune everything. So, there is still some work to do. The next step will be to finish the software by figuring out a lot of stuff like an individual menu structure, free detuning of my second and third oscillator as well as preset save and recall and sending presets from and to the midibox by sysex.  Thank you all very much for your support! I would never have come this far without the help of many passionate synth builders and midiboxers. I'd love to also post some samples. But since our first baby is due in the next couple of days, I can't promise much for the next days, weeks or even months. But stay tuned. I promise, some sound will eventually get posted. Until then, enjoy your hobby and see you soon :-)    
  2. Fried LPC17 output

    Just a quick followup: It was indeed a fried pin. After replacing the LPCxPresso board (Rev D) and going through the horror of figuring out how to get the bootloader onto that darn thing (as well as bending all of the header pins on the right side of the board in order to finally ram the displaced row into the headers of the midibox board), my LCD went back to operate perfectly. In case you need to set up a Rev D LPC17 as well one day, better find this post instead of figuring out the steps by yourself:  
  3. LPC1769 rev D board how to load bootloader

    after a couple of hours going exactly through these steps myself, tripping over exactly the same stumbling blocks and figuring out exactly the same solutions, I find your post ...face palming myself. But at least I can confirm, that it indeed works after a lot of pin bending and ramming the board onto the headers. I also soldered a short wire for the two Ethernet LEDs onto the left side of LED3 and 4. The network connector ones lit up, but only dimly. I guess, I should have done that either onto the right side of the SMD LED's or onto the left side of the corresponding resistors on the LPCxPresso board. But here is how I did it:   By the way, that's how the headers had to be bent in order to be able to give them a firm push to fit them onto the headers:   ...and I can confirm that the Rev D board actually works with all the midibox bells an whistles (I'm using it with DIO, AIO, SCS, standard 2xmidi IO, USB, Ethernet and a single GLCD).
  4. Fried LPC17 output

    Thank you for the compliment as well as your sympathies for the SEQ. Rest assured, the SEQ is all fine and dandy. It is my second project (a full fledged analog synth, based on Midibox NG) I am talking about, which also got a nice looking case. Pictures will follow, as soon as I get the display running. In my case, the two J5s as well as the J4s would be unused, as I'm running a SCS at J10.  Also thank you for pointing me into the right direction with the pin mapping file. It is not very appealing to build own explicit hex files of course. Especially, since I am more the hardware guy than the software specialist. But as a last resort, I am definitely looking into that.    Concerning the new LPC board, Embedded Artists state, that: If I compare the schematics, the pinout is also exactly the same. There is only an additional RBG LED onboard, which will flash wildly in different colors, since it is driven by three DOs used for other purposes in the midibox standard. So I tossed my money in and ordered a new LPC. We will see, if it works properly and if all goes well, I'll have a spare LPC for a display less midibox application :-)   Cheers, Andy
  5. Fried LPC17 output

    Hey everybody As it seems, I fried the R/W output pin of my LPC17 (p1.27 of the LPC1769 xpresso). When I moved my Synth from the cardboard housing over to the new wood case, I accidentally plugged the 5V supply into J27 next to J2, the actual supply pins. The 800mA slow blow fuse blew instantly, so I assumed, that I had shorted 5V to GND of J27 but everything except for the fuse  was alright. Of course, the move from one housing to the other lead to a lot of cables being too short and a bit of debugging due to shorts with the front panel and so on and so forth. The last thing to do, was to solder a longer cable to the KS0108 compatible GLCD, which at least for me is always a hassle to get the specific pinout as well as pullups, pulldowns and trimmerpots correct. After the first power on, the LCD started up normally with the init text, but then things got bad very quickly. After a couple of seconds, it continuously started looking more like a snow storm with random pixels being on or off, firstly changing, whenever the LCD was updated, but becoming static after a while. Meanwhile, with each power cycle, I either get a blank LCD or the mentioned snow storm. Of course, I doubted my skills first, checked the wiring several times, also changing RST high and low, but nothing helped. For a short time, I also believed that the 45cm long cable was too long, but the internet taught me otherwise. So I was left with two possible root causes, either the LCD has to be broken or the LPC. With the built in testlcdpin function, I was able to find R/W always being high (not mattering if an LCD is connected or not). This leads to my conclusion, that I probably fried the output of the LPC, since the pin is directly connected to the micro controller on the lpcxpresso board. Is there a possibility to assign another pin as the LCD R/W pin in a config file, so I can cut and rerout it to P1.27 on the lpcxpresso board and still be compatible with future updates? If this is not an option, does anybody know if the newly released LPC1769 board is fully compatible with the old version: http://www.mouser.ch/ProductDetail/Embedded-Artists/EAX00242/?qs=sGAEpiMZZMtWuggIubTlfyQKvxcc1sy3C%2fHLDQO4Us4%3d ?   Thanks for your help! I am a bit in a hurry to fix this quickly, since I have to give up my electronics lab as soon as possible to make room for our firstborn :-) :-( :-) Cheers, Andy
  6. IMG-2876.JPG

    I used the following TC011 switches with the 4 button boards I designed a while back, attached in the button's description: The small boards are mounted on four M3 standoffs each with 15mm spacers. In total, it's 16 of these small boards, an additional matrix board for the shift registers and eight ribbon cable strands with 20pin connectors. My initial thought was, that these small boards would be very versatile (which they are) and ultra-cheap in production as a 20 pack of small PCBs is a fraction of the price of one single large PCB. However, this also meant, that I needed 64 standoffs on the back side of the front panel to mount the PCBs as well as many IDC connectors and it also was a lot of work to mount everything. In the end, the additional price for the front panel was about the same as a larger PCB would have been.   I also went for single colour buttons, whereas dual colour would have been nicer.
  7. IMG-2876.JPG

    Thanks guys! 
  8. IMG-2880.JPG

  9. IMG-2878.JPG

  10. IMG-2877.JPG

  11. IMG-2876.JPG

  12. IMG-2875.JPG

  13. IMG-2873.JPG

  14. IMG-2866.JPG

  15. Saving/Dumping and Loading Snapshots

    Hi Thorsten Ah, I got it. I have to first "save" each snapshot number (like set it up the first time) at least once, in order to "dump" values in it. As it seems, I haven't fully understood the difference between saving and dumping a snapshot. Can you please explain this? What I intend to do is simply store all current set values into a snapshot whenever I hit the button. Can I simply use save every time? How about the multiple banks of presets? Is my assumption correct, that I have to save them in different .NGS which would mean that I need to have copies of all configuration files with the same name as the corresponding .ngs for each .ngs?   Thanks for your reply and best regards, Andy