If it were me, I wouldn't be running that engine too much until I could verify the fuel pressure. That 'total misfires' counter ("MFTot" in the upper right corner for anyone following this) is increasing steadily in one of your Torque Pro videos and that's a bit worrisome, IMHO.
4. I mention Baro, because it's part of our MAF.
Are you sure? Typically, IIUC, a barometric pressure reading comes from a MAP
(Manifold Absolute Pressure) sensor. But my 2004 Ranger does not report MAP via the usual SAE-standardized PID, even though some of my other (non-Ford) vehicles do
. I don't think my Ranger has a MAP sensor. And I see no input pin on a PCM "pinout" diagram for a relevant sensor or related input. In fact, Ford's own documentation says that the "BARO" PID "may be software[-]determined", so I suspect that the value is computed somehow from other sensor data, but how? I really don't know and would love to find out!
Regardless, there's certainly no harm in occasionally monitoring the "BARO" PID with FORScan. Just don't expect it to be changing very often, per my previous post. And when you're monitoring something that does
change very frequently, like O2 sensor voltages, each extra PID being monitored only slows down the overall update rate, so it's good to "shed" useless PIDs when possible and appropriate. As for MAF
, you can monitor that directly, so if the MAF sensor is acting up, you should be able to see it by graphing the PID (more on that below).
1. So, the injector communication I'm referring to is the percentages for long-term, short-term and fuel trim. I'm not certain of the significance of there's any at all.
OK, I thought there was some confusion. Be aware that the STFT and LTFT values come from the PCM, not the injectors. The PCM, based on feedback from the O2 sensors when running "closed-loop", computes and uses those values to control
the injectors, adjusting the pulse width to control how long the injectors are, well, "injecting".
The injectors do not compute, store, or report STFT or LTFT. So I'm even more
curious now why you stopped seeing values in FORScan or Torque Pro for those STFT and/or LTFT percentages with the new injectors! I've never seen that happen. What exactly, if you can recall, did FORScan or Torque Pro show for those PIDs? Just a blank display? I wonder if the PCM was reporting any fuel injector faults at that time? You should probably find and monitor those 6 "injector fault" PIDs (1 for each cylinder) at some point, regardless of whether you have old or new fuel injectors installed. (Torque Pro might be useful here because it allows multiple screens of groups of PIDs. That way you can easily select groups of PIDs that you're only occasionally interested in monitoring.)
Another thought crosses my mind, but I don't know if this is sensible. Maybe, at some point (not yet?), you could install just 1 of the new fuel injectors and then monitor the PIDs related to fuel injectors, especially the 6 "fault" PIDs, but also the Bank #1 and Bank #2 pulse widths. Also, since STFT and LTFT reports from the PCM are per-bank, if you stopped seeing 1 of them it would be interesting if it correlated to the cylinder/bank in which the new injector was installed. I'm not sure it's worth doing that just yet, if ever -- it's just "food for thought".
[...] the forscan app is new to me and kinda tricky compared to the torque app, but I'm figuring it out.
When I use FORScan, it's always on a laptop, under Windows. I've run the very limited FORScan Demo
(for Android) but never FORScan Lite
(for Android). FORScan for Windows has the most capabilities, but FORScan Lite (on Android) will probably be adequate for your immediate needs. For Ford (and Lincoln, Mercury, and Mazda), FORScan is better than Torque Pro because it typically already "knows" all the available PIDs (for all modules -- PCM, ABS, etc). But Torque Pro is clearly useful in many cases, so it's good to know both, IMHO.
Does FORScan Lite allow graphing of PIDs? It's called "Oscilloscope" on FORScan for Windows. Graphing a PID's response is virtually indispensable in some cases (like when monitoring STFT on upstream O2 sensors) because a single display (even in a video showing the changes in value) just isn't adequate to discern how the PID is really behaving.