Image Map Image Map
Page 1 of 4 1234 LastLast
Results 1 to 10 of 40

Thread: Microscience HH-725A in 5160 Clone need help on error codes

  1. #1

    Default Microscience HH-725A in 5160 Clone need help on error codes

    I got a CanTech 5160 Turbo XT (4.77/8.0Mhz) with a Microsience HH-725A HD. (A Canadian PC clone)
    The drive spins up, the red activity LED flashes a few times, and there is a click, then 3 buzzes, a click during POST. It dose not boot to C: I can only boot from FD.
    When I boot to FD, the Green HD LED flashes in this pattern. Short, Long, short pause, Short, Long, long pause, and repeat, with no Red LED activity.
    One of the IC's on it's PCB, U6, gets hot.
    The HD card it is connected to is a Data Technology 5150BX 1 P/N 10-00476. The IC on this card MB113T303, 8505 Z41, DCT-P078-1B also gets warm to the touch.
    Thoughts, ideas, suggestions??
    Thanks!
    Atari Falcon 030/FX-1 CF & SD 14mb, Atari MSTE, Atari PS3000, STACY 4 /w UltraSatan SD, 4160STE-CosmosEX, Atari PC1-PCH204-2xPCF-551-PCM124, 1040STFM, 1040STF, 520ST(4mb, 16mhz), 400-48K & std kybrd, 800, 600XL, 800XL, 1200XL(256 Rambo,svideo,31-OS,APE upgrade), 130XE, XEGS, matching peripherals for all,
    Apple llGS ROM 3-4mb-CF HD, C64, 4+, IBM XT 5160, IT 99/4+, TRS80-4P, Amiga 500,

  2. #2
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,571

    Default

    Quote Originally Posted by KLund1 View Post
    The drive spins up, ...
    So, you can hear and feel the platters spinning. That rules out head stiction.

    Quote Originally Posted by KLund1 View Post
    When I boot to FD, the Green HD LED flashes in this pattern. Short, Long, short pause, Short, Long, long pause, and repeat, ...
    That reminds me very much of error codes that certain drives display if their self-test fails.
    As an example, see the 'Diagnostic and Exercise Routines' section at [here].

    Quote Originally Posted by KLund1 View Post
    The HD card it is connected to is a Data Technology 5150BX 1 P/N 10-00476. The IC on this card MB113T303, 8505 Z41, DCT-P078-1B also gets warm to the touch.
    If I were to go through my vintage computer collection, feeling the temperature of each IC, I would find quite a variation. I could even burn my finger on the CPU in my fully functional 8 MHz IBM AT.

    Quote Originally Posted by KLund1 View Post
    Thoughts, ideas, suggestions??
    Are you confident that the switches on the controller are appropriately set, and cabling is correct?
    If not, that needs to be verified.
    If so, perhaps as a start, see if SpeedStor software can get the drive to do a seek test.

  3. #3

    Default

    See below for confirmation. but if my morse code is right, then I am getting error 05, drive not getting up to speed fast enough.
    Anyone agree with me?
    If so, then what might a solution be? Is there a way to lubricate the motor in some useful way?
    Thanks

    from spec sheet:
    Error codes may be generated by the microprocessor to indicate hard-
    ware failures or warnings that are detected during power-on
    diagnostics, burn-in mode, or normal operation. Error codes are
    diaplayed in a "morse-code" type manner. Bits may be interpreted
    and converted into hexadecimal error codes. "Zeros" are indicated by
    a short (1/2 second) flashingn mode. "Ones" are indicated by a short
    (1/2 second) continuous ON mode. Error "Words" are separated by a one
    second LED off time.

    Zero = 0.5 second flashing mode
    One = 0.5 second continuous ON mode
    Between Bits = 0.3 second Off
    Between Repeat Cycles = 1.0 second Off

    Listed Below are the binary to hexadecimal conversion values:

    0 = 0000 4 = 0100 8 = 1000 C = 1100
    1 = 0001 5 = 0101 9 = 1001 D = 1101
    2 = 0010 6 = 0110 A = 1010 E = 1110
    3 = 0011 7 = 0111 B = 1011 F = 1111

    Message Definitions
    -------------------
    Code 0 - Microprocessor RAM error
    Code 1 - Microprocessor ROM checksum error
    Code 2 - Interface chip diagnostic failure
    Code 3 - Write Fault latch will not reset
    Code 4 - Index pulse not detected during spinup
    Code 5 - Unable to reach 3600 rpm in 600 revs.
    Code 6 - Unable to stabilize spin speed in 10 seconds
    Code 7 - Unable to maintain spin speed to 0.5%
    Code 8 - Unable to uncover Track Zero sensor
    Code 9 - Unable to cover Track Zero sensor
    Code A - Track Zero interrupter misadjusted
    Code B - Shipping zone error, crash stop misadjusted
    Code C - Carriage stuck during recal error
    Code D - Seek errror during burn-in or recal
    Code E - No hall transitions during spin-up
    Code F - Unexpected interrupt from processor
    Atari Falcon 030/FX-1 CF & SD 14mb, Atari MSTE, Atari PS3000, STACY 4 /w UltraSatan SD, 4160STE-CosmosEX, Atari PC1-PCH204-2xPCF-551-PCM124, 1040STFM, 1040STF, 520ST(4mb, 16mhz), 400-48K & std kybrd, 800, 600XL, 800XL, 1200XL(256 Rambo,svideo,31-OS,APE upgrade), 130XE, XEGS, matching peripherals for all,
    Apple llGS ROM 3-4mb-CF HD, C64, 4+, IBM XT 5160, IT 99/4+, TRS80-4P, Amiga 500,

  4. #4
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,571

    Default

    Quote Originally Posted by KLund1 View Post
    from spec sheet:
    Note that the example I pointed to is for a Miniscribe M8425S, not a Microscience HH-725A.

  5. #5

    Default

    My bad, Thanks.
    I found the 'manual' on the same site. Not much there. Looks like they were built about 2 years apart. How likely they used the same codes? Not too likely, but the blinking LED must mean something. I will try 'exorcising' the drive with jumper 10 and see if that might help.
    I did find this.
    http://angelohouben.nl/restoring-an-ibm-5150-computer/
    Possible last resort would to low level format.
    Atari Falcon 030/FX-1 CF & SD 14mb, Atari MSTE, Atari PS3000, STACY 4 /w UltraSatan SD, 4160STE-CosmosEX, Atari PC1-PCH204-2xPCF-551-PCM124, 1040STFM, 1040STF, 520ST(4mb, 16mhz), 400-48K & std kybrd, 800, 600XL, 800XL, 1200XL(256 Rambo,svideo,31-OS,APE upgrade), 130XE, XEGS, matching peripherals for all,
    Apple llGS ROM 3-4mb-CF HD, C64, 4+, IBM XT 5160, IT 99/4+, TRS80-4P, Amiga 500,

  6. #6
    Join Date
    Sep 2012
    Location
    Indiana, USA
    Posts
    359

    Default

    I have been searching for some info on Microscience drive error codes, but have come up empty so far. It's pretty safe to assume the blinking LED represents an error code. It's also very unlikely the codes are the same as Miniscribe's code. Those aren't even the same for different Miniscribe models.

    If this were my drive, I would very carefully remove the circuit board from the drive, then after a light cleaning and a visual inspection, I would work all of the connectors on and off, and rock any socketed ICs. I have had this bring a few old drives around. A low level format is almost a given for these old drives to operate reliably, or at all, but I'll bet this one won't take a format command until the error is resolved.

  7. #7

    Default

    Took drive PCB off, reseated only socketed large IC. When I looked closely to the drive ecumenism under the PCB there was a lot of dust around the spindle. Dusted it off, also dusted sensor over spindle on the PCB. When I reconnected, the drive spun up to a much faster speed. No blinking LED. PC now show 'not a system Disk'. So I think things are looking up.
    Loaded Dos 2.1, Fdisk; it shows 1 partition as Non-Dos type, Start 2, End 638, size 637. Fdisk can not delete this partition.
    Atari Falcon 030/FX-1 CF & SD 14mb, Atari MSTE, Atari PS3000, STACY 4 /w UltraSatan SD, 4160STE-CosmosEX, Atari PC1-PCH204-2xPCF-551-PCM124, 1040STFM, 1040STF, 520ST(4mb, 16mhz), 400-48K & std kybrd, 800, 600XL, 800XL, 1200XL(256 Rambo,svideo,31-OS,APE upgrade), 130XE, XEGS, matching peripherals for all,
    Apple llGS ROM 3-4mb-CF HD, C64, 4+, IBM XT 5160, IT 99/4+, TRS80-4P, Amiga 500,

  8. #8
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    25,660
    Blog Entries
    20

    Default

    You can clobber the partition table if you can run DEBUG from a DOS prompt:

    Code:
    A:\>debug
    -F200 L200 0
    -A100
    0822:0100 MOV AX,0301
    0822:0103 MOV BX,200
    0822:0106 MOV CX,0001
    0822:0109 MOV DX,0080
    0822:010C INT 13
    0822:010E INT 3
    0822:010F (empty carriage return)
    -G=100
    
    AX=0001  BX=0200  CX=0001  DX=0080  SP=FFFE  BP=0000  SI=0000  DI=0000
    DS=0822  ES=0822  SS=0822  CS=0822  IP=010F   NV UP DI PL NZ NA PO NC
    0822:010F 44            INC     SP
    -Q
    A:\>
    Then you can proceed with your FDISK.

    In the above script, I've used capital letters to avoid confusion, but lower-case alphas will also work. Basically, this wipes out your master partition table, so FDISK thinks it's working with a new drive. Your entries are in boldface. The location numbers in the assembly prompts are DOS version-dependent and shouldn't bother you if they're different.

  9. #9
    Join Date
    Sep 2012
    Location
    Indiana, USA
    Posts
    359

    Default

    I'm delighted to here the drive seems to have come ready. It is indeed promising. Since we are not trying to salvage what is on the drive, why not just do a low level format. I've had many old drives benefit from refreshing the low level format, and it will certainly clobber any partitions. Just let the drive run long enough to come all the way up to temperature first. I think especially a drive like the Microscience with it's rack and pinion/stepper motor combo, is susceptible to thermal head alignment drift.

  10. #10
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    25,660
    Blog Entries
    20

    Default

    My concern was that the DTC 5150 BX may not have a BIOS that allows for LLF. I've had a couple in the past, and may in fact still have one installed, but LLFs are so uncommon for me, that I don't recall. I do know that the IBM Xebec cards need an external program to LLF.
    Last edited by Chuck(G); January 9th, 2018 at 08:43 AM.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •