Skip to main content

ARP Omni repair

Hi there. Long time.

Last summer, I bought a non working ARP Omni.

Powered up: no sound but a small glitch. Here is what I've done to fix it.

  1. Deep cleaning. Vacuumed first, then I pull all the board off and bath them. Yes, in water with soap and an old tooth brush to gently scrub. Rinced and thorough dried them with common a hair-dryer.
  2. Cleaned the Pratt-Reed keyboard.
  3. Cleaned the casing. Sanded the wood ends and sprayed some Pledge. Looks nice now.
  4. Check the PSU; every thing was OK in this department.
  5. At that time, I had no scope. My first guess was a dead output op-amp. Replaced, but still dead.
  6. Suspected the 4007 on upper board; replaced it. Still no sound.
  7. Got a small digital oscilloscope (116 $ incl shipping and taxes).
  8. Upper Voicing Board. Check the output of main osc: OK, outputs of MK50240: Ok. Checked the 4069s and found 2-3 dead gates. Replaced the dead 4069.
  9. Ground was shorted to -15V on Upper Voicing Board. Once forced to 0V, could produced some notes. The ground default was due to bad tantalums. I replaced them. Upper Voicing Board now OK.
  10. The dividing logic on Lower Voicing Board was bad. Once again, due to faulty tantalums (nearly half of them). I replaced them all. I could save some cash by replacing the 10uF tantalums by equivalent modern electrolytics.
  11. That was pretty much it. Still have a faulty capacitor on the String Control Board (attack always short), but not a big deal. I will replace it later.

ARP Omni a quiet a good synth, rather pleasant to play.

Update (Sept 2018)

I've found another issue with the Omni:

  • keys G#4 to D#5 (notes G#5 to D#6) become silent when 4' (only) is selected
  • keys E6 to C7 become silent when 8' (only) is selected
  • keys E5 to D#6 sounds "richer" than others
I suspected Z31 and Z53 on Upper Voicing Board, but before purchasing new ones, I did the following test: disconnecting P17 and testing all TDA0470 one by one by connecting the output to P17 pin 1. Surprisingly, all chips were fine. I then tested all the inputs of P17 (same process), and they all were good as well. What's going on? After days of head scratching, I finally noticed...P17 was simply connected in the wrong way!

Anyway, this gave me the opportunity to fix the remaining issues: scratchy pots and non-working Attack of strings.

Cleaning the pots is time consuming. I first tried with Deoxit D5 + MCL. This was not a good idea, the pots remained scratchy (less though) and gummy. So my next option was to remove and clean them one by one. Many tutorials explain the procedure:

The issue with the Attack on String Control Board is simply an attempt to fix it by a previous owner. A resistor (R31, 100 Ohms) has burned in place, partially roasting the nearby tantalum. The tant was left in place, and the resistor was replaced, but with a too hot iron that unglued the tracks; a nice job indeed!

Next job is to replace the tantalums, replace R31, cut the loose tracks and fix them with wires.

Update (Oct 2018)

Other issues:

  • key F#2 inaudible after power on: a dry join found and fixed
  • Strange behavior of ADSR and String Attack: the gate signal was missing.

    I realized my Omni has a mix of voicing boards: Lower Voicing Board is v1, but Upper Voicing Board is v2. On v2, there is a filter on the gate signal, resulting to a too weak signal sent to ADSR and AD. More to come...

Update (Oct 2020)

All issues fixed!

  • Strange behavior of ADSR and String Attack: actually, one of the 2 BREL capacitors (flat green) on the String Control Board had a broken leg. Replacing fixed the issues.
  • I took the opportunity to replace all the sliders with the Precision LED Slider Kit from Synthchaser. Really a must-have!

Comments

Popular posts from this blog

Drive replacement for Fostex DMT8-vl

The IDE hard drive on my Fostex DMT8-vl multitrack recorder shows signs of its imminent death; when getting hot, I could not record anymore. Must be said this drive comes from an old Sun Station, and has been replaced because I/O failures were detected by Solaris. It worked at least 5 years in my recorder: not so bad. However, time is now to replace it. The DMT8-vl is not able to handle drives bigger than 8.4 GB. Well, it is able to (the current drive is 15 GB), but only 8.4 GB will be usable. My tought was to use a 8 GB CompactFlash; having no moving parts means no noise, which is quite temptating for a music recording device. I purchased a CompactFlash-IDE adapter on the internet (8$) and I had to build a male-male IDE cable adapter (4$). Unfortunately, this doesn't work. The drive is correctly discovered by the operating system, which proposes to format it ("format IDE?"). After answering "yes", the formating runs pretty fast (faster than on a real drive), ...

Samba: Clients get "system error 1223" (or 123) after a server reboot

Facts: a Linux+Samba server shares anonymously a folder. After a reboot, Win clients could not attach the share drive anymore. C:\>net use \\mylinux\folder Enter the user name for 'mylinux': System error 1223 has occurred. The operation was canceled by the user. C:\>net view \\mylinux\ System error 123 has occurred. The filename, directory name, or volume label syntax is incorrect. The process are present, and tcpdump doesn't provide much information. What's going on? After hours of headscratching, the light came: the firewall was on and no rules for the Samba protocol! Grrr!

Issue with Soundpool MO4

I have a Atari STe with a Soundpool MO4 MIDI extension. It used to work very well, but unfortunatelly doesn't anymore: Cubase still detects it, and I can output MIDI to it but nothing is coming out from any MIDI Out. It took me a while to tackle it (lack of time, lack of tool, other items to play with), but I gave a glance last week-end. The parallel port on the Atari uses only the following signals: Pin 1 : Strobe (Atari -> MO4) Pin 2 : Data 0 (Atari -> MO4) Pin 3 : Data 1 (Atari -> MO4) Pin 4 : Data 2 (Atari -> MO4) Pin 5 : Data 3 (Atari -> MO4) Pin 6 : Data 4 (Atari -> MO4) Pin 7 : Data 5 (Atari -> MO4) Pin 8 : Data 6 (Atari -> MO4) Pin 9 : Data 7 (Atari -> MO4) Pin 11: Busy (MO4 -> Atari) The MO4 also decodes few other pins, but since the Atari doesn't, my guess is the MO4 was also targeted for PC. Inside the box, the MO4 is architectured around a CPLD (IspLSI1016 from Lattice) which contains the logi...