hesitation, kicking engine

[fastfun]

Regarding widebands, you truly get what you pay for. I like the innovative brand products for simplicity of use, but, they're not necessarily the most accurate despite all their claims.

Per cylinder logging is fantastic if you can pull it off, but largely not required as long as compression is even, injectors flow closely, and the air flow is even to each cylinder. On a twin though, I would definitely do a perfect by cylinder map as they are much more temperamental and the differences in temperature of each jug can make a big difference.

Update (18.00 European/Greenwich timetable):
Sooow, after a hard day's laptopworking we got still at a sh.... mapping. Especially everytime at the same low rpm range/ throttlemoment Roadtuning is hardly possible and dangerous in this Dutch busy beehivetraffic.
What did we do just now : got out from the 2004 Rlll its map , which was running fine in that bike.
Next, saved it as a TuneEcumap.
Next, the Roadster didn't like this map : "not compatible".
Next, got out the OEM Roadstermap and saved it in TuneEcu, copied everything suchas fueltables, the F and L ones and also ignition and paste these into the OEMroadstermap, wrote them to the ECU.
Now, those settings were accepted.No issues with that.(PcV set to O ).

Although this 'new'map is a copy of the 2004 map, this map is running way off target. Even with the PcV it has to run well.

If it does the matter,question too is, does the OEM MAPsensor still be connected with its connectorplug?If I can recall correctly, TTS removed the MAP of the 2004 bike.

By the way, as I did in the 2004 one and still do in this Roadster, I use the Siemens deka ones, 80lb/hr







Does the Mapsensor still be in connecting with its connectorplug ?

 

[warp9.9]

Update (18.00 European/Greenwich timetable):
Sooow, after a hard day's laptopworking we got still at a sh.... mapping. Especially everytime at the same low rpm range/ throttlemoment Roadtuning is hardly possible and dangerous in this Dutch busy beehivetraffic.
What did we do just now : got out from the 2004 Rlll its map , which was running fine in that bike.
Next, saved it as a TuneEcumap.
Next, the Roadster didn't like this map : "not compatible".
Next, got out the OEM Roadstermap and saved it in TuneEcu, copied everything suchas fueltables, the F and L ones and also ignition and paste these into the OEMroadstermap, wrote them to the ECU.
Now, those settings were accepted.No issues with that.(PcV set to O ).

Although this 'new'map is a copy of the 2004 map, this map is running way off target. Even with the PcV it has to run well.

If it does the matter,question too is, does the OEM MAPsensor still be connected with its connectorplug?If I can recall correctly, TTS removed the MAP of the 2004 bike.

By the way, as I did in the 2004 one and still do in this Roadster, I use the Siemens deka ones, 80lb/hr








Does the Mapsensor still be in connecting with its connectorplug ?

If you run the map sensor, and F to L switch point at zero it should not be looking for the map sensor signal except to verify it has one and to find out its not supposed to use it. Like it does not once you go above the original set point in the tune. Of course you F tables at the lower RPS will be off and need to be adjusted to add the fuel as Claviger pointed out above. Yes Richard had us remove them back in the day. Not sure what he does now you might want to give him a ring.

Maybe he can add some of his opinions on the differences between the tune edit (tune boy) which has ignition timing for when your on the map sensor and for when you on the F tables. This might be a tune boy specific software change as tune ecu does not have that just the straight ignition tables like the old tune boy had. The only guy I know that has added the latest TTS kit to his bike has a 08 so its a different ecu altogether. I will send Richard a message but like most businesses I've run into lately are very slow to respond.

If you want to send me the two maps I would like to take a look see. All my older maps for mine were tune boy because there was no tune ecu back then.

 

[Vampire]

I took a look at this bike and here´s what i did. To get tune spot on i think its best to find a good tuner with a dyno or have the knowledge what to do by using some sort of datalog to set fuel to Rpm vs TPS, reading Afr values. It´s not that difficult when everthing is working the way it should. But first be sure all the hardware is okay, if it´s not, there ´s no way to get the fueling right. There´s no way to ride this bike on the public road and make a proper fuel map without reading data. It ran well so where to start..? i copied the OEM Roadster map and saved it in TuneEcu. Also the 2004 map was saved there, aswell as the PowercommanderV map on which the´old´supercharger bike was running. The TuneEcu map wasn´t compatiblle with the newer Roadster ECU. The newer Roadster TPS fuel map starts at 400rpm i.o 0. The RPM fields are different untill 1200rpm, so copy -paste wont work unless you modify the map to fit in. That´s what i did and added the PC5 map to it. F/L switch was allready set to zero in this map. At this point the TuneEcu map with the PCv map are very close to the supercharger mapping the 2004 bike ran. Something´s different or not working well on this bike vs the old one influencing the fuelling. ECU settings are nearly the same, should be okay for riding according to the old mapping. In the end, pistons, ignition, fuelinjektors, cams , exhaust etc are the same. And it´s making the same amount off power, running well from over around 10%TPS to full throttle.