After fitting a Remus with "Race Baffles" and destroying the pleasant driveability of the Uly, the fuel and ignition is coming under scrutiny...
You may remember on the old forum where the Firebolt came under the knife, well things have moved on, a more capable version of ECMSpy is available and although the steep learning curve is less steep than it was, we still don't know it all....
So, the story starts with the kind donation of a set of headers by WKD1 to UKBEG, onto which I got some lambda sensor bosses welded. These were fitted to Uly with two LC-1 wideband sensors:
The beauty of the LC-1s is that ECMSpy for Mono, or MonoSpy as I like to call it, supports LC-1s for datalogging, so I can have the lambda (or AFR) included on the same timebase as all the other engine parameters, which means I no longer need a dyno to set the fuelling up in open loop, I can do it by logging...
So, after loading the Uly up with the lambda sensors and a laptop connected to the ECM and dumped in the Triple Tail Pack (TM), I took her for a spin, following Daywalker through the traffic across Bristol and taking in the spectacular ring road...
Not long been back, however the log was only 40 minutes long as the battery in the laptop is not as it used to be. Quite some alarming data though; check this out, this data is influenced by the top line of the fuel map. I am not sure if it is rubbish data, but the fact that it is repeatable suggests not.
Attachment:
wotlambda.jpg [ 40.53 KiB | Viewed 2308 times ]
I'll need to dedicate a logging session to WOT runs to check the validity of data.
I do though have sufficient data to remap the closed loop area for front and rear, which I may get round to doing this weekend...
go for it 
.......never mind that, get yourself busy with race kit headers and mufflers 
.......only ones I have are bolted to my bikes and that's where they're staying