Shift points

[FoMoCoSHO]

2015 shifts at 6200

2013 shifted at 5700 iirc.

[Scott4957]

What were the shift points on either of the cars? Were they low or like mine at 6200rpm?

Have you been doing revisions on your tune? Or is your 12.9 the first base tune?

[f8tlSHO]

What were the shift points on either of the cars? Were they low or like mine at 6200rpm?

Have you been doing revisions on your tune? Or is your 12.9 the first base tune?

Yes I have had revisions done. But my 12.9 tune was setup to be used in 40 degree weather. The day I went to the track it was a freak 72 degrees. So the tune was dialed back because of fuel pressure safety


Sent from my iPhone

[f8tlSHO]

2015 shifts at 6200

2013 shifted at 5700 iirc.

Torrie had mine set at 5700 on my original tune. It felt slower so I had him change it to 6200. Maybe it wasn't slower, I didn't actually test it. The same can be said for the mustang foxbody cars, shifting around 5-5100 always got me better e.t's at the track. Redline on tach was 5500 I think.


Sent from my iPhone

[Scott4957]

2015 shifts at 6200

2013 shifted at 5700 iirc.

Torrie had mine set at 5700 on my original tune. It felt slower so I had him change it to 6200. Maybe it wasn't slower, I didn't actually test it. The same can be said for the mustang foxbody cars, shifting around 5-5100 always got me better e.t's at the track. Redline on tach was 5500 I think.


Sent from my iPhone

You could look at logs to get an idea. Pick two speeds with one or more shifts in between and compare the time between the two with different shift points. For example 60-100 with the 3/4 shift might be 7.2 seconds with one shift point but 7.1 with another. Not an exact science but a start.

Sent from my SM-N910V using Tapatalk

[FoMoCoSHO]

You could also use Torque, logging only WOT Torque/HP/RPM to figure it out.

Looking at where my power peaks, 5850 might be my new shift point.

[f8tlSHO]

I have been playing with torque, I don't have it all figured out yet. It seems to be a tad delayed, is there a way to get it to respond quicker? And in the logs I thought the time in between each piece of information was too big. Tuning on my mustang  I feel like it records more information per second ( if that makes sense)


Sent from my iPhone

[FoMoCoSHO]

In my application, Torque seems to catch all the data, there is just a lag writing to the gauge on the screen.

[FoMoCoSHO]

I wouldn't use Torque to data log anything critical, that is what the X4 is for. Yes, X4 is much faster.

I need to look at the graphing function in Torque again, that might be the ticket to see a basic power curve.

[SHOdded]

To record at anything other than idle, you need to log on the order of 1/100ths of a second (up to 6000 rpm) to catch the live curve.  1/10ths of a second (Torque Pro's current limit) is 1/10ths of a second (600 rpm).  I think OBDLink goes to 5 msec intervals (1/200th of a second) but don't think even the OBDLink can keep up.  Will have to try it with just a couple of PIDs and see.

[f8tlSHO]

To record at anything other than idle, you need to log on the order of 1/100ths of a second (up to 6000 rpm) to catch the live curve.  1/10ths of a second (Torque Pro's current limit) is 1/10ths of a second (600 rpm).  I think OBDLink goes to 5 msec intervals (1/200th of a second) but don't think even the OBDLink can keep up.  Will have to try it with just a couple of PIDs and see.

Can you change it in torque?


Sent from my iPhone

[SHOdded]

Maximum resolution in Torque Pro is 1/10ths of a second.  Default is 1 second, IIRC.

[f8tlSHO]

Maximum resolution in Torque Pro is 1/10ths of a second.  Default is 1 second, IIRC.

1 second is worthless


Sent from my iPhone

[SHOdded]

Depends on what you are using it for.  If you are monitoring a lot of parameters, and just generally keeping an eye on things, I think it's fine.  But if you are troubleshooting, or running diags, or datalogging, then definitely, you want faster data returns.

[f8tlSHO]

Depends on what you are using it for.  If you are monitoring a lot of parameters, and just generally keeping an eye on things, I think it's fine.  But if you are troubleshooting, or running diags, or datalogging, then definitely, you want faster data returns.

im talking about logging... I did a log and I thought to my self "what is wrong with this log" then I realized it was taking information every second. Rpm was jumping several hundred rpm in between points.. Lol. I'm just used to logging in my mustang where each data point is like 15 rpms.. I will look for that setting in torque. 1 thing I was trying to look at was fuel pressure since it's finally getting cold here in pa.


Sent from my iPhone