Ford Transit - North America #334
-
Hi WiCAN Friends, I have a 2021 Ford Transit in which I'm using WiCAN to connect to my RV's home assistant via MQTT. I was able to get the standard PIDs working using 6- ISO 15765-4 (CAN 11bit/500K). In my next step, I would like to build a custom profile to pull in Ford specific sensors. I've scoured the Internet and have assembled a list of what I believe are workable PIDs with their respective expressions. It's unclear to me whether these require specific "init" values or not. Nonetheless, I've used the custom PID in the GUI of v4.04 without any luck. It seems regardless of what I enter, I'm not seeing anything pop up in MQTT explorer. Here's an example: It seems to me that I either have the wrong PID or missing a required init to pull this data. From what I understand on this page, I need to setup ELM327 on BT with CarScanner, isolate my desired sensor, and capture the logs to know what it is I need to use for init and PID. Do I have that right? If so, I'll go through the process of building a profile for a Ford Transit (North America). |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
@anthonysecco please follow the instructions in the link to export the logs for the specific sensor. For your custom PID to work you need to set the proper header and address filter commands in PID init, we can find these values in car scanner logs. |
Beta Was this translation helpful? Give feedback.
-
Thanks - I went through the process and got a number of additional PIDs using Car Scanner. Here's a sensor of interest:
This should be Trans Temp with the expression:
The init is ATSH7E0. I believe the header is 7E8 with a value of 65 F. Mind you this was a cold start. I've attempted to add this as a custom PID, but I'm unable to find where to add the header details. In any event, I haven't been able to get anything to show up on MQTT explorer. I've added ATSH7E0 but that didn't seem to matter. I feel like I'm missing something basic. Once I sort that out, I'll have a number of other sensors that could of interest to justify a vehicle profile. Thanks! Full log here: signal-2025-01-30-095526.txt |
Beta Was this translation helpful? Give feedback.
-
I've probably spent more time than a care to admit fidgeting. It's probably something related to the initialization. I've combed over the logs and it's not clear to me the sequence. It's something like this, but it still doesn't produce the data:
I've even connected to the ELM327 protocol mode in raw on a terminal from my PC and issued commands. I can access some PIDs, but not 221e1c like car scanner could. It always came back 'no data'. Time to take a break. Anyone who can parse the logs and enlighten me to another initialization string would be immensely appreciated. |
Beta Was this translation helpful? Give feedback.
I think you're almost there :)
The expression is incorrect, the format you're using is not supported. It has to be something like
([B4:B5]*9/80)+32