Yahoo Groups archive

Emax

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

Message

Re: EMAX I Rack ERAM Error

2013-08-16 by ajarlev

Hello

I have the same problem. Eram test says is 71sbc bk01c, AD777778 ADRESS
The emax se plus works somtimes, but suddenly it frezes up. Also somtimes difficult to load disks. I found the service manual, but the eram dignostics pages were missing.

I tried the ic cleaning on the ram board. I will try to take it out to see if there is a problem
on the backside.

I hope someone here has the answer

-alx



--- In emax@yahoogroups.com, "odyssey3001" <odyssey3001@...> wrote:
>
> 
> Hello fellow EMAX users,
> 
> 
> 
> I recently acquired an EMAX Rack. As it seems the unit was stored in a
> damp environment for quite some time.
> 
> It boots up until the "Please Insert Disk" message appears and
> the following LEDs are lit:
> 
> Master, Transponse and Enter.
> 
> The Floppy drive did not take any disks, so a HXC-emulator was hooked
> up.
> 
> It is possible to load floppy images with the HXC.
> 
> There is no sound, the only thing that is heard is a click sound if
> notes are sent via midi.
> 
> The following measures were taken so far with measures against static
> discharge:
> 
> -       PCB cleaning.
> 
> -       Reseating of all socketed ICs on the digital board, except for
> the E-Chip because it was not possible to get it out of the socket.
> 
> -       Results of The Internal tests: Bank RAM test passed, ERAM test
> failed.
> 
> Message:
> 
> is80sb01 bk0ic??
> 
> ad000000 galpat
> 
> -      If I remove any of the RAM chips the message stays the same.
> 
> 
> 
> To make a long story short: What can I do to bring the unit back to
> life?
> 
> As for test equipment I am in possession of a scope and a logic
> analyzer.
> 
> I don't know exactly where to start to look for errors.
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
>

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.