 Re: checksum error while trying to read ECU |
| Ok good, i suspect it was a loose wire or harness issue that may have been resolved when you were moving things around. good that its all working well for you. |
| |
| Re: checksum error while trying to read ECU |
| No, but have flashed the ECU twice now with no issues. |
| |
| Re: checksum error while trying to read ECU |
| Ok great to hear you got it sorted, it does sounds like a harness or USB type issue. Did you isolate what it actually was? |
| |
| Re: checksum error while trying to read ECU |
Nevermind - next read attempt completed.
I have unified maps etc and reflashed  |
| |
| Re: checksum error while trying to read ECU |
| After disconnecting the ECU and Yosh plugs for inspection, and reassembling without making any changes I have tried to read the ECU with WRT again.
This time I plugged into a normal USB 2.0 port on the laptop, instead of the (backward compatible) USB 3.0 port I used yesterday.
The read got to about 60% on the first attempt, then gave the error:
Unexpected response while reading checksum for Block:12 Page:60
Any suggestions? Is it worth trying with a different laptop?
Regards,
Jasper |
| |
| Re: checksum error while trying to read ECU |
| There was an audible click when each terminal seated past the retaining catch in the plug housing.
I have popped the plug off to inspect, and it looks OK (different appearance of the two new terminals is residue grease from insertion):
http://s8.postimg.org/gxdftcif9/B_King_Logbox_ECU_Plug.jpg
screengrab
Also tested continuity from ECU plug to the Yosh plug for each of the wires which was OK.
"Test Interface" from the tools menu in WRT software came back as OK too. |
| |
| Re: checksum error while trying to read ECU |
You have to make sure the pins lock in, I know, that happened with mine  |
| |
| Re: checksum error while trying to read ECU |
| Hi Justin,
I have installed the logbox on my 2010 B-King and after connecting to the ECU ok, I can't get a complete read.
The reading starts ok, but part way through (usually between 4 and 13%) it stops with the following error:
Unexpected response while reading checksum for Block:xx Page:xx
I was able to download the contents with ECUEditor v2.5.5.115, and opened this bin in WRT v1.1.97 then sent the bin file to Woolich Racing.
Can you let me know if the file I retrieved is viable and complete?
Will using EE to flash autotuned bins created by WRT still give full functionality?
Thanks,
Jasper |
| |
| Re: checksum error while trying to read ECU |
Yep, that was it. ECU connector pins didn't get inserted fully... recovered and now she's talking beautifully!
Now to get that wideband O2 sensor wired into this harness and logging... 
Really liking this little LogBox... |
| |
| Re: checksum error while trying to read ECU |
| Ah... good to know, thanks.
Guess it's time to go back through the harness, since everything else seems OK... |
| |
| Re: checksum error while trying to read ECU |
| Logging data and flashing are done on separate communication busses in the harness. Just because you can read engine data doesn't necessarily mean you are able to flash or read the ecu file. |
| |
| Re: checksum error while trying to read ECU |
| I guess what I don't understand is how it can pull data OK (since the LogBox works fine) yet not read the map... reading seems to indicate improper wiring of the harness, but that doesn't match up with the successful use of the LogBox... |
| |
| Re: checksum error while trying to read ECU |
| Short of just trying a different, laptop, any suggestions?? |
| |
| checksum error while trying to read ECU |
| Having a tough time with the COM setup. Drivers installed fine; have tried re-doing that a few times, but no variance. COM5 port is clearly indicated when the LogBox is plugged in (Windows XP, looking in Hardware Config)... and Com5 is available for selection in Settings. But I can't read the ECU or serial #.
Engine is 2008 GSXR1000; stock engine mapping, never flashed before. I've been able to collect data with the Logbox - works great for that! I am able to pull the data off the LogBox with USB cable in logging mode, no issues.
Exact text of the error is...
"Unexpected or missing ECU response during initialization. Programming aborted, reset ECU and reprogram"
(repeats twice, then the following message)
"Unexpected response while reading checksum for Block:0 Page:0"
Open to suggestions... Logbox is new, fresh out of the box, only logged data once... ECU power is on... LogBox in Flashing mode... Harness definitely good, since I can log data...
Only other thing I haven't tried is to actually flash the ECU, but I'd really like to be able to read data first before pulling the trigger on that... |
| |
| |
| View Topic on the Woolich Racing Forums |