Kawasaki ZX-10R Forum banner
1 - 13 of 13 Posts

·
Registered
Joined
·
231 Posts
Discussion Starter · #1 ·
Having trouble with Woolich recently.

My ECU was warrantied a few months ago and there's currently the 2017 model in it. Woolich kindly supplied me with a new bin file due to the warranty free of charge.

About a month ago I went to write to my ECU and it failed multiple times (auto-retries) and then stopped. This resulted in the ECU being left blank and so Woolich software was unable to associate a writable bin file to it. As such the bike was effectively bricked and I was unable to read or write to the ECU without buying another bin file.
Sharon from Woolich seemed to have got a notification from this and sent me an email and assigned a new bin file to my account to use. She said something along the lines of it appears I lost my bin file, and told me to double check all connections, power to laptop, and internet connection. I'm pretty vigilant with this since I work in IT.

With the new bin file I managed to write to the bike, but any flashes since then has gone through 2-3 failed writes before successfully writing. Concerned me but seemed to be working.

I'm currently trying to fine tune the autoblipper and today it did the multiple fails again and then stopped saying it couldn't write to the ECU like just last a month ago. Now the bike is back to being bricked, no bin file on the ECU, and the Woolich software unable to confirm that the ECU is indeed tied to a valid bin file. So I can't even flash the stock bin file back to it without having to buy a new bin file ($133 Aussie buckeroos). Being Sunday I can't get a hold of anyone from Woolich to try get help. Left an email and voicemail though.

Has anyone else had any experience with this. It's driving me nuts, and makes me fearful to work on the map any further because I never know if this write is going to fail.

USB device and connection are firm and wires are not damaged. ECU bypass wire is tightly in and connecting. Always reboot and connect everything to check all is good first, then perform a read to double check it's good. This never fails, it's just the writing that fails.

One concern is that I have to run it from a Windows VM since I have a Macbook. I'm not going to go buy a Windows laptop to do this obviously. This however in theory should be fine since it's done it plenty of times before without issue. And like I said, I work in IT so everything is configured properly and there's no issues with my VM's etc.

Help. :(
 

·
Registered
Joined
·
481 Posts
Figured it out. VMWare uses an intermediate USB driver which can interrupt data transfer. I guess the transfer to the ECU can't auto-recover from dropped packets like generic file transfers.
good to know. I have done at least 15 flashes to my ecu without any issues but I used a windows 7 laptop to do the writes. If i was you I would invest in a cheap windows laptop.. you can find them for under $200 for a decent one (local small computer shop/craigslist/ebay/newegg). I keep mine in my garage to lookup stuff/read pdf manuals/read/write ecu. :thumbsup:
 
  • Like
Reactions: Boxtradamus

·
Registered
Joined
·
1,088 Posts
good to know. I have done at least 15 flashes to my ecu without any issues but I used a windows 7 laptop to do the writes. If i was you I would invest in a cheap windows laptop.. you can find them for under $200 for a decent one (local small computer shop/craigslist/ebay/newegg). I keep mine in my garage to lookup stuff/read pdf manuals/read/write ecu. :thumbsup:
I have done over a 1000 lol. :lol:
 

·
Registered
Joined
·
231 Posts
Discussion Starter · #6 ·
So the problem was your end and nothing to do with Woolich. That's normally the case about 99% of the time.
Problem is Woolich software is not configured to handle millisecond data interruptions like every other application and protocol on the planet can. They didn't even know the reason, just a broad statement of "Oh something with it doesn't work but we don't know what so just don't use it.".
 

·
Registered
Joined
·
782 Posts
I have used parallels and win7 pro on a macbook pro mid 2014 without any issues. I do have to ensure the device is connected to the win 7 machine and sometimes reconnect the ecu and computer.

How did you figure this out? It is not an everyday issue you encounter.
 

·
Registered
Joined
·
179 Posts
Guys, a dumb question, please....

IS it possible to mess up an ecu, or other electronic bit, by flashing it so many times?

Is there an upper limit when the ecu will finally say, "No more?"
 

·
Registered
Joined
·
481 Posts
Guys, a dumb question, please....

IS it possible to mess up an ecu, or other electronic bit, by flashing it so many times?

Is there an upper limit when the ecu will finally say, "No more?"
no you can flash them as many times as you want. Only way you could really mess it up would be to disconnect it in the middle of flashing the bike.
 
  • Like
Reactions: bbsteinnewyork

·
Registered
Joined
·
51 Posts
Guys, a dumb question, please....

IS it possible to mess up an ecu, or other electronic bit, by flashing it so many times?

Is there an upper limit when the ecu will finally say, "No more?"
Apologies for the thread jack. I can't contribute to problem at hand as I don't have any experience with the woolich kit yet, but I remember reading in the manual when I had the Kawasaki kit ecu in my 09 zx6r that you were only able to write to the ecu X amount of times before you could no longer write to it. It was a crazy absurd amount, but with my limited knowledge in electronics, I was always curious as to why that was? -Steven

Sent from my HTC Desire 625 using Tapatalk
 

·
Registered
Joined
·
450 Posts
Apologies for the thread jack. I can't contribute to problem at hand as I don't have any experience with the woolich kit yet, but I remember reading in the manual when I had the Kawasaki kit ecu in my 09 zx6r that you were only able to write to the ecu X amount of times before you could no longer write to it. It was a crazy absurd amount, but with my limited knowledge in electronics, I was always curious as to why that was? -Steven

Sent from my HTC Desire 625 using Tapatalk
You are right about that, EEPROM can be read/write 100,000 times. After that Either need to be replaced or change address. some say it is lower than 100,000. Different ATMEL may have different capacity. need the spec of the chip that is inside the ECU , but I am sure that if you can not tune the bike by 5-10k times you should give it up, LOL
 

·
Registered
Joined
·
51 Posts
You are right about that, EEPROM can be read/write 100,000 times. After that Either need to be replaced or change address. some say it is lower than 100,000. Different ATMEL may have different capacity. need the spec of the chip that is inside the ECU , but I am sure that if you can not tune the bike by 5-10k times you should give it up, LOL
Interesting stuff for sure, I appreciate the response. Haha, I'd have to agree with you if it's taking that long to get it right. However even with the large number, it's a nice piece of information to retain if buying used a couple times over maybe. Thanks again!-Steven

Sent from my HTC Desire 625 using Tapatalk
 
1 - 13 of 13 Posts
Top