thanks dieter-
it generally works as an lfo, i haven't tre=ied that in a while, but
that shouldn't be a problem. i just recall once or twice it didn't
work regardless of the A or D settings (with sustain at 0).

anyhow i will take out the module and check the places you
mentioned.since the LEDS are opposite the gate inputs i can't imagine
i disturbed the wire. anyhow i changed the LED a long time back, and
this problem just happened. perhaps a mechanical break from traveling
with my suitcase playing gigs

i'll post here if i discover the problem for posterity.

thanks!-
tom


- In Doepfer_a100@yahoogroups.com , <hardware@...> wrote:

>
> Tom,
>
> maybe the normalling wire has been interrupted when you replaced the

LEDs.

> It's a blank wire going from the main contact of the first gate

socket to

> the switching contacts of the three remaining gate sockets (it leads

from

> JP2 of the first board to JP2 of the other three boards but

crosswise: for

> the upper board the solder point close to the printing "JP2" is

used, for

> the boards 2, 3 and 4 the solder points close to the front panel are

used).

>
> btw. you cannot measure the gate signal at the gate sockets 2, 3 and

4 as

> the normalling from gate #1 is interrupted as soon as a plug is inserted
> into the corresponding gate socket 2,3 or 4!
>
> If a submodule is working as an LFO depends upon the settings of the
> controls ! Not for all settings and patches an LFO is obtained. As an
> example this patch/setting has to work as an LFO: EOD -> GATE IN,

Attack =

> 5, Decay = 5, Sustain = 0, Release = 5. Changing the time parameters

(A/D/R)

> will change the rise and fall time of the LFO.
>
> Best wishes
> Dieter Doepfer
>
> > -----Ursprüngliche Nachricht-----
> > Von: Doepfer_a100@yahoogroups.com
> > [mailto: Doepfer_a100@yahoogroups.com ]Im Auftrag von thomasborax
> > Gesendet: Donnerstag, 31. August 2006 18:28
> > An: Doepfer_a100@yahoogroups.com
> > Betreff: 1 a143-2 issue
> >
> >
> > hi lads/lasses-
> >
> > i've been loving my a143-2 for quite some time. i have encountered
> > a bug in the normalization, and i wondered if anyone else had the
> > issue, or had a fix. i am happy to go into the ciruit itself and do
> > a fix, if need be.
> >
> > here's the issue- the gate of env 1 is no longer triggering the
> > other 3 envs (there are no gate/trigger signals present at the g
> > jacksof 2,3, and 4).
> >
> > this is a wonderful feature of this module. i'd like to get her
> > back to this. incidentally, the gate jacks work on all the envs,
> > just not the normalized gate input 1 controlling all others. all
> > the digital outs work etc. everything works fine.
> >
> > actually, now that i think about it. the module has been slightly
> > buggy from the start. occasionally in "lfo mode", with patch cables
> > routing the digtal outs into the gate jack, nothing happens.
> > usually it starts blinking away like an lfo, but occasionally
> > nothing.
> >
> > also, a few months ago, i noticed env 4 just up and stopped running
> > in tandem with the others, but worked individually. then it jumped
> > back up with the others.
> >
> > very odd. the only mod i've done to this module is i soldered in
> > different colored LEDs, just to make my system look more like a
> > carnival ride. i can't imagine how doing this could effect the
> > operation, but i may be missing the picture.
> >
> > anybody
> >
> > --------tom
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>