BMW S1000RR Forum banner
241 - 254 of 254 Posts
Ok let me try to explain this in more detail, I have issues at work with explaining stuff to coworkers because I am impatient and a little bit of a smart ass, even when I am not trying to be. So please tolerate my bad habits for this issue.
I am flashing my bike without issue. I rode the bike today with the tune in it. I am happy with its direction and grateful to everyone who has added information and has brought up good questions that make me think and dig deeper into the data. Thank you @QuickSliver for helping me spend my money lol.

There is 1, just 1, table that is not working for me the way it does for QuickSilver, and that is the ETV-Requested Torque. This is the table in factory from my '24 S1Krr. View attachment 231073

If you use the table as is, you will get this result from your Hex 911.
View attachment 231074
Please notice the Throttle Valve Senor both 1 and 2, this is in a non-running state, just the bike powered on for scanning purposes. Yes, the adaptations have been reset at this point, if you are wondering. The adaptations did not alter/resolve this issue. The picture below is the bike running on said tune during that same scan.
View attachment 231075
Once I flash the ECU with the below values on the ETV-Requested Torque..Which is what QuickSilver can do with his bike
View attachment 231076

The values on the throttle valve sensors change dramatically.
View attachment 231077
If you crank the bike with this setting it will welcome you with something that sounds like a dragon dying (watching Game of Thrones with the wife, sue me lol). In other words a rev bomb. I, while also typing this, just added 50% to the ETV- Requested Tourqe Table to see how the Throttle valve sensors like it. So maybe all of that data will help everyone understand I am not trying to figure out to flash, I am trying to figure out how a table that needs ETV and RPMs to choose how much TQ will be delivered can affect the EVT so much at idle or when not even running. If you feel like I have left anything out please ask me to clarify. That is the setup I have in the kitchen for flashing until the wife kills me View attachment 231078
Chatting with a dude on a fb group who does lot of tuning and bin file work and he states

It’s not about setting all cells to 100 and you shouldn’t.
There are a number of 3D torque monitoring tables that need to match or else the bike will go into limp. But yes, the first step is getting rid of the throttle limits in the midrange and near the rev limit. Throttle does need to be limited in the low end though. If you set it to high, you’ll lose torque by slowing the intake charge velocity thru the TB which harms tumble and in-cylinder air/fuel mixing.
which sort of makes sense, DI engines have different fuel atomisation characteristics to traditional engines that use an inlet manifold for fuel/air mixing
 
Chatting with a dude on a fb group who does lot of tuning and bin file work and he states



which sort of makes sense, DI engines have different fuel atomisation characteristics to traditional engines that use an inlet manifold for fuel/air mixing
Thank you for sharing that info. I believe I have a good range now on the ETV tables now. I might tweek them a slight bit more, but only 1% to 2%. I have done a ton of data logging on the AFR side of things and cleaned up that fuel map.
 
Guys thanks a lot for this great thread. Lots of useful comments. I'm trying to learn to use the tool on a different BMW bike that uses the same ECU but different part number. In other words, it shares many maps with the S1000RR. I noticed that one these shared maps is the Max Requested Torque Correction. This is a factor of the max torque which the ECU uses to adjust timing to be able to produce the torque. Has someone played with this map?

The column header on the map goes all the way to 130. I thought it was the lb-ft of my model, but I see that the S1000RR map also has a range of 130 as well, but the torque on the 2024 is only 83 lb-ft. To make things worst, the graph has the axis as TPS, which I guess is wrong. Any idea of what I'm missing?

Thanks,
Azari
 
The axis on my chart has the column header as engine load and row header as RPM. I have not adjusted this table.
Does it looks like this one? I'm still trying to figure what units are used for the Engine load (ft-lb, Nm???) and how is the correction factor applied. The header row on the K1600 has the same range of 60 to 130 and that engine has completely different torque values compared to the S1000rr.

Image
 
Identical to yours. Engine load isn't a Tq value. Here is a Ai explanation of it,
In the context of Woolich Racing's tuning software, "engine load" refers to the percentage of the engine's potential torque being used, a value that can be viewed in real-time or logged for later analysis, particularly useful for diagnosing issues, especially on a dyno.

Here's a more detailed explanation:
  • What it is:
    Engine load, as displayed in Woolich Racing's software, is a percentage representing the engine's current load, or the amount of power being demanded from the engine.

  • How it's used:
    • Real-time monitoring: The "Engine Data" screen in Woolich Racing Tuned (WRT) software shows engine load in real-time, which can be helpful for observing how the engine responds to different conditions.

    • Data logging: You can log engine data, including engine load, to a file using "Data Viewer - Live," allowing for later review and analysis of the data.

    • Troubleshooting: Understanding engine load values can help identify potential issues, such as misfires, incorrect fuel trims, or other performance problems.
  • Context is key:
    It's important to remember that engine load values should be interpreted in the context of the specific engine, driving conditions, and the tune.

  • Calculated vs. Absolute Load
    • Calculated Load: Ranges from 0 to 100% and reflects the current airflow compared to the peak airflow at WOT (wide open throttle).

    • Absolute Load: Ranges from 0 to 100 on a naturally aspirated application and 0 to 400 on a boosted application, reflecting the normalized calculation of air mass per intake stroke.
  • Woolich Racing Software:
    Woolich Racing's website provides tools for viewing and logging engine data, including engine load, which can be customized to display specific parameters.
 
Only engine mod is removal of stock exhaust and exhaust valve. This is a simple street tune. All it does is restore full power from the factory/EPA limitations and reduce the high engine temperatures. Perform at your own risk. I bear no responsibility for anyone that does their own tuning. As you can see from the images, the bike is very restricted from factory. Suck it, Bren.
Hi Qicksliver , Thank you very much for you post. I want to ask can do the same tune on my 2025 s1000rr?
 
241 - 254 of 254 Posts