Page 1 of 1

Seeking Assistance with Adding a PID to Dash Manager

PostPosted: Wed Jan 15, 2025 8:01 am
by Sedrick
I have a C125 I'm attempting to set it up to display various parameters from my factory ECU and I am struggling to understand Dash Manager. I also purchased Display Creator should it be necessary.

I've included a PID for my vehicle below.

    name: PIDs - Oil Temperature (705C)

    name: PIDs - 705C

    format: UBYTE

    operations:
    coefficient: 40.0
    operation: SUBTRACT

    coefficient: 1.0
    operation: DIVIDE

    unit: CELSIUS

How would I set this up in Dash Manager? I have jumper cable to get CAN messages from the steering angle sensor and I also have the ODBII connector. So I can do either, but from my basic understanding ODBII connector is needed since I'm using PIDs.

Re: Seeking Assistance with Adding a PID to Dash Manager

PostPosted: Wed Jan 15, 2025 11:25 am
by David Ferguson
What is the vehicle make/model you are working with?

Is that a non standard OBD2 Service Mode 21 or Mode 22 PID (Paramater ID)? if so, the format is unique to each OEM and I'm not sure it's documented enough to easily figure out the request/response.

Is there any chance this info might be broadcast on some CAN bus -- if you can figure that out, it usually much easier to deal with.

You can learn about OBD2 standard PIDs from this webpage:

https://en.wikipedia.org/wiki/OBD-II_PIDs

Re: Seeking Assistance with Adding a PID to Dash Manager

PostPosted: Thu Jan 16, 2025 2:57 am
by Sedrick
I have a US market 22' Subaru WRX.

I don't have an exact answer for your second question.

I am referencing a config file (.yaml) from an opensource project. In addition to PIDs, it contains base addresses, byte order, data length, memory name, memory type, scales, operations, coefficients, parameters, units and so on.

Everything is specific to my vehicle, but I think its using memory addresses, from its use of memory base address, length, and offsets, instead of CAN frames. So it might be non standard OBD2, but I could be wrong.

I can monitor CAN bus traffic, for example using Savvy CAN, to see Frame IDs and the entire 8 x 8 byte packet, but I am having difficulty determining where an individual message starts and stops when reviewing logs.

Other than the Wikipedia article, are there other resources detailing OBDII that don't require purchasing the standard? Nothing illegally obtained and posted online either. I don't like that the standard bodies charge, huge sums of money to access standards, but I don't want to steal it either. :lol: