I have to ask what bad data did the edelbrock unit give you? You may have not
believed it or thought it wrong but was the data wrong. NOt necessarily as an
absolute number but as a trend or indication that something was wrong?
I can state categorically that info from the driver in 99% of the time is
useless .. Most of the time the best you can hope for from a driver is what gear
they thought they were in and possible an rpm reading that has been 'filtered '
by the driver. I.E. if they were over red line they will have been right at it.
If it was an exit speed add 200 rpm etc.. Same goes for throttle position.. I
have seen a lot of half throttle runs and ones with the boost turned down..
Throttle position will tell you more about how the run went than almost any
other sensor input I have seen as a driver will unconsciously peddle the car if
they are feeling insecure about the handling or anything else in the run. Don't
even bother asking about water temp or oil pressure because the best you will
get is ok or fine unless the car is either blown up or steam rolling out of the
hood then it would have happened suddenly in the last mile and they shut it
right down. LOL... There are very few data recorders that will report this type
of info inccorectly.
Dave
Russel Mack wrote:
>
> Bryan:
> re: your comment "Bad gages or an eyeball glitch are bad enough, but a
> logger can add
> enormously to the garbage information load"--
>
> I completely agree. I have encountered many cases in my "industrial" work
> where (unrecognized) bad data led to bad decisions and costly results.
> In LSR, I have had unexpected results from three channels that we decided to
> ignore (assuming that they were related to transducer or logger problems)--
> and later found that that data was probably trying to tell us how to save an
> engine. Too bad we had not enough experience with the datalogging package
> to have had confidence in it.
> The bottom line is-- if you can't be REALLY SURE of your data, it's best not
> to even have it. You can manage your program better by using instincts
> developed through your racing experience. Bad data will only make you
> ignore those instincts at the wrong times.
>
> Having said that, a high priority for me is to get the datalogger going on
> my bike so I can test all the sensors thoroughly and gain the needed
> confidence in all the data.
> Russ, #1226B
/// unsubscribe/change address requests to majordomo@autox.team.net or try
/// http://www.team.net/mailman/listinfo
/// Archives at http://www.team.net/archive/land-speed
/// what is needed. It isn't that difficult, folks.
|