First of all I present myself, I am polpat from Italy and I am a new EII user (I hope...) After a lot of time I found a broken EII on ebay and I've got it. Here I will describe my experience during the repair hoping it will be useful for others. Once received the EII I opened it and I saw a not pleasant situation: some rust on the internal part of the chassis (this means this EII had been in a wet place) and most of all (unfortunately) oxidation traces on sockets in the logic board, especially on the right side of the pcb. I know the best would be to desolder all the sockets, clean accurately and resolder new sockets but since I don't have a desoldering station, I would to know if some product like sprays or similar can help me to just limit the oxidation process. Next I powered up the EII just to have an idea of the problem and here I try to describe what happens: after I switch on the display is ok (also retro) and the firmware boots up but a wheezing comes from the power supply. After just 2 seconds the display starts to blink and letters disappear (but retro is ok). Leds blinks almost in sync with the display. Well, it seems to be the power supply. Next step is to boot the power supply out of the analog and digital boards (PSU alone without any load). Here are voltages present on the 8 pin connector: -15V line is ok, +13.2V line is ok, +5V line seems to be ok but not very stable (it oscillates between 4 and 6.5V), +12V is dead. Ah, also a periodic "tic" comes from the C125-C126 area (according to the schematics downloaded from this helpful group), it seems like the PSU goes in selfprotection. I suppose a problem with the +5V line (not properly stable for logic TTL) and the +12V through the SCR A103 (following the scheme a +5V signal should trigger on the SCR to let him give +12V). I can think also the SCR is dead. What do you think about? Any of you had similar behavior? Thank you in advance for your help. Greetings from Italy, Patrizio
Message
EII in repair phase
2008-05-16 by mencoripieno
Attachments
- No local attachments were found for this message.