Altitude

Members
  • Content count

    1,162
  • Joined

  • Last visited

Community Reputation

52 Excellent

3 Followers

About Altitude

  • Rank
    MIDIbox Guru
  • Birthday 02/22/1975

Profile Information

  • Gender Male
  • Location Detroit, MI
  1. New eurorack modules from midiphy - preview

    @latigid on   I didnt get that far.  The TI parts good and proven (all the MI stuff, OC, Performer etc) so I wanted to use those parts.  They would need a driver for sure but again, given all the STM based hardware out there using them, I figured they would be a good choice since those could be used as a guide
  2. New eurorack modules from midiphy - preview

    I'd just use my aout euro panel, that has all the shift registers, jacks, and line driver already on there, the old aout just plugged into that
  3. New eurorack modules from midiphy - preview

    OC is VERY similar to yarns but those are all 4 channel devices..  The way I went about it it was just like this thing:  https://github.com/westlicht/performer-hardware/blob/master/sequencer.pdf 8 channel 16 bit DAC (DAC8568) and same output stage as Yarns using the internal reference of the DAC (Not the power rails like AOUT, yarns uses an external reference also).  I started working on the board but other things got in the way and its on hold.  It was a small modular type device that was supposed to be plugged into the back of my 10hp breakout  
  4. New eurorack modules from midiphy - preview

    My euro design really fell apart since the orginal AOUT design used the power rails as references for the trim and offset pots and while that worked fine on the bench supply, when you put that in a big rack the noise on the +/-12 power rails made the device unusable.  Hopefully you dealt with that accordingly. I did revise mine based on Yarns (actually, the same circuit is used in the Performer which is just an 8 Channel DAC with the same opamp staging) but never finished it.
  5. New eurorack modules from midiphy - preview

    are the schematics posted?  Curious how you went about it..  I never got to revising my design
  6. MIOS32 LCD Connectivity 01

    Ugh.  Memories.   Try this next time: https://oshpark.com/shared_projects/cGkUNv1n
  7. dipCoreF4 and dipBoardF4, a compact Core.

    My new euro module: https://michigansynthworks.com/p/sy0-5-analog-drum-module-coming-fall-2018
  8. dipCoreF4 and dipBoardF4, a compact Core.

    and thats why we run prototypes :)     
  9. dipCoreF4 and dipBoardF4, a compact Core.

    Im with Andy, I always make the isolation as BIG as practical.  If you have to pack it in, you have to pack it in but only do so where absolutely needed.  You can pour different polygons with different isolation on the same net too if you need it tight one place and not another.  Every time i've gotten bad boards from OSHpark (3 times this has happened) it was because there was a super tight/dense space and the etching didnt get all the copper.  They are probably way more sensitive to this than other fabs since they do big ass boards with many designs and i bet its easy to have issues etching something that size.   I think it boils down to getting a handle of what the fab says they can do and what they can actually do reliably.  I had problems with Seeed with my first order there and never went back, the etching was rough, the soldermask was poorly registered, just blah everywhere.  JLC i'll use for big stuff since their pricing is good but small stuff they have issues with clean screens even at their minimum text size spec.  PCBway has nice machines but they take a maximum X size of 110ish mm so big stuff gets pricey there too,  They cant do small text like OSHpark can on that machine.  So it's a mixed bag always where ever you go.  I go through a thousand boards a year and have yet to see a etching fault on any of the Chinese fabs which is why I dont use OSHpark anymore, it was a convenient service 5 years ago but the prototype biz in china has exploded and you can do much better for much less time and money.  Standard turn around for protos is 2 days at any place out there
  10. dipCoreF4 and dipBoardF4, a compact Core.

    works for me :)
  11. dipCoreF4 and dipBoardF4, a compact Core.

    Oh, in for sure.  I have clamshells for F405s to flash the bootloaders too
  12. MIDIbox SEQ V4 Release + Feedback

    Oh this is great.  This was something I wanted to add along with the new aout im working on based on TI DAC8568 (8 channel part, same as used in O_C, Yarns, others)
  13. Hey altitude how did you make you connector for your oled display in in your mb6582? 

  14. awesome to see this done!
  15. I've built a bit of experience with this and that euro module in the last year or so and been working on my own Aout in parallel and found it's pretty unsuitable in it's present state.  Namely: The bipolar circuit is referenced to the power rails and in a full euro cab, that is a VERY bad idea, massive noise ingress is the result making it useavle.  Removing that part of the circuit brings it back to very decent levels but 0-10V isnt terribly useful in euro.  Also, scaling the DAC outputs with a trimmer is a bit crude, per volt adjustments would be MUCH better (like in Ornament_crime or Yarns). My idea is to keep the MAX525s since they are available and decent parts and serial addressed but switch the analog output stage to that of Yarns or O_C (-3 to 7V or -3 to 6V outputs respectively) and port over the code for the calibration of those devices (whichever is easier).  The hardware side is covered but I really need someone who can code to deal with that end of it.  O_C is teensy 3.2 base but Yarns is STMF405 which should be very close to the current core code base.. I'll provide hardware to work with for any takers