Yahoo Groups archive

Doepfer

Index last updated: 2026-04-29 00:15 UTC

Message

Fwd: WG: [Doepfer_a100] new G6 Frame? (doepfer's answer)

2004-04-19 by Bakis Sirros

--- Dieter Doepfer <hardware@doepfer.de> wrote:
> From: "Dieter Doepfer" <hardware@doepfer.de>
> To: "Bakis Sirros" <synth_freak_2000@yahoo.com>
> Subject: WG: [Doepfer_a100] new G6 Frame?
> Availability?
> Date: Mon, 19 Apr 2004 15:17:02 +0200
> 
> > -----Urspr�ngliche Nachricht-----
> > Von: p.hendricks [mailto:ph@comcast.net]
> > Gesendet: Samstag, 17. April 2004 20:59
> > An: Doepfer_a100@yahoogroups.com
> > Betreff: [Doepfer_a100] new G6 Frame?
> Availability?
> >
> >
> > any idea when the new G6 frames will be shipping?
> with the higher PSU?
> > lots of new modules but nowhere to put them....
> 
> The new PSU is now in production at our assembly
> company. I hope they will
> arrive early May 2004. The G6 frame remains
> unchanged as the new PSU has the
> same mounting holes and connectors as the old one
> (but more connectors for
> GND and +/-12V to be able to connect more than 2 bus
> boards). The price for
> the new PSU will be about 90.00 Euro or about 25.00
> Euro additional compared
> to the old PSU. The new PSU would be able to drive
> 1.5A but we will specify
> it for 1.2 or 1.3 A only as the heat sinks,
> rectifier and the transformer
> become very hot at full 1.5A. We still have to do
> some duration tests with
> the PSU built into a A-100 frame full with modules
> and top/bottom covers to
> find the final spec with tolerable temperatures.
> 
> Best wishes
> Dieter Doepfer
> 
> 


=====
Bakis Siros
Parallel Worlds / Polariton
Athens-Greece
[Doepfer_a100] group owner
http://www.shimarecords.co.uk
http://www.ward12.com
http://www.rubber.gr


	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25�
http://photos.yahoo.com/ph/print_splash

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.