Diablosport Forums

I recorded a 5 minute run on the Predator and downloaded to my computer using the latest version of dataviewer (3.1.5.4). Predator version when recorded was r18. The numbers for the various PIDs don't correlate to anything. For instance - RPM at redline displays as 419299328 instead of ~ 6250. I've tried changing the scale and English / Manufacturer/ Metriic settings with no effect. Is there anything I can do to make it readable? It looks like I'm getting quite a bit of knock, but I can't be sure since the numbers mean nada.

/Edit: 06 Charger SRT8

Somebody else reported a similar problem. If you would, email me your log file. Thanks for the screen capture, that helps.

Raffin, there is no VIN in the log file. The DataViewer uses the VIN to identify the vehicle so that it can choose a PID set.

Plug your Predator into your car. On the menu select Options -> Troubleshooting -> Show VIN. Does the Predator find the VIN?

I think I figured things out. Try DataViewer 3.1.5.5.

John,

I am able to view the VIN per your instructions.

I downloaded and installed the Dataviewer update. No change - the numbers still look the same. I opened the previously saved log I sent you and also redownloaded it in case it made a difference. Oddly enough I have another previously saved log from 10/29 and when I open that one it displays the expected values for the various PIDs.

- Rick

Rick,

Thanks for the follow up. The logs you saved on your PC with the old version will still be fubar. However, re-downloading the log from your Predator should have worked.

If you would, delete all your previously saved logs to avoid confusion. Then re-download the log from the Predator. Then save it to disk. Then email me that new file.

John

Sent.

- Rick

Rick, that appears to be a problem with the Predator. I have handed it off to another developer, and the fix may take some time.

John,

Thanks for looking into this!

- Rick

John,

I have the exact same issue with my U7135 on my 06 SRT8 Charger using the R18 and latest dataviewer as of today. But more importantly I see the numbers are reading way out of range in real time while I'm driving around so I agree the issue seems to be on the predator side and not the dataviewer. Thanks for the help and please let me know if you need any log files or info from me!

sweetsrt8, how many parameters are you seeing strange values for? Is it always the same 1 or 2 parameters, or does it seem to malfunction randomly across various parameters?

This is a problem that we have not been able to reproduce in-house, which is strange. I am wondering if it is specific to certain vehicles.

The Predator developer looking into this wants a copy of the raw flash data from both of your logs. I am going to email you both an application that will pull the log. This is assuming your email addresses in your profiles are correct, please let me know if they are not.

Also, when (and if) you reply to that email, please include your calibration id and some details about what vehicles you have (year, make, model, etc).

No problem, I'll check email now and send info and files you need. Thanks for the excellent support!

just wondering what's been happening with all the crazy numbers cause i have the same issue on all PIDS, nothing makes sense