I'm looking at my buddy's Datalogs with respect to a knock count issue he's having and I've come across some odd reporting (see attached screenshot). As you can see, rows 1263 and 1279 show an odd timing value of 10,000 plus degrees.......I'm stumped as to what might cause this. Does anybody have any thoughts? This anomaly also occurs rarely in other locations of this D/L and in others as well..... The car is a modified 90 Corvette and we're using an arfp 8d bin, with an 8d XDF; are these correct?

Thanks for any input!!!

 

There is other erroneous data within that same sample, look at the injector PW, and I'm sure there is more.

Some code has glitchy ALDL datstreams that cause things like this.

What are you using for an ADS/ADX?

 

Thanks for the reply! You're right, the screenshot just doesn't show the other discrepacies. The ones out of view that are also affected are: fuel pump voltage (25.3), engine run time (64129), and spark advance (4621.3). It's odd only some of the entries are skewed and even then only once in a while. I thought maybe an intermittent short??????

I'm using a 1227730.ads and I *think* I got all these files from the Moates or Tunerpro websites. I do remember having a difficult time locating them though. I normally use '165 - 6e for my car.

Thanks again!

 

I have the same problems when using tp rt v5 with my dell laptop.
when I use my newer lg laptop, there are no such spikes.

but I don't think it's the laptop itself which causes the problems. on my dell i have windows7 x86 sp1 ; the lg is x64 with sp1.

another option instead of installing another os, try to use "windows xp mode" (if you are using windows 7) works well for me with my Dell.


rgds
Alex

 

Thanks Alex, but I don't think this is it. I'm using V4 on my old Dell running XP w/ SP3. Thanks!

 

Bump for the new week!

 

What interface do you use?
I use the aldlxtreme from moates. You could either try another definition file (same 8d, but from another source) or maybe just try tunerpro v5.
When using the aldlxtreme, be sure to have the resistor-switch turned "open" instead of "10k".

 

Youre problem can be solved by adding a "pause before resend" command to the macro in your tunerpro ADS. I had to do this on my mac, whereas my brother's Toshiba works fine.

The difference between yours and the OP's problems, is the "glitchyness" you're seeing probably affects ALL values in the datastream, whereas his affects only one or two values in any random sample.

 

Thanks for these thoughts, I'll contact my buddy and see if we can't locate another XDF............we're currently using the 8d from the Moates website I believe.