• Behringer DPM5 Audio Effects module Error d2

    From Usenetist@21:1/5 to All on Sat Jan 27 23:48:26 2024
    I have a Behringer power mixer (PMX1000) that features a DSP effects
    module with a 2-digit 7-seg display.

    The DSP module is a daughterboard with legend on it DPM5 PCB304030REVI

    Photo here https://community.musictribe.com/discussion/products/24/34/324663/dpm5-effects-module-error-d2

    It has a TMS57002 DSP and P80C32SBAA microcontroller and EDO DRAM (2 off HY514404).

    On power up, the display shows F1 for about 100ms and then stays on d2

    I only have a schematic for the main mixer board, which basically
    contains just the 7-seg displays, so I am assuming the d2 code
    originates from the software running on the DSP board.

    I have seen some threads suggesting replacing the DRAM fixed it, but I
    have tried that (once) with no effect.

    Does anybody have a schematic or any official info on what the d2 code specifically means?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Usenetist@21:1/5 to Usenetist on Sat Feb 3 02:07:04 2024
    On 1/27/24 23:48, Usenetist wrote:
    I have a Behringer power mixer (PMX1000) that features a DSP effects
    module with a 2-digit 7-seg display.

    The DSP module is a daughterboard with legend on it DPM5 PCB304030REVI

    Photo here https://community.musictribe.com/discussion/products/24/34/324663/dpm5-effects-module-error-d2

    It has a TMS57002 DSP and P80C32SBAA microcontroller and EDO DRAM (2 off HY514404).

    On power up, the display shows F1 for about 100ms and then stays on d2

    I only have a schematic for the main mixer board, which basically
    contains just the 7-seg displays, so I am assuming the d2 code
    originates from the software running on the DSP board.

    I have seen some threads suggesting replacing the DRAM fixed it, but I
    have tried that (once) with no effect.

    Does anybody have a schematic or any official info on what the d2 code specifically means?

    Well, I removed and replaced the EDO RAMs a second time and the problem
    was solved. Putting it down to a soldering error the first time, or
    possibly a bad chip.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)