WEIRD Bug PLEASE HELP

My bad Jimmie.

I made the tests, nothing solves the problem. The first thing I´ve noticed is that the pad 04 just shows that level as it´s being hold if I rise the sensitivity almost to the maximum level. It is the pressure level that changes, not the velocity. The pad 03 is with the same problem too but a little less. If I hit the pad 03 or 04, the pressure level shows activity but not the velocity. So the pads 03 and 04 isn´t working no more. I really don´t understand how the velocity ain't working if the pressure are working on pad 03 and 04.

I tried to put out the 128 RAM, nothing changes. Tried to pull out the pads, nothing happens.

Whatever the problem that is causing this, probably my MPC came with it already out of the box and that´s why it´s sensors stopped working in 3 months so I had to change it. What takes me to the conclusion that the sensors will probably die soon. But at the first time this weird bugs didn't happened, but I remember that the lower pads stopped working first and suddenly one day none of them worked no more. What takes me to the conclusion that they´ll probably die soon.

The problem is that my city doesn't have any support from Akai, so I´ll probably have to fix it myself. So I appreciate any help. I think I´ll have to change the complete pad assembly as @punchdrunk said. But I just fear that this could not be the problem. If someone knows any other test that I can do please tell me, I appreciate any help.

* I still could not factory RESET this shit. There´s any other way to reset than holding erase as turning on the unit ? When factory RESETing anything appears on the screen so I know that the reseting is being done ?

** I still can´t relate the 'autoplay' problem with my pad problem. Could anyone please do the test of holding the pad 03 or 04 or them 2 while browsing some audio files at the load screen and see if it triggers the audio files as you scroll up and down with the DATA wheel ?

*** In the Akai OS everything ok except the broken pads. No autoplay. Continuous audio track is working fine, no problem looping the second or any bar alone... Sh*t... this could't be more complicated.

Please anyone with a 2500 and JJOS do this test to me. I´m bout to buy a pad PCB but first I want to know if this have anything to do with the JJ bugs, cause the Akai Os is running ok despite the dead pads.

dunego wrote:Could anyone please do the test of holding the pad 03 or 04 or them 2 while browsing some audio files at the load screen and see if it triggers the audio files as you scroll up and down with the DATA wheel ?

Yes it does. On JJOS2XL v1.39, if I hold down pad03 or pad04 and browse through samples in the load screen it triggers the samples to play. This may not be relevant to akaios because it probably doesn't play the samples in the load screen when you press a pad.

The problem is that one of your pads is constantly being held down.

Service notes here if any help -> http://www.eserviceinfo.com/downloadsm/ ... C2500.html

Maybe you can track through the relevant chips to find the problem, being that you already bought a new set of sensors which don't seemed to have solved the issue.
But then you said everything worked when you first got the pads.. Then maybe it's a dodgy capacitor that you need to replace?
I dunno... I'm def not a qualified electronics guy.

Thanx a lot bro ! I think I´ll try to change the PCB and the sensors and the pads all at the same time... Please if you can do just one more test. Keep holding the pads 03 and 04 while you move from one pad settings to another with the cursor in the Program->Sample screen, in the sample field or any field and see if one program pad settings will be overwrote by the last one. If this is confirmed, I´ll be 100% sure that all the problems is related to the pad problem so I think changing the PCB and sensors and pads will solve this (hopefully).

I don't know much about what his exactly does, but you can run what is called a boot block. You just power up while holding the play button. It runs sime kind of check through the Mp. It runs 4 (i think) different tests. Though the results may not mean much to you (or anyone else here for that matter) it may show a specific error that Akai may be able to help you with. Worth a try.

Nobody did the test so I did it myself. Thanks to the JJ feature that you can access the pad options like load and save by the MODE+numeric pad. So I disconnected the pad sensors from the PCB, and also disconnected one of the PCB cables with the qlink PCB, like you can see in this photos:






AND GUESS WHAT ? NO PROBLEMS ! NO AUTOPLAY, AND NO WEIRD THING ON THE PROGRAM MENU. So I even connected the cable I disconnected and let just the sensor off. Like this:




NO PROBLEMS.

That takes me to the conclusion that the problem MUST be the PCB since the sensor is almost brand new. I´ll try to clean up the PCB connector where you put the sensor connectors... Let´s see what happens...

Good luck in getting it sorted out, it's a dirty job but somebody has to do it

I´m ordering a Pad Assembly PCB, a pad sensor, and also a black pad set just for a little fun after all this stress.

I stopped using it since I think the PCB is in shock (short circuit) and the other pads is dying slowly one by one.

So I think I´d rather keep the MPC off till I install the new PCB; I hope it solves the problem. I´ll post here my results.

Did you try just disconnecting the ribbon cables and maybe put some rubbing alcohol to see if it helps the problem?

It's hard to tell in these circumstances if it is a short or a bad connection :/.

Well here I am, a few months later, with my MPC working again. I replaced the pad assembly PCB, the pad sensors and the pads itself (in that case just to get a black one).

My conclusions are:

1. The problem was really the PCB (Pad Assembly), maybe I damaged it on the first time I did a pad sensor replacement, probably for one of that reasons:

a) I forced too much the pad sensors to fit the PCB, before I realized that there was a lock there. Or...
b) I didn´t cleaned well the metal case where the pad sensors adhesive fits. This last time, I went paranoid with that, and the adhesive was almost new so was hard to clean, even with a adhesive remover, so I had to use a razor to clean it perfectly. Believe me, I did it for about an hour to get this shit completely out of the metal case.

2. The solution was purchase a new pad assembly and a pad sensor (that was probably damaged by a short circuit that I caused forcing the pad assembly lock) and install it very carefully. Now there´s no pad showing wrong activity on the pad screen, and everything seems to be fine. I hope it stay like that for at least 2 years.

3. Numark AKAI still sucks, because my original pad sensor came already **** up, and I had to replace it with 3 months of use. And if I damaged the pad assembly for trying to put the new pad sensor without unlocking the PCB, is because this component sucks. Should be more resistant.