I would suggest going back and checking the traces and chips again.? The acid damage can be subtle, and cover a wider area than you would think.? It is also best to actually remove any damaged traces, not just jumper past them. Drfuzz -----Original Message----- From: spistrich <wasteking@verizon.net> To: PolySix@yahoogroups.com Sent: Thu, 8 Nov 2007 8:21 am Subject: [PolySix] polysix bat tery leak issues i did a battery transplant and a little trace repair a few months ago and my Polysix was fine, but it had this 'slow warmup' when 2 of the program LEDs would stay lit and the 'write' LED for 30 seconds then flash and go off at which point everything was fine....now, months later, the 'warmup ' period is a few minutes, and the keyboard goes in and out of having the 'write, and program #6 LEDs' on ...when these LEDs are on, on the unit plays an odd 'mixed ' sound like there are competing patches. since it is now worse i was supposing that maybe that battery acid has worked its way in somewhere. I was wondering if anyone knew which specific contact points controlled those 2 LEDs...are they on IC 31?, this chip had the corrosion and is where i had to do some splicing repair of traces. It would be handy to know if there was a specific point that controled these things... ALSO...when working correctly,i tried to download the sounds onto cassette, hitting the tape loading button, the unit would not load and the #6 LED would go on again, even if it was fine before the attempted loading. and would take a while to go back into normal with only one program #LED lit. I have schematics, but I am wondering if anyone has specific pin identification info that could help. The unit is now inconsistant. ________________________________________________________________________ Email and AIM finally together. You've gotta check out free AOL Mail! - http://mail.aol.com [Non-text portions of this message have been removed]
Message
Re: [PolySix] polysix bat tery leak issues
2007-11-08 by drfuzz@aol.com
Attachments
- No local attachments were found for this message.