Thread: FYI: Nissan Datascan logs + Virtual Dyno = Fail

So I figured out tonight that virtual dyno requires sub-second logs to correctly guess your whp. I was thinking perhaps it would 'split' up the seconds into sub-seconds within the programming if it knew how many occurrences of said second were there but that appears not what it does. I played around w/some of my logs I took in ECUTalk and realized the issue. Just an FYI for anyone doing the same. Record your logs through ECUtalk and NOT datascan!

For example...

This is how Datscan logs time:

06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07
06:54:07

this is how ECUTalk logs time:

06:54:07.101
06:54:07.148
06:54:07.195
06:54:07.257
06:54:07.304
06:54:07.351
06:54:07.398
06:54:07.460
06:54:07.507
06:54:07.554
06:54:07.601
06:54:07.663
06:54:07.710
06:54:07.757

Got the ECUtalk logs. An average of 3 runs w/the dynojet correction factor, I'm pretty much right at 300whp at 12psi which is pretty good I think. That's track boost. With a correction factor of 1.01 I'm at around 280whp as the average, which is still good.

I do notice a flat spot from about 6800-7400 rpm where whp doesn't increase very much. Not sure if I should raise or lower timing or perhaps a fuel issue.

That 280WHP is right at the spot where the 2871R should make flow wise (I think the flow map has 14.7 PSI for about 300lb/min). Not bad

That flat spot is fine. It's just your turbo running where it should be boost wise vs backpressure. You can add some timing, but not necessary.

I was guessing it'd keep making power w/the s4 cams and O2 induction manifold. I'm at about 24* between that band. I think I need to back off timing a bit as a whole.

hi gomba. so did you use ecutalk for data log and have it upload on virtual dyno? as i try on nissan data scan it doesn't work..

wait a second, first off, don't use datascan as I stated. Second, there could be many reasons why it's not showing anything for you. Get ecutalk logs first.

-G

i wouldnt play with the timing a whole lot with virtual dyno.. its very very picky an if you dont use the same exact perfectly flat straight stretch of road results will vary..

This reminds me of that G-tech thingy

I do have a ecutalk, and i also have a nds software.. as it can log the wideband...

I email the author of nds. and this is his response.

The NDS logs are not currently compatible with Virtual Dyno software. It requires throttle opening in % which can not be supplied by the Nissan Consult protocol. The Throttle parameter would have to be converted from Volts to % before the logs could be used.

Regards,
Tom

wrong!

The only thing the TPS does is try and cut out full throttle runs for a huge log. You can simply cut and paste your runs when in full throttle and it works fine. The issue is the way it logs time (at least in v1.4).

-G