Diablosport Forums

I would like to log these additional PIDS. How do I do that? I don't see them in the menu. Do I need to add them some how?

2008 Brillant Black Dodge Magnum SRT8 w/ Techco Twinscrew Supercharger
Predator U7135 w 9r12



ADDITIONAL PIDs...
Injector Pulse Width Cylinder 1
Injector Pulse Width Cylinder 2
Injector Pulse Width Cylinder 3
Injector Pulse Width Cylinder 4
Total Mis-Fire Since Clear
Cylinders that Misfire During 200 revs
Desired FA CYL1
Desired FA CYL2
Desired FA CYL3
Desired FA CYL4

Also,
1. Cylinder 1 CAT Mis-Fire Counter
2. Cylinder 1 FTP Mis-Fire Counter
3. Cylinder 3 CAT Mis-Fire Counter
4. Cylinder 3 FTP Mis-Fire Counter

Ok, so I think I found my answer, but please jump-in and reply.

I have to use a laptop connected to the diablo as a pass through device using the dataveiwer software on the laptop. I should be able to veiw all available PID's for my vehicle and record live data.

Is that correct?

Yes - hook up the Predator to your laptop w/ serial-to-usb cable (drivers need to be installed on the laptop for this). Run the DataViewer to get your Predator to be recognized and it will search through your OBDII port all the PIDs that work for your car model/year. The PIDs will appear in a tree on the left side of the DataViewer app. Check off the PIDs you want to monitor. You can show either guages or line-graphs. Most of the time you will use 'record' to save results over a period of time (and be able to play them back, save to a file...). Or, you can just look at the guages and graphs in realtime.

So you can view live data with your laptop while the predator is hooked up to the laptop and the vehicle's OBD-II port?

Yes, you can and you get more PIDs also.

HOWEVER, I don't recommend logging all that stuff at once. The more parameters you log, the slower the refresh rate. The CAN Bus can only move so much data at a time. I would never log more then 5 or 6 parameters at once.

Same end result, but it's not the capacity of the bus. The spec only allows the diag port to have one outstanding request at a time. Assumably the scanner "round robins" through the pids it's polling (unless it does something smarter). It's most likely the case that more pids being polled results in each pid being polled less frequently. The response time for querying one pid may also be different than the response time for another pid. The PCM may defer responses if it's busy, it may take some time to calculate a pid value or it may need to poll other modules for information to make the response.