So, Gunter and I have been discussing and he points out that the step change in sensor reading is unlikely to be an internal ECM fault as I suggested, instead it looks like a dropout in data collection. Since I made the cable, I won't be blaming that. Other data that Bigpete sent me doesn't appear to have this dropout.
So, using Gunter's plot he sent me:
Attachment:
Bildschirmfoto-MegaLogViewer MS 3.3.02 - 20130405_1813.JPG [ 302.64 KiB | Viewed 393 times ]
we can see that Time also has a step change. Lesson learned for me there...
I believe Bigpete is using PCSpy, and I am not 100% sure how that manages logged data, whether it declares a comms failure or whether it logs data when it is available, however there is a 3 minute loss of data and assuming it logs data when available, that could be any of the following; ECM, harness, cable, PC.
But back to the real issue of the bike not running properly...
Looking at where Pete has set the idle:
Attachment:
bigpete 3.jpg [ 191.68 KiB | Viewed 403 times ]
With throttle closed, TPS 8 bit is 24, TPS deg is 8.1.
This is consistent with Kevmean's Muffin, but only at a partially open throttle.
Attachment:
to Gunter 2 - from Muffin.jpg [ 169.35 KiB | Viewed 403 times ]
However at idle, Kevmean's Muffin is TPS 8 bit 12 and TPE deg is 4.2:
Attachment:
kevmean 4.jpg [ 160.17 KiB | Viewed 403 times ]
This suggests the TPS reset has been done correctly, but additional throttle is needed to get the bike to tick over, and with the slow return to min idle speed (which is higher with Bigpete's bike), suggests a lean condition.
I have suggested manifold seals (tested with propane around the manifold/head interface), but it could be other things, such as:
* a blocked fuel tank vent - does the engine run OK with the fuel cap off?
* a poorly performing fuel pump - does the bike run OK at wide open throttle?