microkorg always enters write protect mode :(

astralpilot · Post by **astralpilot** » Tue Oct 08, 2019 8:53 am

hello dear people!

i just bought an old microkorg off ebay and have the problem that after turning it on, it always shows 'bat.'. i then can not edit almost anything and it doesn't let me turn off write protect.

after selecting the write protect mode with shift + 8 i turn knob 1 but nothing happens in the display. also other functions can not be changed with the knobs.

i tried with a replacement power adapter but also with fresh batteries - both the same result, so i guess it's not the power adapter. after kicking out bat with shift, i can play the stored patches without problem and also access through midi - so it seems everything else works just fine.

what am i doing wrong or where do i have to search for a solution?
anybody had the same issue?

really would like to tweak that little monster

thanks in advance for you help!!!

OpAmp · Post by **OpAmp** » Wed Oct 09, 2019 9:04 pm

Hi,

Sounds like a board problem...

It is normal that when BAT. is indicated that write protect mode goes on automatically and that you can not edit anymore. It is like a sort of protection for you to avoid just making a new patch and not able to save it properly anymore because your batteries are running low.

Now the fact that you get this also with the power supply is not normal. It looks like the circuit for detecting the input voltage is broken and does not pass the information correctly anymore to the main CPU. your little monster needs some surgery...

Bye.

astralpilot · Post by **astralpilot** » Sun Oct 13, 2019 4:29 pm

OpAmp wrote:Hi,

Sounds like a board problem...

It is normal that when BAT. is indicated that write protect mode goes on automatically and that you can not edit anymore. It is like a sort of protection for you to avoid just making a new patch and not able to save it properly anymore because your batteries are running low.

Now the fact that you get this also with the power supply is not normal. It looks like the circuit for detecting the input voltage is broken and does not pass the information correctly anymore to the main CPU. your little monster needs some surgery...

Bye.

hi OpAmp,

thanks for your answer!
i hoped it could be something else, but yeah, now i will try to find a surgeon :S
hope this goes with my budget...

cheers!