I have a 2012 California model. Is the number printed on the ecu itself? I will check it out in the morning

Yes, number is etched on top of ECU

* Last updated by: johnnyo on 11/24/2013 @ 12:56 AM *

It's possible the Cali model has some different programming.IDK...just a thought...'bad bin file' may be nothing serious...hard to believe Kawasaki allowed something like this to interfere with any programming?I can't see it it...no way IMO.Prove me wrong please...

It's possible the Cali model has some different programming.IDK...just a thought...'bad bin file' may be nothing serious...hard to believe Kawasaki allowed something like this to interfere with any programming?I can't see it it...no way IMO.Prove me wrong please...

No GRN, don't see that as being plausible. My view is "We" the "Users" down loaded the corrupt file into the compare bin. With 9 diff ECU's for the same bike that makes most sense. Minor problem, very easy to fix. I just need a clean ECU to do a proper read, then down load the clean bin file into the compare software and the world is good. We Fix.

"Preignition problem"...pls elaborate...what's going on Hag?You've had your 14R for how long now?And she's displaying a preignition issue?

Nothing big... just an annoyance. Been there from day one. Whenever I hear it I just back out of the throttle a tad. A smidgen more fuel in the low rpm cells would probably cure it.

Preignition....not okay.Shouldn't be there...ever.Not on a bike of this caliber.Ignition tweak?Maybe you should Hag.I couldn't live with a problem like this...no way...you know this isn't okay for this motor....from day one...mine had a mild bog in 1st....I felt it wasn't right...had a flash done...problem solved...ignition.Please don't blow your motor.....

I have a 2012 California model. Is the number printed on the ecu itself? I will check it out in the morning.

maverick1441 any luck ?

Hagrid I am curious as to Your ECU #. I have never heard of any other reports on Pre ignition. Winter here, I would be happy to take a look at if you would like ?

Subthrottle flapping under hard throttle is 1 of 3 interventions happening. It sounds like engine knock when I heard it. Since day one is when I heard it. I now have the subs locked open, hear very little, sans a short hard throttling, yes, I did hear a higher pitch knock and it's all stock running the lower octane number.

Hagrid I am curious as to Your ECU #.

I'll have that # for you this evening Romes.

Hagrid worry not I have your ECU on file. Romes it's 666!

If an ecu is corrupt from factory. Bike will not even run. If an ecu flash is layered in incorrectly, you can corrupt the entire bin with faulty math. :)) hahahaha. Didn't I mention this once before??? :) yup. Fixing a corrupted ecu when it's corrupt because you don't have a clue what ur doin???? Good luck with that. :)) when it comes to flashing ECU's it is about knowledge, patience, mathematics, and an understanding of the technical layering build of an ecu's 3D math. Without those tools in the box, stuff like corrupt files happen. Kawi DOES NOT SHIP corrupted ecu's. They test every single one. Just sayin.

If an ecu is corrupt from factory. Bike will not even run. If an ecu flash is layered in incorrectly, you can corrupt the entire bin with faulty math. :)) hahahaha. Didn't I mention this once before??? :) yup. Fixing a corrupted ecu when it's corrupt because you don't have a clue what ur doin???? Good luck with that. :)) when it comes to flashing ECU's it is about knowledge, patience, mathematics, and an understanding of the technical layering build of an ecu's 3D math. Without those tools in the box, stuff like corrupt files happen. Kawi DOES NOT SHIP corrupted ecu's. They test every single one. Just sayin.

C'Blast what has happened has nothing to do with your post above. Not sure why you added this. Or am I ? We the users have uploaded a corrupt file into(Not Me)Woolich compare bin. It's just a shame I found it the hard way, that's all. And yes it can be fixed. Please don't make everything into a pissing match. And Of course when I push forward and fix it you will post a retraction, correct ? Or just delete like always. Nice.

Remember, the ECU is tested OK before its sent to the kawi factory. The factory sets the bike on the running dyno, runs up every gear, and that too is a PASS before it's crated. I believe the ECU comes under an emission related clause. So when past the 12/36 warranty, you still have 5 more years on the ECU for emissions related issues. It may have changed, but that's what I remember.

Hub when we use Woolich hardware and plug in a ECU that has never been seen or used before the Woolich softtware will ask "WE the USER" to upload the brand new Bin file. Once saved, From that point on the bin becomes the compare bin we all use. Remember there was only one, then two Now nine diff ones for us all to use(sweet).

If you look the 0175 has been removed as it was corrupted by the uploader. 0176 Still has never been plugged into Woolich, yet ?. The shop who read the 0175 ECU for the first time uploaded it and is resposible for the bad binfile. Honest mistake, could have been a bad read or voltage was off lots of reasons. This is not about anything other than to fix a problem.

Justin has been outstanding in providing us with support from the very beginning. The second I found this was to late for me. Once any new ECU's are found they will run the same process to provide Access to us all. Nothing Bad all Good, but with computers and human beings there will always be errors. That's how we learn.

I'm asking for Help for anyone who is willing.

One way you can tell a bad ECU is it misses at a certain rpm/mph. If X meets Y = Miss-fire within an rpm range. No stick coil will help. No compression test will show up as a miss-fire, if all are even across the board.

In this case Hub it's code 39

I've seen your flash romans. Don't get me started. I'm still runnin version 1. Cause its flawless.

I've seen your flash romans. Don't get me started. I'm still runnin version 1. Cause its flawless.

This is malicious, unwarranted, and VERY POOR FORM.

Play nice boys.

Ok guys i'm going to post up and express my thougts. I've been busy with other issues here on my End so i haven't posted up yet. Not going to get into the who's got the better flash.. Romans or Cblast. In my opinion both are good depending on what your looking for out of your bike. This problem with my ECU could have happened with whomever i sent my ECU to...Yeah i'm bummed that my babies siting still...But I'll be straight up with you guys.. I've talked to Romans, Cbast, and other members here. In my opinion Romans is a standup guy. He's doing eveything to get the problem fixed. No disprect to any one. Once the problem with the ECU is fixed i'll post up my imperssion on what it feels like. Riding impressions and dyno run to what what i perviously had with my set up. This is not my 1st rodeo. I'm 51 years old and have been riding and modding bikes and cars for years. I've got 18.5k miles on here since i bought her in agaust of last year, on alot of diffrent roads, weather conditions and stock and modified configurations. I also have a race preped 06 zx10 that i street and track that has over 12k street and track miles on her during the same time period. The zx10 has almost 50k miles on her in 4 years, got it used with 6800 miles, and has honest 180-190hp and 82-86 trq to the real wheel depending on dyno run on. Gives zx14's and busa's fits of frustration. I also do 5-10 track days a year. Im my opinion in stock motor configuration and with just bolt ons your only going to get from 195-210hp and 110-120 trq depending on the dyno and area where the dyno is run on. Lets face it every tuner has a differnt idea on what works and what doesn't to get to the same ponit. The best performance possible. Then it all comes down to riding style and feel for you the rider and what works for you...

The 14R is a wonderful platform to mod...EVERYTHING that a guy can do performance wise shows up on this bike....I mean...you can feel it...I love this bird and the flashes here are most excellent....

This problem with my ECU could have happened with whomever i sent my ECU to...

Yes and it would have. But, it happened to Me, or Us. Make no mistake, no matter the cost I will make it right. I am truly sorry. I am making no attempt to hide what happened.

Just could use a clean cali ECU for one min.

In my opinion Romans is a standup guy. He's doing everything to get the problem fixed.

Thank you for the kind words and the Understanding. Especially at a time like this. Speaks Volumes.

In this case Hub it's code 39

Here is my kidney cruncher, stool sitter of a read so far. Computer speak wise, we calc in the decimal to binary-binary to decimal to binary: is the final calc of the 1 and 0 conversion is the processing. That's my understanding of it in a nutshell. So if we see these numbers in the cell blocks it goes something like this.

The math checker that computes the numbers, sends it along to another rechecker is that conversion happening. The math again, then sends it to the ECU to finally spit it out in binary. And that 3rd entry of the ECU pushing out that number is more like trying to start the bike in a math of a decimal. Junk in is junk out, some number went decimal? It has to compute back to the binary system to see it spit out the 1's and 0's in that 'bi' of 2 = 1's and/or 0's.

If I knew the math readout to dissect 0011 1010, this represents a bi number that will properly be read as a number to represent a 1 or an 0. Right now, that corruption imo is nothing more than a calc not being within the binary's math. So this block in red or whatever map is bleeding out: is not speaking ECU in the 1 and 0 count. So my thought and it is sure off the wall, is to think that the number change corrupted to a red zone. Red may mean + or - is out of scale in the math of it. Play with the numbers in the cells, I could make the cells [playing with kit-ECU], have a number with a minus or plus in the column that says something is wrong or too much or too little or not in final binary?

If that's the case, why not lower the numbers back to binary and reburn? Or, Mikuni may use decimals in the cells to make it easy to read for some? Or they can use a binary number to rep a cell. It's possible to see these map numbers as binary numbers? That's my guess until I read more or reread 20 pages over again. It's so one understands that it has to compute eventually to a binary number in the end.

If the red cell blocks are that spread out, lower the numbers so they turn down in layer colors to blue is it? Then yellow, then white? Burn it, see if the changed map starts the bike back up? Something like that?

* Last updated by: Hub on 11/25/2013 @ 11:25 PM *

If the red cell blocks are that spread out, lower the numbers so they turn down in layer colors to blue is it? Then yellow, then white? Burn it, see if the changed map starts the bike back up? Something like that?

Was my thoughts exactly. So I rebuilt the flash in all files from ground up. #'s good. But it's the files I can't see ?

Hub, Can you think of any reason why other ECU's wont work in this case. The Cali bikes have a Evap Canister only diff I can see. I have Run almost every other ECU in my bike. I am going to give him mine, if it works he can keep it. Thoughts ?

Hey Rick, good on you for giving the guy your own ECU, one way or another we will get the problem sorted ;)

Romes, If you look at each pin, there is a "fetch/execute" kind of addressing going on. So for every pin you see out the ECU, there is a program written in binary, which is needed to fetch that execution in ROM.

So when the burn happened, ROM was changed, correct? Ram just executes in the language ROM understands [in binary] meaning. Execute is drop a coin (0) in the coffee machine. The one move now drops the cup (1), the next ping says to (0) spill the beans in liquid form. The (1) says to stop the measured flow.

So if you cannot pop up more bin maps to find the 'why' it won't run/start, it seems strange you cannot reverse the process with the bins you can see now? After all, these are the only maps that pop up when hacked into, right? Is there another set of RAM bins you can change that did not pop up on the hack? Not unless you can find/change that hidden map. But if there was a change made, wasn't it caused by the bins you can see now?

See where I'm going with this? Lets take the ECU swap and cause a scenario like this. The 0715 has a wire harness that uses 2 more (not used) pins than say a 48 state model that has no recovery canister system. So those 2 extra pins need a wire added to the harness. When you plug in that exchanged ECU, the wire has dropped out in a way, as if saying a code 38 is going to be shown on the dash. So technically, you'd have to swap an 0715 with another 0715 just for that reason alone or she codes.