Ranger Mods

saeb wrote: ↑Sun Jul 12, 2020 1:22 pm Mode will always be 22.

If you have a shortlist then put them up and I will supply the PIDs, I do have all for all modules but compiling everything is just to time consuming, hence the short list up the top. Depending on how many whether I can spend anytime doing the calc.

All good, I ended up just bluetooth sniffing and working backwards from there.

If you want a specific PID or a few, let me know the name of them and I will post them.

Hi,
How to get the complete list of PID?
Thanks

I will re add them at some point but need to clean it all up again.

Most common PIDs are in the calculator and all are in Forscan to monitor. Well 98% are in Forscan, sometimes I add additional PIDs in the calculator that are not in Forscan.

Has anyone been able to find the Cabin (Inside car temperature) and Ambient (Temp sensor in front of radiator)?

The list I'm after is:
Cabin Temperature - I think this has to do with the HVAC.
Ambient Temperature - Sensor in-front of radiator. Attached to plastic shroud.
Boost - MAP sensor.

I tried the following, but they seem incorrect.
Cabin temperature 7d08.
Ambient 9D0E.

The PID list in the first post is giving a PHP error.

Any luck with the actual boost pressure?

These are from an F-truck in the USA, I think. Not everything translates between different module hardware, but sometimes it works out.

Long name: Short Name PID Units Max/Min Equation
Barometer BARO 221442 PSI 15.0/10.0 ((A*256)+B)*0.03625
Manifold Absolute Pressure MAP 221440 PSI 45.0/0.0 ((A*256)+B)*0.03625
Manifold Gauge Pressure Boost 221440 PSI 30.0/0.0 (((A*256)+B)*0.03625)-[221442]

Also found
MAP 7E0 220187 PSI 40.0/0.0 ((((B*256)+C)*0.00393)+2.25)
and
MAP 7E0 220187 PSI 40.0/0.0 ((A*256)+C)*0.03625

jonchaka wrote: ↑Fri Jan 08, 2021 9:05 am Has anyone been able to find the Cabin (Inside car temperature) and Ambient (Temp sensor in front of radiator)?

The list I'm after is:
Cabin Temperature - I think this has to do with the HVAC.
Ambient Temperature - Sensor in-front of radiator. Attached to plastic shroud.
Boost - MAP sensor.

I tried the following, but they seem incorrect.
Cabin temperature 7d08.
Ambient 9D0E.

The PID list in the first post is giving a PHP error.

I assume we are talking PX1 as per tag so will give the correct PIDs but calcs may be off and have no idea what device you have.

You will never generally se a boost PID as it is a calculated value from actual baro sensor and manifold. Hence 99.9% of devices have a boost as a selectable items from the generic OBD PIDs.


Engine Oil Temp F45C
Ambient Air Temp F446
Intake Air Temp F40F
Intake Air Temp 2 03CA
Coolant Temp F405
Ambient Air Temp DD05
Inside Air Temp DD04
Fuel Temp 0522
Air Charge Temp (Intercooler) 051C

As above there is no boost PID.

Math is most likely A-40 for all. I don't have enough time at the moment to check if they a 1 or 2 byte high precision PIDs so worst case a couple may have incorrect maths.

All are extended PIDs mode 22 and module 7E0.

Would anyone have the PID and code for Commanded Fuel Rail Pressure, for comparison to the actual Fuel Rail Pressure?? Cheers

RangerNZ wrote: ↑Wed May 04, 2022 8:17 pm Would anyone have the PID and code for Commanded Fuel Rail Pressure, for comparison to the actual Fuel Rail Pressure?? Cheers

To use in what device?

Hi, the vehicle is a 2013 3.2L PX2 XLT manual 4x4 at 120,000km's, device is an OBDLink MX+ currently just using the OBDLink app for android. I haven't found anything else app wise that has the Commanded Fuel Rail Pressure as an inbuilt selectable PID - but what we are mainly interested in is the variation between actual fuel rail pressure and the commanded fuel rail pressure. I think they talked about downloading the logged data, and then converting to a .csv and running it through Excel or the like to create a comparison graph, biggest issue first is collecting the right data...

I think the Suction Control Valve duty % was something that they might like at some stage as well - basically if there is a large variation between commanded and actual rail pressures at the same time that the SCV duty% is climbing it confirms either a failure of something pump related and the ECU cannot maintain the pressure it wants in the rail so is increasing the SCV duty time, or there is a failing component between the tank and the CAV injection pump allowing air in on occassion. Keeping an eye on the fuel temperature as well, in case this vehicle has a glitch in the fuel cooler plumbing or something else weird which is allowing the temp to spike over the magic 85degC cutoff and throwing itself into limp mode.

It's a very pesky fault that we can't replicate on command, and it's a little dangerous (we've in jest suggested it's hooked into the reversing camera and waits until it spots a fully loaded 50t truck trying to get a run up the hill behind you before it goes into limp mode and limits itself to 2000RPM). I've just about been a hood ornament twice now, not keen on another round of that!!!

The actual code that's getting dropped is P0089 - Fuel Rail Pressure out of specification - but at this stage we just cannot fault the thing in operation (no tiny shiny metal flakes in the tank or filter which would indicate a failing piston spring in the pump, no hard starting or rough running, no white smoke indicating leaking/contaminated injectors, just an occassional random P0089 fault and limp mode). Dealer service center is suggesting replace injection pump, rail and all 5 injectors - but not convinced that this will cure the vehicle's issue which is why we are trying to id the actual cause. Thinking is that if it was the injectors or pump, we would be able to replicate the fault and cause it to happen but so far it's run perfectly well. There's a possibility that it could be electrical related, fault in the loom or a sensor but at this point it's wait until it happens and hope we can spot the fault with the data logger.

So far I've had close to 3 hours with the NZ$10K mechanic's scan tool - this records the commanded and actual fuel rail pressures as a numeric so I'm fairly sure that what we need is possible to get off the MX+. Unfortunately I can't keep that scan tool long term (would be nice haha). First time for me in setting a code reader up for very specific data logging and I haven't been able to stumble over the PID codes I am looking for so any help you can offer is hugely appreciated!

Thanks!

RangerNZ wrote: ↑Thu May 05, 2022 8:26 am Hi, the vehicle is a 2013 3.2L PX2 XLT manual 4x4 at 120,000km's, device is an OBDLink MX+ currently just using the OBDLink app for android.

Personally with all those items then just use Forscan on a laptop and your current adaptor to monitor and log. You can then save your logs.

Or purchase Forscan Lite for your phone and do the same thing.

Although I do have specific data I will spend a reasonable amount of time converting PIDs to suit devices then test them, where that work is already done in Forscan and if the PID does not exist in there then it probably does not exist.

Stewart might be able to provide specific SID208 ECM PID info, but it appears far more limited than the later SID209 (DPF motors) which have heaps of available PIDs.
However, I had a look at a 2012 ECM file and there is definitely a hard 2000rpm cut to power if fuel temp exceeds 85C (faulty sensor?). Also the max SCV duty cycle is listed as 56%, although I'd use that as informational to start with.

As Ian says.

Check fuel filter has been installed the correct way. Common problem for lines to be put on reverse to what they were and then high fuel temps will occur.

Yes to the fuel lines the wrong way around - this by the dealer... Had the tank out and the fuel sender/lift pump replaced, had one instance of tripping to limp mode since but can't replicate (was not running the data logging at that stage).

Fuel temp - this is definitely a cause of the 85degC hard shut off of RPM exceeding 2000, but after fixing the fuel line hookup problems it seems that the fault might remain. I've had one instance of limp mode which might mean that the 85DegC fuel temp shutoff is not the cause of my issue (what I saw in the three hours with the scan tool was a max of 39DegC...).

So Forscan on a laptop - this sounds easy enough, but just connecting the bluetooth dongle to a laptop that isn't bluetooth enabled? Or is it easier to go the path of least resistance here and Forscan lite...

Thanks!

Buy an eBay Bluetooth USB dongle to use with OBDlink or get a hardwired adaptor from my store.

Ok, downloaded Forscan Lite - yep that works pretty much straight off. Awesome, exploring .csv data files exported via email which looks like just the ticket. Only possible thing I suspect I'll struggle with is the SCV Duty% values - can't see that in there but could also be listed under another name.

Now just need the ute to play nice and fault for me on command (not that it's ever done that before!!!).

Thanks for the advice and pointer towards that app, much appreciated!

Sure it is not under FCV?

Have usually found the main symptom when SCV/FCV is no idle and stalling straight away.

Goochie wrote: ↑Thu Apr 30, 2020 2:02 pm Well, almost a year after I posted above that I was going to bring some equipment home from work to help me monitor the bus directly, I got round to doing so this week. Luckily it's not needed at work for a couple of weeks so I have time to play.

So far I've only identified things I can easily operate from the driver's seat (because I'm doing it after dark on my driveway!) but will add others as I find them.

For those who may not be familiar with the inner workings of a CAN system, its important to say that reading the raw data on the bus is not the same as requesting information from the bus via an OBD-II device. With an OBDII device you're asking the car to give you the information, but what I'm doing here it spying on the data to see what the vehicle is sending around itself. Its unlikely that you'd be able to take this information and get it to display on a common OBDII display (scangauge, Torque app etc.)

I started out on a quest for tyre pressures but have yet to go looking for them as I dont want to annoy the neighbours re-inflating tyres at 9PM.

Whilst much of what I've found is pretty pointless for most people, its an interesting exercise none the less.

Items identified so far:

Steering wheel angle
Windscreen wipers on
Windscreen wiper speed
Windscreen courtesy wipe in progress (may also indicate auto wipe in progress)
Steering wheel button - Speed Limiter
Steering wheel button - radar distance +
Steering wheel button - Radar distance -
Steering wheel button - Cruise SET
Steering wheel button - Cruise RES
Steering wheel button - cruise ON
Brake off
Brake on
Brake on (second address)
Brake on (third address)
Hill descent control on
Accelerator position
Gear selector position (PRNDS)
Climate On
Windscreen de-mist
AC on
AC Fan speed
Ignition On
Door lock status
Reverse lights
Indicator left (Front) - Goes on/off with the lamp
Indicator left (Rear) - Goes on/off with the lamp
Indicator right (Front) - Goes on/off with the lamp
Indicator right (Rear) - Goes on/off with the lamp
Indicator left - Stays on with either the stalk position or during the timed number of flashes
Indicator right - Stays on with either the stalk position or during the timed number of flashes
Instrument cluster brightness
Driver door open
Passenger door open
Rear driver door open
Rear passenger door open
Bonnet open
Fog lights on
High beam on
Lights On (Does not tell me which, just indicates that some white lights on the front of the vehicle are illuminated)
Light selector switch position (off, side lights, head lights, auto)
Park brake on

Hi Goochie, pretty impressive.

I'm interested in what your doing, for a project where a unit can translate or simulate the canbus in order to keep as much of the instrumentation as possible and convert to an EV, one day.

How much of what you've done here would lend itself to that?

Goochie wrote: ↑Thu Apr 30, 2020 2:02 pm Well, almost a year after I posted above that I was going to bring some equipment home from work to help me monitor the bus directly, I got round to doing so this week. Luckily it's not needed at work for a couple of weeks so I have time to play.

So far I've only identified things I can easily operate from the driver's seat (because I'm doing it after dark on my driveway!) but will add others as I find them.

For those who may not be familiar with the inner workings of a CAN system, its important to say that reading the raw data on the bus is not the same as requesting information from the bus via an OBD-II device. With an OBDII device you're asking the car to give you the information, but what I'm doing here it spying on the data to see what the vehicle is sending around itself. Its unlikely that you'd be able to take this information and get it to display on a common OBDII display (scangauge, Torque app etc.)

I started out on a quest for tyre pressures but have yet to go looking for them as I dont want to annoy the neighbours re-inflating tyres at 9PM.

Whilst much of what I've found is pretty pointless for most people, its an interesting exercise none the less.

Items identified so far:

Steering wheel angle
Windscreen wipers on
Windscreen wiper speed
Windscreen courtesy wipe in progress (may also indicate auto wipe in progress)
Steering wheel button - Speed Limiter
Steering wheel button - radar distance +
Steering wheel button - Radar distance -
Steering wheel button - Cruise SET
Steering wheel button - Cruise RES
Steering wheel button - cruise ON
Brake off
Brake on
Brake on (second address)
Brake on (third address)
Hill descent control on
Accelerator position
Gear selector position (PRNDS)
Climate On
Windscreen de-mist
AC on
AC Fan speed
Ignition On
Door lock status
Reverse lights
Indicator left (Front) - Goes on/off with the lamp
Indicator left (Rear) - Goes on/off with the lamp
Indicator right (Front) - Goes on/off with the lamp
Indicator right (Rear) - Goes on/off with the lamp
Indicator left - Stays on with either the stalk position or during the timed number of flashes
Indicator right - Stays on with either the stalk position or during the timed number of flashes
Instrument cluster brightness
Driver door open
Passenger door open
Rear driver door open
Rear passenger door open
Bonnet open
Fog lights on
High beam on
Lights On (Does not tell me which, just indicates that some white lights on the front of the vehicle are illuminated)
Light selector switch position (off, side lights, head lights, auto)
Park brake on

Could I ask if you could supply me with the list please? And also where you tapped into the Bus lines? (I'm wanting the raw data btw, not the PID's) So if I could possibly get the ID's and bytes that would be great!