Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Message

Re: [emax] EMU Parts Jammie or Ted?

2013-12-03 by jammie

no filters are ssm actually designed by emu ssm was there chip company

cutis was made by doug curtis now onchip since he died and they still make a few of the cuurtis chips

the dual vca is still produced and a resonant vc 4pole filter is still made for dave smith

the octal sample and holds are still made but with better slew rate like the analog devices sm08 and sm16

most of the other parts are logic devices and you can buy new equivelents that perform the same but use less current

most chips are still available as nos chips

the echip is the only chip that is hard to get

the emax 2 does not have analog filters but uses a special dsp asic chip for the filters known as the g chip then in later models like the EIIIX the h chip was used and they used 2 of them to create the zplane filters first saw in the morpheous then the e4 range of samplers  and the later emu modules

you know if an eprom has gone bad by reading it on a reader burner as it will let you know if there are any bad sectors

most of the time its a bad cap or resistor dragging pins down to ground or leaving a open circuit in the case of bad resistor

same if a signal diode goes 
  ----- Original Message ----- 
  From: windrumscoggin@... 
  To: emax@yahoogroups.com 
  Sent: Tuesday, December 03, 2013 4:28 PM
  Subject: [emax] EMU Parts Jammie or Ted?


    

  Is it my imagination or are internal EMU parts getting extremely hard to come by?
  Mine went on the bllink over something simple yesterday and I was shopping
  local techs who mostly said they couldn't or wouldn't do the work.
  Luckily for me, Ted was kind enough to take a look at mine when it stopped reading from the SCSI bus..
  As far as parts, where would we go if we needed replacements? Old junk units like the one being sold  from a member who just listed in on eBay UK?
  I will take a wild swing and assume the analog filters used on EMU are Curtis and not some other proprietary....also....
  the EEPROMS...how do you know if they have gone bad? and if you are skilled enough to determine one indeed went, and you need the EEPROMS replaced you will have to find someone with the ability to 'blow ' a new one using the original code off the bad one if it isn't already fried and lost its 1's and 0's. That being said someone needs to figure out a way to find replacement blank EEPROMS then blow the code on them so we have backups for the future....It would certainly help.....
  As far as the mobo, its find an old one, right? Aside from the obviouls 'burn through' you will get with some, not all trace burns are obvious... and if you do find the bad trace you better be a  damned good soldering man who can work PCB's -this is where the  original schematics would come in handy...which I am sure are readily available...needless to say, all time consuming and by the time you ared done, makes you an bona fide EMU repair guy....get good at this and you would have a nice side business stocking up old emu EEPROMS/parts/filters/mobos etc.....the thing is, with the EEPROMS you just gotta get the burner for it and learn how to burn em right?
  As far as  the FDD..they are extremely hard to find /rare in the tooth...and good luck finding a replacement FDD if it goes bad. especially the bigger EMU units...you actually need to find someone that can (or is willing to) repair and recalibrate the 5-1/4 inch FDD on most of the EMU units. If I am not mistaken there is a  special proprietary boot sector read/write schema that EMU used for their FDD's, correct?. Any new unit must be calibrated to the same if it is not an NOS FDD, correct?
  Feel free to chime in
  Cheers and happy music making with your Emulator II!

  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2014.0.4259 / Virus Database: 3629/6887 - Release Date: 12/03/13

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.