![]() |
ECU tuning in Europe
Hi guys, apologies for a new thread if this has already been answered - I can't find the info.
Is there a reputable tuning shop someone can recommend, in Europe? I'm located in Slovenia, and would consider going to Italy, Austria, Germany or any other neighboring countries if anyone can recommend a reliable tuning company. I don't have many mods, just intake filters and catback exhaust, but I believe the engine should be able to safely squeeze out some 20ish hp or more (I figure it should at least get the nismo figures out). Any info or recommendations? Thanks! |
Remote tune with Eugene turkov or Seb?
Sent from my iPhone using Tapatalk |
For that I would have to find a dyno, right? Not sure they would be cool with me having someone remotely tune the car....although I do like the idea.
|
ECU tuning in Europe
Quote:
No you just data log the car via street driving and then send the data files to your tuner and they send you revised tune files. Might take a few back and forth to get it right but considering you have mild mods I’m sure it’s not bad at all. The Carizon on YouTube has a good break down video of the process when he remote tuned with Eugene Sent from my iPhone using Tapatalk |
Quote:
Thanks! |
Bear in mind it takes a bit longer than if you were to dyno. I've been tuning since April and it's on hold for now as the car is stored for the winter.
|
Quote:
|
ECU tuning in Europe
Quote:
To be blunt.. what’s taking so long to get your car tuned? How many iterations of your tune have you gone through? Sent from my iPhone using Tapatalk |
Quote:
It's my summer daily but back and forth to work is 10 minutes each way so I guess this makes it take longer? idk. Sorry for hijacking the thread a bit here. |
Not hijacking at all, it's valuable input. How long should each of these sessions for data logging supposed to last?
|
Quote:
|
Quote:
So, 8 revisions including the base which opens the ECU to allow logging and to my knowledge doesn't change anything else. Rev1 - 184mb - 11 logs Rev2 - 32mb - 3 logs Rev3 - 265mb - 36 logs Rev4 - 216mb - 26 logs Rev5 - 162mb - 26 logs Rev6 - 184mb - 29 logs Rev7 - 121mb - 21 logs Rev8 - 588mb - 68 logs Rev9 - 644mb - 57 logs This spans April 13 - Nov 14 '22. Mods are Berk cats, Z1 intakes, Invidia Gemini C/B. |
Quote:
each driving scenario results in a different engine speed & engine load. So you have tables in within the ecu and most of them are indexed as such X: engine load Y: engine speed As you drive, the ecu does a lookup in various tables to control fueling, vvel, cam timing, etc etc. Here is an example of a timing map: https://www.ecutek.com/EcuTek/media/...ighResMaps.png So as you can see there are many cells. If you are only tuning full throttle at sea level, then generally your load will stay around 100% as your rpm increases, this is a very small portion of the "tune". There are some scenarios where you will have a very hard time reaching them on the dyno and other scenarios that are difficult to reproduce on the dyno, so real world driving is required. In addition, and this is probably the most important part, you can't just go off of a small sample. You need to drive the car as conditions change and repeatedly log the vehicle to determine the ideal values for each cell. One day your car might pull timing, the next day it might be fine, so the best value will lie somewhere in between. It's common to see knock sensors desensitized or turned off completely to avoid having to do this extra work. Analysis of why a car pulls timing can be complicated and made more difficult by lack of tooling, especially in a remote tuning situation. Seeing as how the values may change somewhat significantly, some smoothing of the tables will be needed and this will again require additional adjustments until there is a convergence.. This process can take a while to complete depending on the vehicle, there is no other way. Each tune I do comes with unlimited revisions and data processing/review, until no more practical changes need to be made. You can keep collecting data for the entire duration of the tune support. The more data you collect, the more accurate the results of the tune will be. It's only in your favor to collect as much data as you can over a longer period of time to get the best results. |
Quote:
|
Quote:
Having large data sets increases confidence when making tune changes because outliers don't skew the value. You also don't always catch knock in certain load/rpm cells in a single drive or weather condition. I don't understand why people are complaining about starting a data log for a drive they would have already done when it means a more accurate tune that covers wider drive conditions? Plus, after your first couple of revisions with Eugene, you still probably have a better tune than most out there. The last few revisions is icing on the cake. |
All times are GMT -5. The time now is 08:01 PM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 PL2