intermittent touch pad fails for Kaoss Pro
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
intermittent touch pad fails for Kaoss Pro
I've had this unit for about seven months now. It stays hooked up to my DAW, and has not received any rough or "dirty" treatment. We've never had any magnetism close by or any electrical storms affecting any other electronics in the house.
About a month ago, I noticed that sometimes when I power it up, the touch screen does not always respond. At times after it has apparently finished loading, it will still not respond for almost an extra minute. At other times, for about a minute it will respond well, like right out of the box, but then it responds neither by LED or sound. Sometimes also, there's about quarter-second delay between the time the screen is touched and when the unit produces sound. The weirdest thing that has happened more than once is all the recorded banks suddenly lose their data.
I don't use the unit on a very regular basis, but I'm sure when I'm not around no cat is sitting on it or jealous lover sabotaging it.
Have there been any issues, problems with the touch screen losing responsiveness, the sound banks suddenly dropping their recorded data when a person isn't even within touching distance of the entire unit?
I've had the unit over the warranty time, and I didn't purchase an extended warranty. I'm not at all reluctant to investigate its inside connections AFTER I get some ideas and suggestions from this board.
PS I had saved this message to post later. Today, when I tried powering up the unit, the touch screen now remains totally unresponsive. I'm going to try the recalibrate solution that I read earlier on this forum, but I had tried that before and got no improvement.
About a month ago, I noticed that sometimes when I power it up, the touch screen does not always respond. At times after it has apparently finished loading, it will still not respond for almost an extra minute. At other times, for about a minute it will respond well, like right out of the box, but then it responds neither by LED or sound. Sometimes also, there's about quarter-second delay between the time the screen is touched and when the unit produces sound. The weirdest thing that has happened more than once is all the recorded banks suddenly lose their data.
I don't use the unit on a very regular basis, but I'm sure when I'm not around no cat is sitting on it or jealous lover sabotaging it.
Have there been any issues, problems with the touch screen losing responsiveness, the sound banks suddenly dropping their recorded data when a person isn't even within touching distance of the entire unit?
I've had the unit over the warranty time, and I didn't purchase an extended warranty. I'm not at all reluctant to investigate its inside connections AFTER I get some ideas and suggestions from this board.
PS I had saved this message to post later. Today, when I tried powering up the unit, the touch screen now remains totally unresponsive. I'm going to try the recalibrate solution that I read earlier on this forum, but I had tried that before and got no improvement.
Last edited by locrian on Sun Oct 23, 2011 12:21 am, edited 1 time in total.
calibration
I tried holding down 7/8/record while powering up. I got CAL 1 and the four squares at the lower left of the pad illuminated. However, touching these lit squares has NO EFFECT. Now I think the touch pad has become completely disconnected over time. Weird, but a hardware fail makes sense. I'm waiting for any replies here. I've read elsewhere on this forum about the ribbon cable internally that might be poorly connected. I'll seek contact with tech support at KORG too.
repair?
I found out that the unit is still under warranty and that a service center is about twenty miles away. Well, I left the unit on for about an hour, and when I went to turn it off, I gave it a try and lo, the touch pad is totally responsive again. WTF. Does this thing need to warm up or something? The house is usually about sixty five degrees. :S
Insight?
Not too much action these days on this forum....hope that means people are making music instead of being online....
So, I recorded some data to some banks and saved it to the SD card, as I have often done before. When I later powered back up the unit, I noticed something that I hadn't mentioned or considered before. Before this latest SAVE/Power cycle/LOAD process, the unit was powering up and the third button of the program memory banks would always be lit first. I would have to switch it manually to the first bank to start on L000 if that is how I wanted to work. I remember that out of the box, the unit would always start up with the first memory bank button lit and the program would always start at L000. I've never made ANY changes to the program memory. One day the unit seemed to spontaneously begin at 3 rather than 1. So now I'm thinking that it might have had a corrupt SAVE at one point, but now that I've used the SAVE function again, something has righted itself. Regardless, since this last SAVE/power cycle/LOAD process, I haven't been able to replicate the original problem.
I'm continuing to post here because it would be nice to know what other glitches if any anyone here has come across. This is a very complex machine and I'd expect a glitch or two considering what it can do in such a small package.
So, I recorded some data to some banks and saved it to the SD card, as I have often done before. When I later powered back up the unit, I noticed something that I hadn't mentioned or considered before. Before this latest SAVE/Power cycle/LOAD process, the unit was powering up and the third button of the program memory banks would always be lit first. I would have to switch it manually to the first bank to start on L000 if that is how I wanted to work. I remember that out of the box, the unit would always start up with the first memory bank button lit and the program would always start at L000. I've never made ANY changes to the program memory. One day the unit seemed to spontaneously begin at 3 rather than 1. So now I'm thinking that it might have had a corrupt SAVE at one point, but now that I've used the SAVE function again, something has righted itself. Regardless, since this last SAVE/power cycle/LOAD process, I haven't been able to replicate the original problem.
I'm continuing to post here because it would be nice to know what other glitches if any anyone here has come across. This is a very complex machine and I'd expect a glitch or two considering what it can do in such a small package.
thanks for the suggestion roblabs!
When I boot up I normally DON'T load anything from the SD card. However, just to see, I took the card out and rebooted. Still the same intermittent malfunction of the touch pad. Yesterday, the unit was working without any fails for over three hours--I couldn't make it fail. Now today, same problem all over again.
I guess I'll get this thing down the road.
When I boot up I normally DON'T load anything from the SD card. However, just to see, I took the card out and rebooted. Still the same intermittent malfunction of the touch pad. Yesterday, the unit was working without any fails for over three hours--I couldn't make it fail. Now today, same problem all over again.
I guess I'll get this thing down the road.
Why didn't the guy tell me during our phone call that he closes up at four thirty pm? Anyway, even though I'm going to have to drive thirty miles again one way to drop off the unit during his business hours NOT stated online, I am glad I talked to him. He said that the touch pads commonly have responsiveness problems!! Most likely my unit's problem is HARDWARE and not software. So I'm thinking, great, what if the replacement touch screen has the same problem? My first problem didn't start happening until I had the unit for six months. I have only three months left on the warranty....does having it repaired under warranty extend its warranty? Will investigate.
In the meantime, I did a hard reset, which I hadn't come across before. So far so good.
In the meantime, I did a hard reset, which I hadn't come across before. So far so good.
Thanks roblabs for your continued attention.
The hard reset seems to have done the trick. I never did this procedure before: with unit off, hold 1 and 2 program buttons and the record button while powering up. The D bank will flash. The LED digits will read Pr D or something like that. Press the D and the LED will read Pr off or something like that. The C bank lights up but I don't know why.
The hard reset makes sense to me because now that the unit has been reset I notice that the LED "show" on the touch pad no longer continues to display the name of the program long after I've switched it. I think the unit was getting hung up on the scroll display, maybe some kind of interrupt request malfunction... But I don't think this is a hardware problem. I'll be back here if the next time a hard reset does not set things right again.
What members here routinely or occasionally do a hard reset? I haven't seen any posts to this effect.
The hard reset seems to have done the trick. I never did this procedure before: with unit off, hold 1 and 2 program buttons and the record button while powering up. The D bank will flash. The LED digits will read Pr D or something like that. Press the D and the LED will read Pr off or something like that. The C bank lights up but I don't know why.
The hard reset makes sense to me because now that the unit has been reset I notice that the LED "show" on the touch pad no longer continues to display the name of the program long after I've switched it. I think the unit was getting hung up on the scroll display, maybe some kind of interrupt request malfunction... But I don't think this is a hardware problem. I'll be back here if the next time a hard reset does not set things right again.
What members here routinely or occasionally do a hard reset? I haven't seen any posts to this effect.
-
- Posts: 15
- Joined: Wed Nov 09, 2011 12:54 pm
Hey there,
Maybe you could try the inspection commands? Haven't tried them myself though, because my kp3 always works good until now, bu't those aren't there for nothing, you should try it. (copied from tips n tricks thread)
With Connection switch on [SEND], press the keys and then turn the power on.
[3] + [TAP/RANGE] : Pad all surface inspection only. the lcd displays firmware version then Pad2. Moving the finger on the pad will display the X,Y position from 1,1 to 9,9.
[4] + [TAP/RANGE] : Full inspection (internal and external)
I think with the pad inspection you can touch every square to see if it reacts well. The other one I don't know, but it can't harm your kp3 to try it.
Maybe you could try the inspection commands? Haven't tried them myself though, because my kp3 always works good until now, bu't those aren't there for nothing, you should try it. (copied from tips n tricks thread)
With Connection switch on [SEND], press the keys and then turn the power on.
[3] + [TAP/RANGE] : Pad all surface inspection only. the lcd displays firmware version then Pad2. Moving the finger on the pad will display the X,Y position from 1,1 to 9,9.
[4] + [TAP/RANGE] : Full inspection (internal and external)
I think with the pad inspection you can touch every square to see if it reacts well. The other one I don't know, but it can't harm your kp3 to try it.
-
- Posts: 16
- Joined: Sun Oct 16, 2011 5:22 pm
- Location: London, Ontario Canada
My KP3 would lose responsiveness periodically. I finally took it apart and reconnected the ribbon cable coming from the X/Y pad. Works great now. I wouldn't suggest doing this unless you are familiar with electronics. Losing the memory from the banks could also be an intermittent issue with power. However it would probably reboot if you had a loose power connection. Sorry to hear you're having problems, let us know how it gets resolved!
-
- Posts: 16
- Joined: Sun Oct 16, 2011 5:22 pm
- Location: London, Ontario Canada
I reseated the cable(s). I work with industrial automation and the second thing I do when there is trouble is make sure all the connections are tight. Thermal creep, oxydation and vibration can loosen or cause intermittent connections. So a quick snugging or reseating can often fix a simple problem. Again, only if you know what you're doing. I remember pulling about three layers of boards off to get to the X/Y pad. I did clean the contact points but my experience shows usually just loose wires cause the most problems.
undetektable:
The kaoss pro doesn't seem to have the same ways to do what you call inspections. I did get the version readout, but the touch pad never responded to touch.
ToughDuck36:
I agree that very often, malfunctions are due to poor connections. I still have time left on my warranty, but when I don't...
For the past couple months or so, I've at times been able to work with the unit for an hour or so before the touch pad stops responding. At first I thought I had a new solution: a subwoofer under the table might have been creating a magnetic field disturbance. So, I moved the woofer, and for a time, had no problems, but then, alas, the pad quit responding again.
Now I'm really curious: which kind of touch screen is in the kaossilator pro? Resistive? Capacitive, Surface Acoustic Wave?
I've got a reason to drive far enough south again that I could drop off the unit at the designated authorized repair service. Will do. However, I appreciate all input, and I'll report back if the tek finds anything interesting.
The kaoss pro doesn't seem to have the same ways to do what you call inspections. I did get the version readout, but the touch pad never responded to touch.
ToughDuck36:
I agree that very often, malfunctions are due to poor connections. I still have time left on my warranty, but when I don't...
For the past couple months or so, I've at times been able to work with the unit for an hour or so before the touch pad stops responding. At first I thought I had a new solution: a subwoofer under the table might have been creating a magnetic field disturbance. So, I moved the woofer, and for a time, had no problems, but then, alas, the pad quit responding again.
Now I'm really curious: which kind of touch screen is in the kaossilator pro? Resistive? Capacitive, Surface Acoustic Wave?
I've got a reason to drive far enough south again that I could drop off the unit at the designated authorized repair service. Will do. However, I appreciate all input, and I'll report back if the tek finds anything interesting.
-
- Platinum Member
- Posts: 594
- Joined: Fri Nov 18, 2011 12:02 am
- Location: Canada East
When my new KP2 was screwing up, I took the time to figure out how to modify the MIDI settings because it turns out I was accidentally changing stuff anytime I'd tweak knobs on my Electribe. Where you're using a DAW I'm guessing you might have got some kind of MIDI interface going on. Make sure you aren't inadvertantly sending MIDI parameter changes though your DAW by filtering out the MIDI stuff you don't want the KP to recieve. Try that out and let us know if it helps!