Beogram 8002 motor control issues

  • This topic has 5 replies, 3 voices, and was last updated 2 weeks ago by alf.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #5110
    alf
    BRONZE Member
    • Topics Started 6
    • Total Posts 20

    Hi All,

    working on my Beogram 8002 which decided to die over night ?!

    no Standby LED, nothing….

    After a complete recap the unit partially worked again:

    when Play is activated the carriage moved to the 33 to 45 switching point and stopped.

    STOP wasn’t working but only the manual ‘in function’ (<<) was working.

    checked the motor control circuit (1TR3 and 1TR4) – acc to the service manual

    1TR4 = PU51 transistor ! What I found was a dead MPSW 51 transistor instead ?

    I ordered a Pu51 but was wondering if there are equivalent types I could use ?

    advice would be greatly appreciated.

    ALF

    #5123
    Mark-sf
    Beoworld Member
    • Topics Started 0
    • Total Posts 57

    95GU55 or 95GU56 should work fine as replacements for the PU51.

    #5124
    alf
    BRONZE Member
    • Topics Started 6
    • Total Posts 20

    Thanks Mark,

    i will take that on board (if I can find one!!!)

    perth isn’t exactly a semiconductor hub.

    ALF

     

    #5620
    morgan_mad
    BRONZE Member
    • Topics Started 0
    • Total Posts 1

    The part PU51 is for sale in Beoparts shop.

    #5623
    alf
    BRONZE Member
    • Topics Started 6
    • Total Posts 20

    Thank you for the info – part has been ordered 3 weeks ago – still waiting……!

    ALf

    #5832
    alf
    BRONZE Member
    • Topics Started 6
    • Total Posts 20

    Hi All,

    still waiting for the Beoparts order…..in the meantime after some research I decided to replace the faulty 92PU51 transistor with a M BD 508 type which is working fine.

    The motor control function is now fully restored and the Beogram is back in business

    thanks to all interested members.

    ALF

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.