happy for ya.Thanks for commenting back the results.Good to know.Have a safe fun time....

Unbelievable that a faulty sensor that is causing a fault to trip an error code message is not replaced first. It would have been the first thing in the fault chain to check after crap/mud in the slotted wheel component - wonder if the TS guide told the knuckleheads what parts to throw at it.

Glad its fixed

I doubt they'll charge it for that long... expect to buy a battery when you pick it up, unless they take it out and charge it for those months ahead.

Well.The 'faulty sensor' is a misnomer.When it throws a code,it isn't saying the sensor's bad.It's directing the tech to the area of problem.At least that's what mine did.BUT,I suppose it COULD also mean a sensor was bad.As in this case?

This is odd though.I heard numerous reports early on when this 2012 came out that guys were getting rough motor action from changing sprockets.If this is a fact,shouldn't they ALL(2012'and up)do this?Neither my 07 OR my 2012,and 2013 did this on gearing and tire changes.How could it be that one does it,and another doesn't.It's factory built the same,right?Programmed the same,yes?And Kawi's saying..'this is your problem'...someone's not on the same page.Maybe HUb can answer this...I wondered for a long time ever since these types of issues came up over the years.I went from a 16 to an 18 up front,and 41 to 43 rear several times.And in between.NEVER had running issues.

* Last updated by: Grn14 on 1/18/2019 @ 8:11 PM *

Hey GRN14 what's up. I been away for a while with work and life but I'm back. some of you may not know but I'm on my 3rd ZX14r. My 1st one the candy green zx14r you'll likely remember. I went through many gear changes stock wheel base and when stretched. no issues with so called stutter issues. she was unfortunaly wrecked and totaled. 2nd black an green 2013 zx14 I did same multiple gearing changes and no stutter issue. 3rd 2013 white zx14r I did similar gearing changes. 17/40, 16/43, 17/45, 16/44, did 17/44 and now I'm seeing the weird stutter issue.. note I've put over 12k on the bike during theses changes so I know what it should feel like. its raining and bad weather now so I haven't had rime to ride much. but once weather clears i'll dig more into it. special note all my bikes average about 10k-15k miles a year commuting/backroad , pls track use.

Heya Blk.Glsd things are doin good for ya.Yeah,it's a strange deal.Throwing off the KTRC function?Power mode circuits?IDK.

* Last updated by: Grn14 on 1/19/2019 @ 2:25 AM *

As I recall, and it was back in Sept, they did "check" the sensor and it must've seemed to check out. Then Kawi Warranty Tech, whatever they are, said to replace the ECU. it took a couple days to arrive and that didn't cure it. So, at this point my dad, brother and I had to get back to the Midwest. Then Kawi said to put a stock size tire on. That didn't work, so Kawi said to put the stock rear spkt on. I shipped the stock spkt and they installed it. As we know, not fixed. So, yes, I suggested to replace the part that the bike is telling you is bad,,,,,and they finally did. Crazy.
So, with a 1 tooth lower rear sprocket, AND a taller 190/55 tire, I never noticed any issues at all. It truly must have been the riding in the pouring rain for 5 hours that finally affected the sensor. At any rate, I'll be very anxious to get back on it this Spring.

Thanks all,
ominousone

As I recall, and it was back in Sept, they did "check" the sensor and it must've seemed to check out. Then Kawi Warranty Tech, whatever they are, said to replace the ECU. it took a couple days to arrive and that didn't cure it. So, at this point my dad, brother and I had to get back to the Midwest. Then Kawi said to put a stock size tire on. That didn't work, so Kawi said to put the stock rear spkt on. I shipped the stock spkt and they installed it. As we know, not fixed. ...

OK, so if a ZX14 is having a stuttering issue Kawi is working on under warranty, and they say change the ECU ... then put the stock size tire back on ... and only then, the stock size sprocket ... that tells me Kawi didn't think the number of rear sprocket teeth mattered (much).

* Last updated by: extrapolator on 1/19/2019 @ 7:48 AM *

I use a theory to chase down things electronic:

"Magnetism = You cannot separate heat from the chemical reaction".

WATT was the last thing that occurred = Rain.
WATT helps electronic (MAG) components go belly up = Heat and a chemRe.
WATT happens if I mix a rainy day with a wet, [now] drying bike at said component = A ChemRe.
WATT are the odds I clean a magnetic pickup, a tone wheel with contact cleaner and wipe away the chemRe = No code present [chemically reacted]:
a. Connectors were connected.
b. No wire(s) out of connector(s).
c. Signal out of range = Ding-Ding-Ding we have a winner!

Now for the complex:
We live in a magnetic world.
We are handcuffed to say the 60 cycle hertz signal.
We can manipulate the timing of this magnetic cycle.
We now set this timing in the computer to recognize a movement out of range.
We say this range is k-skid induced by making the movement seem like the wheel lost traction.
We changed the spin ratio of the gearing so the signal induces an out of range signal that triggers k-skid's design.
We (me) takes the guess that the linear at such a slow spin will hiccup the k-skid's linear X to Y = Shutter within the beginning of the linear. Because it does not continue at the higher spins moving in a linear climb.

As far as a shutter on some bikes, I can only guess an ECU difference. This stumps me because I can keep guessing the map change from clutch pulled in is one map, then the triggering of the switch in the clutch housing swaps to the running maps. And being the next guess is the factory checks these kind of bike sites to note complaints and is rectified with the next year's [subtle] model changes inside the ECU [still using the same part number].

Okay.There ya have it.

* Last updated by: Grn14 on 1/19/2019 @ 1:26 PM *

Not to start this all over again, but I have an update. I got my ZX14 back this last April. Stock size tires, stock spkts. Life was good all summer, over 3,000 miles. My bike now has around 23,000 miles on it total, the last couple thousand not showing up on the ODO cuz that quit working with this issue at about 21k miles.

I put on new (stock size) tires AND put the 1 tooth lower rear Supersprox back on for our almost annual trip to the Dragon again. Rode 600 miles from my dad's, in Chicago area, and a few more hundred around Knoxville, Deals Gap etc. Well wouldn't you f-n know it, the CODE 24 is back and the dash is acting crazy. It runs fine. Only the tach, gear indicator, gas guage, and clock (sort of?) work. I rode another couple hundred miles while down there and road back to dad's with this issue. I sure as hell wasn't gonna leave it in Knoxville again. My Escort 360 has GPS so I know how fast I am going, just not how far.... So, I've put well over 2,000 miles on it with this shit going on.

My riding season is coming to a halt, so I'll address this over the loooooong coooold winter. I'll figure out what sensor(s) need to be replaced and do it.

If there is a moral to this story, I guess the bike likes the stock gearing??? It is just weird that it takes hundreds or thousands of miles before coming up with this issue.

Ride creatively,
ominousone

I put a 43t sprocket on my 2012 14R last fall. Once in a while it will stutter in 1st and 2nd gear between 3,000 and 4,000 rpm's. After 4,000 rpm's it runs perfectly. 3rd, 4th, 5th, and 6th gear it runs perfectly at all rpm's. The stutter only happens once in a while, very seldom in fact. It feels like the traction control when it's on, like it's cutting out or missing. It's not something I can't live with because it happens so seldom. I've heard where some of the 14R's stutter and buck really bad with a sprocket change. I thought I had heard where Don Guhl had a cure for this in the ECU. I'll have to check it out.

Here is a late update. I had my ZX14 shipped back to me from Knoxville last April. With stock gearing and stock size tires, I rode all summer, around 3k miles, with no issues. THEN, I put the 1 tooth smaller rear spkt on and went back the Dragon with my 86 year old dad, and my brother from Calif. I rode about 600 miles to Knoxville, and a couple hundred more, then guess what? Error code back on, with all the fun flashing bullshit on the dash. I put the stock sprocket back on, to no avail, at this point. Rather than leave the bike there again, I just rode it. I prolly put over 2k miles on it with no issues other than the lit up dash. I just ordered the rear wheel speed sensor, and the question is:

Where does it plug in to the harness? Is it under the tank, or somewhere easy to get to? Of course I do see where it "bolts" into the rear. I'm just wondering how much "stuff" I need to remove to plug it in.

Thanks,
ominousone

Not sure what model you have. Looking at the wire diagram in the SM, the non-abs rotation sensor goes into the ECU but the ABS model goes into the ABS processor. ECU is in the rear of the seat section.

From the SM looks like a connector but Im not sure, trace the BL/G and W/G wires

Have you had the ECU checked?? a tuner like Ghul could probably tell you if there were glitches in the ECU, call and ask

Do this first. Get an ohm meter and read the new sensor's ohm reading. Unplug the sensor on the bike, check that number on the sensor you are about to replace. Are they both the same? No need to replace the sensor.
Do this next. The tone wheel has to be clean of debris as does the magnet on the sensor. The windows of the tone wheel should not be damaged in any way [get this] shape or from. Bent window? Ding-Ding-Ding!

I might be repeating myself, but I'll take a guess we have a 3rd gen ECU with the intro of the 02/ABS being standard. From 2016 on, we have a 'keyfob relearn' (for a better term). Is the bike earlier than 2016, omi? Lets get the fob out of the way year wise.

No codes, no mods after any mods before the code, right? So the scenario is you walked away from it and it coded? And then after 2k worth of keyfobbing, which with my experience; it fobs within a chain lube or two and the code goes off. Whereas, I pulled the 02 sensor connector off and rode around coded; plugged it back in and without taking it to a dealer to use their equipment. The other way to remove a code is fob it so many times.

I appreciate the input. It is a n2016 14R SE ABS. The code and flashing dash came on while riding. Both times on or close to the Dragon. This was hundreds on miles after changing the gearing in both case. I've turned the bike off dozens of times. I've unplugged the battery a couple times as well in hopes of a magical fix.

So, I do have a new sensor and need to know where the "tail" plugs in. I do not see where the plug is from having the seat off. Does the tank need to be lifted up, or come off?

ominousone

It is a 2016 14R SE ABS

Start at the rear wheel sensor. Where I'd match sensor heads, then stretch the harness and see how far it goes finding where the connector ends.

'016 might have a longer keyfob cycle time and maybe my '017 has a shorter fob cycling. Bike has to be bone stock gearing so you know the sensor is about to be a waste swapping either way... knowing both read the same ohm reading.

Final update for a while,,,,,I hope. I had the new wheel sensor put in and all is well again. The plug in for the sensor is under the tank, for anyone that wants to know. This time, I will keep the stock size tires and sprockets on and hope I don't have to mess with this thing again. We'll see.

ominousone

Good to hear a closing of the book and/or a post showing it's solved.

I thought I would do another update. I have put on close to 4,000 miles since having the speed sensor replaced. ALL with stock tire sizes and (new)stock size sprockets. 1,361 miles were ridden in 5 days, down on and around the Tail of the Dragon. Chix strips gone, and NO error code, YAY... So, at least on my 2016 ZX14R SE ABS, stock gearing is the way to go.

And now, my riding season is coming to a close soon. Been a great summer.

Stay well all,
ominousone

Great! Good news Thanks for reporting back again.