Yahoo Groups archive

Wiardgroup

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

Message

Wogglebug mod errata!

2007-02-10 by drmabuce

Hi All
   Dan Schierl spotted some errors and ambiguities in my schematics
for the Wogglebug #3 standard. 
   Romeo Fahl's words echo in my cobwebbed mind ..."Scham Dich Alter
Mann!".... Indeed.
   first to business:
   i posted corrected updated schematics in the files section:
WBug3Mods-DrMabuceII
   The Old schematics have been removed. For any of you who have used
them, i direct your attention to two changes, both are circled on the
new schematic.
1) pin 3 of the LF398 (M2) should be connected to pin 6 of U4 , not pin 5.
2) pin 2 of the new 555 CV circuit (M1) includes a CV attenuation pot
(100k) from point "A" (pin 5 of the LF398, M2)

   Dan's comments also indicated that i did a poor job of making it
clear that M2 is an ADDITIONAL and separate LF398 to U1 in Grant's #3
standard schematics.***1
   To clarify...
   mod#2 and mod#3 are related. In the original #3 standard design
LF398 U1 controls BOTH the VC1 vactrol AND the VC2 vactrol (which in
turn controls the rate of the 555)
   My mod#2 isolates the effect of VC1 to U1 and eliminates VC2. 
   In my mod#3, VC2 is replaced by a two transistor exponential
current source controlling the rate of the 555, and i add a separate
LF398 (M2) in order to obtain a vector of control for the clock rate
that is independent of the vector that controls U1. 
   Mo' complexity...Mo' potential strangeness.

   My sincere apologies to all for any confusion or inconvenience
caused by these errors. And equally sincere thanks to Dan for bringing
these issues to my attention.

best to all,
-doc
***1
to Dan...
ignore the first bit of advice i sent you. The R8 pot (& R26 & R2) are
all part the U1 circuit and have nothing at all to do with M2...very
sorry for the bum steer. i reacted rashly and before grokking the BIG
picture.

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.