OBD Fusion PIDs

[HammaMan]

..

Lots of good info from ya here. If you need more screen space, consider getting a kindle fire HD 10 -- easy to sideload things into it. It's a lot of tablet for $85. Going to be using one here soon for the F150 and MME for data collection. What apps / adapters provide the most utility / customization? Have you found all of the PIDs? Didn't see your oil anywhere. Currently in talks w/ naviks regarding just how much communication can be done on the busses. I like their unit hijacking the screen, turning on side view cams w/ blinkers and what not. I want to figure out just how much that device can do via button combos.

I'd like to integrate a PC into it if I can get the touch to work on it via USB or similar. We'll see what all they've been able to achieve. Especially in the MME. Sync4 is such a turd on that display. I'd love to bypass the factory stuff all together if climate can be hijacked.

Sponsored

 

[Snakebitten]

Ok I am familiar with how the obd mx works and I have installed the ford advanced pids. I'm not seeing how to display the graphics like yours. You have arc for the different batterie info that is different from the built in. Yours are much more pleasing. I like the clean colorful screen with the black background. Did you import styles or did you build these pids outside of the mx software?

Ok, all those gauges on my screenshot started out as one of the built in gauges.
Then I customized each one to my liking using the sizeing option and the "Style" properties.

The arched gauges are really circular, but you will discover all the graphical controls that OBDLink offers in the Style section.

Warning. You can go down the rabbit hole. ?
Have fun!

If it's not something you enjoy, you can import my dashboard from an export file I create. (I can attach it to a post)

 

[Snakebitten]

@HammaMan

I have NOT found the formula for the oil pressure pid.
I did manage to find the formula for the OAR pid from a fella on a Focus forum. I built a "user defined pid" in the OBDLink app and it's working perfectly.

I wish I could harvest pid information from either Full Forscan or my HPTuners Ngauge. They both have the Ford Ecoboost variable oil pressure pid and I've been monitoring oil pressure on my Ecoboost trucks since 2017. I really really miss that pid switching over to Android. The oil pressure on the Gen2 and Gen3 3.5 is fascinating to monitor. It's based on load, just like everything else in that amazing engine management Ford built, and it became second nature to glance up at it to verify expectations.
You will KNOW when something isn't right, and with oil pressure you NEED to know when something isn't right!

The built in instrument panel oil pressure gauge is 100% fake. It's off/on graphical image. If oil pressure is greater than 7psi, it's one image. If less than 7psi, it's the other image.

 

[Spiffy]

If it's not something you enjoy, you can import my dashboard from an export file I create. (I can attach it to a post)

Yes please attach it. I love working on this kind of stuff but I have so many projects working with thus stuff.
1. Root phone so the slider on the phone that turns on sending calls away from android auto. I have a music server based in my house called roon arc. It's a piece of software that combines all my music sources like my valt, Spotify, qobuz, tidal. All my music subscriptions that I have on my streamer at home I can access anywhere in the world. I also really like the wireless aa now. I love how it's integrated google maps. I hate that I can't get aa to stop forcing me to use headset. If rooting fails then I might buy the tablet you suggested. Run it through the hi-speed modem using the aa and all my other Android apps. Keep my phone separate with no blue tooth.
Another thing I'm working on is modifying my USB port under the dash to output more than 500miliamps. Presently the USB port is terrible for charging. I measured 460ma.
Then I'm going after those updates that my truck won't get.
I'm a avionics tech. I work on Garmin integrated flight systems. I was always amazed how much integration between the auto pilot, engine management, audio using the can bus. Ford has gone all out. This stuff is really advanced. I think they are taking a big chunk away from Tesla.
I see the transition from sync to android is being delayed. If ford leaves 2021 models behind there is going to be hell to pay.
Thank you for all you contribute.

 

[Snakebitten]

I will post an export when I get out of the office.
The phone I use for OBDLink is dedicated to the truck and I leave it in the media storage bin. So it's not at my desk.

Be SURE you already have the Ford/Lincoln/Mercury package in OBDLink before you import, or the field mapping will not exist and the app will just default to mph, or some other SAE pid. It makes a mess of the dashboard and you have to import again, or manually map each gauge.

Also, during the import be sure to include a check mark in "user defined pids" or you will not get the OAR pid.

 

[Jjdh]

I will post an export when I get out of the office.
The phone I use for OBDLink is dedicated to the truck and I leave it in the media storage bin. So it's not at my desk.

Be SURE you already have the Ford/Lincoln/Mercury package in OBDLink before you import, or the field mapping will not exist and the app will just default to mph, or some other SAE pid. It makes a mess of the dashboard and you have to import again, or manually map each gauge.

Also, during the import be sure to include a check mark in "user defined pids" or you will not get the OAR pid.

I may be copying this as well!

 

[Spiffy]

Good advice. I do have the extended pids for ford. But they are on my personal phone and I'm going to do what you did by using a random phone that stays in the bin. Thanks for doing this.

 

[Snakebitten]

Here ya go Spiffy (see attached)

Note, the attached file is NOT a pdf file.
The native OBDLink file extension is "stg" and you MUST rename the file extension before importing into the app.
The forum software requires a file extension that it recognizes for post attachments.

Also note that depending on the resolution of the screen on the device you are using, there will likely be some padding/spacing issues that you will need to address. The "drag & move" option is your friend. As well as the "bring to front" command if the overlapping layers of each gauge cover something up.

Many of the gauges on the dashboard I exported are really full circle or full square. But I would edit portions to be transparent or invisible.

Enjoy

 

[Spiffy]

Thanks for the info. I'm sure I can figure it out.

 

[Spiffy]

Dang. I must not understand what I'm doing. I renamed the file .stg. "obd*.stg. I assumed that I just import as built in pids or import from file . Both ways when I dig down to where I stored the stg file its not recognized. Do I have to move the stg file somewhere specific? Maybe I should learn what a stg file is and how it's used in the obd app.
The rest of the instructions about resizing, moving around I can muddle through.

 

[Snakebitten]

It should import if the file is called OBDLink Android SettingsJan27.stg

Once you successfully point it at the file you should be prompted for which properties of the file you want.
These are all you would check

 

[M.R.F.O.R.D.]

Here is my main OBDLink dashboard and it has the PIDs you desire. I too come from previous Ecoboost and an Ngauge. (by the way, the Ngauge still can read my 2022 Powerboost pids, but it's missing the EV related Pids for obvious reasons)

The top half is the gasoline related

What does the KR mean? I did import your setting but they are not showing up correctly. Not sure if it is because I switch everyting to the metric system before the import. I have fixed all the gauge but the KR. I am also using OBDLINK® EX with a usb to usb c adpater to my old S10 phone. Its working great !

 

[imnuts]

Just a guess, but possibly Knock Retard off knocking is detected.

 

[M.R.F.O.R.D.]

Thanks it it knock retard

 

[Snakebitten]

Yep, yaw got it.

The KR pid and Spark Advance pid are very much complimentary to each other. And then the OAR pid basically verifies what the other two are implying.

I originally had the timing advance set to a max range of 32°
You can see that I hastily increased it recently to 40°, but didn't adjust the gauges graphics to match the new range. The reason is that I had been experimenting with adding a few gallons of E85 to my typical 93 octane fillups. It's a 30 gallon tank, so depending on how low it is at fillups, I would add maybe 3-4 gallons of E85, ensuring that I was well below E20, knowing that the factory calibration could easily manage and adjust to the proper fueling.
As a result the truck would often peg the spark gauge at 32°! That's amazing.

Anyways, if you watch the knock-sensors data (KR) it is directly driving/influencing the amount of timing advance that the pcm is commanding. It's all very fluid, of course, and so very much a moving target.
The OAR being at -1 is just confirmation that the timing table in play is the highest advanced table available in Ford's timing table database.
If you were to switch to say... 89 octane, you would see the KR start showing +positive values (between 0-6) and the timing advance would get dialed back. After a few minutes of such a circumstance, the engine management would switch completely to a different timing table (less aggressive) and the OAR value will adjust to something like -.76
Switch to 87 octane and you'll see the ensemble of pids reflect the results similarly.

It's an amazing motor. It'll tell you exactly what's going on.

Sponsored