How long can I record with Directscan?

[Dan K]

I hope it's longer than the 1 minute 44 seconds that the T-Link website claims?
Thanks.

 

[TurboDave]

Not really, why would you need to record for so long?

 

[Zero Tolerance]

I believe DS records for 90seconds. What's with 1 min 44 sec anyway?

 

[Dan K]

Originally posted by TurboDave
why would you need to record for so long?

Because not everything I'm going to want to record is going to happen in a 1/4 mile.
Nor are the triggers that you can use in directscan going to help.
I'd like to be able to drive the car for a little while under all "conditions" and see what the car does and how it reacts so that I can have a better understanding of what to do when I start burning my own chips.
Hmm...this sucks.

Thanks guys.

 

[BM Computer Src]

you cannot burn your own chips without directscan. (period). Nothing else will provide enough data to get your chips in the ballpark.

Bob

 

[BoostKillsStres]

It only takes probably less than 10 seconds to hit the space bar to stop the recording then the function key to autosave then enter, enter, spacebar and your recording again for another 90 sec. You do that a couple times and you'll have all kinds of data for review.

HTH

 

[Dan K]

Originally posted by BoostKillsStres
It only takes probably less than 10 seconds to hit the space bar to stop the recording then the function key to autosave then enter, enter, spacebar and your recording again for another 90 sec. You do that a couple times and you'll have all kinds of data for review.

HTH

If it came down to it, I could do that.
Just wish I could have the unlimited recording time of T-Link and speed of Directscan....have my cake and eat it too.

That's how the stuff I have for the camaro is....just wishful thinking.

 

[Eric Stage I]

You can also reduce the frames per second to get more time.

For just driving around stuff, you might only need the lowest setting of 4.6 fr/sec, and you'll get almost 7 minutes.


Regards,
Eric

 

[TurboDave]

Originally posted by Dan K
Because not everything I'm going to want to record is going to happen in a 1/4 mile.
Nor are the triggers that you can use in directscan going to help.
I'd like to be able to drive the car for a little while under all "conditions" and see what the car does and how it reacts so that I can have a better understanding of what to do when I start burning my own chips.
Hmm...this sucks.

Thanks guys.

Well, you really don't need unlimited recording time to burn your own chips, although I will agree, to try and do your own without DS is nothing short of guesswork! Been doing it for years, and when DS came along, there was a MARKED improvement in all aspects of chip making

You really only need 20 seconds or so of data at whatever "mode" of driving you're monitoring to get the info you need, trust me, you'll be overwhelmed with data in short order.

And as for capturing a glitch or problem. It's easy, even if the event just occured and you weren't recording. DS keeps a "look back" buffer, so suppose a "glitch" happened, and you then hit the space bar to start recording right after the event. If you play back that recording, you'll see that the data recorded actually started way back (several seconds) before you even started the recording. Neat feature!!

 

[ijames]

I wanted at least 3 minutes Saturday so I could record my car's IM240 dyno emissions test. A couple of friends have failed and they said that they could clearly see the driver mashing the gas too hard, letting all the way off, then mashing back down, as he tried to keep the speed constant. I just wanted to see, so I set it up to record at 4.1 fps and recorded the whole run. Sure enough, early on the hc spiked and fell, spiked and fell, and I could hear the throttle being mashed and released, and ds showed the tps doing the same thing. By the end of the test the driver had gotten fairly good at driving my car, but by then it was too late, of course. I failed but fully expected to because I was testing some other mods - the retest is free and I don't think I'll have any problem then. If I fail, then I'll pull out the data logs and have a nice chat with the manager.

Oh, don't forget the bug in DS that gives wrong time slip data for any frame rate below 18 fps. So far as I know Kent hasn't fixed that yet.

 

[Dan K]

Changing the update rate should do it. I didn't realize that it was now variable. After looking more closely at directscan's site I see that it is.
OK, you guys talked me into it...looks like it should work for what I want afterall.
Thanks!