Rtek Timing Maps
01-20-07, 08:33 PM
#51
interesting.
also, could someone explain why there is so much negative spit timing in the default timing map? Or point me in the direction of an article or something, because everything ive ever seen says negative split is really bad. Then there are a few that argue that it is good as long as it is only in vacuum
also, could someone explain why there is so much negative spit timing in the default timing map? Or point me in the direction of an article or something, because everything ive ever seen says negative split is really bad. Then there are a few that argue that it is good as long as it is only in vacuum
Last edited by gxl90rx7; 01-20-07 at 08:54 PM.
01-20-07, 09:01 PM
#52
Originally Posted by gxl90rx7
ok i finally started messing with the timing maps and noticed something weird. Did anyone else see the spikes at low load at higher rpms?? I found 3 spikes of 64.7 around that area, but all the cells around it were around 36. I have hardly even looked at the maps previously.
Also, when idling, the log shows "timing leading" at 20, "timing trailing" at 5, yet in the trailing map at 1krpm, ~no load, there is no "5," all the cells are in the 14's. Shouldnt it match what the log is showing?
and just to be sure, the numbers in the map are degrees advanced, right? so 30 would be more advanced than 20?
Also, when idling, the log shows "timing leading" at 20, "timing trailing" at 5, yet in the trailing map at 1krpm, ~no load, there is no "5," all the cells are in the 14's. Shouldnt it match what the log is showing?
and just to be sure, the numbers in the map are degrees advanced, right? so 30 would be more advanced than 20?
01-22-07, 09:33 AM
#53
Originally Posted by Karack
if you are idling just above 1000 RPMs or near enough to it the ECU may interpret it as a driving situation and not an idling situation in which case the split is reduced to 0 and and the timing increased, also if your TPS is off adjustment you may get the same result.
01-23-07, 01:09 PM
#54
The spikes seem to be an intermittent display bug. Seems more prone at higher RPMs. If you back out to the main screen and go back into the tune screen, the spikes should not be there anymore. Though if a change is made to the map when the spikes are on screen, those spikes will be written to the ECU.
Version 1.03 is attached. Updating is highly recommended.
As for the difference in the timing on the map and timing in the logger, there are other factors that effect the final timing. Henrik will post with details.
Version 1.03 is attached. Updating is highly recommended.
As for the difference in the timing on the map and timing in the logger, there are other factors that effect the final timing. Henrik will post with details.
01-24-07, 06:40 PM
#55
Senior Member
Join Date: Mar 2001
Location: Vancouver
Posts: 429
Likes: 0
Received 0 Likes
on
0 Posts
Here's a bit of additional information regarding timing maps and indicies.
The timing maps are interpolated between entries. The ECU will compute
a fractional index between two points and use this for interpolation. ie if
rpm was 1500 and the indicies were 0 at 1000 and 1 at 2000, the ECU
would use an index of 0.5. A simple example with a fictitious simple map:
1 50 100
0 25 50
0 1
If the computed index was 0.5, 0.5, the logger would show 0,0. The
computed timing would then be:
((100-50)/2+50 - (50-25)/2+25) / 2 + (50-25)/2+25 or 56.25.
There are also a couple of retard components that are applied to base
timing based on coolant T, intake air T and knock sensor. In a warmed
up normally operating car, these will all be zero. Graphs attached.
The timing maps are interpolated between entries. The ECU will compute
a fractional index between two points and use this for interpolation. ie if
rpm was 1500 and the indicies were 0 at 1000 and 1 at 2000, the ECU
would use an index of 0.5. A simple example with a fictitious simple map:
1 50 100
0 25 50
0 1
If the computed index was 0.5, 0.5, the logger would show 0,0. The
computed timing would then be:
((100-50)/2+50 - (50-25)/2+25) / 2 + (50-25)/2+25 or 56.25.
There are also a couple of retard components that are applied to base
timing based on coolant T, intake air T and knock sensor. In a warmed
up normally operating car, these will all be zero. Graphs attached.
03-15-07, 12:07 AM
#58
Senior Member
Join Date: Mar 2001
Location: Vancouver
Posts: 429
Likes: 0
Received 0 Likes
on
0 Posts
My understanding is that it was done for emissions and mileage reasons. People are quite secretive about sharing timing information, but you will see negative split discussed on occasion in some threads. Its always in vacuum.
-Henrik
-Henrik
03-23-07, 03:13 PM
#59
Senior Member
Join Date: Nov 2001
Location: Las Vegas, NV
Posts: 318
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by turbo2ltr
The spikes seem to be an intermittent display bug. Seems more prone at higher RPMs. If you back out to the main screen and go back into the tune screen, the spikes should not be there anymore. Though if a change is made to the map when the spikes are on screen, those spikes will be written to the ECU.
Version 1.03 is attached. Updating is highly recommended.
As for the difference in the timing on the map and timing in the logger, there are other factors that effect the final timing. Henrik will post with details.
Version 1.03 is attached. Updating is highly recommended.
As for the difference in the timing on the map and timing in the logger, there are other factors that effect the final timing. Henrik will post with details.
i downloaded this software today, cause my car is finally up and running from the upgrades i did. i synced with my palm and plugged into the computer, but when i got to TUNE and the ECU edit screen, my software still seems to show 1.00 instead of 1.03. Am i doing something wrong or is it not supposed to show?
Thread
Thread Starter
Forum
Replies
Last Post
Skeese
Adaptronic Engine Mgmt - AUS
65
03-28-17 03:30 PM
stickmantijuana
Engine Management Forum
11
11-09-15 01:15 PM
befarrer
Microtech
3
08-22-15 05:52 PM
