Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!rutgers!gatech!udel!mmdf
From: Ata@radc-multics.arpa (John G. Ata)
Newsgroups: comp.sys.amiga
Subject: Re: A501 clock failure
Message-ID: <6224@louie.udel.EDU>
Date: 4 Jan 89 20:29:53 GMT
Sender: mmdf@udel.EDU
Lines: 48


    Delivery-Date:  3 January 1989 09:51 est
    Delivery-By:  Ata.SysMaint
    Sender:  amiga-relay-request at LOUIE.UDEL.EDU
    Date:  Sunday, 1 January 1989 16:49 est
    From:  George Robbins <grr at CBMVAX.UUCP>
    Subject:  Re: A501 clock failure
    To:  amiga-relay at LOUIE.UDEL.EDU
    Organization:  Commodore Technology, West Chester, PA
    
    In article <8901011415.AA07578@MATH.Tau.Ac.IL> <finkel%TAURUS.BITNET@CUNYVM.CUNY.EDU> writes:
    > Help!
    >
    > The clock module of my A501 has stopped functioning.
    ...
    > Battery Backed up clock not found
    ....
    > I tried using the 'setclock opt reset' but it didn't help.
    >
    > I opened my A501 unit. The Battery output is 4.12V, and according to
    > the schematics it should to be 4.5V. Is this the problem?
    > According to the schematics, the battery is also supposed to be NiCad.
    > Is it charging while the machine is on? Also, The RAM on the module
    > works OK. Only the clock stopped working. What can I do?
    > What output should I expect on the test point TP3 on the A501 board?
    > I'm an EE student, and I'd like to try and fix it by myself. What is the
    > cost of a new 6242 chip? ( If this is the problem )
    
    The voltage you mention is probably OK if measured at the clock chip,
    it's a little bit suspect if measured at the battery.  You should check
    that the battery is charging when the machine is powered up - it is
    trickle charged through a resistor.
    
                              .
                              .
                              .    
    
    --
    George Robbins - now working for,       uucp: {uunet|pyramid|rutgers}!cbmvax!grr
    but no way officially representing      arpa: cbmvax!grr@uunet.uu.net
    Commodore, Engineering Department       fone: 215-431-9255 (only by moonlite)

Wasn't there a posting a while ago stating that the 1.3 version of
setclock had a deficiency where it would not work sometimes after a
crash with this exact error message?  They claimed that using the 1.2
setclock would fix this situation.

                              John G. Ata