Here's my take on the subject, which is limited only to Scanmaster 2.0
(SM), Turbo-Link 2.13 (TL), and Direct Scan 1.52 (DS). I can't
speak for other tools/recorders, as I have no experience with
them. I did purchase TL V3.xx, but I still haven't used it yet.
I know nothing of TL V4.0. I have not used SM 2.1 either.
I currently use
SM and DS the most (SM because it is always there, DS for the frames
per
second), but I'll never get rid of TL as it it so handy to have because
it
is "portable" from car to car.
Usually the question arises of with of the three to buy. Personally, I wouldn't be comfortable without but the SM and TL or DS. Typically I recommend SM first if funds are tight and you are currently driving blind, followed by TL if you want simplicity, DS if you want all the data you can get. Although Scanmaster can't record a run, by always being there in the car, being on every time you start the car (in clear view on top of the radio pod in my case), it is invaluable as an on-the-fly scan tool. But that is about all it is, a scan tool, not a data recorder, so you can't go for a drive and then review the data later for diagnosis. On a WOT blast, it will have a "recall" available to display the lowest O2 reading at a specific MPH, and the highest knock retard reading at a specific MPH, but that's it.
TL, on the other hand, is a very easy to use data recorder that also serves the purpose of a scan tool, but it requires a laptop. DS is also easy to use, but the installation is a bit more complicated... not a "plug-n-play" as TL is. The disadvantage of both of these is needing to have a laptop plunked down somewhere… a bit cumbersome.
I'll presume you have been to Ken Mosher's turbo-link.com
and checked out the Scan Tool Comparison Chart with the rest of his
web-site, so I won't go into all of the specifics he already has
available. If you haven't been there, do it. Also check out
Kent Chu's chuengineering.com
for additional information on DS, as well as bmcomputersource.com.
For SM, see Ramcharger's ramchargers.com. Lastly, check out gnttype.org to figure out what
it is you see on your tool/recorder & what to do. As I
mentioned before, I can't speak to any other units.
All three of these units have their positives and negatives, but in
a nutshell, here are what *I* consider the biggies:
SM-
Pro: 3-wire installation (positive, negative, data stream).
Compact, always there. (See Note.)
Con: Only records high knock (& @ what speed) and low O2
(& @ what speed) during a WOT blast. Limited to ALDL data stream
rate
(1 frame of data every ~1.5 seconds). Only shows one, sometimes two,
data
fields at any given time (selectable).
Summary: Fine for simple tuning and checking real-time operating
parameters, but not a data recorder, just an "enhanced" scan tool, so
best used with TL or DS if you are going to be "pushing" your Turbo
Regal quicker than ~12.5s, in my opinion.
NOTE: With a bit of ingenuity, it does not have to be hard
wired; some folks use various connectors (female 0.125" terminal plug
for the ALDL, and a cigarette lighter plug for power and ground) so it
is "transportable" between vehicles.
TL-
Pro: Just plug the data cord (supplied with TL) from the laptop
into the ALDL port (which makes it easy to go from one car to another)
and you are ready to go. A true data recorder, capturing up to ~7.5
minutes with v2.13, (3 HOURS with v3.0, as I understand), so you can
cruise around town and hopefully to "capture" data for an intermittent
problem. Has an easy
to use boost sensing option (VERY desirable!!). Displays all TL
available
operating parameters at the same time. Unbeatable technical support
from
Ken Mosher himself.
Con: Requires laptop computer. Limited to ALDL rate.
Summary: An excellent choice for a data recorder, especially
considering the boost sensing which is a major parameter when you get
into
the fine tuning of the car.
DS-
Pro: 18.2 (maximum - selectable 18.2, 9.1, 6.1, 4.6) frames per
second of data. More operating parameter readouts than TL.
Con: ECM needs modification for installation (not a big deal,
really... ~30-45 minutes on the first one, ~15-20 minutes the next time
you do it). Limited record length ~104 seconds @ 18.2fps, 208 seconds
9.1
@ fps, 312 seconds @ 6.1fps, 416 seconds @ 4.6 fps.
Summary: WOW! 18 frames per second! Consider, on a full throttle
launch I hit 2nd gear in ~1.2 seconds. With TL, that would mean only 1,
MAYBE 0, frames of data even though I just ripped through first gear up
to ~5200+ rpms. With DS, @ 18.2fps, in 1.2 seconds I will have ~21
frames
of data. In a 13 second 1/4 mile run, you would have ~9 frames on TL,
~236
on DS... a substantial difference when analyzing data.
NOTE: Supposedly Kent Chu is working on allowing 2 additional
operating parameter inputs, though I first heard about that in 2000, or
so. Although the variables are kinda endless, I suppose most folks
would
use those two inputs for either boost sensing, exhaust gas
temperatures,
or wide band oxygen sensing. Actually, using the TL Boost Sensing
harness, there is a method to do boost sensing similar to TL, but it is
not a s simple as the TL way. See DS Boost
Sensing for how to do it.
Some final comments: