Shift points

[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

 

[ecoboostsho]

I use Forscan with my obdlink MX and I can get updates at about 30 ms...not great but better. As everyone else has mentioned Torque is great for gauges....not for logging.

Sent from my XT1096 using Tapatalk

 

[SHOdded]

Settings > Data Logging & Upload > File Logging Interval

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

1 second is worthless

 

[f8tlSHO]

Settings > Data Logging & Upload > File Logging Interval

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

1 second is worthless

gonna go try this out, will this change the speed of the gauges or just the log?


Sent from my iPhone

 

[SHOdded]

You know, I am not sure!  I have ignored the gauges for so long (datalogging is my primary purpose).  I'm sure the TPro wizards on here know for sure!

 

[FoMoCoSHO]

I have not figured out how to decrease the response time of the actual gauge. It drives me insane.

Hopefully one of these days I can master programming dash command as its much more responsive. I'm in the process of procuring a new desktop with a dual monitor setup which should help facilitate the process. It is way more involved than Torque.

 

[SHOdded]

Might be part of Torque's load-limiting programming so it is compatible with a wider array of devices.  Even though the display is relatively Atari-like in its' design

 

[f8tlSHO]

Well, changing it to the smallest interval has given me skewed results.. Mph was stuck in the log at 43.xxx for like 2 seconds then shot to 60mph.. Ahhhhhhh, so I'm gonna dial it back to every .3 seconds to see how it reacts


Sent from my iPhone

 

[Scott4957]

Just curious, but why aren't you guys using the SCT with a laptop? I know its easier to just bring up torque with a bluetooth OBD reader but if you want the most accurate data I would think you would want to use the SCT. The SCT can do a handful of PID's on the device at full speed without a laptop, so if you just want to check some times like we were talking about you wouldn't even need the laptop.

 

[f8tlSHO]

I do, I just got the torque setup to check it out. I know laptop and x4 is better. Just more of a pain for a quick log


Sent from my iPhone

 

[SHOdded]

Well, changing it to the smallest interval has given me skewed results.. Mph was stuck in the log at 43.xxx for like 2 seconds then shot to 60mph.. Ahhhhhhh, so I'm gonna dial it back to every .3 seconds to see how it reacts

Sounds like the OBD reader can't read fast enough?  How many PIDs are you logging at one time?  If not using an OBDLink MX, I'd definitely keep it under 15 or so.